Calendars

How to Build a Weekly Plan That Survives a Lost Day

Plan a week from net available hours, keep a fallback tier of work, and recheck the plan when a day disappears.

On Monday, a supplier call and a file handoff can fit comfortably on the same calendar. If the call runs long or a colleague goes home sick, the handoff may have to move. Whoever is waiting for the file needs to hear about that while there is still time to adjust.

Start with the hours you can actually spend. Give the work a priority order and set aside a short review halfway through the week. Decide in advance which tasks can move if a day disappears.

Calculate the hours you can actually use

A week has a nominal size, and almost none of it is available. Take the hours between the start and end of your working day, subtract the recurring meetings that already occupy the calendar, subtract the handling time for messages, invoices and status updates, and subtract any day or half day you will not be at your desk. What remains is the budget the plan has to fit inside.

Stanford's time blocking guide advises students to allow extra time for tasks and aim for at least fifteen hours of blank space in their weekly calendars. For a work schedule, set aside a buffer that fits the interruptions you usually get.

A worked example for one person:

Line Hours
Nominal week, five days at eight hours 40
Recurring meetings already on the calendar 6
Message and status triage across the four working days 5
One day of leave 8
Net hours available 21
Buffer held for overruns and new requests 5
Hours the plan may claim 16

The budget leaves sixteen hours for planned work. Check whether those hours exist in usable blocks. If the calendar shows only four hours for tasks that need uninterrupted attention, narrow the work or talk to whoever owns the deadlines.

Give each task a finish line

Hours are only half of a plan. The other half is knowing when a block can end. "Work on the pricing sheet" can absorb any amount of time and still look unfinished. "Fill columns B to E for the three new plans and send the file to the account owner" has a visible end.

Doist's guide to time blocking recommends assigning each block a specific task or group of tasks. It also warns that people often underestimate how long work will take. Put the finish line in the calendar entry so you can see whether the estimate held when the block ends.

Keep the wording short enough to read in a calendar pop-up. A block that needs a paragraph of explanation needs its own note, with the calendar entry pointing to it.

Sort the week into three tiers

Tier A holds the work that must ship this week because someone downstream is waiting: the file a colleague needs before their own deadline, the reply a client is blocked on, the report that feeds a Monday meeting. Tier A should fit inside roughly half of the hours the plan may claim. That sounds wasteful until a day disappears, at which point the remaining half is what keeps Tier A intact.

Tier B holds work that matters but can move a week without breaking anything. Tier C holds work that is genuinely optional this week: reading, cleanup, the tidy-up that feels productive on a quiet Friday.

Fill the calendar Tier A first, then B, then C, and leave the buffer rows empty. On a normal week Tier C gets done and the week feels generous. On a disrupted week Tier C is the first thing to go, and nobody has to renegotiate anything to make that happen.

Decide the fallback before you need it

Write one sentence at the top of the plan: if the week loses a day, which two items move? Do this on Monday, while the trade-offs are cheap to think about. A plan with a written fallback needs no meeting on Thursday morning to decide what to abandon, and the person who asked for the dropped item hears about it early.

The same logic applies to a lost morning rather than a lost day. A single meeting that overruns by ninety minutes rarely destroys a week, but it can destroy the one block a task was assigned to. Two rules help: never schedule a task in exactly one block if it can be split, and never let a displaced task silently consume the buffer. Move it to a named later block or drop it to a lower tier.

Recheck the plan at the midpoint

Put a fifteen-minute review on the calendar for the middle of the week, before the second half fills up. Read the calendar, not the task list, because the calendar shows what the week actually became. Three questions are enough.

First, how many planned hours remain and how many tasks are still open? If the open work needs more hours than remain, the plan is already broken and no amount of focus will fix it. Second, did any estimate miss by more than half? A task planned for one hour that has taken three is information about the estimate, not about the person. Third, does the buffer still exist? If earlier overruns have eaten it, the second half of the week has no shock absorber.

The review produces exactly one kind of change: items move between tiers or off the week. Adding work at the midpoint because the calendar looks empty is how the original plan got into trouble.

Keep a short record of estimate error

Estimates improve only if the misses are written down. A three-column log is enough: what the block was, hours planned, hours used. Fill it at the end of the block, not at the end of the week, while the memory is fresh.

After three or four weeks, look for patterns by task type rather than by individual task. Writing may consistently take twice the planned time. Reviewing someone else's document may consistently take less. Those are the adjustments worth making, because they change future plans rather than explaining past ones.

Treat a persistent gap as a planning signal. If every writing block runs long, the weekly budget is overstated even if every task was legitimate. Renting the gap by working later is the option that quietly turns a forty-hour plan into a fifty-hour one.

Make the plan readable by someone else

A weekly plan that only its author can interpret cannot be handed over, and handovers happen at the worst times. Keep the plan in one place, with a line at the top naming the week, the owner and the hours claimed. Put the tier next to each item so a reader can see what is protected.

When a colleague takes over the week, they need three things: the calendar with blocks and finish lines, the tier labels, and the written fallback. That is enough for them to keep the week running without guessing which items matter. The one-hour handoff checklist covers the rest of the transfer.

When commitments exceed the available hours

If you have sixteen usable hours and the commitments need thirty, raise the fourteen-hour gap on Monday. Agree which deadline can move, whether someone else can take part of the work, or what can be cut from the deliverable. Update the plan and let anyone waiting on the work know what changed.

Sources