The Weekly Review: David Allen's Most Underrated GTD Habit (And the Science Behind Why It Works)

There's a specific mental state that most knowledge workers know: lying in bed Sunday night, half-thinking about the work week ahead. Not planning it, exactly — just anxiously cycling through things you might have forgotten, things you need to do, things you're not sure about.

That state has a name in the research literature. Masicampo and Baumeister (2011) documented it as the Zeigarnik effect in action: unfinished tasks generate intrusive thoughts that interrupt unrelated thinking, including rest and sleep.

The weekly review is, at its core, a protocol for ending that state — not by finishing everything, but by converting anxious background monitoring into concrete plans that your brain can stop actively tracking.

The Problem the Weekly Review Solves

David Allen developed GTD (Getting Things Done) over years of observing how knowledge workers lose track of commitments and accumulate cognitive overhead. The weekly review — a 1-2 hour end-of-week protocol — is the mechanism that prevents that accumulation from compounding week over week.

Without a regular review:

• Tasks captured during the week pile up without processing
• Commitments made in meetings don't make it into any system
• Projects drift without updated next actions
• The system you have stops reflecting reality, so you stop trusting it
• You default to managing by memory and anxiety rather than by plan

The weekly review prevents all of this. Not because it eliminates work, but because it closes the open loops — converts every unprocessed item into either a committed next action, a someday/maybe, or a deliberate decision to delete.

The Masicampo & Baumeister Research

The 2011 paper by Masicampo and Baumeister directly tested the Zeigarnik effect in controlled conditions.

In one experiment, participants were asked to think about an important unfinished task, then had their thinking tested on an unrelated task. As expected, thoughts about the unfinished task intruded on the unrelated thinking.

The key finding: when participants were asked to make a concrete plan for the unfinished task — not complete it, just write down specifically when and how they would address it — the intrusive thoughts stopped. The unfinished task no longer competed for cognitive resources.

The plan functioned as psychological closure. The brain's "monitoring task" process — the background loop that keeps checking whether the open item has been addressed — was satisfied by the presence of a concrete forward plan.

This is exactly the mechanism the weekly review exploits. You're not finishing everything. You're converting open loops into plans, so the brain can stop monitoring them.

The Structure of a Useful Weekly Review

Allen's GTD weekly review has several steps. The most cognitively valuable:

Capture sweep: Go through every inbox, notebook, desk, bag, and digital capture point. Get every unprocessed item into a single inbox for processing. Nothing should remain in "pending thought" — it all becomes a concrete item with a concrete decision.

Process to zero: For every item, make one of five decisions: do it (if under 2 minutes), delegate it, defer it to a specific date, file it as reference, or delete it. The goal is an empty inbox and every open commitment represented somewhere in the system.

Review projects: For every active project, confirm there's a clear next action in the system. A project without a next action is an open loop — the review closes it by adding the action.

Review the coming week: Block time for the priorities of the coming week in your calendar. Not just meetings — the deep work sessions for the work that actually matters.

Mind sweep: At the end, a 10-minute written capture of anything still floating — things you haven't thought of yet, vague anxieties, background concerns. Get them on paper where the brain can stop monitoring them.

Combining the Weekly Review With the Fresh Start Effect

Milkman's fresh start research found that temporal landmarks — new weeks, months, years — create genuine motivational boosts by partitioning time into psychological accounting periods. Monday, specifically, shows consistent spikes in goal-directed behavior.

A Sunday evening or Monday morning weekly review combines two effects:

• The Masicampo/Baumeister mechanism: clearing open loops and creating plans that free working memory
• The fresh start effect: using the temporal landmark of the new week to recalibrate priorities and generate genuine forward momentum

The combination is more powerful than either alone. The fresh start provides the motivation to engage with the review. The review provides the structural clarity that gives the motivation somewhere productive to go.

Making the Review Actually Happen

The weekly review is the GTD habit that most people skip most often. It requires protected time, doesn't produce immediate visible output, and the cost of skipping it doesn't appear until the following week.

The most reliable implementation:

• Same time every week: Friday afternoon (capturing the week before weekend) or Sunday evening (preparing the week ahead). Both work; consistency matters more than timing.
• Protected block in the calendar: Treated as an appointment that doesn't get moved. A standing 90-minute block works for most people.
• Ritual signal: Start the review the same way each time — a specific cup of coffee, a specific playlist, the same physical setup. The ritual activates the reflective mental state the review requires.
• Minimum viable review: When time is genuinely short, a 20-minute version that covers only capture, project next actions, and week preview is better than skipping. The full review when possible; the minimum when necessary.

The Bottom Line

The weekly review is not a productivity exercise — it's a cognitive hygiene practice. Masicampo and Baumeister's research shows that unfinished tasks with no concrete plan generate persistent intrusive thoughts that occupy working memory and degrade performance on unrelated tasks. The weekly review systematically converts open loops into plans, freeing the mental resources those loops were consuming.

Combined with the fresh start effect of the new week, a Sunday/Monday review creates both cognitive clarity and motivational momentum heading into the workweek.

Frequently Asked Questions

How long should a weekly review take?

Allen estimates 1-2 hours for a complete review. For people with well-maintained systems, 45-60 minutes is achievable. The time investment pays for itself in reduced anxiety, fewer dropped commitments, and better-planned weeks. The minimum viable version (20-30 minutes) works as a maintenance review when the system is already current.

What if I miss a week?

A missed weekly review is like missed exercise — one missed session doesn't collapse the practice, but it's harder to return after two or three misses because the backlog grows. The recovery protocol: do a longer, more thorough review to process the accumulated backlog, then re-establish the weekly cadence. One miss is noise; a pattern of misses requires structural intervention.

Is the weekly review the same as planning?

Planning is a component, but not the whole thing. The review includes capture, processing, and clearing — it's as much about the past week as about the coming one. Pure planning (what am I doing next week?) without the capture and processing steps leaves the open loops from the previous week intact.

How does the weekly review interact with daily planning?

The weekly review sets the context; daily planning operates within it. A good weekly review means each day's planning starts from a clear, current picture of priorities and commitments, rather than from a vague anxiety about what might have been missed. The daily planning takes 10-15 minutes when the weekly context is clear; it can expand indefinitely when it isn't.