How to run a weekly review (that actually helps next week)

A simple weekly review checklist

The four steps above go quicker if you turn them into a short list of questions you ask yourself the same way each week. Keep it to what you can answer honestly in a few minutes.

• What did I plan for this week, and what actually happened?
• What slipped, and what was the real reason behind it?
• What unfinished work is still important enough to carry into next week?
• What can I let go of, without guilt?
• What are the two or three priorities that would make next week a good one?
• Is anything quietly building up outside work (health, money, relationships) that a busy week has let me ignore?

# Weekly review

Week of: ____________

## Look back (5 minutes)
- What actually got done this week?
- What slipped, and why? (Underestimated, no energy, priority changed, hidden dependency, or never mattered?)
- What did the week feel like: too full, about right, or too empty?

## Decide what carries (5 minutes)
For each unfinished item, pick one:
- [ ] Carry it forward as it is
- [ ] Resize it into something smaller
- [ ] Hand it off to someone who should own it
- [ ] Defer it to a named later week
- [ ] Delete it, it stopped mattering

## Set up next week (5 minutes)
Three to five priorities, across the parts of life that need attention:
1.
2.
3.
4.
5.

One adjustment for next week (one thing to do differently):
-

The five-way rule for unfinished work

Carryover is where reviews get slow and heavy, because 'move it to next week' quietly becomes the answer to everything and next week starts pre-loaded with this week's guilt. The fix is to force one of five decisions for every unfinished item, and to treat all five as legitimate:

• Carry it
  • still important, still right-sized
  • it moves forward with its context, not as a bare task
• Resize it
  • the item was honest, the size was not
  • cut it to the version that fits a real week
• Hand it off
  • it matters, and you are not the right or only person
  • give it an owner and stop carrying it
• Defer it
  • it belongs to a named later week, not vaguely to 'sometime'
  • date it and drop it from view until then
• Delete it: it stopped mattering, and dragging a dead task forward week after week costs attention every single time you skim past it

A worked review, start to finish

Here is a real-shaped week reviewed in full, five planned items in, four decisions out, so the process stops being abstract. Total time: about nine minutes.

Review the week, not yourself

The fastest way to kill a review habit is to let it become a weekly trial with yourself as the defendant. 'I failed at three of five' is a verdict, and verdicts make people stop looking. The review's language is evidence, not judgement, and almost every slip resolves into one of five ordinary causes: you underestimated the size, you lacked the energy, the priority genuinely changed, a hidden dependency surfaced, or the thing never actually mattered. Not one of those five is a character flaw. Each one implies a different, concrete fix, which is precisely why naming the real cause matters more than feeling bad about the outcome.

The tell that a review is working is that it gets less emotional over time, not more: five minutes of reading evidence, four calm decisions, one line for next week. If a week was genuinely hard, the review is also where that gets acknowledged without ceremony: some weeks the finding is simply 'this was a heavy week and one priority surviving it was enough', and writing that down is a correct result, not a consolation.

How long should a weekly review take?

Ten minutes is the working answer, split roughly as the template splits it: five looking back, and five deciding carryover and next week's priorities. Anything much longer tends to get skipped, and a review you skip helps no one.

A monthly-ish deeper pass, twenty five to thirty minutes, earns its place about every fourth review: read the month's learn lines together, look for the slip that keeps repeating, and sweep the areas a busy month ignores (money at month scale, the friend you keep meaning to call, the routine that quietly died). That deeper pass is the bridge to the rungs above; the cadence guide covers how the levels fit together.

When should you do your weekly review?

Most people run their weekly review at the end of the week or just before the next one begins, so the reflection feeds straight into planning. Friday afternoon, Sunday evening and Monday morning are all common, and the exact slot matters far less than picking one and keeping it.

Anchor it to something you already do so it does not rely on willpower: your Friday wind-down, your Sunday coffee, or the first ten minutes at your desk on Monday. The best time is the one you will actually repeat.

Carry forward, don't restart

The single most valuable output of a weekly review is carryover with context. Unfinished work that moves into next week should arrive with its why attached: what it is, where it got to, what the real next step is. Bare tasks re-imported from a dead week are how backlogs grow teeth.

This is also the honest test of any planning tool you use: does last week inform this one, or does every week start cold? However you run it, in a notes file, on the template above, or in a planner that carries it for you, the carry-forward is the mechanism that makes weeks compound instead of repeat.

Common weekly review mistakes

The failure modes are consistent enough to list, and all of them have the same cure: smaller, calmer, more regular.

• Making it long
  • a forty-minute ceremony gets skipped by week three
  • ten minutes survives
• Making it a trial
  • verdicts kill the habit
  • evidence sustains it
• Carrying everything
  • 'move to next week' as the default answer pre-loads next week with guilt
  • force the five-way call
• Reviewing only work: the sweep question exists because health, money and people drift silently in busy weeks
• Producing nothing
  • a review that changes nothing about next week was a mood with a calendar slot
  • end every review with at least one decision and one line