What makes the SCAN Method different from GTD's weekly review?

The GTD weekly review is comprehensive and assumes a functioning GTD system. The SCAN Method is system-agnostic — it works whether you use GTD, Notion, a paper notebook, or nothing at all. It's also designed with a hard time cap: the minimum viable version runs in 20 minutes, which matters for consistency. GTD practitioners can use SCAN as a lightweight alternative when they don't have time for the full GTD review.

Does SCAN work for teams as well as individuals?

Yes, with slight adaptation. In a team context, the Sweep phase becomes a shared inbox review, the Check phase includes team commitments and dependencies, and the Navigate phase produces a shared sprint intention rather than an individual plan. Many Agile teams run a version of SCAN without naming it — it maps closely to a condensed retrospective plus sprint planning session.

How do I handle the Analyze phase when I don't have good data?

Start with your calendar. Even rough analysis of your calendar — what types of events dominated, where you felt most and least productive, what got pushed — produces useful pattern data. The Analyze phase doesn't require a time-tracking tool. It requires honest engagement with whatever record of the week you have, which is almost always your calendar.

The Weekly Review Framework That Actually Sticks: The SCAN Method

The test of any productivity framework is not how good it sounds in theory. It’s how many weeks in a row you actually use it.

Most weekly review frameworks fail the consistency test. The GTD weekly review is comprehensive but takes 60–90 minutes, which makes it vulnerable to any week where Friday afternoon is constrained. Other systems are so minimal they don’t produce anything actionable. The Bullet Journal migration works for analog practitioners but has no obvious digital equivalent.

The SCAN Method is designed for durability above all else. Four phases. A minimum viable version that runs in 20 minutes. A full version that runs in 60. No tool dependency. No format dependency. Compatible with GTD, with Agile retrospective language, with Second Brain-style information management, or with no prior system at all.

Here is the full framework — how each phase works, why it’s there, and how to adapt it to your specific working context.

Why Most Weekly Review Frameworks Break Down

Before the framework: a clear-eyed look at why most weekly review attempts fail within two months.

Scope creep. The initial design is modest — maybe 30 minutes. Then you add a project review. Then a goal review. Then a reflection section. The review is now 90 minutes, and it can’t survive a single constrained Friday. Scope creep kills the habit before the habit has a chance to form.

No minimum viable version. If the framework has only one speed — comprehensive — you can’t adapt to a week where you only have 20 minutes. You either do the full review or skip it. The skip becomes the habit.

Analysis without commitment. The review generates observations but not decisions. You notice that deep work blocks kept getting interrupted, but you don’t change anything about your Monday calendar. Observations without behavioral commitments are journaling; they produce reflection but not improvement.

Tool dependency. The review requires specific data from a specific app, and when that data isn’t available (you forgot to track one day, the app has a sync error), the review feels incomplete and you skip it.

The SCAN Method is designed to solve each of these failure modes explicitly.

The SCAN Method: An Overview

S — Sweep: Clear your inboxes and capture all open loops. The week hasn’t been processed until the information from it has been moved out of temporary storage (email, inbox, voicemail, open browser tabs, your head) and into your system.

C — Check: Review your current reality. Calendar, projects, tasks, waiting-for items. Confirm that your picture of what’s happening in your work is accurate and current.

A — Analyze: Find the pattern in the week. What does the data reveal about how you actually worked, versus how you intended to work?

N — Navigate: Commit to intentions and behavioral changes for the coming week. Schedule them specifically enough that they could be put on a calendar.

Each phase has a minimum viable version (5 minutes) and a full version (15 minutes). The total ranges from 20 minutes (all minimum viable) to 60 minutes (all full). The two-speed design is not optional — it’s the architectural feature that makes the habit durable.

Phase 1: Sweep

What it is: The clearing phase. Before you can review the week, you need to finish processing it. Open loops living in temporary storage (email flagged for later, notes app full of week’s captures, paper notes on your desk, voicemails) create cognitive load and introduce incomplete data into the review.

The minimum viable Sweep (5 minutes):

Two-minute brain dump: write down everything still floating in your head
Scan email inbox: flag anything requiring action, capture the action, archive the rest
Look at your desk or physical inbox: any unprocessed items that need a home?

The full Sweep (15 minutes):

