Buffer Time Is Missing From Most Schedules

A schedule with no gaps looks efficient and behaves badly. The reason is that tasks vary in length, and a plan with no slack has nowhere to put the variation.

Every task has a distribution, not a duration

A meeting scheduled for thirty minutes sometimes takes twenty-five and sometimes forty. A journey has a usual time and a bad-day time.

Planning uses the usual figure, because that is the number people remember. The result is a schedule built entirely from optimistic estimates.

Individually these errors are small. Assembled back to back, they combine into a day that runs progressively later.

Overruns cascade when there is no slack

Without gaps, an overrun does not stay where it happened. It pushes the next item, which pushes the one after it, and by afternoon the delay has grown rather than dissipated.

Recovery requires an item that can absorb it, either by being shortened or by being surrounded by empty time. If nothing can absorb it, the delay is carried to the end of the day.

This is why a single fifteen-minute overrun in the morning can wreck an evening. The mechanism is transmission, not the size of the original problem.

Transitions are real time and rarely counted

Moving between activities takes longer than the movement itself. There is finishing, packing up, travelling, arriving, settling and reorienting to the new task.

Calendars record only the activities. The transitions happen anyway, and they are taken from whatever was scheduled next.

Booking meetings to end slightly early, or leaving a short gap between commitments, simply makes the existing cost visible.

Where to put the gaps

Buffers are most valuable before anything that cannot move. A fixed appointment, a train or a call with several people is the point where a delay becomes expensive.

A single larger gap in the middle of the day is more useful than many tiny ones. It can absorb a substantial overrun and, if nothing overran, it becomes usable time.

Small gaps get consumed by the transitions they were meant to cover, so they disappear without ever functioning as buffers.

Empty time is not wasted time

The main obstacle is that unbooked time looks like idleness. A calendar with gaps reads as under-committed, particularly in workplaces where a full calendar signals effort.

The alternative is a schedule that is technically full and reliably late. The apparent efficiency is paid for in overruns, missed endings and the sense of being permanently behind.

A gap that goes unused is not lost either. It becomes the only place in the day where something unplanned can happen.