How Much Buffer Time to Leave Between Tasks and Meetings
The calendar says the 10:00 call ends at 10:30 and the next one starts at 10:30. In practice the first call runs to 10:34, you still need to send the follow-up note while it is fresh, the coffee from 8:00 is long gone, and you join the...

The calendar says the 10:00 call ends at 10:30 and the next one starts at 10:30. In practice the first call runs to 10:34, you still need to send the follow-up note while it is fresh, the coffee from 8:00 is long gone, and you join the second meeting at 10:41 apologising. By 3 pm every block on the page is shifted twenty minutes to the right, and the hour you saved for focused work has quietly disappeared.
The usual fix is "add buffer time", which is correct and almost useless, because nobody says how much. Too little and the day still slides. Too much and the calendar fills with empty slivers that other people book over. I have tried most of the ratios floating around, and the answer that works depends less on a rule and more on three specific things about your tasks.
Where the lost minutes actually go
When I logged a fortnight of my own transitions, the overrun was rarely the task itself. It was the edges. A meeting that ended on time still cost me six to ten minutes afterwards: writing down what was agreed, answering the message someone sent during the call, finding the file for the next thing. Switching from a writing task to a spreadsheet took even longer, often twelve minutes before I was properly working again.
There are really three kinds of buffer hiding under one word:
- Overrun buffer catches tasks that take longer than planned. This depends on how good your estimates are.
- Wrap up buffer covers the small admin that follows almost every task: notes, replies, filing.
- Switching buffer is the time it takes your head to leave one kind of work and arrive at another.
Most advice treats these as one block. Separating them is what lets you size buffers properly instead of guessing.
A starting point for how much to leave
These are the numbers I use as defaults. They come from my own logs and from roughly a dozen people I have helped rework their weeks, so treat them as a reasonable first guess, not a law.
| Situation | Buffer after the task | Why |
|---|---|---|
| Back to back video calls | 10 minutes | Notes plus a short break from the screen |
| In person meeting in another building | 15 to 20 minutes | Walking, lifts, small talk on the way out |
| Same type of task, such as two writing blocks | 5 minutes | Little switching cost |
| Change of type, such as writing then budgeting | 10 to 15 minutes | Switching cost is the largest part |
| Task you have never done before | Add 50 percent of its planned length | Estimates on new work are reliably low |
| Driving between appointments | Travel time plus 25 percent | Parking and traffic |
On top of those, I leave one unscheduled 30 minute block around the middle of the afternoon. It absorbs whatever ran over in the morning so the late afternoon does not inherit the whole morning's debt.
If your overruns are big and consistent, the problem may be the estimates rather than the buffers. The method in how to make task time estimates you can trust fixes the estimate itself, which then lets the buffers shrink.
Why a fixed percentage rule misleads
A common rule of thumb says to add 25 percent buffer to everything. It is simple and it is better than nothing. But in my logs it produced the wrong answer for most of the day.
For short tasks, 25 percent is too little. A 20 minute task gets a 5 minute buffer, yet the wrap up and switching costs do not shrink just because the task is short. A quick call still needs its notes. For long tasks, 25 percent is often too much. A three hour block of focused writing gets 45 minutes of padding, and I rarely needed more than 15 after it, because there was only one transition instead of several.
The fixed overhead per transition matters more than the length of the task. So I count transitions, not hours. A day with eight short meetings needs far more total buffer than a day with two long work blocks, even if both add up to the same scheduled time.
Count the number of times you switch, not the number of hours you work. That is where the buffer goes.
Protecting the buffer from other people
Buffers that look empty on a shared calendar get booked. Someone sees 10:30 to 10:45 free and drops a quick sync into it, and suddenly the gap is gone.
A few things help. In Google Calendar and Outlook you can set default meeting lengths shorter than the hour, 25 or 50 minutes instead of 30 or 60. Google calls this "speedy meetings" and Outlook calls it "end appointments and meetings early". It builds the gap into every invite you send, without anyone needing to notice.
For the afternoon catch up block, I give it a dull, specific name like "Follow ups from morning" and mark it busy. Calendar blocks titled "Buffer" seem to invite negotiation in a way that a named task does not.
And if you are the one booking, leave the gaps for other people too. An invite that ends five minutes before the hour is one of the small courtesies that makes everyone's day run on time.
Testing your own numbers in one week
Run a quick experiment rather than adopting my table wholesale. For five working days, note the time each task actually ended and the time you actually started the next one with a clear head. You do not need an app; a sticky note next to your keyboard works. At the end of the week, average the gaps by type: calls, deep work, admin, travel.
Those averages are your real buffer sizes. Mine came out higher than I expected for calls and lower than I expected for long writing sessions. Most people find one category is badly underestimated, and fixing just that one recovers a surprising amount of the day. If lateness is the bigger pattern, the approach in how to stop running late pairs well with this.
Then add those buffers to next week's calendar before anything else goes in. More on structuring the day is collected under time management.
FAQ
How much buffer time should I leave between meetings?
About 10 minutes between video calls and 15 to 20 minutes between in person meetings in different places. Adjust after a week of tracking your real transitions.
Is buffer time wasted time?
Only if nothing runs over, which is rare. Unused buffer can go to quick admin, so the time still gets used.
Should I schedule buffer time as a calendar event?
For the larger afternoon catch up block, yes, with a specific name and marked busy. Short gaps work better through shorter default meeting lengths.
What is the difference between buffer time and slack time?
Buffer time sits next to a specific task. Slack time is a general reserve in the day or week that can absorb any delay.
More in Time Management
Time Management
How to Rescue a Workday That Got Hijacked by 10am
A Tuesday in September. I had three things written down, the first one blocked out from 9 until 11, and by 9:52 a client had...
Time Management
Eat the Frog Method and When Hard Tasks Should Go First
There is one task on your list that you keep moving to tomorrow.
Time Management
Time Management for Remote Work That Fits a Real Day
Working from home was supposed to give you more time.