The math of meeting buffers

Most scheduling tools let you add buffer time between meetings. Most people do not use it. The reason, I think, is that it feels like giving something away — you are reducing the number of slots available, which feels like reducing your capacity.

The math says otherwise.

The no-buffer scenario

Suppose you take six calls a day, five days a week. Each call is 45 minutes. Back-to-back, that is 270 minutes of scheduled time — four and a half hours. The remaining time in your working day is nominally free.

In practice, it is not. Each transition between calls costs you something. You need to close the previous context — make a note, send a follow-up, mentally file away what was discussed. You need to open the next context — review who you are talking to, what the call is about, what you want from it. If you are moving between different kinds of work (a client call, then a sales call, then a support call), the context switch is more expensive.

Research on context switching suggests the cost is somewhere between 5 and 20 minutes per switch, depending on the complexity of the tasks involved. For calls, the lower end is probably more accurate — say 7 minutes per transition.

With six calls and five transitions between them, you are spending roughly 35 minutes a day on context switching that you are not accounting for. Over five days, that is 175 minutes — nearly three hours a week — of cognitive overhead that does not appear anywhere in your calendar.

Adding 10-minute buffers

Now add a 10-minute buffer after each call. Your six 45-minute calls now occupy 6 × 55 minutes = 330 minutes, or five and a half hours. You have lost one hour of schedulable time compared to the no-buffer scenario.

But you have gained something more valuable: the context switching is now contained. Those 10 minutes are enough to close the previous call properly, make notes, and arrive at the next one with a clear head. The 35 minutes of invisible overhead largely disappears, because you have given it a home.

Net change: you lose 60 minutes of schedulable time, but you recover approximately 35 minutes of invisible overhead. The real cost is about 25 minutes a day — roughly half a slot.

More importantly, the quality of each call improves. You are not arriving distracted. You are not rushing to finish because the next call starts in two minutes. The people you are talking to notice this, even if they cannot name it.

The slot reduction is smaller than it looks

The objection to buffers is usually: "I can't afford to lose a slot." But the math on this is worth examining.

If you have six 45-minute slots in a day and you add 10-minute buffers, you can fit five 55-minute blocks (call + buffer) in the same time window, plus one final call without a trailing buffer. So you go from six slots to six slots — you have not lost anything, because the buffer after the last call of the day is not needed.

The real constraint is your working window. If you have a hard stop at 6pm and your first call is at 10am, you have 480 minutes. Six 45-minute calls use 270 minutes. Six 45-minute calls with 10-minute buffers (five buffers, since the last call needs no trailing buffer) use 270 + 50 = 320 minutes. You still have 160 minutes of unscheduled time in the day.

The slot count does not change unless you were already filling every available minute, which is a different problem.

Where schedulers get this wrong

Most scheduling tools treat buffers as a simple subtraction: add a 10-minute buffer, lose 10 minutes of availability. The slot before the buffer is blocked, the slot after is open.

The problem is that this is applied uniformly. A buffer after your last call of the day is pointless — there is no next call to prepare for. A buffer before your first call of the day is also of limited value. The useful buffers are the ones between calls, and specifically between calls of different types.

A good buffer implementation would let you set buffers per event type, not globally. A 30-minute strategy call probably needs a longer buffer than a 15-minute check-in. A call with a new client needs more preparation time than a recurring call with someone you know well.

Kaien handles this at the event type level. You set buffer time per event type, so your "New client intro" event type can have a 15-minute buffer while your "Quick check-in" event type has none. The availability calculation accounts for this correctly — a new client intro followed by a quick check-in will have 15 minutes between them, not zero.

The compounding effect

The case for buffers is not just about individual days. It is about what happens over weeks and months when you are consistently arriving at calls prepared versus consistently arriving distracted.

The 25-minute daily cost of buffers is real. But the return — better calls, fewer errors, less end-of-day exhaustion — compounds in ways that are harder to measure but not harder to notice.

The math is in favour of buffers. The question is whether your scheduling tool makes them easy enough to use that you actually do.