Why the plan and the room disagree
A facilitator plans an exercise and thinks: this takes ten minutes.
What they have timed is the working part — the ten minutes a group spends doing the thing. What actually happens is this. Two minutes explaining the exercise. A minute of people finding out which group they are in, and another of moving chairs. Thirty seconds of a group sitting in silence deciding who goes first. Then ten minutes of work. Then a three-minute debrief that becomes six because the second group's answer is genuinely interesting.
Twenty-two minutes of clock time for a ten-minute exercise. Do that four times in a morning and you are forty-five minutes behind by lunch, which is when it becomes visible, which is when you start cutting the afternoon.
The correction is blunt and reliable: multiply your working-time estimate by 1.5 and schedule that. A facilitator who does this consistently runs on time and looks unhurried, which is itself most of what makes a workshop feel well run.
Realistic durations
| Activity | Plan for | Notes |
|---|---|---|
| Welcome and framing | 10–15 min | Longer if the group does not know each other |
| Introductions, per person | 45–60 sec | 12 people is 12 minutes, not 5 |
| Instructions for an exercise | 2–3 min | Always longer than you think |
| Transition into groups | 2–3 min | Physical movement is not free |
| Small group work | Working estimate × 1.5 | |
| Debrief, per group | 3–5 min | Six groups is 20–30 min |
| Individual reflection | 5–10 min | Genuinely needs silence to work |
| Break | 20–25 min | Anything shorter is a queue |
| Lunch | 60 min minimum | |
| Closing and actions | 15 min | Protect this absolutely |
The debrief row is the one that breaks agendas. Facilitators plan a twenty-minute activity and a five-minute debrief, then discover that six groups reporting back is a half-hour block. If you have more than four groups, either debrief a sample rather than everyone, or schedule the real number.
Where to put the slack
About 15% of the day, and — this is the part that matters — in one or two visible blocks rather than spread thinly.
Slack distributed as two minutes here and three minutes there is invisible, and invisible slack gets absorbed without anyone noticing it has gone. By 11:00 it has silently disappeared and you have no idea where.
A named fifteen-minute buffer before lunch is different. You can see it. You can spend it deliberately when the morning's second exercise produces an argument worth having. And if you do not need it, you break early, which no group has ever complained about.
Put buffers before the fixed points — before lunch, before a guest speaker, before the closing — because those are the moments where overrun becomes other people's problem.
Build your workshop agenda freeThe agenda builder applies durations across the session and recalculates downstream blocks when one runs long, so you can see mid-morning exactly what a fifteen-minute overrun costs the afternoon.
Recovering a session that has slipped
You are forty minutes behind at 14:20. Three options, in order of how much damage they do.
Cut scope. Always first. Drop an activity entirely rather than compressing several. A workshop that does five things properly is better than one that does seven badly, and the group will not know what was not on the agenda.
This works far better if you decided in advance which activities were optional. Mark them on your own copy — not the participants' — so that dropping one at 14:20 is executing a plan rather than improvising in front of a room that can tell.
Shorten debriefs. Sample two groups instead of six. Ask for one insight per group rather than a summary. This recovers real time and costs relatively little.
Do not cut breaks, and do not cut the closing. Both are tempting and both are mistakes. Cutting the break trades fifteen minutes for an afternoon of degraded attention, which is a bad trade. Cutting the closing means the workshop ends without actions or owners, and a workshop that produces no actions has produced nothing durable regardless of how good the discussion was.
The closing is the deliverable
Fifteen minutes, protected, every time.
What goes in it: what we decided, who owns what, and when it happens. Written down, visible on a screen, and confirmed out loud by the people who own each item before anyone leaves the room.
A workshop that ends with "great discussion, we'll follow up" has generated goodwill and nothing else. The follow-up email written three days later by a facilitator reconstructing flip-chart photographs is not the same artefact, and everyone's memory of who volunteered for what will have diverged.
Educators running teaching sessions face a version of this with a hard bell, where the closing is the first casualty of any overrun and the one that most affects whether anything is retained. University event coordinators running multi-session days have the compounding version: one session's overrun is the next facilitator's lost setup time, which is why turnaround between sessions belongs on the schedule as an item rather than being assumed.
A note on repeat workshops
If you run the same workshop more than twice, the agenda should be a saved structure you adapt, not a document you rebuild.
More usefully: after each run, adjust the durations to what actually happened rather than what you planned. Three iterations of that and you have an agenda that reflects reality, runs on time without effort, and is worth more than any amount of planning discipline applied to a fresh document each time.
Most facilitators never do this, which is why most facilitators make the same twenty-minute error every time they run the session.
Adaptable structures sit in the training and education template collections, and for multi-day programmes the corporate retreat schedule builder handles the longer shape.