Brain dump (as above)
Email inbox to zero: every unread message either archived, actioned, or scheduled
All secondary inboxes: Slack, voicemail, digital notes apps
Physical inbox cleared
Any browser tabs left open as reminders: either acted on, bookmarked, or closed

Why it comes first: Reviewing a week you haven’t finished processing produces an inaccurate picture. The full Sweep ensures that when you move to Check and Analyze, you’re working with a complete dataset rather than just the parts that happened to be tidied.

The failure mode to avoid: Turning the Sweep into a working session. The goal is capture, not completion. When you find a task during the Sweep that needs action, log it — don’t do it. That distinction is the difference between a Sweep that takes 15 minutes and one that takes 90.

Phase 2: Check

What it is: The current-reality phase. A systematic review of your active work — calendar, tasks, projects, delegations — to confirm that everything is current and nothing is invisible.

The minimum viable Check (5 minutes):

Scan last week’s calendar: anything incomplete that needs to be recaptured?
Look at next week’s calendar: any approaching deadlines or pre-work needed?
Quick scan of task list: anything stale, completed, or needs immediate action?

The full Check (15 minutes):

Last week’s calendar: full review, one day at a time. Any action items from meetings that weren’t logged? Any rescheduled items that need to be recaptured?
Active projects: every project should have at least one visible next action. If a project has no next action, add one or mark the project as stalled.
Waiting-for list: who has something you need? What follow-ups are due?
Next two weeks on the calendar: anything needing preparation, an agenda, or a travel arrangement that hasn’t been handled?

Why this phase is often undervalued: The Sweep captures what’s in your head. The Check captures what’s in your system. Combined, they ensure your review is operating on a complete picture. A review that skips Check is a review that might be missing a project deadline, an outstanding delegation, or a meeting that needs preparation — all of which change what Navigate should produce.

The specific Check question that most reviews miss: “Does every active project have a visible next action?” This is the GTD weekly review’s most important diagnostic. Projects without next actions are invisible to your daily task system — they exist as project names but generate no daily reminders to progress them. A five-second scan asking this question for each project consistently surfaces stalled work that would otherwise stay stalled for weeks.

Phase 3: Analyze

What it is: The pattern-finding phase. This is where the review earns its name. Not reviewing tasks — reviewing your week as a whole to understand what it reveals about how you’re working.

The minimum viable Analyze (5 minutes):

What was this week’s clearest win?
What was the most significant thing that didn’t happen, and what caused it?
What would you do differently if you could redesign last week from scratch?

The full Analyze (15 minutes):

All three minimum viable questions, with more depth
Calendar pattern analysis: what proportion of the week was meetings versus focused work versus reactive work? Does that ratio match your priorities?
Task pattern analysis: any tasks that migrated from last week? Any task type that consistently gets deferred?
Energy pattern: when were you most and least productive? Did your scheduling reflect that?
Multi-week analysis: what patterns are repeating across the last three or four weeks?

Where AI adds genuine value: The Analyze phase benefits more from AI assistance than any other phase. Pattern recognition across multiple weeks is genuinely difficult for humans — we overweight recent experience, underweight patterns that developed gradually, and miss correlations between different types of data. A well-structured AI prompt analyzing three or four weeks of calendar and task data consistently surfaces patterns that unaided reflection misses.

A reliable prompt for multi-week analysis:

Here are my last four weekly review summaries. Please identify:
1. Any pattern in what types of tasks consistently get deferred
2. Any pattern in when my deep work blocks get interrupted
3. Whether my stated weekly priorities and my actual time allocation are aligned
4. One systemic change that would address the most significant pattern

Review summaries:
[paste four weekly review notes]

Beyond Time (beyondtime.ai) stores your weekly review data and surfaces this kind of multi-week pattern analysis automatically, so you don’t need to manually aggregate four weeks of notes before each Analyze phase.

The diagnostic framing that changes Analyze quality: Ask “why” at the system level, not the discipline level. “I didn’t write the proposal because I was distracted” is not a useful diagnosis — it describes a symptom. “I didn’t write the proposal because I scheduled it on a day with three back-to-back meetings and no cognitive energy left by 3pm” is a diagnosis. The system-level diagnosis points to a specific fix. The discipline-level diagnosis points to vague resolve, which produces no durable change.

Phase 4: Navigate

What it is: The commitment phase. This is where the review converts analysis into scheduled intention. A review that ends without a specific behavioral commitment is intellectually interesting but operationally inert.

