Event schedule compression decisions: shorten it or move the date
The schedule says the work needs more time than you have, and the date is not moving unless someone decides it should.
The short answer
Only changes to the critical path shorten a schedule. There are five honest ways to do it: overlap tasks that were planned in series, add people or paid capacity, cut scope, remove or shorten review steps, or move the date.
Each one has a cost or a risk, and each belongs to a decision owner. Write the options down with their trade-offs and have the owner choose, rather than letting the team quietly work faster.
First find what is actually critical
Compressing a task that has float changes nothing. Use your critical path or the dependency mapper to find the chain that sets the date.
Then look at which tasks on that chain can change: a long approval, a sequence that could overlap, or a scope item that could go.
The five options and their trade-offs
| Option | What it means | Typical cost or risk | Who should decide |
|---|---|---|---|
| Overlap tasks (fast-track) | Start a task before its predecessor is finished, for example book AV before the programme is final. | Rework if the earlier task changes. | Date owner, with the risk named. |
| Add capacity | More people or paid support on a task that is limited by effort. | Money, briefing time and coordination. Does not help tasks limited by waiting. | Budget holder. |
| Cut scope | Remove a session, a track, a printed item or a feature. | Reduced value; some stakeholders may object. | Committee or sponsor. |
| Shorten reviews | Fewer rounds, a single approver or pre-approved wording. | Higher chance of errors getting through. | Whoever owns quality for that content. |
| Move the date | Hold the event later or earlier. | Venue availability, member diaries, cost changes. | Board or committee. |
How to run the decision
- State the gap in working days between the current forecast and the required date.
- List the options that could close it, with an estimate of the days each saves. Mark estimates as estimates.
- Name the cost, risk and who is affected for each.
- Ask the decision owner to choose, and record the choice and the risk accepted in the decision log.
- Update the schedule and compare with the baseline.
Pitfalls
- Adding people to a task limited by waiting for a decision.
- Overlapping tasks and not telling the supplier that scope may still change.
- Cutting scope item by item with no one owning the overall effect on the event.
- Compressing the same chain repeatedly until no buffer remains.
Worked example · Fictional example
Ten days too long
Fictional organisation and figures. Durations and savings are hypothetical estimates.
A fictional professional institute has a 58-working-day critical path and only 48 working days before the event. The secretariat lists four options and an estimate of the days each saves.
The committee rejects moving the date because the venue cannot offer another. It accepts shortening the programme approval from two committee rounds to one, and asks speakers for content in a simpler format. The remaining gap is closed by cutting one breakout. The secretariat logs each choice and who accepted the risk.
| Option | Days saved (estimate) | Cost or risk | Decision |
|---|---|---|---|
| Single programme approval round | 4 | Programme errors found later | Accepted by chair |
| Overlap AV booking with programme sign-off | 3 | Possible rework on AV scope | Accepted by secretariat head |
| Cut one breakout session | 3 | One speaker disappointed | Accepted by committee |
| Move event date | 10 | Venue has no other date | Rejected |
Use this yourself
Compression options sheet
Fill one row per option. Send it to the decision owner with a requested decision date.
- Gap to close: forecast end minus required date, in working days
- Each option and the tasks on the critical chain it affects
- Estimated days saved, labelled as an estimate
- Cost, risk and who is affected
- Decision owner, decision date and chosen option
- Updated forecast date after the decision
| Option | Critical task affected | Days saved (estimate) | Cost or risk | Decision owner | Chosen? |
|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- The gap is a few days and one owner can choose between options.
- The critical chain is short and well understood.
- The team can accept some rework risk.
Outside planning help earns its fee when
- The gap is large and each option affects a different group.
- Compression has been applied before and no buffer is left.
- The date is fixed by a board or funder and trade-offs need an impartial recommendation.
Need the options laid out for your committee?
An Event Blueprint documents the schedule and the trade-offs, so that when the date is at risk, the options and their consequences are already written. A project lead would prepare the options sheet with your team and bring it to your decision owner for a clear decision.
Questions organisers ask
Is it ever right to just work faster?
Sometimes, for a small gap and low-risk tasks. Say so in the log so the decision is visible, and do not rely on it for large gaps.
Which option is usually the cheapest?
It depends on the event. Overlapping tasks costs little but carries rework risk; moving the date can be costly if the venue or speakers are fixed.
Does adding people always help?
No. It helps tasks limited by effort. It does not help when the delay is waiting for an approval or an outside supplier.
Where does the milestone back-planner fit?
Use the milestone back-planner to re-run dates after you choose an option and confirm the new dates are feasible.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.