The weekly review is the single highest-leverage habit in any productivity system. GTD users know it as step 4 (Reflect). Bullet Journal users know it as the migration log. Calendar-first systems know it as Sunday planning. The name changes; the function does not. It is the regular maintenance window where commitments get re-aligned, the calendar gets reviewed, projects get assessed, and the week ahead gets a deliberate shape rather than a reactive one. Users who do it weekly outperform users who do not by a wide margin, and most of the difference shows up in projects that actually finish versus projects that stall.
This guide covers a practical 60-minute protocol, the order that works, the common failure modes, and how to maintain the habit when life gets busy.
Why most people skip it
The weekly review is the obvious thing to skip when the calendar is full. It feels like meta-work rather than real work, and the cost of skipping one week appears low. Skip it three weeks in a row and the cost becomes very real: the inbox has 800 items, the project list reflects the world of three weeks ago, and three commitments have quietly slipped past their actual deadlines.
The other reason people skip it is that the review is poorly designed. A 3-hour review feels like punishment after a long week. A vague review with no checklist drifts into procrastination. A review held on Monday morning is too late to prepare for the week it should be preparing for.
The fix is the same for both problems: define a repeatable 60-minute protocol, run it at the same time every week, and refuse to skip it more than once in a row.
The 60-minute protocol
The protocol below assumes a knowledge worker with 3 to 8 active projects, an email inbox, a calendar, and a task list of some kind (paper or digital). Adjust the time allocations to match the volume.
Phase 1: Loose ends (15 minutes)
Walk around the physical desk, look at the email inbox, check the notes app, listen to any voicemails. Get every loose item into a single place. This is the GTD capture step compressed.
The point is to start the review with one inbox to process, not seven.
Phase 2: Process inboxes to zero (15 minutes)
Take each item from the unified inbox and decide:
- Two minutes or less: do it now.
- Reference: file it.
- Someday/maybe: add to the someday list.
- Active commitment: clarify the next action and add it to the right list.
- Project: add to the project list with a clear next action.
- Delete: if it does not require action and is not reference.
By the end of Phase 2, every inbox should be at zero. This is non-negotiable. A review that ends with 40 unprocessed items in the inbox has not done its job.
Phase 3: Calendar review (5 minutes)
Look at the past week’s calendar. Was there a meeting that generated commitments? Capture them. Was there a follow-up that did not happen? Add it to next actions.
Look at the next 14 days. Are there meetings that need preparation? Block prep time. Are there deadlines? Confirm the work is on track. Are there travel days? Make sure the calendar matches reality.
Phase 4: Project list review (15 minutes)
Walk through the full project list. For each project:
- Is it still active? If not, mark it complete or archive it.
- Does it have a clear next action? If not, define one.
- Has it moved this week? If not for two weeks running, ask why.
- Is the deadline still realistic?
Add any new projects that emerged during the week. Move stalled-but-still-valid projects to someday/maybe rather than letting them pollute the active list.
Phase 5: Waiting-for and follow-ups (5 minutes)
Look at the waiting-for list. Is anyone overdue on something they owe? Send a polite nudge now. Move completed items off the list.
Phase 6: Next week planning (5 minutes)
Identify the 3 most important things for the coming week. Block calendar time for the deep work that supports them. Set the intention for the week.
The checklist
The protocol works because it is a checklist, not a vibe. A printable or digital version with 12 to 15 items is enough. Keep it the same every week so the brain stops having to make decisions about what comes next.
Sample checklist items:
- Clear the physical desk
- Process email inbox to zero
- Process notes app inbox to zero
- Process voicemails
- Review past 7 days calendar
- Review next 14 days calendar
- Review project list, confirm next actions
- Review waiting-for list, send follow-ups
- Review someday/maybe list
- Identify top 3 priorities for next week
- Block calendar time for those priorities
- Personal life section: household, family, health
- Close the review with a one-line note
The note at the end (a single sentence: “Good week, finished X, started Y, watch out for Z next week”) is useful for retrospective patterns over months.
Tools
The review itself does not require special tools beyond whatever task system is already in use. A paper checklist printed once and reused weekly is fine. A Notion or Todoist template works too.
For users who prefer voice, recording a 2-minute audio summary at the end of the review captures context that text misses. The recording is rarely re-listened to but the act of speaking it crystallizes the week.
If the calendar and task app feel duplicated, settle the calendar versus task management decision before the next review.
Running the review with a partner
Some couples and business partners do a 30-minute joint review weekly. The format is usually:
- 5 minutes each on what happened this week
- 5 minutes each on what is coming up that affects the other
- 5 minutes on shared commitments (household, finance, family)
- 5 minutes on the joint priorities for the coming week
This works particularly well for two-income households with kids, where dropped commitments have real costs. It does not replace each person’s individual review, but it adds a coordination layer that prevents most scheduling collisions.
When the review breaks down
If three reviews in a row feel like punishment, something is wrong with the design. Common diagnoses:
- Too long. Cut the protocol to 45 minutes by trimming the project list (probably has dead projects) and being stricter about the two-minute rule during the week.
- Wrong time. Friday after a long week may feel exhausting. Move to Sunday evening or Monday morning early.
- Wrong format. Paper checklist for people who do digital all day, or a digital template for people who think on paper. Switch the medium.
- System mismatch. If the underlying task system (GTD, Bullet Journal, Things) does not fit the user’s life, the review reveals that mismatch. The fix is at the system level, not the review level.
The honest framing
A weekly review is the maintenance step that makes any productivity system actually work. The output is not a tidier task list. The output is the trust that the system reflects reality, which lets the rest of the week be spent doing rather than worrying. Sixty minutes once a week is the cheapest possible price for that trust. Users who pay it consistently look more productive than users who do not, because they actually are.
See our /methodology page for our broader productivity testing approach.
Frequently asked questions
How long should a weekly review take?+
Sixty to ninety minutes for most knowledge workers. Less than 30 minutes usually means the review is being rushed and important items get missed. More than two hours usually means too many items are being processed during the review that should have been processed during the week. The sweet spot for someone with 3 to 8 active projects is roughly 60 minutes. Senior managers and people with many direct reports may need 90 to 120 minutes.
When during the week is best to do the weekly review?+
Friday afternoon or Sunday evening, with Friday being slightly preferable for most people. Friday afternoon catches everything from the week while context is still fresh, closes the loop before the weekend, and allows real rest. Sunday evening works for people who prefer to look ahead and feel prepared on Monday morning but tends to spill mental work into the weekend. The wrong answer is Monday morning, because the review should set up the week, not start it half-blind.
What if I miss a weekly review?+
Do a 20-minute mini-review as soon as possible: process inboxes, check the calendar for the next 7 days, scan project list, identify the top 3 priorities. The full review can wait until next Friday. Missing a single week is recoverable. Missing three weeks in a row is a sign that the system needs adjustment, either the review process is too long, the wrong time of week, or the task system has grown beyond what is actually being used. Diagnose the root cause rather than blaming the habit.
Do I need a checklist or can I just review from memory?+
Always use a checklist. The whole point of the weekly review is to catch the items that memory misses, and reviewing from memory defeats that purpose. A simple paper or digital checklist with 10 to 15 items takes 30 seconds to follow and ensures nothing is skipped. The checklist also makes the review faster because there is no decision about what to look at next, only execution of the next step. David Allen's original GTD checklist is a good starting template.
Should the weekly review include personal life or only work?+
Both, but treat them as separate sections within the same review session. Mixing them produces a chaotic list and reduces the quality of attention given to each. A 60-minute review might spend 40 minutes on work (projects, inboxes, calendar, next actions) and 20 minutes on personal life (household, family commitments, health, finances, learning). Some people prefer entirely separate reviews on different days, which also works as long as both happen weekly.
Morgan Davis
Morgan Davis writes for The Tested Hub.