Pro · a list in, a day out
AI time blocking
Paste what you have to do and the hours you have. Get back a day with the demanding work where your attention actually is, the small things batched instead of scattered, and every block ready to run as a timer.
Time blocking is a Pro tool
List what you have to do and the hours you have. It comes back as a day: the demanding work where your attention actually is, the small things batched instead of scattered, real breaks, and an honest list of anything that did not fit. Every block starts as a timer.
Example · a 9:00–17:30 day with six things on the list
The report gets the first and best block of the day, everything small is bundled into two admin windows, and the afternoon is protected for the second focus stretch.
4h 30m of deep work across 2 blocks
- 09:00–11:00Q3 report, first draftHardest thing, most attention available120m
- 11:00–11:15BreakTwo hours is the limit before quality drops15m
- 11:15–12:00Email and the accountant callSmall things batched so they cost one context switch45m
- 12:00–13:00LunchAway from the desk, or the afternoon suffers60m
- 13:00–14:30Review both pull requestsFocused but less demanding than the report90m
- 14:30–14:45BreakReset before the last stretch15m
- 14:45–15:45Team updateWriting you can do on lower fuel60m
- 15:45–16:15Book flights, clear the inboxEnd-of-day admin when focus is gone anyway30m
Durations for the report and the reviews are estimates, and the day assumes no meetings drop in. If one does, the 15:45 admin block is the one to sacrifice.
Why a list is not a plan
A to-do list is a statement of everything that exists. It has no opinion about how long anything takes, what order it should happen in, or whether all of it fits in the day you actually have. That is why a long list can feel productive to write and terrible to work from: you finish six easy things, the hard one is still there at five o’clock, and the list looks shorter without the day having gone anywhere.
Blocking forces the arithmetic. Nine hours of work does not go into seven hours of day, and the useful moment is discovering that at nine in the morning rather than at four in the afternoon. Which is why anything that does not fit comes back as an explicit overflow list here instead of being quietly squeezed in.
Put the hard thing first
Most people have more available at the start of their working window than at the end, and demanding work is the thing that suffers when that runs out. Answering email at 9am with a full tank, then attempting the difficult document at 4pm, is the most common way a perfectly reasonable day produces nothing that mattered.
The other half is protecting it. A deep block with notifications on is a shallow block wearing a label, and the pomodoro timer is a good companion if you need the structure inside a block as well as around it.
Breaks are part of the plan
A day with no breaks in it is not an ambitious plan, it is an inaccurate one, because the breaks happen anyway and just end up unplanned and guilty. Scheduling them means the afternoon block starts with something left, and it makes the plan honest about how many hours of real work a day actually contains, which for most people is closer to four or five than eight.
Frequently asked questions
- What is time blocking?
- Giving every task a specific slot in the day instead of working from an open list. The list tells you what exists; the block tells you when it happens. The difference matters because an unscheduled list quietly assumes you have unlimited hours, and a blocked day forces the question of what actually fits.
- How long should a deep work block be?
- Somewhere between an hour and two. Under about 45 minutes you rarely get far enough into hard work to make progress, and past two hours attention degrades for most people whether or not they notice. Two solid blocks in a day is a good day; four is usually a plan that did not survive contact with reality.
- Why does it group my small tasks together?
- Because the cost of a small task is rarely the task. Fifteen emails scattered through the day cost fifteen context switches, and each one takes minutes to recover from even when the email took thirty seconds. Batching them into one window is the single change that gives most people their afternoon back.
- What happens to tasks that do not fit?
- They come back in a separate list rather than being quietly dropped or crammed in. A plan that pretends nine hours of work fits in seven is worse than no plan, because you only discover the problem at 4pm. Seeing the overflow is the point at which you can actually decide what to cut.
- Does it know about my calendar?
- No, and it never sees it. Nothing is connected and nothing is stored. Tell it about fixed commitments in the same box — a 14:00 call, a school run at 15:30 — and it will schedule around them. The plan assumes no meetings drop in, which is what the note at the bottom of each plan is for.