Time Blocking When You Always Run Over: Plan the Overrun Into Your Day

You blocked 9:00 to 10:00 for the proposal. At 10:40 you're still in it, the 10:00 block is dead, the 11:00 block is dead, and by lunch the calendar is a museum of things you meant to do. So you conclude time blocking doesn't work for you, go back to a list, and three weeks later try time blocking again. The method isn't the problem. The problem is that your day has no room in it for the one thing that happens every single day: work taking longer than you thought.

Overrunning isn't a discipline failure

If you overran one block once, that's a bad estimate. If you overrun most blocks most days, that's a pattern, and patterns aren't fixed by trying harder.

There are a few ordinary reasons a block runs long, and none of them are about willpower:

• You estimated the clean version of the task. You budgeted for "write the proposal," not for finding last quarter's numbers, not for the formatting, not for the two questions you had to ask someone.
• You estimated the work, not the transitions. Closing one context and opening another costs real minutes — finding the file, re-reading where you stopped, answering the thing that came in while you were away.
• The task was actually several tasks. "Fix the onboarding flow" is a project wearing a task's clothes. Projects don't fit in blocks.
• You don't know the real duration yet. Anything you've never done before is a guess, and your guess is systematically low. Psychologists call this the planning fallacy: we predict from the best-case path rather than from how similar work has actually gone. You don't need a statistic to confirm it — your own last two weeks will.

The standard advice here is "estimate better." You will estimate better, slowly, with practice. But you need a day that works before your estimates improve, not after.

The fix: give the overrun somewhere to land

A schedule where every block is load-bearing fails on the first overrun, because there is nowhere for the extra twenty minutes to go except into the next block. One miss cascades through the whole afternoon.

So stop building the day out of back-to-back blocks and start building it in two kinds of time:

1. Committed time — the blocks where the real work happens.
2. Absorbing time — blocks whose entire job is to swallow the overflow from committed time.

Absorbing time isn't a break and it isn't slack you feel guilty about. It's a deliberate part of the plan with a defined purpose: it catches what ran long, and if nothing ran long, it gets used for a short pre-chosen task. That second half matters. Unassigned empty time gets eaten by your inbox. Absorbing time with a fallback task doesn't.

Build the day in three layers

Layer 1: anchors. Things that genuinely start at a fixed time — meetings, the school run, a call with someone in another timezone. These are the only true appointments in your day. Put them in first and don't negotiate with them.

Layer 2: one to three committed blocks. Real work, 60 to 90 minutes each, each with a named deliverable, not a topic. "Draft the three pricing tiers" instead of "pricing work." A named deliverable tells you whether the block succeeded, which is the information your next estimate runs on.

Layer 3: absorbing time after each committed block. Twenty to thirty minutes. If the proposal ran over, it continues here. If it didn't, you take the top item off a short list of 15-minute jobs you keep for exactly this purpose.

That ratio — roughly 90 minutes committed to 25 absorbing — feels wasteful on paper. It isn't. It's the difference between a plan that describes three hours of real output and a plan that describes six hours of fiction.

Four places an overrun can go

When a block runs past its end, you have four moves. Decide which one you're making, consciously, in the moment:

• Continue into the absorbing block. Default move when you're close to done and the work still has momentum. This is what the absorbing block is for; using it is success, not slippage.
• Cut scope and ship the smaller version. The proposal goes out with two pricing tiers instead of three. Best move when the deadline is real and perfect isn't on the menu.
• Park it at a clean seam. Stop at a point where you can describe in one line what comes next, write that line down, and leave. The note is the whole trick — without it, resuming costs you the first fifteen minutes of the next block.
• Let it eat the next block, on purpose. Sometimes finishing is genuinely worth more than whatever was next. Fine — but then move the displaced block to a specific new slot right now, before you forget it existed. An overrun you decide on is a plan. An overrun you drift into is the thing that makes you quit time blocking.

Stop blocking the hours you've never once protected

Most broken time-block schedules have the same two fantasies in them: a 7:00 a.m. deep work block from someone who gets up at 7:40, and a 4:00 p.m. block from someone whose attention is gone by 3:30.

Block the hours you actually control. For most people that's a smaller window than they'd like — maybe two reliable stretches a day. Two reliable stretches, fully used, beat six aspirational blocks that collapse by 11 a.m. If you've never once protected the 7 a.m. hour, it isn't available to you, and putting work there is just scheduling your own disappointment.

This is also where a week's worth of planning beats a day's. If you only decide what matters at 8:55 on Monday morning, everything urgent wins by default — the same failure mode as an overstuffed to-do list. Planning the week first is what lets you put the right two things into today's committed blocks instead of the loudest two.

A day that survives contact

• 9:00–10:30 — committed: draft the three pricing tiers
• 10:30–11:00 — absorbing: overflow, or two 15-minute jobs from the short list
• 11:00–12:00 — anchor: team call
• 12:00–1:00 — lunch, genuinely away from the desk
• 1:00–2:15 — committed: rework the onboarding emails
• 2:15–2:45 — absorbing
• 2:45–3:30 — admin batch: inbox, invoices, scheduling
• 3:30 onward — unblocked

That's about three hours of committed work in a workday, and it's honest. Note what isn't there: no block titled "catch up," no block that depends on the previous one ending exactly on time, and nothing scheduled in the hour where you know your attention falls off.

Log two numbers so your estimates can improve

For each committed block, write down the estimate and the actual. Nothing else. After a week you'll have the only metric that matters: your personal ratio between what you predict and what's true. If writing tasks consistently take you half again as long, you now budget half again as long, and your blocks start holding.

Keep this somewhere you already look, in the same place as your tasks and your week. A separate tracking app is a new habit competing with the habit you're trying to build, which is why most systems fall apart around week two and why one dashboard beats four apps for anything you need to do daily.

Two things aren't worth tracking: how many blocks you "completed" and how closely the day matched the plan. Both reward writing plans you can hit rather than plans worth hitting, and both label a productive day as a failure because the shape changed. Judge the day on whether the named deliverables moved, and judge the plan on whether one overrun took the whole afternoon down with it. When the answer to that second question is no, time blocking is working — even on the days nothing ran on time.