The 20-Minute Weekly Review: A Template for People Who Hate Planning

The original weekly review from David Allen's Getting Things Done (GTD) method is an eleven-step checklist that includes processing every inbox to zero. If you have ever started one late on a Friday and found yourself still sorting email ninety minutes later, you know how it ends: next week it gets skipped, and the week after that it is gone.

This guide gives you a version that fits in twenty minutes and ends with a decision instead of a list. It keeps the four things we judge do the most work (emptying your head, looking at the calendar both ways, checking that every project can move, choosing what matters next) and cuts the rest. You get a copyable sheet with a five-minute minimum for weeks when even twenty feels like too much, a worked example, and variants for students, freelancers, and team leads.

You also get an honest account of the evidence: parts of a weekly review are backed by real studies, but we found no study that tested the twenty-minute format itself.

What Allen's full review asks for, and what this version cuts

Allen's official checklist has eleven steps, which the David Allen Company groups into three phases. Get Clear collects loose papers, gets your "In" tray to zero, and empties your head. Get Current, the longest phase, reviews next-action lists (each project's next physical step, such as "email the client for the brand file"), the past and upcoming calendar, the waiting-for list (things you have asked other people to do), project lists, and relevant checklists. Get Creative reviews the someday/maybe list (ideas you might act on later) and asks for new, bold ideas.

The checklist sets no time limit and calls the review "the critical behavior" for making the system work. Allen suggests early Friday afternoon, because the review surfaces small actions you can finish while people are still at work. On frequency, the official GTD blog quotes Allen: "Any time, any frequency, is better than not at all."

"Process to zero" is where the clock disappears; in our judgment, an inbox backlog absorbs whatever time you give it. The short version triages instead:

This gives something up: a full in-to-zero pass keeps a large backlog from building. Run the long version after a holiday or a chaotic month, and the short one otherwise.

The 20 minutes, block by block

It is fifteen minutes of clearing, looking back and ahead, and measuring, and five of committing to what comes next. Any timer works,.

Set the slot before you need it

Put a recurring event in your calendar, same day and time every week, with the sheet attached. A late-week afternoon is a good default; Sunday evening works if you will keep it. Tie it to something that already happens ("after my last meeting on Friday") so you are not relying on memory.

Allen's own onboarding advice is to put "do weekly review" in your calendar for the next four Fridays, then build a personal checklist of reminders unique to your life. Before the first run, spend ten minutes listing your active projects, meaning anything you want finished that takes more than one step, because Block 3 assumes that list exists. Judge week three against how long habits take to form, not against week one.

Block 1 (5 min): Empty your head and capture dates

Spend two minutes on a brain dump: everything still on your mind, in one place, in no particular order. Tag each line with one letter as you write: C needs a calendar slot, P becomes the next action on a project, W you are waiting on someone, X delete it or leave it for the monthly pass. Tagging takes seconds. Acting on the tags waits: P items feed Block 3, C items get their slots in Block 4, and W items join your waiting list.

Spend three minutes scanning email, chat, notes, paper, and open browser tabs for two things only: items with a date and people waiting on you. Anything needing more than two minutes becomes a calendar slot, not something you do now. If open tabs are the problem, a four-bucket system for browser tab overload covers a separate session for them.

Note: When a block runs out, stop and write what you did not finish on the sheet as "overflow", with its own calendar slot next week. The review never gets longer; the leftovers get a home.

Block 2 (5 min): Check last week's promises and next week's capacity

Spend two minutes on last week. Score it first: how many of its outcomes did you finish, and how long did they take against your estimate? Then scroll back through its calendar, asking of each event: did this create something I promised?

Spend three minutes on the next two weeks (deadlines, travel, anything needing preparation) plus a one-line scan of what you are waiting on from others. Then work out next week's capacity: take your expected working hours, subtract meetings and travel, and write down what is left as unbooked hours. As a rough rule of thumb, not a research finding, only about half of that becomes focused work, so halve it and write the result as usable hours. The halving is meant to absorb email, admin, and interruptions, so do not subtract those separately.

Block 3 (5 min): Count your habits and unstick projects

Count up to three habits as "days done out of the last 14", for example on a paper calendar or in a spreadsheet. A missed day nudges a density number instead of resetting it to zero, the argument made in why streak-based habit trackers get abandoned, which also has starting targets by habit type. Three is a cap so the block fits in five minutes; a habit you no longer want goes under "dropped on purpose" instead of being rescued.

Write a target beside each habit: 10 of 14 is our default for a daily habit, and for one planned fewer than seven days a week, use planned days per week × 2 (three a week is 6 of 14). These bands are heuristics to tune after a month:

• At or above target: leave it alone.
• Between half the target and the target: the habit works but the cue is unreliable. Change when or where it happens.
• Below half the target: the habit is too big. Shrink it before pushing harder, or drop it.

Then answer Allen's project question and write one next action for each stalled project (a P-tagged dump item often supplies it). Finish with one written sentence: what did this week teach me? Writing it is closer to what the reflection study below did than just thinking it.

Block 4 (5 min): Pick up to three outcomes and book them

