Why back-to-back meetings go wrong
A calendar with meetings stacked end to end looks efficient. In practice it is fragile. The first meeting runs three minutes over, so the second starts late, so the third is rushed, and by the afternoon someone is apologising to a customer who has been waiting in a meeting room.
The cost is not only lateness. People walk into a meeting without having read the brief, finish a call without writing down what was agreed, and spend the next meeting thinking about the last one. The work that turns a meeting into an outcome happens in the minutes around it, and back-to-back scheduling removes those minutes.
What a buffer is for
A buffer is a deliberate gap between meetings. It does several jobs at once:
- Absorbing overruns, so one late finish does not cascade through the day.
- Recording the outcome: two minutes to note what was agreed, the next step, and who owns it, while it is fresh.
- Preparing for the next meeting: re-reading the brief, checking who is attending.
- Moving: between rooms, buildings, or video links.
- Being human: water, a break, a moment of quiet before the next conversation.
How much buffer to leave
There is no single right number. These are starting points to adjust for your own team, not measured standards:
| Situation | Suggested buffer | | --- | --- | | Internal video calls | 0–5 minutes | | External video calls with customers or prospects | 5–10 minutes | | After a demo, negotiation, or other demanding meeting | 10–15 minutes | | Meetings in the same building at an event | 5–10 minutes | | Meetings in different halls or venues | Walking time plus 10 minutes | | Meetings in different locations in a city | Travel time plus 15–20 minutes |
Two simple habits get most of the benefit. The first is to end meetings early by default: 25 or 50 minutes instead of 30 or 60, which many calendar apps can set automatically. Our guide to how long a meeting should be covers the trade-offs. The second is to put a longer gap after any meeting that needs real follow-up work.
Buffers at events
Event days are where buffers matter most and are most often removed. With rooms and experts in short supply, there is pressure to fill every slot. Resist it.
- Count buffers in your capacity plan. A day with ten-minute gaps holds fewer meetings than one without, and knowing that up front is better than discovering it at 3 p.m. The meeting capacity calculator includes the gap between meetings in its count.
- Print the gaps on the schedule. The meeting schedule generator lays out slots with a gap of your choice, so everyone can see them.
- Allow for walking. At a large venue, getting from one hall to another can take longer than you expect. Check the walking time between your rooms when you arrive.
- Protect the stand team too. People working on the stand need breaks as well. See booth staffing schedules.
Protecting buffers in a shared calendar
Buffers disappear when someone else can book into your calendar. A colleague, an assistant, or a booking link sees a free ten minutes and fills it.
- Build buffers into booking rules, not just good intentions. Most scheduling tools can add a gap before or after each booked meeting automatically.
- Use a single source of availability, so a gap is visible to everyone who books. Our guide to reducing scheduling conflicts explains why.
- Cap meetings per day, as well as leaving gaps. Eight meetings with buffers is still a very long day.
When to skip the buffer
Buffers are a default, not a law. Skip them when two meetings are genuinely continuous: the same people, the same topic, one following directly from the other. And if a day has slipped badly, it is better to shorten or reschedule a meeting early than to keep running every meeting late.
CallShark is being built with buffers, daily caps, and travel time between rooms as part of every schedule, so a full day stays a workable one. The product is temporarily down.