Work breakdown and scheduling
Setting approval milestones for an event
The committee has said yes to the event, but each later decision still needs someone's signature and nobody has put dates on them.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
An approval milestone is a dated decision gate with a named approver, a defined pack of material to approve, and a fallback if the date is missed. Plan them first, because work downstream cannot start until they pass.
Work backwards from the dates your approvers actually meet or are available, not from the dates you would like.
Which decisions usually need a gate
- Purpose, audience and format (the project brief).
- Budget envelope and who can approve a variance.
- Programme outline and speaker list.
- Venue selection and contract signature.
- Appointment of major suppliers.
- Invitation wording, registration terms and public announcements.
- Final programme, printed material and run-of-show.
Define each gate in four lines
- Decision: what exactly is being approved, in one sentence.
- Approver: one named person or body, plus who deputises if they are unavailable.
- Pack: the documents the approver needs, and the date they must reach them.
- Fallback: what happens if the gate is missed, for example a circular resolution or a delegated limit agreed in advance.
Back-plan from the approver's calendar
If the council meets on fixed dates, those dates are your milestones. Anything that must pass at a meeting needs its pack circulated before it, so the working deadline is earlier than the meeting.
Enter these as fixed dates in the milestone back-planner, then check that downstream tasks still fit. Where they do not, the options are an extra meeting, a delegated approval, or a later event date.
Contracts, privacy and other specialist sign-off
Who is authorised to sign a venue or supplier contract is a governance question for your constitution or finance policy, not a scheduling one. Where legal review or data protection review is needed, add it as its own gate and ask the competent adviser how long they need.
The gate only records that the review is scheduled and by whom. It does not replace the review.
Pitfalls
- Treating a verbal yes as approval. Record who approved what, and when, in the decision log.
- Several approvers for one decision with no rule for disagreement.
- Gates placed after the money is spent, so approval becomes a formality.
- Packs sent the day before, so the approver defers.
Worked example · Fictional example
A council that meets monthly
Fictional organisation, dates and durations, used only to show the method.
The fictional Persatuan Pengurus Fasiliti Contoh holds a one-day conference. Its council meets on the first Thursday of each month. The secretariat lists the gates, marks which need a council meeting, and sets a pack date one week before each.
| Gate | Approver | Pack due | Decision date | Fallback if missed |
|---|---|---|---|---|
| Brief and budget envelope | Council | 1 week before meeting | Council meeting 1 | Chair and treasurer jointly, within a limit set at meeting 1 |
| Venue shortlist and contract | Council, then authorised signatory | 1 week before meeting | Council meeting 2 | Chair may approve a hold, not a signature |
| Programme outline and speakers | Programme committee chair | Draft circulated 5 days earlier | Committee call | Council chair decides |
| Invitation wording | Chair and secretariat head | Draft 3 days earlier | Email sign-off | Secretariat head proceeds with chair's text |
| Final programme for print | Programme committee chair | Proof 3 days earlier | Email sign-off | Print waits; ask designer for next slot |
Use this yourself
Approval milestone register
Copy into a shared sheet and review it at each committee meeting. Every row must have an approver and a date; an empty cell means the gate is not yet planned.
- Add a column for the date the decision was actually made.
- Highlight any gate with no deputy named.
- Link each gate to the tasks it unlocks.
| Gate | Decision | Approver | Deputy | Pack and due date | Decision date | Unlocks | Fallback |
|---|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- One body approves everything and meets on predictable dates.
- The secretariat can prepare the packs and chase replies.
- Signing authority is already clear in your governance papers.
Outside planning help earns its fee when
- Approvals sit across a council, a finance department and a regional office with different calendars.
- Decisions keep being reopened because the pack and approver were never defined.
- Contracts are waiting on review and the team cannot say who signs or by when.
Want the approval gates set up and run for you?
An Event Blueprint can set out the approval milestones, the packs each approver needs, and the dated fallbacks, linked to the timeline they unlock. If you want someone to chase the packs and keep the decision record current, a project lead can take that on with your committee.
Questions organisers ask
How many approval milestones does an event need?
There is no fixed number. List the decisions that commit money, reputation or contracts, and give each a gate. Small decisions can stay with the project owner under a limit agreed in advance.
What if the approver is unavailable on the date?
Name a deputy and agree a fallback before the date, such as a circular resolution or an email sign-off within a stated limit. Check your constitution or finance policy to see what is permitted.
Should approval time be inside the task duration?
Show it as its own wait so it is visible. The duration estimates page explains how to record waiting time separately from effort.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.