A Weekly Planning System That Leaves Room for Real Work

What makes a weekly planning system useful?

A weekly planning system connects the work you have agreed to do with the time and decisions available to do it. Review what is open, choose this week's proposed outcomes, place commitments in the calendar, and revise the plan when conditions change. Keep a separate place for new requests. If commitments cannot fit agreed working hours, raise the conflict rather than silently extending the week.

The distinction is between a list of wishes and a record of choices. A long list may be useful for remembering possibilities. A weekly plan should also show what you have accepted, what you are waiting for, and what you have deliberately left out.

This guide offers an original planning method for ordinary administrative work, with a fictional worked example. It is not a tested productivity program. Adapt it to your role, authority and workplace arrangements; required operational procedures remain separate.

What belongs in the system?

Use four connected records rather than four competing lists:

These are our editorial labels, not an official method or a requirement to buy software. They can live on paper or in an approved digital system. If your team already has a task record, use that record rather than creating a private competing version.

Our end-of-day shutdown routine deals with the daily handoff. The weekly page makes the broader choice about which work belongs in the coming week.

How should you review before planning?

The official GTD Weekly Review includes reviewing action lists, past and upcoming calendars, waiting items and projects. Its review is broader than choosing tomorrow's first task. We borrow that distinction between reviewing the situation and deciding what to schedule; the system here is our own, not a reproduction of the GTD checklist.

For this article's worksheet, the review produces three decisions: retain a commitment, change it through the appropriate agreement, or remove an obsolete item. Do not carry a task forward solely because it occupied the same line last week.

Write the reason for a change where another person depends on it. "Still waiting for the source file" is different from "No longer needed." One needs a dependency decision; the other may need confirmation that the work can stop.

Finish the review with a short list of unresolved questions. You can plan around a known uncertainty without pretending it has been resolved.

How much time is actually available?

Atlassian's capacity-planning play asks contributors to list their typical weekly activities and estimated hours. Its examples include administrative work, recurring meetings and incident response. That prevents a project plan from treating all working time as project time.

Use a recent ordinary week as a starting point, then account for this week's known differences. Keep estimates labeled as estimates. Do not describe an unmeasured allowance as an average or a guaranteed completion time.

The worked example below is ours. Its numbers illustrate subtraction and trade-offs, not recommended working hours, break lengths, workload percentages or a universal reserve.

What does a complete weekly example look like?

Imagine an administrative coordinator with 30 working hours available across five days for this exercise. The figure already excludes nonworking time. The coordinator has agreed appointments, recurring responsibilities and several proposed project outcomes.

First, the coordinator records the following fictional allocations:

The calculation is 30 - 6 - 8 - 1 - 3 = 12 hours. The three-hour allowance is an assumption in this example, not evidence that three hours is sufficient for any real job.

Next, compare the proposed project work with those 12 hours:

All three outcomes together would require 5 + 4 + 5 = 14 hours, leaving a two-hour mismatch. The coordinator does not solve it by changing the estimate to fit the page. After discussing timing with the responsible person, the archive-index work moves to a later planning period.

The selected project work now totals nine hours. Twelve available minus nine selected leaves three hours still unassigned within the project allocation. That is separate from the earlier three-hour incoming-work allowance. Neither amount is a promise to accept any request.

This example has a deliberately visible gap. A plan does not become more honest because every available cell contains a task.

How should the calendar reflect that decision?

For the fictional nine-hour selection, a possible arrangement is:

• Monday: two hours on the handout.
• Tuesday: two hours on the contact list.
• Wednesday: two hours on the handout.
• Thursday: two hours on the contact list.
• Friday: one hour on the handout.

The handout receives 2 + 2 + 1 = 5 hours and the contact list 2 + 2 = 4 hours. The arrangement must also fit around the appointments and recurring work already counted. It is an illustration, not a timetable readers should copy.

