Why weekly reviews fail
Start with the blank page. A weekly review as usually taught is an authoring job: sit down, survey everything, and write the coming week from nothing. Brains are bad at exactly this. Ask someone to plan a week from scratch and they stall. Hand them a draft and they instantly know what is wrong with it. Generation is expensive, reaction is cheap, and the classic review is built almost entirely out of generation.
Then there is the archaeology. Most reviews open on a list that has been silting up for weeks: the errand written twice in different words, the task from March that quietly stopped mattering, the thing you finished elsewhere and never ticked. Before any reviewing can start, you are cleaning. Cleaning your own list feels like being told off by a past version of yourself, and nobody volunteers for more of that.
The third failure is scatter. The raw material of your week does not live in your task app. It lives in a text from your sister, a line from Thursday's meeting, an email you starred and forgot, a photo of a whiteboard. Getting Things Done, the method that made the weekly review famous, is honest about this: the first steps are collect everything and clarify each item. Those steps are also why the full ritual runs long, and why it gets abandoned. The exhausting part comes first, and it spends your energy before the useful part begins.
Put all three on a Sunday evening, when the week has already taken most of what you had, and the outcome is not a mystery.
What a weekly review actually needs to answer
Strip the ceremony away and a weekly review holds four questions. The first: what got done? This is not a feel-good exercise. Psychologists have known since Bluma Zeigarnik's work in the 1920s that unfinished tasks keep a claim on your attention in a way finished ones do not. But the release only happens if the finish gets noticed. A week of real work that nobody counted, including you, just reads as tiredness.
The second: what slipped, and does it still matter? Every open task past its date needs exactly one of three verbs: move it, chase it, or drop it. Not an apology, not a re-litigation of why it slipped. One verb each.
The third question is the one almost nobody asks: where did the week actually go? Not where you meant it to go. If work took every completion this week and health took none, that is worth knowing while it is a two-week pattern, not a year-end surprise. Intentions drift quietly. Tallies do not.
And the fourth: what is next week already holding? The deadlines, the promise you made a colleague, the first thing on Monday's plate. Notice what is not on this list: building next week hour by hour. A review is a look back and a look ahead. The moment it becomes a scheduling session, it grows past the size a Sunday will tolerate.
A ten-minute Sunday review, step by step
Here is the ten-minute version, and it works with paper, a plain list app, anything. Minutes one and two: mark everything you finished, then read the finished list once, slowly. This is the step people skip and the step that changes how the rest feels.
Minutes three through five: triage what slipped. Three verbs, one decision per task, no ceremony. The car insurance moves to Tuesday. Sam's invoice gets a chase. The article you were going to read gets deleted, and deleting it is a decision, not a failure.
Minutes six and seven: sweep the orphans. Scan your texts, your inbox, your notes app, your camera roll for commitments that never made it into the system. Do not organize them. Just get them in, so nothing lives only in your head.
Minutes eight and nine: read next week. Pick the two things that must come true and write them at the top. Note who is waiting on you, because a deadline with a person attached is the kind that hurts to miss.
Minute ten: stop. A review that overruns this Sunday gets skipped next Sunday. And if ten minutes is nowhere near enough, the problem is not the review. It is that the list went unmaintained all week, and Sunday is paying the interest. Which raises the better question: what if the week maintained itself?
The Sunday that writes itself
This is the job Matters was built around. During the week, capture does the collecting for you. Say the commitment out loud, share it from any app, paste it, forward the email, photograph the whiteboard. Each one comes back as a filed task with its date, its person, its project. The scatter never accumulates, because nothing waits for Sunday to be collected.
The archaeology gets handled the same way. Matters reads your list like a tidy friend and suggests the cleanup: these two are the same errand, this one from March can go, this one looks already done. Each suggestion is one tap, and nothing is applied without you. The list you open on Sunday is alive, not sediment.
Then, on Sunday, Matters writes the review itself. Not a dashboard. A short paragraph, the way a friend would recap your week over coffee. It opens with what got done, the count and the standouts by name. It gives one honest line on where the week went, drawn from your completions by area and project: work ate the week, health did not get a bite. It names what slipped, how many and the oldest, plainly and without shame. And it closes with what next week is already holding and the first thing on its plate.
One detail is worth knowing. Every number in that paragraph is tallied from your real tasks before a single word is written. The words narrate the count; they never do the counting, so the review cannot round your week up or invent a win. A week where nothing got done is told gently, and told true.
What remains is the only part that ever needed you: read it, pick your two things, done. From Monday, a two-sentence brief opens each morning and reminders keep their hours. None of it ever writes a block onto your calendar. It suggests when. The time stays yours.
Is Sunday the best day for a weekly review?
Sunday evening works because one week has ended and the next is visible, but the honest answer is that a consistent slot beats a perfect one. Friday afternoon suits people who want to close the work week while the context is warm, then actually rest. Sunday suits people whose week is bigger than work. Matters writes its review on Sunday, dated by the Sunday you are sitting in, and the review waits there until you are ready to read it.
How long should a weekly review take?
Ten to fifteen minutes, if your list is clean and complete. An hour or more, if the review is also doing a week's worth of capture and cleanup. When a review keeps running long, the fix is rarely a better Sunday routine. It is cheaper capture and steady upkeep during the week, so Sunday inherits a list that is already true.
Do I still need a weekly review if Matters writes one?
Yes, and it shrinks to the part that was always yours. The recap hands you the facts: what got done, where the effort went, what slipped, what is coming. Judgment does not automate. Only you know that the plumber is suddenly urgent, or that Thursday's deadline moved in a hallway conversation. Reading the week and choosing the two things that matter takes a few minutes, and it is the only meeting with yourself left standing.
If you have spent years failing at the hour-long version, try one Sunday of the short one. Matters is free for 14 days, no card needed, on iPhone, Android, Mac, and Chrome. Capture the week as it happens, and let Sunday read it back to you.