How long should a weekly
review take? Thirty minutes.

Thirty minutes is the goldilocks number. Long enough to think rather than check boxes. Short enough that you actually do it every week. Here is why ten-minute reviews fail and ninety-minute reviews collapse.

Thirty minutes. That's the working answer for almost everyone, and the constraint matters more than the exact duration. Short enough that you'll actually do it every week. Long enough to think rather than just check boxes. Below ten minutes the review becomes superficial. Above sixty minutes it becomes a thing you skip on a busy Sunday. Thirty is the goldilocks number.

This post is the short version of the case. Why thirty minutes is the right ceiling. How to structure the review so it fits. Why most people end up doing either ten-minute reviews that don't work or ninety-minute reviews they abandon. And — at the end — the practical workflow that delivers a useful review in exactly thirty minutes every Sunday.

Why thirty minutes

The weekly review has five jobs to do, and each one needs roughly six minutes:

Each section depends on the one before it. Skipping the brain dump means the processing has nothing to sort. Skipping the cascade means this week's intentions get picked from short-term urgency rather than long-term priority. Each section needs roughly six minutes — long enough to think, short enough to stop and move on. Thirty minutes is the sum. (See the full weekly review post for the detailed sequence.)

What goes wrong with a 10-minute review

Most people who do a ten-minute review are running a checklist version: glance at the calendar for next week, write down three tasks, close the notebook. This version doesn't fail in obvious ways — you've done something on a Sunday — but it produces no real benefit. There's no brain dump, so the week's open loops continue running in your head. There's no debrief, so you don't learn anything from last week. There's no cascade, so the three tasks you've written down are arbitrary.

The ten-minute review feels productive but isn't. The difference between ten and thirty isn't a tripling of effort — it's the difference between a ritual that produces nothing and one that genuinely changes the following week.

What goes wrong with a 90-minute review

The other failure mode is the elaborate review. Open three notebooks. Pull up six spreadsheets. Review each domain in detail. Update the long-horizon trackers. Reflect on the broader direction of life. Process every email. By the end of ninety minutes you have something comprehensive — and you'll skip it next Sunday because ninety minutes is too much.

The 90-minute review survives for about six weeks. Then a busy Sunday lands and you don't do it. The week after that, you don't do it either, because you'll need to do a double-length one to catch up. By month three, the practice has stopped.

The thirty-minute version survives because thirty minutes always fits. Even on a difficult Sunday with a poorly-slept Saturday night and a busy afternoon, thirty minutes can be found. The flexibility is what makes the cadence robust over years.

The setup that makes 30 minutes possible

The thirty-minute review is only possible if the rest of the system is doing its job. Specifically:

This is the meta-point about thirty-minute reviews. The thirty minutes is achievable only because the artefacts are doing the structural work. With the right pre-formatted pages, the cognitive load is just thinking — not also designing the page layout.

The artefact · and the OS that runs it

The Weekly Review sheet — designed for exactly 30 minutes

Five sections, pre-laid-out, with the right amount of space for each six-minute block. The Weekly Review is £3.99 standalone in any format. Inside the Groundwork OS, the Weekly Review auto-populates from the 90-day plan above it and feeds the Daily Focus Sheet below it — your weekly intentions inherit from quarterly objectives, and your daily priorities inherit from weekly intentions. The thirty-minute review becomes the connecting tissue of the whole cascade. £19.99 for the OS, £54.99 for the complete bundle.

See the Groundwork OS →

The day-of-week question

Sunday evening is the most common choice, and it's the right one for most people. The week is ending, the next week hasn't started, and you have the perspective of distance from Monday-to-Friday's activity. Around 7pm-9pm works for most household rhythms.

Two alternative slots that work:

Whichever you pick, the consistency matters more than the choice. Same day, same time, every week. The review that happens "when I have time on the weekend" becomes the review that doesn't happen.

Builder's note My weekly review has been at Sunday 7pm for four years. The duration has come down from sixty minutes to forty to thirty as the framework got tighter. The thirty-minute version is what I sustain now, with very few exceptions. The two times I skipped a review last year, the following Monday felt notably different — reactive, more email-driven, less intentional. The Sunday review is doing more work than it looks like it's doing.

The honest answer

Thirty minutes. Five sections at six minutes each. Sunday evening at 7pm. Same time, same place, every week. The cadence that produces a better Monday than no cadence at all.

If you want the pre-formatted artefact, the Weekly Review sheet is £3.99 standalone or part of the complete Groundwork bundle at £54.99. The Groundwork OS at £19.99 holds the weekly review inside a connected Notion workspace where the inputs (quarterly objectives) and outputs (daily priorities) are automatically linked.

Or run the framework with a paper notebook and a timer. The framework matters more than the format. Thirty minutes, every Sunday, every week. That's the answer.

Continue reading

Sat 30 May 2026 · Cornerstone
How to do a weekly review (the 30-minute version that actually works)
Sat 29 Nov 2025 · Cornerstone
How to plan your week like Cal Newport