Time Blocking: How to Plan a Workday in Blocks, With Sample Days and What to Do When the Plan Breaks
Time blocking is a planning method where you divide your workday into blocks on a calendar and give each block one task or one kind of work, such as deep work, email, meetings or admin. You build the blocks before the day starts, follow them, and redraw the rest of the day whenever the plan breaks.
Picture 8:55 on a Tuesday. Your to-do list has twelve items, your calendar has four meetings in odd places, and your inbox is ready to fill every gap in between. The list tells you what needs doing, but never when.
This guide covers the block types every day needs, a plan-tomorrow routine, a weekly version, three sample days with every hour assigned, and how to re-block when a meeting blows up the plan.
What is time blocking?
Every working hour gets a job in advance, including the reactive hours that go to email, chat and whatever lands on your desk. A block is a promise to yourself about what happens in that window, written where you will see it.
The key difference from a to-do list is capacity. A list can hold nine hours of tasks and still look fine. Put the same tasks on a calendar, and you see at once that they do not fit into the three free hours you actually have. The same view shows the cost of every new request, because anything you agree to has to take a slot from something already planned.
Where the time blocking method comes from
The writer and computer science professor Cal Newport made the name popular in a 2013 post on planning every minute of your work day. He spends ten to twenty minutes each evening building the next day's blocks on paper. He leaves room beside the blocks to fix the plan when the day changes, and he blocks off reactive work like any other task.
In the same post, Newport estimates that a 40 hour time-blocked week produces as much as a 60+ hour week without structure. That is his personal estimate, not a study result, so treat it as a claim to test.
Time blocking vs timeboxing, task batching and day theming
These four terms often get used as if they mean the same thing. They do not. Each one fixes a different part of your time in advance.
| Method | What you fix in advance | Best for | Example |
|---|---|---|---|
| Time blocking | When each kind of work happens, across the whole day. | Days where many demands compete for the same hours. | Report draft 9:00 to 11:00, replies 11:00 to 11:30, meetings after lunch. |
| Timeboxing | A hard limit on how long one task may take. When the box ends, you stop and judge the result. | Tasks that grow to fill any time you give them. | Forty-five minutes for a first draft, then send it or book a second box. |
| Task batching | Which similar small tasks get done together in one sitting. | Replies, approvals and other small, repeated jobs. | All of this week's expense reports in one 30 minute block. |
| Day theming | What a whole day, or half day, is for. | Roles that juggle several areas, such as clients, hiring and planning. | Monday morning for planning and admin, Friday afternoon for reviews. |
In practice, they stack. A time-blocked day usually holds batched admin blocks and a few timeboxed tasks, and day theming is time blocking at the scale of the week. Marc Zao-Sanders makes a short case for the timeboxing part in Harvard Business Review, and short timed sprints such as the Pomodoro Technique can run inside any block.
The five block types every workday needs
Most plans fail because they only schedule the important work and leave the rest to chance. Then email and chat take the gaps, and the gaps take the day. A plan that holds up uses five kinds of block.
Deep blocks
A deep block holds one demanding output and runs 60 to 120 minutes. Name it after the output, such as "Finish the vendor comparison," not "Work." For the rules of the work itself, see the deep work guide.
Shallow blocks
Shallow blocks hold real work that needs less thought: reviews, edits, ticket triage and short documents. Grouping them keeps that work out of your deep blocks.
Admin blocks for email and chat
Plan two or three admin blocks a day, 20 to 45 minutes each, with email and chat closed between them. The deep work guide already explains why replies should wait for fixed windows. What matters here is length and placement: put one admin block right after a run of meetings, when replies have piled up, and one near the end of the day.
When you re-block, admin blocks are the first to merge or shrink. If an admin block is mostly typing replies, you can speak them at the cursor with VoiceSnap Pro dictation, and the dictate-in guides cover specific apps. For why constant switching costs so much, see the post on context switching.
Meeting blocks
Meetings already on your calendar are fixed blocks. Where you control them, stack them next to each other instead of scattering them. That way the time between them is long enough to use.
Buffer and overflow blocks
Leave 15 to 30 minutes after hard blocks (deep blocks and meeting runs), plus one overflow block late in the day for whatever ran long. Lunch or a light admin or follow-up block counts as buffer. These blocks exist because of the planning fallacy: people reliably underestimate how long their own tasks will take, as Buehler, Griffin and Ross showed in 1994. A practical rule of thumb is to add a quarter to a half more time than your first guess.
Breaks and lunch are blocks too. If they are not on the plan, they are the first thing to vanish. Block your stop time as well, or the overflow block quietly spreads into the evening.
How to time block your day in 7 steps
This routine takes about 10 to 15 minutes at the end of the working day. Newport does it in the evening. If evenings never work for you, do it first thing in the morning, before you open email.
- Start with what is fixed. Put tomorrow's meetings and hard deadlines on the page first. Everything else fits around them.
- Empty your head into a list. List every task before you place any of them. If the list lives in your head, a brain dump by talking is a fast way to get it out.
- Pick the one output that would make tomorrow a good day. Give it the first deep block, in the hours when your energy is best.
- Estimate, then add buffer. Guess how long each remaining task takes, then add the buffer from the rule of thumb above.
- Batch the small stuff. Put email, chat and small tasks into two or three admin blocks.
- Add an overflow block and a planning slot. Place one overflow block late in the afternoon. Keep the last 15 minutes of the day for planning the next one.
- Put the blocks on your calendar. Name each block after its output, and silence alerts during deep blocks with Focus on Mac or Focus in Windows. In Google Calendar, a focus time event can decline meetings for you, but only on eligible work or school accounts.
Research on specific when-and-where plans, called implementation intentions (Gollwitzer, 1999), finds they raise follow-through compared with vague goals. That research is about planning in general, not time blocking in particular, and the post on the Zeigarnik effect covers it in more depth.
A time blocking template: the plan-tomorrow checklist
Copy this checklist and run it at the end of each day:
- Tomorrow's fixed meetings are on the page.
- One main output is chosen and named.
- The first deep block sits in your best hours.
- Two or three admin blocks are placed, one after the busiest run of meetings.
- Every deep block and meeting run has a buffer or admin block after it.
- One overflow block sits late in the afternoon.
- The last 15 minutes are kept for the next day's plan.
Plan the week first, then the days
A daily plan works better when it fills in a weekly one. Set aside 20 to 30 minutes on Friday afternoon or Monday morning. Choose three to five outcomes for the week, give each one a deep block on a specific day, and anchor the recurring meetings.
This is also where day theming fits. You might keep Monday morning for planning and admin, stack one-on-ones into a single afternoon, and use Friday afternoon for reviews. The daily plan then only fills in the details around those anchors.
The Stanford Center for Teaching and Learning shows a clear weekly time blocking example written for students. Its advice carries over to any job: overestimate how long things will take, and leave real buffer in the week. If you keep a full task inventory with a weekly review, the weekly plan draws its outcomes from it.
Time blocking examples: three sample days
These three days are illustrations to adapt, not prescriptions. Each time blocking schedule covers a common kind of calendar and gives every hour a job, email and chat included.
Maker day: one big deliverable
This day suits a consultant writing a report, an analyst building a model or a technical writer finishing a guide. There is one call and very little else that is fixed.
| Time | Block | What happens |
|---|---|---|
| 8:00 to 8:20 | Admin | Scan email and chat for anything due today. Reply only where someone is waiting on you. |
| 8:20 to 10:20 | Deep block 1 | Write the findings section of the client report. Chat and email stay closed. |
| 10:20 to 10:45 | Buffer | Stretch, or finish a paragraph that ran over. |
| 10:45 to 11:15 | Admin | Replies, scheduling and quick questions from the morning. |
| 11:15 to 12:00 | Call | Weekly client check-in. |
| 12:00 to 13:00 | Lunch | Away from the desk. |
| 13:00 to 14:15 | Deep block 2 | Build the table of recommendations. This is the block to give up first. |
| 14:15 to 14:30 | Buffer | Short break. |
| 14:30 to 15:15 | Shallow | Edits, comments from a colleague and formatting. |
| 15:15 to 15:45 | Admin | Replies, plus anything the call turned up. |
| 15:45 to 17:00 | Buffer and overflow | Finish whatever ran long. If nothing did, outline the next section. |
| 17:00 to 17:15 | Plan tomorrow | Run the plan-tomorrow checklist. |
The first deep block is long and early, before the inbox has a chance to set the agenda. The second one is shorter and goes first if the day breaks, because the morning block has already moved the report forward. The single call sits just before lunch on purpose: Paul Graham's essay Maker's Schedule, Manager's Schedule explains why one meeting in the middle of a maker's morning costs far more than its length.
Manager day: meetings most of the day
This day suits a team lead whose calendar is mostly booked by other people. The goal is one protected hour and a home for every reactive minute.
| Time | Block | What happens |
|---|---|---|
| 8:00 to 8:15 | Standup | Daily team standup. |
| 8:15 to 8:45 | Admin | Clear overnight email and chat. Note anything to raise in the one-on-ones. |
| 8:45 to 9:45 | Focus block | Write the decision memo on the hiring plan. Alerts off. |
| 9:45 to 10:00 | Buffer | Prep notes for the first one-on-one. |
| 10:00 to 11:40 | One-on-ones | Three 30 minute one-on-ones, stacked, with 5 minute gaps. |
| 11:40 to 12:30 | Lunch | Away from the desk. |
| 12:30 to 14:30 | Meeting run | Project review, vendor call and planning meeting, back to back. |
| 14:30 to 15:00 | Follow-up | Send notes, decisions and owners from every meeting. |
| 15:00 to 16:15 | Open door | Handle requests from the team. If it is quiet, review the draft budget. |
| 16:15 to 16:45 | Admin | Last pass on email and chat. |
| 16:45 to 17:15 | Overflow | Whatever slipped earlier in the day. |
| 17:15 to 17:30 | Plan tomorrow | Block the next day before you leave. |
The one protected hour comes before the meetings start, because after 10:00 there is no hour left to protect. The follow-up block right after the meeting run is where notes, decisions and owners go out while they are fresh, and the guide to writing action items covers how to phrase them. The open-door block borrows an idea from Newport: give a reactive block a second purpose, so a quiet hour still moves a named task forward.
Mixed day: a PM or support lead
This day suits a product manager or support lead with some deep work, plenty of triage and a block of meetings.
| Time | Block | What happens |
|---|---|---|
| 8:00 to 8:15 | Admin | Check for overnight escalations only. |
| 8:15 to 9:45 | Deep block | Write the spec for the next feature. |
| 9:45 to 10:00 | Buffer | Short break. |
| 10:00 to 10:15 | Standup | Daily team standup. |
| 10:15 to 10:45 | Admin | Email and chat. |
| 10:45 to 11:45 | Shallow, batched | Ticket triage and design reviews in one sitting. |
| 11:45 to 12:30 | Lunch | Away from the desk. |
| 12:30 to 14:30 | Meetings | Roadmap sync, customer call and design review, stacked. |
| 14:30 to 14:50 | Admin | A short round of replies and meeting notes. |
| 14:50 to 16:15 | Escalations | Handle escalations from support or engineering. If it is quiet, update the roadmap doc. |
| 16:15 to 16:45 | Buffer and overflow | Finish what ran long. |
| 16:45 to 17:00 | Plan tomorrow | Run the checklist. |
Mixed days fail when reactive work has no home and spreads across everything. Here it gets its own escalation block, with a fallback task for when nothing is on fire. Triage and reviews are batched into one shallow block, so the morning deep block stays clean.
What to do when the plan breaks
The plan will break on most days, and that is expected. A time-blocked day is a plan you redraw, not a test you fail. Newport leaves room on the page next to his blocks for exactly this reason.
Re-block the rest of the day in two minutes
When a meeting lands on your deep block or a task runs an hour over, run this short procedure:
- Stop at the next natural break. If the new meeting starts soon, stop right away.
- Look only at the hours left. Do not try to win back the morning.
- Keep the block for the one output that still has to happen today. Shrink it if you must, since 45 minutes beats none.
- Move shallow and admin work first. Merge two admin blocks into one if that is what it takes.
- Push the rest into the overflow block or tomorrow's plan, by name. If a meeting is about to start, say the moved tasks into one voice note that ends "remind me tomorrow at 9."
- Redraw the blocks. Update the calendar or the page so the plan matches the day you now have.
In VoiceSnap Pro, hold Right Command on Mac or Right Ctrl on Windows (see the shortcut list). With Reminders from your voice on, the phrase sets a reminder on the note, not a calendar event. The alert arrives while the app runs, and missed ones wait under Overdue. Focus or Do Not Disturb can silence the alert during a block, but due reminders still show in the app's Reminders view.
When an urgent request lands mid-block
If the request truly cannot wait, stop and re-block with the steps above. If it can wait, reply with the time you will handle it and put it in the next admin block. The post on context switching has more on this reply-by habit.
Catch stray thoughts without leaving the block
A thought that is not urgent should not cost you the block. Say it into a voice note with one shortcut, or jot it on paper, and leave it for the next admin block. The deep work guide has the full capture-inbox method.
An open task keeps nagging until it has a plan, which is the Zeigarnik effect at work. When a block ends, a one-line note about where you left off, as in interstitial journaling, makes the next block easier to start.
If you re-block every day
Re-blocking every day means the plan is too tight, not that you are failing at it. Count your re-blocks for a week and note what caused each one. Then fix the pattern: add buffer if tasks run long, shorten deep blocks if they keep getting cut, or give reactive work one more block if requests keep landing.
Common time blocking mistakes
When a plan keeps failing, check it against these six mistakes first.
| Mistake | Fix |
|---|---|
| Planned work adds up to more than the free hours. | Add up the estimates before you place blocks. If they exceed the open hours, move the extra tasks to tomorrow by name now, not at 16:00. |
| Email and chat never blocked, so they leak everywhere. | Give them two or three admin blocks a day, and set your chat status to say when you will reply next. |
| Deep work placed in low-energy hours. | Move it to the hours when you think best. If you are not sure when those are, rate your focus from 1 to 5 after each block for a week. |
| Blocks are invisible to colleagues, so meetings land on them. | Put deep blocks on the calendar people book from, shown as busy and titled with the output. |
| Planning the day but never the week. | Book a recurring 20 to 30 minute weekly plan on Friday or Monday, so it survives busy weeks. |
| Never comparing the plan with what happened. | In the last 15 minutes, note which blocks ran over and by how much. Pad tomorrow's estimate for that kind of task. |
Frequently Asked Questions
What is an example of time blocking?
A simple morning looks like this: 9:00 to 10:45, finish the vendor comparison; 10:45 to 11:15, email and chat; 11:15 to 12:00, meetings. Each window has one job. For full days, see the three sample days above.
What is the 3-3-3 rule at work?
It means about three hours on your main project, three urgent tasks and three maintenance tasks each day, an idea usually credited to Oliver Burkeman. As blocks, that is one or two deep blocks, one admin block for the three urgent tasks and one shallow block for the three maintenance tasks.
What are the best time blocking apps?
For most people, the best time blocking calendar is the one their meetings already live in: Google Calendar, Outlook or Apple Calendar, with one event per block and a color per block type. On a shared work calendar, colleagues see your blocks as busy before they book you. If you want tasks and blocks in one view, a task app with a calendar view, such as Todoist's calendar layout on its paid plans, lets you drag each task onto a time slot. Paper works too.
Does time blocking actually work?
There is little direct research on time blocking itself, and the closest studies look at planning in general. A better test is your own record: for two weeks, count the deep blocks you finished as planned and the times you re-blocked. If finished deep blocks hold or rise while re-blocks fall as you add buffer, it is working for you.
Does time blocking work if your job is mostly reactive?
Yes, if you block the reactive work instead of fighting it. Newport's answer is to block open-ended reactive time like any other obligation, then keep a few small blocks at the edges of the day for deeper work. Give each reactive block a fallback task for quiet stretches, as the open-door and escalation blocks in the sample days do.
What is the golden rule of time management?
There is no single official rule. The idea most methods share is to decide in advance what your time is for, and give the important work a fixed slot before urgent requests fill it. Time blocking is one direct way to do that.
Block tomorrow before you close the laptop
Spend ten minutes today blocking tomorrow: one deep block, two admin blocks and an overflow block, with buffer after the hard ones. When the day breaks, re-block once and keep going.
With VoiceSnap Pro, you can speak moved tasks into one voice note and dictate admin-block replies at the cursor in any app. Download free for Apple silicon Macs and Windows PCs. It is free to start, with no card. Pro is $9 a month when you need unlimited transcription and manual AI actions, subject to fair use.