TL;DR. Time blocking answers when: it gives work a place on the calendar. Timeboxing sets a hard ceiling on how long, and the end time is the point. Task batching and day theming are two cousins constantly mislabelled as one of them. The decision rule: rabbit-holers and perfectionists need boxes, people whose days dissolve need blocks, and most of us need blocks all day with boxes inside the two hardest things. Run both on one calendar by writing the ceiling into the block title. Three failure modes kill it: a day blocked to the minute with no buffer, treating a block as a promise instead of an intention, and re-blocking the day three times before lunch.
Every article on this topic opens by promising to explain the difference, then uses the two terms interchangeably for a thousand words.
I understand why. On a calendar they look identical: a coloured rectangle with a start and an end. The difference is not in the rectangle. It is in what you do when the work runs over, and that decides which one will actually help you.
So here is the clean version, and then the version where you run both.
The definitions, cleanly
Time blocking assigns work a place. You look at the day, decide that the proposal gets the 9am to 11am slot, and put it there. The question it answers is when. A block makes work concrete: it stops existing as an item on a list and starts existing as a piece of your Tuesday. What a block says about the end time is basically nothing. If the proposal takes until 11:40, most people just keep going.
Timeboxing sets a ceiling. You decide the proposal gets 90 minutes, and at the 90 minute mark you stop. Not "stop unless it is nearly done". Stop. The question it answers is how much of my life does this get, and the end time is not a prediction, it is a constraint you chose deliberately.
The word comes from software project management, where a timebox is a period you do not extend. If the work does not fit, you cut the scope, you do not add days. That is the whole idea imported onto a personal calendar: the duration is fixed and the output is what flexes.
The test that separates them: if you could move it two hours later and nothing would be lost, it is a block. If the finish time is what makes it work, it is a box.
Most people who say they time block are blocking. Most people who need help are the ones who need boxes and have never heard the word.
The two cousins
Two more practices get swept into this conversation and mislabelled as one of the above.
Task batching groups similar work so you pay the switching cost once. All the calls in one run, all the invoices in one run, all the code review in one run. Batching is not a scheduling shape at all. It is a decision about what belongs next to what, and you still have to block or box the batch for it to happen.
Day theming is batching at day resolution: Monday is admin and calls, Tuesday and Wednesday are build days, Friday is review and planning. It works well when you control your week and collapses immediately when you do not.
| Practice | Answers | Fails when |
|---|---|---|
| Time blocking | When will I do this | The day is packed with no buffer |
| Timeboxing | How long does this get | The work has a genuinely unknown shape |
| Task batching | What goes next to what | The batch grows past one sitting |
| Day theming | What is this day for | Other people own your calendar |
Four different tools. The reason articles blur them is that all four produce a tidy-looking week, and a tidy-looking week is the thing being sold.
Which one you actually need
You need boxes if work expands to fill whatever you give it. You plan an hour on a slide deck and lose an afternoon. You cannot stop refining. A five minute check becomes a research hole. For you the ceiling is the medicine, and the discomfort of stopping at a rough version is the treatment working.
You need blocks if your days dissolve. You were busy all day and cannot name what you did. The important thing keeps sliding to tomorrow. You open whatever is loudest. For you the calendar is the medicine, because the problem is not overrunning, it is never starting.
Most people are both, in different places. Drifters at the day level, rabbit-holers inside two or three specific tasks. So the practical answer is usually: block the day at a coarse resolution, then put a hard ceiling on the two blocks you know you will overrun.
That is the actual recommendation here, and it is less tidy than "timeboxing is the advanced version", which is what most of the results above this one will tell you.
Running both on one calendar
One calendar. Not a blocking calendar and a boxing calendar.
Write the ceiling into the title. Proposal draft (box: 90). When you open the day you can see at a glance which rectangles are intentions and which ones are commitments to stop.
Decide the ending before you start the box. Three legal endings: ship it as it is, park it and schedule the next box, or escalate because the thing is bigger than you thought. Choose in advance. Decide in the moment and you will always pick "ten more minutes", and a box you extend by default is just a block with anxiety attached.
Do not box the first block of the day if your problem is starting. A ceiling helps someone who cannot stop. It does nothing for someone who cannot begin, and it adds pressure to the exact moment that was already the hard part. Pick that first task by dread rather than importance, which is the argument in eat the frog.
The planner
The time blocking planner is the surface I built for designing the shape of a day before it starts. Here is precisely what it is.
The grid runs from 6 AM to 11 PM in 30 minute slots. Drag down the column to create a block of any length, using eight categories: Deep Work, Meetings, Admin, Exercise, Break, Personal, Creative and Learning, selectable with the number keys 1 to 8. Click a block to rename it or change its category, drag its bottom edge to resize. A summary panel totals hours per category and shows what share of the 17 hour window you have committed, which is the number I actually use: past about two thirds, the day is fiction. The Export button copies the whole plan as plain text.
The honest limits. It plans one day and clears itself when the date changes, so there are no saved templates and no recurring blocks. It does not sync with any calendar, and nothing leaves your browser. And it has no timeboxing feature, because a ceiling is not a property of a rectangle: you write (box: 45) in the label and then you honour it, or you do not.
So it is a rehearsal surface, not a system of record. Design the shape, read the totals, paste it where your day actually lives. The weekly version of the same exercise is the ideal week planner.
The three failure modes
Over-blocking. A day with a rectangle in every slot has no capacity for the thing that always happens. One interruption at 10am and every subsequent block is now wrong, which means the plan is now lying to you, which means by 2pm you are ignoring it. If you have never blocked before, block three things and leave the rest empty.
Treating a block as a promise. This is the one that quietly ends the practice. A block is an intention with a place, not a commitment to a future self who will definitely feel like it. When you miss one, you move it, and moving it means nothing. What people do instead is experience three missed blocks as three small moral failures and then abandon the calendar rather than the expectation. The same mechanic ends habits, and the fix is identical to the one in how to stop quitting habits: do not let a system report a normal week as failure.
Re-blocking three times before lunch. Planning is comfortable in a way that work is not, so a bad morning turns into a redesign of the afternoon, then a redesign of that. Give yourself one re-plan at a fixed moment, after lunch, and outside that window the plan is what it is.
What neither of them fixes
Neither creates time. If eleven hours of work is being planned into eight, the shape of the plan is not the problem. That is a subtraction problem, and you find it by measuring, not by rearranging. The three day protocol in the time audit guide is the cheapest way to see it.
Neither prioritises. A calendar tells you when, not what matters. That decision belongs to a capped list: nine slots in the 1-3-5 rule, or six ranked items in the Ivy Lee method. Block after you have chosen, not instead of choosing.
Neither survives a calendar owned by other people. If most of your week is booked by someone else, blocking the leftovers is triage, not planning. Knowing what the meetings actually cost is the argument you need before you can protect anything, and that is priced out in what meetings really cost.
Neither decides when to stop within a block. That is a separate question with two reasonable answers: a fixed interval, or a stopwatch and a log, which is the Flowtime technique.
The first week
- Block three things a day. Not nine. Three that would otherwise slide.
- Box exactly one of them, the one you always overrun, and write the ceiling in the title.
- Leave a third of the window empty and resist filling it.
- Move blocks freely. Every time you move one without feeling bad, the practice gets more durable.
- On Friday, count how many happened, not how neat the calendar looked.
If four out of fifteen happened, block two things a day next week instead of three. The plan is supposed to describe a day a real person could have. Most people's first attempt describes a day for someone with no colleagues, no children and no bad afternoons.
Last updated: November 2026.
Written by Eusebiu, the solo founder building Loggd in public. I write code for clients during the day and build this in the evenings around a small daughter, so my own calendar is about a third plan and two thirds negotiation. I share what the aggregate data keeps showing on Threads.
See which blocks actually happened. Loggd tracks your consistency as a forgiving contribution grid, so a week where the plan bent stays a lighter square instead of a reset to zero. Start free.
