Event float and buffer planning: where to hold spare time
Every task has a comfortable estimate, yet the event still ends up in a last-week scramble.
The short answer
Float is spare time a task already has because nothing depends on it straight away. A buffer is time you add on purpose to protect a date. Both are useful; neither should be hidden inside individual task estimates.
Hold the spare time in a few visible places: before milestones that depend on outside parties and ahead of the event date. Name an owner who may spend it.
Float and buffer are different things
| Term | What it is | Who controls it | Example |
|---|---|---|---|
| Float | Spare time a task has without moving the end date, calculated from the plan. | Nobody. It exists or it does not. | AV scoping can slip by up to 21 days without moving the run sheet. |
| Buffer | Time added deliberately as a protected block. | A named owner, with rules for spending it. | Eight days held before the final run sheet. |
| Padding | Extra time hidden inside a task estimate. | The estimator, invisibly. | A 10-day task quoted as 15. |
Why padding fails
When each task owner adds a private cushion, the plan looks safe but nobody can see or manage the spare time. Work expands to fill the estimate, and the cushion is gone by the time it is needed.
Take padding out of the estimates, and keep spare time in one shared, visible place.
Where to place buffers
- Before milestones that depend on outside parties, such as speaker slides, venue sign-off or printer proofs.
- At the end of the critical path, ahead of the event or the run sheet date.
- Where a non-critical chain joins the critical one, so a late side task does not push the main path. This is a feeding buffer.
- Not at the start of the plan. Early buffers get used by default.
Rules for spending a buffer
- Record the buffer as a line in the schedule with its size, position and owner.
- Allow it to be spent only when a task on the chain above it is late, and log each use.
- Review the remaining buffer at every milestone. If more than half is gone before the halfway point, raise it with the sponsor.
- Use schedule compression decisions when the buffer is exhausted.
Worked example · Fictional example
Buffers for a 58-day plan
Fictional organisation and figures. Durations are hypothetical working days; the buffer sizes are illustrations, not recommended percentages.
A fictional logistics association has a 58-day critical path from its critical path exercise. Instead of padding each task, the secretariat adds one buffer of 8 days between speaker slides arriving and the final run sheet, because speaker materials come from outside the organisation and are most likely to be late.
It adds no buffer to the AV chain, which already has 21 days of float, and instead notes the float in the schedule. The council is told the plan is 66 days with the buffer, and that the buffer belongs to the conference chair.
| Buffer | Position | Size (working days) | Protects | Owner |
|---|---|---|---|---|
| Speaker content buffer | Between slides due and run sheet | 8 | Event run sheet date | Conference chair |
| Feeding buffer for AV | Not added: 21 days of float already exist | 0 | Run sheet date | Secretariat head |
Use this yourself
Buffer register
Keep this beside the schedule. Add a row each time you add or spend time, so the committee can see what is left.
- Where the buffer sits in the schedule
- Size in working days and the reason for that size
- Which date or milestone it protects
- Owner who may authorise spending it
- Rules: what counts as a valid use
- Log of each use with date, reason and remaining time
| Buffer | Position | Size | Protects | Owner | Used so far | Remaining |
|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- You can calculate float on your own plan and one person owns the date.
- The committee accepts a visible buffer line in the schedule.
- Few external parties feed into the plan.
Outside planning help earns its fee when
- Many suppliers and approvers feed the plan and nobody can say how much time is left.
- The date is fixed and the board expects a defensible schedule.
- Past events ran late and the team cannot tell which estimates were padded.
Need spare time built into the plan properly?
An Event Blueprint schedule shows float, places buffers where outside inputs arrive and records who may spend them. A project lead would review the buffers with your committee at each milestone and raise decisions early when they run low.
Questions organisers ask
How big should a buffer be?
There is no standard figure. Size it by how uncertain the inputs are and how costly a miss would be, then agree it with the date owner. Start with the most uncertain external inputs.
Can I use the back-planner for this?
The milestone back-planner shows when milestones fall and flags dates that are too late. Record buffers as their own milestone lines so they stay visible.
What if the committee wants the buffer removed?
Show the date it protects and what happens if that date moves. If the committee still removes it, record the decision and the risk accepted.
Is float the same as slack?
In scheduling, yes. Both mean the time a task can slip without moving the end date.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.