Time Blocking: How to Plan a Day Around Your Task List

Time blocking is planning your day as a sequence of blocks, each with one job: 9:00 to 11:00 for the proposal, 11:00 to 11:30 for email, 1:00 to 2:00 for calls. You do it the evening before or first thing in the morning, you draw the jobs from your task list rather than from memory, and when the day goes off plan you redraw the remaining blocks instead of abandoning them. The method, how it differs from timeboxing, a template, and how to pick blocks from a board are below.

How time blocking works

Cal Newport, a computer science professor at Georgetown and the author of Deep Work, describes planning every minute of the workday↗ (opens in a new tab) on paper: he spends ten to twenty minutes each evening building the next day’s schedule, divides each hour into blocks labeled with specific assignments, and leaves room beside them to make corrections “if the day unfolds in an unexpected way.” The idea is not to predict the day perfectly. It is to decide in advance what each hour is for, so you are not deciding under pressure all day long.

1. Start from the list, not the calendar. Look at what is committed for this week and pick the few tasks that must move today.
2. Put fixed events in first: meetings, calls, school pickup. They are the walls the rest of the day is built between.
3. Give your best hours to your hardest task, in one block of at least 90 minutes if you can find it.
4. Batch the small things. Email, messages, approvals and quick fixes go into one or two short blocks rather than scattered across the day.
5. Leave slack. Block no more than about three quarters of the day. Something unplanned always arrives.
6. End with a short planning block: check what moved, update the list, and sketch tomorrow.

Timeboxing vs time blocking

The two terms are used interchangeably, but they come from different places. Timeboxing comes from agile software work. The Agile Alliance glossary↗ (opens in a new tab) defines a timebox as “a previously agreed period of time during which a person or a team works steadily towards the completion of some goal,” and the point is that you stop when the time is up and look at what was done, rather than running over. Time blocking is a way of laying out a whole day.

• Time blocking answers “what is each part of today for?” It covers the whole day, including email and breaks.
• Timeboxing answers “how much time will I give this one thing?” It sets a hard limit on a single task, often to stop it expanding.
• In practice you do both: block the day, then treat each block as a timebox. When the block ends, stop, note where you got to, and move on.
• A Pomodoro round is a small timebox inside a block. The Pomodoro Technique covers when those 25-minute rounds help and when they get in the way.

Task batching: why the small blocks matter

Switching between tasks costs time, and the cost grows with the complexity of the tasks. The American Psychological Association’s summary of the research on multitasking and switching costs↗ (opens in a new tab) describes experiments in which people lost time every time they switched between tasks, and lost more time as the tasks got more complex. Batching is the practical answer: do similar small tasks together, so you pay the switching cost once per batch instead of once per task.

• Communication batch: email, chat and voicemail, two or three times a day at set times.
• Admin batch: invoices, expense reports, approvals, scheduling.
• Review batch: pull requests, drafts from colleagues, documents waiting on you.
• Errand batch: the five-minute fixes that each feel too small to plan and together fill an afternoon.

Meetings are the hardest thing to batch because other people schedule them. Paul Graham’s essay Maker’s Schedule, Manager’s Schedule↗ (opens in a new tab) explains why they hurt people who make things: a manager’s day is cut into one-hour slots, while a maker needs “units of half a day at least.” If you can, ask for meetings to cluster on one or two afternoons, and block the mornings for making.

A time blocking template to copy

Day: [Weekday, Month day, year]
Must move today (from Next Up): [task 1], [task 2], [task 3]

08:30 - 08:45  Plan: check the list, confirm today's three tasks
08:45 - 10:45  Deep block: [task 1]
10:45 - 11:00  Break
11:00 - 11:30  Batch: email and messages
11:30 - 12:30  Block: [task 2]
12:30 - 13:15  Lunch
13:15 - 14:15  Meetings: [call], [call]
14:15 - 15:15  Block: [task 3]
15:15 - 15:45  Batch: reviews and approvals
15:45 - 16:30  Buffer (unplanned work lands here)
16:30 - 16:45  Shutdown: update the board, sketch tomorrow

Rebuilt at: [time]  Reason: [what broke the plan]

Keep the “Must move today” line to three tasks or fewer. The buffer block is not optional: without it, the first surprise pushes every later block, and by 2 p.m. the plan is fiction.

Picking blocks from the Next Up lane

A time-blocked day is only as good as the list it is drawn from. If you pick blocks from memory, you pick what is loud, not what matters. Keeping the list on a board with a small Next Up lane makes the morning planning step quick: Next Up holds what is committed for the next few days, so choosing today’s blocks is choosing from a short list, not from everything.

On fenbs the lanes are To Do, Next Up, In Progress and Completed, and every task has a priority from 1 to 10, where 1 is the most urgent. Sort Next Up by most urgent first, take the top two or three as today’s blocks, and move the one you are working on to In Progress when its block starts. fenbs has no calendar, no due dates and no time tracking, so the blocks themselves live on paper or in your calendar. The board holds what the blocks are for. Each task can carry an optional size from XS to XL, and the sizes map roughly to blocks: XS is under an hour, S an afternoon, M a day or two. An L or XL task will not fit a block and should be split first.

If an AI assistant is connected to the board, the planning step can start with a question: “List the tasks in Next Up, most urgent first, with their sizes, and suggest which three fit into a day with meetings from 1 to 2 p.m.” You still decide; the assistant saves you the scrolling. For the lanes on a board of your own, see personal kanban.

What to do when the day breaks

It will. A client calls, a production bug arrives, a meeting runs long. Time blocking handles this by rebuilding, not by giving up:

1. Stop and take two minutes. Look at the time left and the blocks still ahead.
2. Decide whether the interruption is really urgent. If it can wait, put it on the list as a task and go back to the block.
3. If it must be done now, redraw the rest of the day. Move the most important remaining block into the buffer, and drop the least important one to tomorrow.
4. Write down what broke the plan. After two weeks, the notes show the pattern: the same meeting that always overruns, the same colleague who needs answers at 10 a.m. Plan for it.

A day rebuilt three times is still better than one that was never planned, because each rebuild is a deliberate choice about what to drop. Deciding what to drop is easier when tasks are already sorted by urgency and importance, which is what the Eisenhower matrix is for.