Skip to content

Guide

What Is Time Blocking? A Practical Guide

Time blocking means assigning every task a start time and a duration, so the day is planned as a sequence of blocks rather than an open list of intentions.

The short answer

A list tells you what. Time blocking answers when. You take each task, decide the hour it starts and how long it runs, and place it on a calendar or grid. The day stops being a backlog and becomes a schedule you can actually check against a clock.

The practice is old — Benjamin Franklin ran a block schedule, and Cal Newport's deep work writing put the term back in circulation — but the mechanism is simple. Capacity becomes visible. If eleven hours of work does not fit into a seven-hour day, you see it before the day starts instead of discovering it at 6 p.m.

Time blocking, timeboxing, day theming

These get used interchangeably and they are not quite the same thing.

  • Time blocking reserves a stretch of the day for a task or a kind of work. The block is the container.
  • Timeboxing fixes the limit: the task gets 45 minutes and stops at 45 minutes, finished or not. The constraint is the point.
  • Task batching groups similar work — all email, all calls — into one block so you pay the context-switch cost once.
  • Day theming gives whole days a subject: Monday is planning, Thursday is writing.

Most people who say "time blocking" are doing some mix of the first three. You do not need to pick a camp; you need the day drawn somewhere you will look at it.

How to block a day

  1. Start with the fixed points. Meetings, school runs, the gym class that only exists at 7 a.m. Everything else fits around these.
  2. Place the hardest work in your best hours. For most people that is the first two to three hours after they properly wake up. Guard that block before you fill it with admin.
  3. Give each block one job. "Work on report" is a block. "Work on report and answer email" is two blocks pretending to be one.
  4. Leave slack. Plan roughly 70% of the available hours. The remaining time absorbs the overruns that will happen anyway.
  5. Add a buffer between blocks. Ten or fifteen minutes. Transitions cost real time, and a schedule with no seams falls apart at the first delay.
  6. Review at the end of the day. Not to score yourself — to learn how long your work actually takes. Estimates improve fast once you can compare them to something.

Where it usually breaks

Over-packing. A plan with no gaps is a plan that fails at 10 a.m. If you consistently need more time than you allowed, your estimates are the problem, not your discipline.

Treating the plan as a contract. Blocks are meant to move. A day where you dragged three cards to new hours is a day the method worked, not a day you failed it.

Blocking in a tool you never open. The plan has to be somewhere you actually look — a home screen widget, a lock screen, the app you already have open.

Forgetting the small stuff exists. Email, messages and interruptions do not disappear because you did not schedule them. Give them a block so they stop eating the others.

Blocking a day in TaskCard

TaskCard is built on this method rather than bolted onto it. A task needs a start time and a duration, and it becomes a block on a 24-hour grid. Blocks that share an hour sit side by side, the current-time line is always on screen, and a block that crosses midnight stays visible on both days.

Because plans move, dragging is the primary gesture: pick a card up, drop it on a later hour, pull its edge to change its length. Pinch out and the same schedule becomes a week, a month shaded by how full each day is, then a year — so a heavy week is visible before it arrives. Reminders fire when a block starts and when its time is up, and a Live Activity keeps the countdown on the Lock Screen.

There is no account and no server: the schedule lives on the device, and syncs through your own iCloud account if you turn sync on. iPhone and iPad, iOS 17.0 or later.

Related