Work breakdown and scheduling
Event critical path: the tasks that set your date
Everything on the plan looks busy, and nobody can say which delay would actually push the event date.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
The critical path is the longest chain of tasks that depend on each other. If any task on that chain slips, the finish slips by the same amount. Tasks off the chain have float, which is spare time before they hurt the date.
To find it, list the tasks, write a duration and a predecessor for each, and add up every route from start to finish. The longest route is critical. Use the dependency mapper to check your arithmetic.
What you need before you can find it
- A task list at work-package level, for example from your work breakdown structure.
- One duration per task, written in working days and labelled as an estimate.
- The predecessor of each task: what must be finished (or started) before it can begin.
- One fixed end point, usually the event date or the date the final run sheet is issued.
The sequence, step by step
- Write every task with its duration and predecessors in a table.
- Work forward: a task starts when its slowest predecessor finishes. Its earliest finish is that start plus its duration.
- The latest earliest finish across all tasks is the length of the plan.
- Work backward from that figure to see how late each task could start without moving the end. The difference is float.
- Mark the tasks with zero float. That chain is the critical path.
What changes the sequence
A critical path is not fixed. A late venue contract, a speaker who withdraws or a new approval step can turn a task with float into a critical one.
Dependencies also change the answer more than durations do. Two tasks that you assumed could run in parallel but that need the same decision-maker are really in sequence.
- Add or remove an approval step.
- Replace a supplier with a different lead time.
- Start two tasks in parallel that were planned in series, if the risk is acceptable.
- Move a fixed external date, such as the venue hold expiry.
Common mistakes
- Listing tasks in the order they feel urgent. A topological order is not a critical path; only durations and predecessors can show it.
- Giving every task a duration but leaving out waiting time, such as committee meeting dates or supplier replies.
- Calling the longest single task critical. It may have float if nothing depends on it.
- Never recalculating after a change. Recheck whenever a date or approval moves, and use float and buffer planning to decide where to protect time.
Worked example · Fictional example
An annual forum with nine tasks
Fictional organisation and figures. Durations are hypothetical working days chosen to show the method, not typical durations.
A fictional logistics association plans a one-day forum for about 300 delegates. Its secretariat lists nine tasks. The route A, B, C, H, I adds up to 10 + 8 + 15 + 20 + 5 = 58 working days, the longest of any route, so it is the critical path.
The venue contract (F) and AV scope (G) finish at day 32. The final run sheet cannot start until speaker slides arrive at day 53, so G has 21 days of float. A delay in speaker invitations, however, moves the whole plan one day for every day lost.
| Task | Duration (working days) | Depends on | Earliest finish (day) |
|---|---|---|---|
| A Confirm date window and venue shortlist | 10 | None | 10 |
| B Approve programme outline | 8 | A | 18 |
| C Invite keynote and panel speakers | 15 | B | 33 |
| D Build registration page | 6 | B | 24 |
| E Open registration and announce | 5 | D | 29 |
| F Sign venue contract | 12 | A | 22 |
| G Confirm AV and staging scope | 10 | B, F | 32 |
| H Receive speaker slides and bios | 20 | C | 53 |
| I Issue final run sheet and briefing | 5 | E, G, H | 58 |
Use this yourself
Critical path worksheet
Copy this table into a spreadsheet. Fill the first four columns from your plan, then calculate the last three.
- Task and owner role
- Duration in working days (estimate, with who gave it)
- Predecessors (task letters)
- Earliest start and earliest finish
- Latest finish that does not move the end
- Float (latest finish minus earliest finish)
- Critical? (float of zero)
- What would change this task's predecessors or duration
| Task | Duration | Predecessors | Earliest finish | Latest finish | Float | Critical? |
|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- You have fewer than about 30 tasks and one person who knows how they connect.
- Durations come from people who have done each task before.
- One approver owns the date and can say yes or no quickly.
Outside planning help earns its fee when
- Several committees or departments own different tasks and no one sees the whole chain.
- Supplier lead times and approval steps are uncertain and the date is already fixed.
- Finance or the board needs a defensible schedule before releasing budget.
Need the sequence checked and documented?
An Event Blueprint includes a dependency-based schedule: the task list, durations your team confirms, the critical path and the decisions that could change it. A project lead would work through the predecessors with your committee and record who owns each link.
Questions organisers ask
Is the critical path the same as the most important tasks?
No. It is only the longest dependent chain. An important task with plenty of float is not critical, while a minor task with no float is.
Can there be more than one critical path?
Yes. If two chains have the same total length, a delay on either one moves the end date. Treat both as critical.
Do I need software?
Not for a small plan. A spreadsheet with durations and predecessors is enough. A dependency mapper helps when the task list grows or links change often.
How often should I recalculate?
Whenever a date, duration or approval changes, and at least at each milestone review. A rolling look-ahead keeps the near term honest between reviews.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.