# How to plan a week with time blocks that still leave room for real work

https://techy.eus/en/resources/plan-a-week-with-time-blocks
Updated: 2026-09-20

Time blocking is not about assigning a perfect task to every minute. It is a way to protect the kind of work that disappears when every open hour becomes available to everyone else.

Techy · Editable offline copy. Examples are illustrative, not customer results. Review the guide's limitations before applying it.

## Block categories before individual tasks

Reserve broad blocks for focused work, meetings, admin and recovery before filling them with exact tasks. Categories survive a changing week better than a calendar that assumes every estimate will be correct.

Start with fewer blocks than you think you need. A plan with no buffer only works in a week with no surprises.

## Leave visible space for the unexpected

Keep part of each day uncommitted for decisions, messages and urgent work. If that space is used, move lower-priority work instead of extending every day indefinitely.

Review the calendar at the end of the day and adjust the next block, rather than treating the original plan as a test you failed.

- Focus blocks for demanding work.
- Meeting windows instead of scattered calls.
- A short admin block.
- A buffer for unplanned work.

## Protect the next action

At the end of a block, leave a note describing the next concrete action. Restarting becomes much easier when you do not need to reconstruct your thinking from scratch.

## Worked example: plan capacity before assigning tasks

Suppose a fictional Tuesday has six usable hours after fixed commitments. A two-hour draft, one-hour review and two-hour implementation leave one hour unassigned. Putting another two-hour task into that day does not create capacity; it hides a trade-off. Mark it as optional or move something explicitly.

When an interruption consumes the spare hour, revise the remaining blocks instead of shifting every commitment later without checking the finish time. Record planned and actual time for a few repetitions to improve estimates, not to judge yourself. Separate a dependency from a duration: a review may take only 20 minutes but cannot happen until another person responds. End the day by moving unfinished work deliberately and writing the next concrete action, so tomorrow does not begin with reconstructing context.

## Replan a day when a dependency misses its slot

Fictional day with six usable working hours after breaks and fixed commitments. A two-hour implementation block depends on approved copy due at noon. Approval does not arrive. Moving the same block later without checking capacity creates an invisible commitment.

There are two newly available hours, but the blocked deliverable is still owed. Choose independent work that fits, record the owner of the missing approval and tell anyone relying on the original delivery date. Do not relabel the implementation block ‘done’ because time was spent checking messages. If approval arrives late, verify a real slot before promising same-day delivery.

Worked example · fictional inputs

| Work | Hours | Dependency | Revised decision |
| --- | --- | --- | --- |
| Draft proposal | 2 | None | Keep |
| Review prototype | 1 | Prototype ready | Keep |
| Implement approved copy | 2 | Approval missing | Move to a named later slot |
| Unplanned work buffer | 1 | None | Use for urgent triage only |

## Test the result and handle the exception

A calendar cannot resolve conflicting priorities on its own. When two urgent tasks exceed capacity, ask the decision owner which commitment changes. Extending every day is not a dependable scheduling rule.

- Committed work plus buffer does not exceed six hours.
- The moved deliverable has a new slot or an explicit unresolved date.
- A restart note identifies the next action and the latest approved input.

## Your working sheet — fill in locally

Situation and date: ____________________

Inputs and where they came from: ____________________

Decision / calculation: ____________________

Expected result: ____________________

Actual check and evidence reference: ____________________

Exception and next action: ____________________

Owner and review date: ____________________

Do not put passwords, patient details or other sensitive data in a shared worksheet. Downloading or checking a box does not verify real-world compliance.