GTD Weekly Review: A Step-by-Step Guide (2026)
The GTD weekly review in 30 to 45 minutes: the clear, current, and creative phases, a working checklist, common failure modes, and how to keep the habit.
A GTD weekly review is a 30 to 45 minute session where you empty every capture point, update every active list, and scan your longer-term lists for what deserves attention next. It is the one habit David Allen treats as non-negotiable, and it is the first habit most practitioners drop. This guide walks the full review step by step, with realistic timing, the failure modes that kill it, and the fixes that keep it alive past week three.
For the method this ritual sits inside, see our playbook on Getting Things Done digital.

What is a GTD weekly review?
The GTD weekly review is the recurring maintenance session at the heart of David Allen's Getting Things Done method. Once a week, you step back from doing and look at the whole system: every inbox empty, every project holding a live next action, every calendar commitment current, and every deferred idea re-examined. Allen describes the review as the critical success factor of GTD, the habit that makes the other four stages hold.
The reason it carries that weight is trust. GTD only works when your brain believes the system will catch everything, and the weekly review is the event that proves the belief. Skip it twice and your head starts holding open loops again, quietly, the way it did before you had a system at all.
How long should a GTD weekly review take?
Thirty to forty-five minutes, once the routine is practiced. The first two or three sessions run 60 to 90 minutes because you are not only reviewing, you are also cleaning up weeks of drift: stale projects, dead next actions, inboxes that never got emptied. That early overhead is normal and it goes away.
If a mature review still takes more than an hour, one of two things is wrong. Either your capture volume has outgrown your lists, in which case the fix is fewer capture points and a tighter project list. Or your checklist is doing filing work that belongs in the daily processing window, in which case the fix is splitting daily triage out of the weekly ritual. The review should be judgment, not filing.
How do I do the clear phase of the weekly review?
Get clear means empty every capture point to zero before you touch a single list. Collect the loose inputs first: papers on the desk, notebook pages from the week, receipts, business cards. Then process every digital inbox: email, voice captures, flagged messages, browser tabs you saved for later. Budget about ten minutes.
Each item goes through the standard GTD processing sequence: clarify what it is, do it now if it takes under two minutes, delegate it if it belongs to someone else, defer it with a written next step, or delete it. If your capture points are the source of the pile, our walkthrough on GTD inbox setup covers how to build capture points that actually get emptied between reviews.
How do I do the current phase of the weekly review?
Get current is the longest phase, about 25 minutes, and it is the one people picture when they say weekly review. You walk four things in order: next actions, calendar, waiting-for, and projects. The order matters because each layer feeds the next.
- Next actions. Read every next action list and mark off what is done. Anything that is done but still open is noise. Anything that is open but actually done is worse, because it quietly teaches you the list lies.
- Calendar. Look back one week and forward two. The backward look surfaces follow-ups you owe people. The forward look surfaces preparation you owe yourself. Capture both.
- Waiting-for. Check everything you delegated. Send nudges where they are due. The waiting-for list is the least-used list in GTD and the highest-leverage one for anyone who works with other humans.
- Projects. Walk every active project and confirm it holds at least one concrete next action, written as a verb. Demote quiet projects to someday maybe. A project with no next action is not a project; it is anxiety with a title.
If you want this phase as a ready-made document, our markdown weekly review template is a plain-text checklist you can copy into any notes app and reuse every week.
What happens in the creative phase of the weekly review?
Get creative takes five minutes and it is the phase most people skip, which is a mistake. You skim the someday maybe list and ask one question: does anything here have energy behind it now? If yes, pull it into active projects and write its first next action. If no, close the list.
Then capture whatever the review surfaced. A good review always generates new items: commitments you noticed while walking the calendar, ideas that appeared while reading a project. Capture them before you close, because the review state of mind produces the best captures of the week. Voice capture works well here; speaking the week's leftover thoughts takes two minutes and lands them in the same inbox you just emptied.
Why do weekly reviews fail?
Weekly reviews fail from vagueness and skipped weeks, almost never from the method itself. The three failure modes we see most often:
- No fixed slot. The review floats on the calendar, so it competes with everything else and loses. Fix: recurring calendar event, same time every week, treated like a meeting with your own commitments.
- No written checklist. Every session starts from memory, which means every session is a small act of willpower. Fix: write the checklist once, reuse it forever.
- The backlog spiral. One skipped week doubles the pile, which makes the next review look painful, which causes another skip. Fix: on return, archive everything older than 30 days into a reference folder and review only what is left. Important items resurface on their own.
How do I keep the weekly review habit past week three?
Week three is where most reviews die, because the novelty is gone and the payoff has not yet compounded. Three things carry the habit through. Fix the slot and defend it. Keep the checklist short enough to finish in 45 minutes on a bad day. And attach the review to something you already enjoy, a good coffee, a quiet room, the end of the workday, so the session has a texture you look forward to.
Tooling helps on the mechanical side. quik.md's AI organize pre-files your captured thoughts into projects before the review starts, so the clear phase shrinks from a filing session to a quick scan of anything the router was unsure about. Everything exports as markdown, so your review checklist and project lists stay portable. The pillar on AI task managers compares how different tools split that mechanical half of the review.
The habit survives when the review is short, fixed, and worth doing. Everything else is decoration.
FAQ
What is a GTD weekly review?
The GTD weekly review is a recurring 30 to 60 minute session where you empty every capture point, bring every active list up to date, and scan your longer-term lists for what to pull forward. David Allen built the method around it: the review is what keeps the whole system trusted, because it is the moment you confirm that nothing has slipped.
How long should a GTD weekly review take?
Thirty to forty-five minutes for most knowledge workers once the routine is practiced. The first few sessions run longer, often 60 to 90 minutes, because you are also cleaning up historical drift. If your review consistently takes more than an hour, your capture volume has outgrown your lists or your checklist is doing filing work that belongs in the daily processing window.
What is on the GTD weekly review checklist?
The core checklist is three blocks. Get clear: collect loose inputs and empty every inbox to zero. Get current: review next actions, past and upcoming calendar, waiting-for list, projects, and any relevant checklists. Get creative: scan someday maybe and capture new ideas the review surfaced. Write your version down once and reuse it; the checklist is what makes the review survivable on a low-energy Friday.
What day is best for the GTD weekly review?
Friday afternoon is the classic slot because the week's captures have landed and the next week is visible. Sunday evening and Monday morning also work. The day matters less than the fixity: the review survives when it occupies the same calendar slot every week, and it dies when it floats.
Why do I keep skipping my weekly review?
Almost always one of three reasons: the review has no fixed time so it competes with everything else, the checklist is vague so each session feels like starting over, or the backlog grew during a skipped week so the next review looks painful. The fix is a fixed slot, a written checklist, and permission to archive stale items instead of processing all of them.
Can AI do my GTD weekly review for me?
AI can cut the mechanical half of the review, not the judgment half. A good AI task manager pre-files your inbox, surfaces stale projects, and summarizes what shipped, which turns a 60-minute review into a 30-minute one. The remaining 30 minutes, deciding what still matters and what to drop, is the part that does not compress, and it is the part the method exists to protect.
Related reads
- Getting Things Done digital: the 2026 playbook
- Markdown weekly review template
- GTD inbox setup: a step-by-step guide
- AI task managers: the pillar guide
References
- What is GTD?, Getting Things Done, David Allen's official site.
- Getting Things Done, David Allen, 2001, revised 2015.
- Inbox Zero series, Merlin Mann, 43 Folders, 2006.
Keep reading
Workflows8 minThe Two-Minute Rule in GTD: Why It Works and When It Fails
The two-minute rule is GTD's simplest instruction and its most misunderstood one. This explainer covers where David Allen's rule came from, why the math behind it holds, the mornings where it quietly wrecks your priorities, and the voice-capture twist that makes deferring nearly as cheap as doing.
Workflows10 minGetting Things Done Digital: A 2026 GTD Playbook
GTD was designed for paper in 2001 and translated poorly to the first generation of task apps. In 2026, AI task managers close the gap. This guide covers the five-step GTD workflow, the digital traps to avoid, and the tools that actually respect the method.
Workflows8 minGTD for Developers: A Practical Guide (2026)
GTD maps cleanly onto a developer workflow once you stop trying to run your life out of GitHub issues. This guide covers the issue-tracker boundary, markdown files as projects, coding agents as delegates on your waiting-for list, and a weekly review that measures shipped work instead of started work.