At 10:20, the task you gave an hour is still open. A teammate needs an answer, a meeting moved, and the rest of the calendar now looks like a row of promises you can't keep.
That's not a reason to abandon time blocking. It's a reason to treat the plan as something you revise, not a verdict on how the day should have gone.
Short answer: time blocking means assigning work to specific spans on your calendar. Plan the fixed parts of the week first, leave room for reactive work, then re-block the remaining day when something changes. At the end of the week, compare a few estimates with what actually happened and use that ratio to size similar blocks next time.
What is time blocking?
Time blocking is a way to give a task or kind of work a place on your calendar, instead of leaving every open hour to a to-do list and incoming requests. A block is a plan for what you intend to work on during that time; it doesn't guarantee the task will be finished.
Cal Newport's time blocking method describes the stricter version as giving every minute a job. The useful part is not a perfectly packed calendar. When a crisis or an overrun knocks the schedule off course, he recommends making a new schedule for the rest of the day and keeping the intention, not the original plan. (Newport (2020))
Start with a lighter version if a full day of blocks feels brittle: schedule the few tasks that need protected time, batch shallow work, and leave open space where interruptions usually land. Batching matters because every context switch has a cost.
How do you time block a week?
Build the week from fixed commitments outward. Put meetings, meals, appointments, and deadlines on the page first; then place your priority work where you can actually do it and reserve explicit capacity for the work that arrives later.
Copy this weekly time blocking template into a note or calendar description. Replace the labels with real tasks after you check your commitments:
WEEK OF: __________
MON TUE WED THU FRI
Fixed events ______ ______ ______ ______ ______
Priority work ______ ______ ______ ______ ______
Reactive work ______ ______ ______ ______ ______
Admin / messages ______ ______ ______ ______ ______
Open capacity ______ ______ ______ ______ ______
Use the rows as categories, not an order to fill every cell. If you're on call, "reactive work" may take most of the day; if your calendar is meeting-heavy, it may be easier to protect one short block than to pretend you have a free morning. Your schedule should show the limits you have, not hide them.
What does a daily time blocking template look like?
Use a daily template with a task, a realistic start and end, and a place where unfinished work can go.
DATE: __________
09:00–10:00 Priority task: ____________________
10:00–10:30 Messages / quick requests
10:30–11:00 Open capacity / spillover
11:00–12:00 Priority task: ____________________
12:00–13:00 Lunch / away from work
13:00–14:00 Fixed meeting or reactive work
14:00–15:00 Priority task: ____________________
15:00–15:30 Open capacity / spillover
15:30–16:00 Admin and closeout
If the plan breaks, next block to move: __________
This time blocking example is a sample workday, not a recommended schedule. Shift the hours, add breaks, and replace a focus block with a second reactive block if your role demands it. A timer can help you stay inside a shorter block; the calendar event still answers what you intend to work on.
How do you set up time blocking in Google or Apple Calendar?
Create ordinary calendar events for the blocks; you don't need a special time-blocking app. Google Calendar and Apple Calendar both let you set events by choosing or dragging across a time range.
For Google Calendar time blocking on a computer, click an empty time, add a title such as "Draft proposal," and save. Drag across the calendar to choose a longer span. Google's separate Focus time event type can mute Chat notifications or decline meetings, but Google lists it for work or school accounts on Workspace Business Standard or Plus, Enterprise Standard or Plus, Education, and Nonprofits. You can create it only from Day or Week view and it needs a start and end time. (Google Calendar Help (2026); Google Calendar Help (2026))
On a Mac, open Calendar and switch to Day or Week view. Drag from the start time to the end time, then type the title and any notes into the event window that opens. Double-clicking an empty time works too. (Apple Support (2026))
Name the event for the work, not just "Focus." "Write first draft — section 2" gives you a useful next action when the block starts. If the calendar is shared, use a title that makes the commitment clear without exposing private task details.
What should you do when the schedule breaks?
Re-plan the remaining hours as soon as you can. Keep fixed commitments, move unfinished work to the next open block, and decide what will be dropped or delayed; don't compress every remaining task into the leftover minutes.
Newport's original example explicitly leaves room beside blocks for corrections, and his later explanation says to make an updated schedule after an interruption. (Newport (2013); Newport (2020))
Try this three-question reset:
- What changed? Write down the interruption or overrun in plain words.
- What still matters today? Keep the deadline-sensitive or high-priority task; move the rest.
- Where is the next open slot? Put the moved task there, or leave it unscheduled if the week has no capacity.
If the workday is mostly reactive, give that time a real block with a fallback task. Newport suggests assigning open-ended reactive periods a secondary purpose: process requests first, then work on a named project if there's downtime. This is more honest than labeling the whole day "deep work" and resenting every call.
How much buffer should you add to a block?
Use your own estimate-to-actual ratio for similar work instead of borrowing a universal percentage. If three comparable blocks were estimated at 30, 60, and 90 minutes (180 minutes total), but took 40, 75, and 110 minutes (225 minutes total), the multiplier is 225 ÷ 180 = 1.25. Next time, a similar 60-minute estimate becomes 75 minutes.
That 25% is an example calculation, not a rule for everyone. Track a few like-for-like tasks first, and keep the planned and actual totals for the same work. If one estimate was unusually wrong, separate it instead of letting it distort every block. This is the same reason I link the planning fallacy and why blocks run long.
You can keep a small table for the next planning pass:
| Similar work | Planned | Actual | Next estimate |
|---|---|---|---|
| Drafting, first pass | 60 min | 75 min | 75 min |
| Client fixes | 45 min | 45 min | 45 min |
| Code review | 60 min | 90 min | 90 min |
The table is hypothetical. Replace it with your own task records. If the work type changes or your process changes, start a fresh comparison instead of carrying an old multiplier forward indefinitely.
Does time blocking work for reactive or meeting-heavy jobs?
It can, if the calendar includes the reactive work and you protect only the capacity you can control. A block does not have to be a promise that nobody can interrupt you.
| Work pattern | Use this kind of block | Adjustment when the day changes |
|---|---|---|
| On-call or customer support | Named response windows, with a project task as the fallback | Keep the response block; use any quiet time for the fallback task |
| Meeting-heavy | Short focus blocks around fixed meetings | Move one task at a time; don't assume every gap is usable work time |
| Mostly self-directed | Longer blocks for priority work, plus open capacity | Re-plan when the task overruns; preserve the next fixed commitment |
If even a short protected block is impossible, use the calendar to expose that constraint and negotiate priorities or deadlines. A packed calendar can describe the problem; it can't create spare hours.
How do you compare a block with what actually happened?
At the end of the week, compare a few planned tasks with the time that went into them, then adjust the next similar block. The comparison is useful only when you can tell what filled the time; scheduled time alone doesn't show whether it went to the planned task, a meeting, or an interruption.
I make Timex, and it doesn't plan, schedule, or read calendars. On its Today timeline, you can drag to select a time window and filter the totals to that selection; that can show what apps and sites filled a Mac-work block. For a task estimate and actual, the free estimate-vs-actual tool calculates your estimation multiplier. Work away from the Mac still needs another record.
The honest limit: your calendar is a plan, and your time record is evidence of what happened.
Time blocking is working when the calendar helps you make the next decision, even after the original plan changes. Download Timex if you want to see what fills a selected block on your Mac.
— DK