Learn

The weekly review: a complete guide

What is a weekly review?

A weekly review is a recurring practice of stepping back from the daily work to look at the bigger picture: what's on your plate, what's been neglected, what matters most, and what next week should look like.

The concept was popularised by David Allen in Getting Things Done, where he called the weekly review "the critical success factor" of the whole system. The idea is that no matter how good your task list or calendar, things drift without regular review. Completed projects don't get archived. Priorities change but the system doesn't reflect them. Things fall through the cracks not because they weren't captured but because they were never reconnected to the current reality.

Almost every serious productivity framework includes some version of this. GTD makes it a formal ritual. PARA benefits from it to keep project lists current. Bullet journals build monthly migration into the system. Even the Ivy Lee Method, at its simplest, benefits from a weekly look at what's actually important before you pick your six daily tasks.

The details vary, but the underlying purpose is the same: a deliberate, regular moment to step back, clear the decks, and reset.

Why most people skip it

The weekly review is probably the most widely recommended and least consistently practised productivity habit there is. People know they should do it. They do it for a few weeks, skip one, feel guilty, skip more, and eventually abandon it entirely.

A few things cause this:

It feels like it has to be perfect. Allen's version of the weekly review is comprehensive: process every inbox, review every project, check every list, work through a trigger list, update everything. That version can take two hours. Two hours every week is a significant commitment, and when life gets busy, it's the first thing to drop.

It's not connected to anything tangible. Running the review doesn't produce visible output. The value is felt the following week: things don't slip, you're less stressed, decisions are clearer. But that payoff is diffuse and delayed, which makes the review easy to defer.

The system it supports has decayed. If your task list is chaotic and your projects are unclear, the weekly review becomes an hour of guilt rather than an hour of clarity. People avoid it because confronting the mess is uncomfortable.

The solution to all three is the same: make the review lighter and more consistent, rather than comprehensive and occasional.

A minimal version that actually sticks

The minimum viable weekly review takes about fifteen minutes. It covers:

Clear the inboxes. Any email, note, or capture that arrived during the week that hasn't been processed. Add to your task list, file, delete, or act on. The goal is zero unprocessed items.

Review the task list. What's outstanding? What's stale? Remove anything you're not actually going to do. Confirm that your active projects each have a visible next action.

Look at last week. What did you plan to do? What actually happened? Note the gap, not to judge yourself, but to calibrate next week's planning.

Plan next week. Given what's outstanding and what matters most, what do you want to accomplish? Write down two or three significant things you want to move forward. These aren't your complete task list; they're the things you'll consider the week a success for having done.

That's it. Fifteen minutes, done weekly, produces most of the benefit of the full version with a fraction of the friction.

If you have time and energy for more, extend into the areas Allen covers: checking your calendar for upcoming commitments that need preparation, reviewing your someday/maybe list for anything that's become relevant, scanning your active projects for anything that needs a decision. But treat these as optional additions to the minimum, not prerequisites.

What to actually review

Different systems emphasise different things. Here's a comprehensive list to pick from based on what's relevant to your setup:

Captures and inboxes. Email, notes, bookmarks, downloads, voice memos. Anything that arrived and hasn't been processed.

Task list. Current tasks: what's still open, what's been done but not marked complete, what's stale and should be removed.

Active projects. For each active project: is there a defined next action? Has anything been blocked or stuck for too long? Does any project need to move to the archive?

Calendar. Past week: any follow-ups or actions that came out of meetings or events? Coming week and beyond: any commitments that need preparation?

Waiting for. Anything delegated that you're expecting back. Anyone you need to follow up with.

Someday/maybe. A quick scan for anything that's become relevant enough to promote to an active project.

Energy and patterns. Optional, but useful: what gave you energy this week? What drained it? Any pattern worth noting for next week?

The last item is the one most productivity guides leave out, and it's often the most valuable. A week that looked productive on paper might have felt exhausting. A week where you made real progress on something hard might have felt great. Noticing these patterns is the feedback loop that improves how you work over time, not just what you work on.

The journalling layer

The weekly review pairs naturally with weekly journalling: writing a short reflection on the week before doing the tactical review. What happened? What went well? What would you do differently? What are you carrying into next week that you'd like to put down?