The minimum viable Navigate (5 minutes):

Name the one outcome that would make next week a success
State the one behavioral change from the analysis — specific enough to schedule
Open the calendar and make the behavioral change visible (block the time, add the constraint, remove the meeting)

The full Navigate (15 minutes):

Two or three priority outcomes for the coming week
One behavioral shift per significant pattern identified in Analyze
Calendar review: does next week’s schedule reflect the stated priorities?
Implementation intentions for each behavioral shift: when, where, and how will you do the new behavior?

Why the calendar step is not optional: Implementation intentions — specifying the when, where, and how of a planned behavior — dramatically increase follow-through compared to stating intentions in the abstract. Peter Gollwitzer’s research on this effect is among the most replicated in behavioral psychology. “I will protect Tuesday and Thursday mornings for deep work” is an intention. “I will block 8–11am on Tuesday and Thursday as ‘no-meetings focus time’ — I’m doing that now before I close the calendar” is an implementation intention. The difference in follow-through is consistent and large.

The Navigate question that most frameworks miss: “Does next week’s calendar already reflect my stated priorities, or do I need to redesign it?” Most people answer this question and find that their calendar was designed by other people (meeting requests) and inertia (recurring events). Navigate is the one moment in the week where you hold the calendar intentionally rather than reactively.

Adapting SCAN to Your Working Context

If you use GTD: Run the full GTD collection phase as your Sweep. Use the GTD project review as your Check. Use SCAN’s Analyze and Navigate as the GTD review’s analytical and planning counterpart — the phases GTD is relatively light on.

If you use Bullet Journal: The migration process is your Sweep. Your weekly log scan is your Check. Add five minutes of Analyze (three questions: win, friction cause, design change) and a two-sentence Navigate before starting the new week’s spread.

If you work in an Agile team: Map the sprint review and retrospective to SCAN’s Analyze phase. Your standup and sprint planning cover the Check and Navigate phases. SCAN can serve as the personal layer underneath the team layer — the individual version of what the Agile ceremonies do for the team.

If you have no current system: Start with minimum viable SCAN. Four phases, 20 minutes, no tool requirements. Build from there.

The Framework’s Design Principles

Three explicit design choices in SCAN that distinguish it from most weekly review frameworks:

System-agnostic. SCAN doesn’t require a specific tool, task manager, or note-taking app. The Sweep phase works with email, paper, or mental capture. The Check phase works with any calendar. The Analyze and Navigate phases require only the capacity to ask and answer honest questions.

Two-speed. Every phase has a 5-minute and a 15-minute version. This means the framework has a 20-minute minimum and a 60-minute maximum. The 20-minute version is not a shortcut — it’s a deliberate design for weeks where the full version isn’t possible. The habit of doing minimum viable SCAN every week is worth more than doing the full version 12 times a year.

Commitment-forcing. Navigate is structured to produce a scheduled behavioral change, not an intention. The framework is only complete when something on your calendar has changed. This isn’t an arbitrary constraint — it’s the mechanism through which weekly reviews actually improve how you work over time.

Run SCAN once this week. Start with the minimum viable version — four phases, five minutes each. See what it produces.

Related:

Tags: weekly review framework, SCAN method, productivity systems, GTD weekly review, personal planning framework

Frequently Asked Questions

What makes the SCAN Method different from GTD's weekly review?

The GTD weekly review is comprehensive and assumes a functioning GTD system. The SCAN Method is system-agnostic — it works whether you use GTD, Notion, a paper notebook, or nothing at all. It's also designed with a hard time cap: the minimum viable version runs in 20 minutes, which matters for consistency. GTD practitioners can use SCAN as a lightweight alternative when they don't have time for the full GTD review.
Does SCAN work for teams as well as individuals?

Yes, with slight adaptation. In a team context, the Sweep phase becomes a shared inbox review, the Check phase includes team commitments and dependencies, and the Navigate phase produces a shared sprint intention rather than an individual plan. Many Agile teams run a version of SCAN without naming it — it maps closely to a condensed retrospective plus sprint planning session.
How do I handle the Analyze phase when I don't have good data?

Start with your calendar. Even rough analysis of your calendar — what types of events dominated, where you felt most and least productive, what got pushed — produces useful pattern data. The Analyze phase doesn't require a time-tracking tool. It requires honest engagement with whatever record of the week you have, which is almost always your calendar.