How time blocking works
Every time blocking template in the top results is a grid: rows for time slots, a column for each day, sometimes in 15, 30 or 60 minute increments. The method behind them is the same. List what has to happen, estimate how long each task takes, place fixed commitments first, then give each task a block. The difference between a time-blocked day that holds and one that is abandoned by 10:30 is what you do when reality disagrees with the grid. Most guides say "be flexible". The template above makes that a procedure.
How to build a time-blocked day
- Count the hours. Start and end of the day, minus fixed commitments and travel. Write the number at the top. It is usually smaller than you think.
- Choose the must-do tasks. Three at most, each with an estimate in minutes. If the estimates add up to more than the hours, cut now, not at 16:00.
- Place fixed blocks. Meetings, appointments, calls with a set time.
- Place deep blocks in your best hours. For most people that is the morning, but the sales example puts calls before 10:00 because that is when prospects answer.
- Add buffers, one flex block and a shutdown. The shutdown is 15 to 30 minutes at the end: fill in Planned vs actual and write tomorrow's first block.
Block length and buffers
Block length should follow the work, not the grid. Deep work needs 60 to 90 minutes. Shallow work goes in batches of 30. Long repetitive jobs, like the grading example, work in 50 on and 10 off. Buffers of 10 to 15 minutes after deep blocks absorb small overruns; anything larger goes to the flex block. If you find yourself using the flex block every day before noon, your estimates are short, and the Planned vs actual section will show by how much.
When the plan breaks
This is the question the top results leave open, and it is why many people try time blocking for a week and stop. A plan breaks in one of three ways: an interruption (the incident at 11:10), an overrun (the demo that ran 40 minutes long) or a wrong estimate (essays taking six minutes instead of four). In each case:
- Write when and why it broke. One line. It is data for next time.
- Decide what still must happen today. Usually one task, because someone is waiting on it.
- Re-block from now to the end of the day. Do not try to rescue the original grid; plan the hours that are left.
- Give everything else a slot tomorrow. "Moved to tomorrow" with a time, not "later".
Three minutes of re-planning keeps the afternoon structured. Without it, the rest of the day turns into reacting.
Daily vs weekly time blocking
Daily blocks suit people whose days differ: a mix of meetings, deep work and errands. Weekly blocks suit people whose work comes in themes: clients, classes, projects. Many people combine them, theming the week by half days and blocking each day in detail the evening before. If the week itself needs planning first, start with the weekly planner template and block from there.
Common mistakes
- Blocking every minute. No buffers, no flex block, no lunch. The plan breaks in the first hour and stays broken.
- Estimates nobody checks. Without a Planned vs actual line, the same task is underestimated forever.
- Abandoning the day at the first interruption. Re-plan the remaining hours instead.
- Treating time blocking as a to-do list. Only the must-do tasks get blocks. The rest stays on your to-do list until it earns a slot.
- Ignoring energy. Put the hardest block where you are sharpest. If you plan your day on the daily planner template first, block only the top three.
A time-blocked day you can re-plan at 11:10
Keep each day's blocks in Scribelet, set a reminder for the ones that cannot slip, and let unfinished tasks carry to tomorrow's daily note on their own. Free to start, encrypted at rest.
Free plan, no credit card. See pricing