Choose up to three outcomes for next week. An outcome is a finished state, not a topic: "Revised onboarding flow sent to the client", not "work on onboarding". For each, write the first physical action, when and where you will do it, and an hour estimate: the kind of concrete plan Masicampo and Baumeister's participants wrote for an unfinished goal (see the research section below; this exact layout is ours, not theirs). If the total exceeds the usable hours from Block 2, drop something and record it under "dropped on purpose". Put the first actions, and any C-tagged items, in your calendar.

Warning: Three is a convention, not a research result; we know of no study showing it beats two or four. Use the number your calendar can honestly carry.

If planning feels like a chore, the 5-minute version is the whole method: one finished state, one first action, one time. Add blocks back only when it feels too thin.

The copyable sheet

WEEKLY REVIEW — week of ________          20 minutes, timer on
ONLY 5 MINUTES? Brain dump (2 min), then one outcome + first action +
when/where (3 min). Skip the rest and book the next review.

1. EMPTY YOUR HEAD, CAPTURE DATES (5 min)
[ ] Brain dump, 2 min. Tag each line: C calendar / P next action /
    W waiting / X delete or monthly pass
[ ] Scan inboxes + tabs: capture dates and people waiting on me
Overflow I did not finish: ________

2. CHECK PROMISES AND CAPACITY (5 min)
Last week: finished __ of __ outcomes   est. __h / actual __h
  Why any were missed: ________
Last week's calendar, anything promised? ________
Next 2 weeks: deadlines / travel / prep: ________
Waiting on others: ________
Working h __ - meetings __ - travel __ = unbooked __   Usable (about half): __

3. COUNT HABITS, UNSTICK PROJECTS (5 min)
Habit (max 3)    Done of last 14 / target     Keep / change cue / shrink / drop
________         ____ / ____                  ________
Projects with no next action: ________  -> next action: ________
One thing this week taught me: ________

4. PICK OUTCOMES, BOOK THEM (5 min)
Outcome 1 (done means ________)  first action ________  when/where ________  est. __h
Outcome 2 (done means ________)  first action ________  when/where ________  est. __h
Outcome 3 (done means ________)  first action ________  when/where ________  est. __h
Total estimate: __h  vs  usable hours: __h
Dropped on purpose: ________
[ ] First actions and C items are in the calendar    [ ] Next review is booked
My own reminders: ________

A worked example: one Friday afternoon, twenty minutes

This is a hypothetical with invented numbers. Say you are a freelance product designer finishing the week at 15:40.

Block 1. The brain dump produces seven items: three tagged C, two P, one W, one X. Of 23 unread emails, two have dates (a client review on Tuesday, an invoice due the 15th) and one person is waiting on you. The other 20, plus the three C items, share a 30-minute slot on Monday morning.

Block 2. Last week you finished 2 of 3 outcomes; the third took 7 hours against an estimate of 5. Wednesday's workshop produced a promise to send a recording. Next week has 4.5 hours of meetings and 3 hours of travel. On a 40-hour week, that leaves 40 − 4.5 − 3 = 32.5 unbooked hours. Halved, roughly 16 usable focus hours.

Block 3. "Write for 15 minutes before email" shows 4 of 14 days, below half of its target of 10, so you shrink it to five minutes. "Evening walk" shows 11 of 14, so you leave it. One stalled project gets the next action "email the client for the brand file". Your lesson: feedback arrived in pieces, so you will ask for it in one batch.

Block 4. Your filled-in lines:

1. Revised onboarding flow sent    first: list the three open comments    Mon 09:00, desk   6h
2. Pricing page copy drafted       first: outline the three plans         Tue 09:00, desk   5h
3. September invoices sent         first: open the invoice template       Fri 11:00, desk   1h
Total estimate: 12h  vs  usable: 16h        Dropped on purpose: new logo exploration

That leaves four hours of slack for the recording and for surprises.

Variants for students, freelancers, and team leads

The blocks stay the same; what you scan, how far ahead you look, and what you count change. These are starting points, not tested protocols.

If all of a team lead's outcomes depend on other people, the work only you can do never gets scheduled.

Why weekly reviews die, and the fix for each

What the research supports, and where it stops

We found no study that tests a weekly review. The studies below test its ingredients, and each has limits.

A specific plan quiets an unfinished goal

In 2011, E. J. Masicampo and Roy Baumeister published a series of laboratory experiments in the Journal of Personality and Social Psychology (volume 101, issue 4, pages 667–683). They started from the Zeigarnik effect, the finding that interrupted tasks are remembered better than finished ones, which is often stretched to mean that unfinished goals keep nagging at the mind. Unfulfilled goals produced intrusive thoughts, made goal-related words more accessible, and worsened performance on an unrelated task. When participants made a specific plan for the goal, those effects went away even though the goal was still unfinished.

The limits matter. These were short laboratory tasks, not a to-do list of forty items.

The Zeigarnik claim has also had replication trouble: a 2025 meta-analysis by Romain Ghibellini and Beat Meier found no memory advantage for unfinished tasks, though people do tend to resume interrupted ones. Read together, the two studies counsel caution about the popular claim that every unfinished task stays lodged in memory, and they leave a narrower claim standing: for a goal you care about, a concrete plan seems to help in laboratory tasks. That is why the template ends with first actions and times, not just a list.

