Buffer Time: Why a Fully Booked Calendar Always Breaks

Buffer time is the empty space you leave on purpose between tasks and meetings so that when one runs long, it does not topple everything after it. A fully booked calendar looks productive but is fragile: the first delay cascades through the rest of the day. Because tasks almost always take longer than we expect, the fix is to schedule only 50 to 75 percent of your day and keep short gaps between items plus one or two larger reserve blocks.

Why a packed calendar always breaks

A calendar with no empty space assumes everything will go exactly to plan. It never does. A meeting runs five minutes over, a task takes longer than you thought, someone stops you with an urgent question, the file will not open. In a packed schedule, each of these small delays has nowhere to go, so it pushes into the next block — and that block pushes into the one after. By mid-afternoon the carefully built plan is in ruins and you are improvising in a state of mild panic.

The problem is structural, not personal. A schedule with zero slack is a chain where any single weak link breaks the whole thing. Buffer time is what gives the chain somewhere to flex. Paradoxically, a calendar that is only three-quarters full gets more done than one that is completely full, because it is not in constant crisis.

The planning fallacy: why tasks run long

There is a well-studied reason your estimates are too tight. The planning fallacy, described by Daniel Kahneman and Amos Tversky, is our tendency to underestimate how long things will take, even when we have been burned by the same tasks before. We imagine the smooth version — no interruptions, no snags — and plan for that. Reality includes the snags.

This is why "it will only take an hour" so reliably becomes ninety minutes. Buffer time is the honest correction: rather than pretending you will beat your own track record this time, you leave room for the overrun you can confidently predict in aggregate, even if you cannot say which task will cause it. For more on estimating realistically, pair this with a 1-3-5 list that caps how much you plan in the first place.

The effect is worse when days are packed, because delays do not simply add up — they compound. A single task running fifteen minutes long is trivial in isolation, but in a chain of back-to-back commitments it pushes every later item late, and each of those may run long too. By late afternoon a schedule with no slack is not fifteen minutes behind; it is an hour behind and fraying. Buffer breaks the chain at each link, so an overrun is absorbed where it happens rather than passed down the whole day.

How much buffer to leave

A practical rule is to schedule no more than half to three-quarters of your working day and leave the rest as buffer. That sounds like a lot until you remember how much of a normal day already disappears into transitions, interruptions and recovery. Concretely:

The more unpredictable your role, the more buffer you need. Someone in a reactive, interrupt-driven job might leave half the day open; someone with long protected focus blocks might need less. The right amount is whatever stops your days from regularly running over.

Where to place buffers

Placement matters as much as quantity.

• Between meetings. Never book back to back. A ten-minute gap lets a meeting run slightly over, gives you time to note actions, and stops stress carrying into the next room.
• After overrun-prone tasks. Put slack after the work you know tends to sprawl, so the overrun lands in empty space rather than in your next commitment.
• Around travel and other people. Anything that depends on someone else is a prime source of delay. Pad it.
• A protected reserve in peak hours. Keep one buffer in your best hours, so when something urgent appears it has somewhere to go that is not your most important Deep Work block.

Guarding your buffer

The hard part is not creating buffer; it is protecting it. An empty slot is a magnet for new commitments, and it is tempting to fill it "just this once". Resist. Buffer is doing its job even when it sits empty, because its value is the capacity to absorb what you cannot predict. Treat it as booked time with an invisible owner: the unexpected.

One useful reframe: buffer is not idle time, it is insurance. You would not cancel insurance because you did not make a claim last month. The month you drop your buffers is the month a single overrun takes the whole afternoon down with it, along with your composure. A little deliberate emptiness is what keeps the rest of the plan standing.

If protecting buffer feels uncomfortable, start by tracking how your days actually run for a week. Most people are surprised to find that the busiest-looking days produced the least, precisely because they had no room to breathe and spent the afternoon firefighting. Seeing that pattern in your own schedule is usually more persuasive than any rule, and it makes the empty slots feel less like waste and more like the quiet margin that lets everything else work.

A calendar with no gaps is not a plan, it is a prediction that nothing will go wrong. Buffer time is simply admitting, in advance, that something always does.