A weekly review updates your commitments before you choose next week's work: check incoming information, projects, dependencies and calendar constraints. Finish with clear next actions, explicit deferrals and a feasible starting point. Reviewing a commitment does not mean completing it or scheduling every task.
Friday's unfinished list is not Monday's plan
A useful weekly review changes decisions about your work, rather than copying every unfinished task into another week.
You close a client call on Friday and notice three tasks still waiting. One needs approval and another no longer matters. The third has no clear starting point.
Moving all three to Monday preserves the list without resolving any of those problems. Next week's meetings and personal commitments already occupy part of the calendar. The copied list ignores that capacity.
A review gives each commitment a current meaning. You identify what can move, what depends on someone else and what deserves a conversation. That information comes before choosing new time blocks.
What is a weekly review?
A weekly review is a recurring check of your commitments, project information and next actions, followed by deliberate choices.
David Allen's GTD Weekly Review checklist separates clearing collected material, bringing commitments up to date and considering possibilities. It includes calendars, projects and items awaiting a response. The original checklist is linked below.
This article offers a shorter decision process for independent work. It is an adaptation, not the complete GTD checklist. Its examples and stopping rules are practical suggestions, not a scientifically validated programme.
Daily shutdown checks what remains open before you leave. Weekly planning assigns time to selected work. The weekly review checks whether the information behind those choices still reflects reality.
Prepare a review you can actually finish
Gather the places where commitments arrive, choose a manageable review window and define the decisions you need before stopping.
Open your calendar, active projects and incoming notes or messages. Include the personal commitments that affect availability. Keep reference material nearby, without turning preparation into a complete archive cleanup.
Choose a time when you can make decisions without regularly interrupting yourself. Friday afternoon and Sunday evening are options, not requirements. A recurring appointment helps only if it fits your working arrangements.
Start with a review window you can protect, then adjust it after observing your workload. No single duration suits every project portfolio. An inherited backlog may need a separate cleanup session.
Write a stopping rule: urgent commitments checked, active projects understood and the next starting action identified. Record any unreviewed area explicitly. A partial review should not create the impression that everything has been checked.
A weekly review checklist in six decisions
Capture loose commitments, check changes, clarify active projects, identify dependencies, compare capacity and choose what to defer.
Use the questions below as prompts. Keep a brief record of decisions that change scope, timing or responsibility. Completing the underlying work belongs in a separate work session.
1. What have I promised without recording it?
Look for commitments in recent conversations, notes and messages. Write the actual request, its source and any agreed date. An interesting idea can remain a possibility; it does not automatically become an active commitment.
2. What changed since the last review?
Check recent appointments for follow-up and upcoming commitments for preparation. Record a changed requirement beside its source. Keep contractual deadlines distinct from the dates you hoped to work on a task.
3. What moves each active project forward?
For each active project, state the next observable action and what it is meant to establish. If the goal is unclear, clarify it. If no work is currently justified, consider pausing the project rather than inventing another task.
4. What depends on someone or something else?
Record the missing input, who can provide it and when you will check again. A task blocked by approval needs a follow-up decision. Giving it a new work date does not make that approval arrive.
5. What can fit the week I actually have?
Compare candidate actions with existing appointments, preparation, transitions and personal limits. Select feasible starting work. If you need a longer uninterrupted session, verify that such a session exists before promising the result.
6. What am I deferring, changing or dropping?
Name the work that will remain outside next week's plan. Note the reason and any condition for reconsidering it. Confirm, reduce or renegotiate expected deliveries with the people affected; a private calendar change does not update their expectations.
Example: a consultant reviews three open projects
A review can produce fewer active commitments while preserving the information needed to resume the others.
Consider Maya, a fictional independent consultant. Her Friday list contains a client proposal, a website refresh and a workshop. She initially intends to carry all three into Monday.
The proposal needs a budget decision from the client. Maya records a follow-up for Monday and keeps the relevant call note attached. She does not reserve drafting time that assumes an answer has already arrived.
The workshop happens on Wednesday. After meetings, preparation and personal commitments, she identifies a suitable work session on Tuesday. She chooses one concrete action: test the exercise instructions against the participant brief.
The website refresh has no external deadline and competes with workshop preparation. Maya records why she is pausing it until after delivery. She keeps the draft and records its next action, instead of repeatedly moving an overdue task.
Her review ends with a client follow-up, a workshop session and an explicit website deferral. These are decisions in a fictional example. They are not a customer result or a claim about how much time the method saves.
Keep a short decision record, not a performance scorecard
Record what changed, the next action, unresolved dependencies and what you deliberately left outside the plan.
A useful review note explains the choices your task list cannot show alone. It can preserve why a project paused or why a delivery needs renegotiation. Next week's review can then test that reasoning against new information.
Counting completed tasks alone treats a trivial reply and a difficult project decision as equivalent. Use an indicator only when it informs a choice. A deliverable accepted, an unresolved approval or a recurring estimate gap may deserve closer attention.
Keep observations separate from judgments about yourself. Repeated postponement might reflect unclear scope, a dependency or more commitments than available time. Identify the constraint before prescribing greater discipline.
- Changed: what new information affects a commitment?
- Next: what specific action is ready, with its context available?
- Waiting: what input is missing, and when will I check it?
- Deferred: what stays outside the plan, and under what condition might it return?
- Capacity: what limit or appointment shapes the next week?
When time is short, make the review explicitly partial
Check immediate commitments and blockers first, record what remains unchecked and schedule a separate review of that remainder.
If a full review cannot happen, start with upcoming obligations and the actions needed to prepare them. Confirm anything whose delay affects someone else. Choose a feasible next action rather than rebuilding the entire backlog.
Write down the areas you skipped. A missed project review is different from a conscious decision to pause that project. Reserve another opportunity to inspect the remainder when you can give it attention.
Avoid using the review as a hidden execution session. If drafting a response or fixing a document absorbs the available window, record that work separately. Return to the remaining decisions before calling the review complete.
What planning research supports, and what it does not
Research on specific plans offers a possible explanation for reduced interference from unfinished goals, not proof of this review protocol.
In their 2011 paper, E. J. Masicampo and Roy F. Baumeister studied cognitive effects of unfinished goals. Their experiments found that making specific plans could remove measured interference effects in the studied tasks.
The published abstract discusses intrusive thoughts, word accessibility and performance on unrelated tasks. It does not test a weekly review checklist, independent consulting or Equilibrition. It establishes no ideal review duration or universal productivity gain.
The modest practical implication is to clarify what happens next instead of preserving an ambiguous reminder. Whether that helps your work remains something to observe. A review is not treatment for persistent distress or exhaustion.
A review cannot solve an impossible workload
When commitments consistently exceed capacity, change the commitments, scope or support available rather than extending the checklist.
A reactive role may require availability rather than a detailed weekly schedule. Keep known commitments visible and revisit the plan when new information arrives. The review should support judgment without pretending the week is predictable.
If every project remains urgent after review, compare the real consequences and agreements. Clarify competing expectations with the people affected. Moving dates privately does not renegotiate a delivery or create additional capacity.
If maintaining the system becomes a project itself, remove unnecessary categories and measurements. Retain the information that changes a decision. You can review a small set of commitments without scoring every area of life.
Keep the decisions connected in Equilibrition
Use linked Projects, Notes, Tasks and the Calendar to preserve why work changed and where the next action belongs.
Keep a project's objective and useful decisions with its supporting Notes and Resources. Describe the next Task so you can start without reconstructing the conversation. Check its dependencies before giving it a calendar slot.
Use the Calendar to compare selected actions with your available time. Revisit a Task's timing when the plan changes. Keep the reason for a deferral in the connected context so that a moved block remains understandable.
The review remains a decision process you carry out. It does not require a dedicated dashboard or an agent that resolves every dependency. The Method explains the wider workflow; this checklist supplies the detailed questions.
Finish with one clear starting point and honest boundaries
Before ending your weekly review, identify the next ready action, important follow-ups and work you are not committing to.
Try the checklist on your current active projects. Keep a short note of changed assumptions and decisions. At the next review, check whether those choices still hold.
A useful result is a week you can begin with the context already available. The backlog can remain unfinished. What matters is knowing which commitments are current, which need action and which remain outside your plan.