Fernando Borretti, in his writing on managing ADHD, describes a structured journal practice where the weekly review includes sections on what went well and what went poorly, followed by reflection on how to change behaviour to make the next week go better. This combination of tactical review (what's on my plate?) and reflective review (what patterns am I noticing?) produces a much richer output than either alone.

It also counteracts the "hedonic treadmill" problem he describes: when you consistently do better than before, what was once an achievement becomes the new baseline and stops feeling like progress. A weekly review that looks back at what you've accomplished, and a journal that traces those patterns over time, makes the progress visible.

Timing and format

Most people find Sunday evening or Monday morning works best. The end of one week connects naturally to the beginning of the next, and doing the review before the week starts means you arrive with intention rather than just reacting to what arrives.

If Sunday evening feels too close to the working week for genuine rest, Saturday morning with a coffee works. If your work week doesn't align with Monday–Friday, adapt accordingly.

The format is personal. Some people work through a fixed template in a notes app. Some use a physical journal. Some talk through the review out loud, either to themselves or as a voice memo. The AI assistant can serve as a thinking partner here: "What haven't I touched in two weeks?" or "Walk me through my active projects" works as a natural language query against your Fabric library.

The only wrong format is one you won't do consistently. Prefer the lightweight version you'll do every week over the comprehensive version you'll do four times a year.

Weekly review vs other reviews

The weekly review sits in the middle of a review hierarchy. Different cadences serve different purposes:

Daily. A brief check each morning: what's on today's list, what's the priority, anything urgent from the previous day that needs handling. Five minutes, not fifteen. This is about execution, not reflection.

Weekly. The review covered here. Tactics and patterns. What happened, what's next, what matters this week. Fifteen minutes to an hour.

Monthly. A broader look at active projects and areas of responsibility. Are there things that have been stuck for more than a week? Are there projects that should be closed? Are there areas of your life getting no attention? Thirty to sixty minutes.

Quarterly/yearly. The yearly review for PARA specifically, or equivalent reviews for any other system. Goals, priorities, life direction. One to three hours, once or a few times a year.

The weekly review is the most important of these because it's the one that keeps everything else from drifting. Monthly and yearly reviews can catch what the weekly misses, but they can't fully substitute for it. Daily checks are too granular to see patterns. The weekly is where maintenance and reflection meet in a format that's sustainable long-term.

Making it stick

The reviews people keep doing tend to have a few things in common:

They're tied to a specific time and place. Sunday at 10am with a coffee at the kitchen table. The ritualistic element matters. A review that happens "whenever I get around to it" is easy to skip.

They start with the minimum. The fifteen-minute version, done every week, is vastly more valuable than the ninety-minute version done every three weeks. Start smaller than feels sufficient.

They're tracked. A simple checkmark in a habit tracker, a recurring task that gets marked done, anything that makes the streak visible. The visual record of consistency is surprisingly motivating.

They feel worth doing. If the review consistently produces a feeling of clarity and direction, you'll keep doing it. If it consistently produces anxiety and guilt, you won't. The solution is usually to simplify (the system is too complex to review without stress) or to be more honest about what you're actually going to do (the list is full of things you've been avoiding for months).

Frequently asked questions

How long should a weekly review take?

Fifteen minutes at the minimum, an hour if you have time for the comprehensive version. Most people find that thirty minutes is a good middle ground: enough to be thorough without being onerous. The right length is "short enough that you'll actually do it every week."

What if I miss a week?

Do a brief version when you can and start again from there. One missed week won't break the practice. Two or three starts to create a backlog that makes the next review feel daunting, which creates a spiral. If you've missed several weeks, consider declaring a version of inbox bankruptcy: archive what you can't process, reset the system, and start fresh.

Can I do a weekly review without a formal productivity system?

Yes. Even without GTD, PARA, or any specific framework, the basic loop (what happened last week, what matters this week, what's outstanding) is useful. A weekly review is a habit of reflection, not a system requirement.

What's the difference between a weekly review and a daily check-in?

A daily check-in is operational: what do I need to do today? A weekly review is both operational (what's on my plate?) and reflective (what patterns am I noticing?). The weekly review also handles housekeeping (clearing inboxes, archiving completed projects) that would slow down a daily check-in.

How do I make the weekly review feel less like homework?

Usually by making it shorter and shifting the framing. The goal isn't to audit everything you didn't do. It's to set yourself up for a good week. If the review consistently ends with a clear sense of what matters and a lighter cognitive load, it starts to feel like something worth doing rather than something you ought to do.