Before accepting a block, ask whether the work is ready for that period. If the approved contact source will not arrive until Wednesday, Tuesday's proposed block is premature. Move it, choose ready work, or raise the dependency. Do not count time waiting for a file as completed checking.

Name the intended output inside each block. "Handout: draft the explanation for review" distinguishes drafting from final approval. Where another person's decision is needed, show that separately; scheduling your own effort does not book their availability.

What changes when a new request arrives?

Suppose a newly agreed two-hour task arrives on Wednesday in the fictional example. The coordinator checks whether it fits the unassigned project time and whether the required materials are ready. If it fits, record its acceptance and leave one of those three hours unassigned.

If it instead needs four hours, the unassigned three hours cannot cover it. The planning conversation must address the extra hour, another commitment's timing, a smaller acceptable outcome, or a different authorized owner. Do not quietly borrow from protected nonworking time.

Use a change note such as:

Original plan: handout and contact-list check. New decision: accept the two-hour request using previously unassigned project time. Remaining project allocation: one hour unassigned. Archive index remains deferred under the earlier agreement.

That is an invented example, not a message to send unchanged. Include the actual decision-maker and communication route in your workplace. An entry in your notebook does not prove a colleague received the change.

Should the week be tightly scheduled or loosely planned?

Choose how much detail to assign to the calendar based on how your work arrives. Our practical starting point is to reserve definite times for commitments that require them and leave movable work visibly movable.

For a role with predictable appointments, a few named work periods may make conflicts easy to see. For a role handling incoming requests, a sequence of ready tasks within an agreed service arrangement may be more useful than assigning every task an exact start time. Neither approach overrides duties to remain available.

You can also mix them. In the fictional week, the handout's review preparation might need a protected period, while the contact-list checks can occupy suitable openings. Mark that difference so an interruption does not automatically displace the wrong thing.

A calendar full of tentative work should not look identical to a calendar full of fixed appointments. Use labels you understand and your team accepts; elaborate color coding is optional.

What is the minimum plan for a disrupted week?

Keep the information required for decisions, even if you stop maintaining the decorative parts of the system. Our suggested minimum is a single page showing:

• The commitments that still apply.
• The currently agreed order of work.
• Any input or approval needed before work can proceed.
• The person who can resolve a conflict.
• The next opportunity to reconsider the plan.

This is not permission to omit required records. It is a way to simplify personal planning while preserving responsibilities.

If you missed the usual planning session, start from the present state rather than reconstructing a perfect account of every previous day. The unproductive-week recovery guide covers that separate restart task. Once current commitments are visible, return to the weekly system at a suitable point.

For recurring overload, the UK Health and Safety Executive's Management Standards on demands calls for achievable demands in relation to agreed working hours and systems that respond to individual concerns. Raise the mismatch through appropriate workplace channels. A better worksheet cannot create extra capacity or replace necessary support.

How do you know what to change next week?

At the next review, examine decisions rather than awarding the week a productivity grade. In the fictional example, useful observations would be specific: the contact source arrived late, the handout needed another review, or incoming work used more time than allowed.

Keep estimates and actual observations separate. If the handout took six hours rather than the proposed five, record the one-hour difference and what contributed to it. Do not describe one occurrence as a permanent rule about every handout.

Then change the relevant part of the system. A late input may need an earlier confirmation point. An uncertain assignment may need a smaller first-stage commitment. Repeatedly moving an unchanged task is a prompt to review its priority or agreement, not to add another reminder automatically.

Keep the daily close short enough to feed this review without duplicating it. Our end-of-day procedures guide covers required handovers and exception routes; those remain intact. More methods sit in Work Systems, but you do not need every method at once.

A usable weekly plan leaves a reader able to answer three questions: what has been agreed, what remains undecided, and what happens when the week changes. The page can be plain. The decisions should be clear.

Sources

• Getting Things Done: the GTD Weekly Review
• Atlassian Team Playbook: capacity planning
• HSE: Management Standards, demands