The GTD review cycle is the mechanism that keeps David Allen’s Getting Things Done framework functional over time. Capture and processing get your commitments out of your head. The review cycle is what keeps them organised, acted on, and current.
Without regular reviews, GTD collapses. Lists go stale, inboxes refill, and the system becomes another source of stress rather than a source of clarity. Allen describes the weekly review as “the critical success factor” for the entire methodology — and that description extends to the whole review cycle.
The cycle has three distinct levels, each operating on a different time horizon. Understanding what each one does — and why all three are necessary — is the piece most people miss.
The daily review (5–10 minutes)
The daily review is not a planning session. It is a brief orientation at the start of each working day — or the end of the previous one — to arrive at your first task without friction.
Allen’s own practice is a quick check of the day’s calendar, any time-sensitive commitments, and one pass over the next actions list. The goal is not to re-process everything. It is to start with clarity rather than guesswork.
For most business owners, the daily review covers:
- The day’s fixed calendar events and deadlines
- Today’s folder in the tickler file, if you use one
- The two or three next actions you plan to clear before the day opens up
This is not the moment to rethink your project list or reorder your priorities. Those belong in the weekly review. The daily review is the five to ten minutes that keeps you oriented rather than reactive.
The weekly review (45–60 minutes)
The weekly review is the engine of the GTD system. It is the only occasion in GTD where you look across everything — projects, next actions, waiting-for items, someday/maybe — and confirm that nothing is falling through the gaps.
The standard GTD weekly review moves through six steps:
- Get clear — Process every inbox (email, physical, digital notes) to empty.
- Get current on projects — Review every project and confirm it has at least one next action. Flag anything stalled.
- Review the calendar — Look at the past week for anything that generated a commitment, and two to four weeks ahead for anything that needs preparation now.
- Review next actions — Check each context list. Remove completed items, update anything overdue.
- Review waiting for — Follow up on anything outstanding from others.
- Review someday/maybe — Is anything ready to move from aspirational to active?
Done properly, the weekly review takes 45 to 60 minutes. Most people rush it or skip it and then wonder why their system does not feel reliable. The reliability of GTD is entirely downstream of the weekly review — if that step is inconsistent, the whole system becomes unpredictable.
The GTD weekly review has its own detailed walkthrough on this site.
The quarterly and annual review
Allen describes a deeper review at the level of areas of responsibility, goals, and life direction. In his altitude model, this is horizons three, four, and five — the territory above individual projects and next actions, where you examine whether you are running the right projects at all.
For a business owner, a quarterly review typically covers:
- Each area of responsibility: is it getting attention proportional to its importance?
- Active projects: which should be completed, paused, or closed?
- Goals and targets: are they still the right ones, and are you on track?
- Someday/maybe: is anything ready to come off the list permanently?
This is where GTD intersects with higher-altitude planning. The weekly review asks whether everything is accounted for. The quarterly review asks whether you are pursuing the right priorities in the first place.
Why all three review levels are necessary
The three review levels exist because they operate on different information and ask different questions.
The daily review asks: what is immediately in front of me today?
The weekly review asks: is the whole system current and complete?
The quarterly review asks: are we working on the right things?
Skipping the daily review means starting each day reactive rather than intentional. Skipping the weekly review means lists accumulate stale entries and projects go without a clear next action. Skipping the quarterly review means executing efficiently on the wrong priorities.
Business owners running three to five concurrent projects — clients, team, personal, finances — tend to find a natural weekly rhythm but let the daily and quarterly reviews drift. The daily review is recoverable once there is a consistent trigger for it. The quarterly review is the one most consistently neglected, and the one whose absence is hardest to diagnose from inside the system.
Running the review cycle in the NP System
The NP System builds on GTD’s structure and adds a weekly planning layer — the Rocks and MITs method — that makes the review cycle practical for owner-operators running multiple projects at once.
In the NP System, the weekly review happens at the same time each week and generates the week’s three to five highest-priority tasks (the Rocks). These are not selected from the full next-actions list at random. They are chosen by scanning active projects and identifying the single most important advance each project needs that week.
The daily review in the NP System is deliberately light. Open the task board, confirm the day’s Rocks are still the right ones, check the calendar. Five minutes at most. The calendar and the Rocks together tell you what the day needs without reopening every project from scratch.
The quarterly review in the NP System is where areas of focus get interrogated: which client engagements, projects, or initiatives are creating the most leverage — and which should come off the plate to free up capacity for what matters more?
If you want to build this structure into your working week, the free NP System course walks through how Capture, Process, Plan, and Do work together across all three time horizons. Or take the productivity quiz to find out where your current system is creating the most friction.