Writing down lessons helped call-centre trainees in one working paper

Giada Di Stefano, Francesca Gino, Gary Pisano, and Bradley Staats tested reflection at Wipro, an outsourcing company based in Bangalore, in a technical-support call centre, as summarised by Harvard Business School's Working Knowledge. Groups of trainees were assigned to a control, reflection, or sharing condition. The reflection group spent the last 15 minutes of each training day (days 6 through 16) writing about that day's lessons, while the control group kept working. On the final training test, the reflection group performed 22.8 percent better than the control group; the sharing group, who also spent five minutes explaining their notes to a fellow trainee, performed 25 percent better.

Four cautions. We found only working-paper versions, circulating since 2014 under changing titles, and a 2015 conference abstract, but no journal article. The summary gives no sample size, and conditions went to whole groups of trainees, which makes the headline percentage less certain. A short training course is not a weekly routine, so the "one thing this week taught me" line is a modest borrowing. And Francesca Gino had her Harvard tenure revoked in May 2025 following a research-misconduct review of other papers; she denies the allegations. We know of no retraction of this study, but it is another reason to treat one working paper lightly.

A 2023 version listed by UNC's Kenan Institute (ten experimental studies, 4,340 participants) finds reflection mostly beneficial at the beginning of the learning curve.

Checking progress raises goal attainment

A 2016 meta-analysis in Psychological Bulletin by Benjamin Harkin, Thomas Webb, and colleagues pooled 138 randomised studies (19,951 participants) in which people were prompted to monitor progress toward a goal. The prompts increased how often people monitored and improved goal attainment (d+ = 0.40, 95% confidence interval 0.32 to 0.48), a small-to-moderate effect by the usual conventions.

Effects were larger when progress was physically recorded or reported publicly. The first supports Block 3: write the numbers down rather than trusting your impression of the week. A private review gets none of the public-reporting benefit. Sending your Block 4 outcomes to a colleague, or explaining your one lesson to one as the sharing group did, would be our extrapolation from these results, not a tested weekly-review step.

Where to start this week

1. Book the slot now: same day, same time, recurring, with a cue.
2. Copy the sheet into a note you can open in two clicks, and run it once with a timer.
3. After four weeks, add up the "finished __ of __" line from Block 2. Finishing all three every week suggests under-committing; finishing none or one suggests optimistic estimates or a too-generous usable-hours rule. Compare estimates with actuals and move the half-of-unbooked-hours rule toward what your record shows.

Frequently asked questions

What if next week has almost no unbooked time?

Run the review anyway, but change its job. If usable hours come out at a few hours or fewer, plan one outcome and spend the Block 4 minutes deciding which meeting or commitment to move, shorten, or decline. A review that shows you have no room is working; writing three outcomes regardless only pre-writes next Friday's dropped list.

Paper or an app?

We found no research comparing the two for weekly reviews. The progress-monitoring meta-analysis above supports recording the numbers, in either medium. Use whichever you will open in two clicks.

How is this different from planning my day each morning?

The weekly review chooses outcomes and checks capacity. A daily plan places those outcomes into specific hours. If the weekly part is done well, the daily part shrinks to deciding which outcome gets today's best hours.

What happens to the someday/maybe list and my longer-term goals?

Add a ten-minute monthly pass: go through the someday/maybe list and your longer-term goals, promote anything now active, and delete what no longer interests you. Keeping these moves monthly is what lets the weekly review stay at twenty minutes.

Sources and further reading

• The Weekly Review (two-page checklist, 2016 version) — David Allen Company, 2016. The eleven steps, "the critical behavior" wording, early-Friday timing, and the four-Fridays and personal-checklist advice.
• The GTD Weekly Review — David Allen Company, 2009. The three phases and the "any time, any frequency" quotation.
• Consider it done! Plan making can eliminate the cognitive effects of unfulfilled goals — Masicampo and Baumeister, Journal of Personality and Social Psychology, 2011. Plans and unfulfilled goals.
• Interruption, recall and resumption: a meta-analysis of the Zeigarnik and Ovsiankina effects — Ghibellini and Meier, Humanities and Social Sciences Communications, 2025. Replication status of the Zeigarnik effect.
• Reflecting on Work Improves Job Performance — Harvard Business School Working Knowledge, 2014. The call-centre reflection experiment, including the sharing group.
• Learning by Thinking: How Reflection Can Spur Progress Along the Learning Curve — Kenan Institute at UNC, 2023. Listing of an SSRN paper naming Bradley Staats; ten studies, reflection mostly beneficial early on.
• Does Monitoring Goal Progress Promote Goal Attainment? A Meta-Analysis of the Experimental Evidence — Harkin et al., Psychological Bulletin, 2016. Progress monitoring and goal attainment.
• What to know as Harvard professor Francesca Gino's tenure is revoked amid data fraud investigation — NBC News, 2025. The May 2025 tenure revocation and Gino's denial.