Weekly Review: A Checklist for Staying on Top of Everything

What is a weekly review?

A weekly review is a recurring appointment in which you close out the week that just happened: you collect everything uncaptured, check every commitment against reality, and decide what carries forward. It is a reconciliation exercise first and a planning exercise second.

The practice comes from David Allen’s Getting Things Done, where he calls it the “critical success factor” of the whole method and recommends running it every seven to ten days. His version has eleven steps across three phases — get clear, get current, get creative — and takes one to two hours when done fully. Most working professionals do not need two hours. They do need the structure, because the value is in the completeness, not the duration.

The distinction that matters: a weekly review is not the same as planning your week. Planning asks “what should I do next week?” A review asks “what actually happened, what is still open, and what am I lying to myself about?” Answer the second question and the first becomes much easier.

Why do productivity systems fall apart without a weekly review?

They fall apart because a list you do not trust stops functioning as memory. Once you suspect the list is stale, your brain starts keeping a parallel copy, and the whole point of writing things down disappears.

The decay follows a predictable pattern. In week one, everything is captured. By week three, some items are captured in the tool and some in Slack and some in your head. By week six, the list has tasks that were completed but never ticked, tasks with dates that passed, and projects that ended without being closed. You stop opening it, not because you are lazy, but because opening it produces anxiety instead of clarity.

There are four specific failure modes a review catches, and none of them are visible during the week itself:

1. Commitments made in conversation. You said “I’ll send that over” in a call on Tuesday and never wrote it down. Only a calendar and notes sweep finds these.
2. Waiting-for items that have gone quiet. A supplier who promised a quote eight days ago, a colleague who owes you a review.
3. Zombie projects. Work you are nominally doing but have not touched in a month and have not decided to stop.
4. Due dates that are fiction. Tasks dated last Tuesday, still open, still claiming to be urgent.

Each one is small. Together they are why people describe their task manager as “a source of guilt” — the tool is fine, the bookkeeping is missing.

What does the close-out checklist look like?

The review has six phases. The timings below add up to 50 minutes, which is a realistic Friday slot for someone with a busy calendar.

Phase 1: Capture everything, everywhere

Open every inbox you own and process it to zero — email, chat, the notes app, the paper notebook, the voice memos, the browser tabs you saved “for later”. Processing does not mean doing. It means every item gets a destination: a task, a project, a calendar entry, a reference file, or the bin.

Add one step most checklists miss: write down what is in your head. Set a two-minute timer and list every commitment, worry and half-idea that has been circulating. You will be surprised how many items only exist in working memory.

Phase 2: Reconcile the week that happened

Read last week’s calendar backwards, entry by entry. For each meeting, ask three questions: did I commit to anything? did anything change? is there a follow-up I owe someone? This is the single highest-yield ten minutes in the review, because verbal commitments are the ones that leak.

Then sweep your notes and chat threads for the same thing. If you use a tool that logs messages, search for “I’ll”, “will send”, “by Friday” and “let me”. It sounds mechanical; it works.

There is also a physical version of this step that people skip. Go through the paper on your desk, the receipts in your wallet, the sticky notes on the monitor and the whiteboard photo you took on Tuesday. Anything with a date or a name on it becomes a task, a calendar entry or a reference file. The desk should be clear when you finish, not because tidiness is a virtue, but because every visible note is a reminder your brain keeps re-reading.

Phase 3: Close the loops

Walk the waiting-for list. For each item, record who owes it, when you asked, and when you will chase. Anything older than a week gets a nudge today, while the person is still at work and the context is still fresh.

Then look at delegated work. Delegation fails quietly: the person is waiting for clarity and you are waiting for delivery, and neither of you says so. One line per delegated item — owner, definition of done, check-in date — prevents most of it.

Phase 4: Audit the system

This is the phase people skip and the one that keeps the system trustworthy. Check for four kinds of rot:

• Completed but unticked tasks. Tick them. An unticked completed task is a lie the list tells you every morning.
• Tasks with no next action. “Plan the offsite” is not actionable. “Email three venues for availability” is.
• Duplicate items. The same task in two projects, or two versions with different dates. Pick one.
• Dead projects. Anything untouched for 30 days gets one of three labels: active, scheduled, or dropped. Dropping is a valid outcome and should not feel like failure.

Phase 5: Record four numbers

Write down four numbers before you close the week: tasks committed, tasks completed, items carried over, and hours in meetings. That is it. No dashboard, no scoring system. Four numbers, one line, in the same place each week.

After six weeks the line becomes a trend, and the trend explains most of your bad weeks better than any reflection exercise. A carry-over rate that climbs while meeting hours climb is not a discipline problem; it is a capacity problem, and it needs a different response.

Phase 6: Decide what carries forward

Now, and only now, look at next week. Take the carry-over list and make an explicit decision on every item: schedule it, shrink it, delegate it, or drop it. “Carry it and hope” is not one of the options, though it is the most popular.

This is the five minutes where the review touches planning. If you want a fuller planning routine, that is a separate exercise — the review’s job is to hand next week a clean, honest list.

What should a 20-minute express review cover?

The express version keeps three phases and drops the rest: capture (7 minutes), waiting-for and commitments (7 minutes), carry-over decisions (6 minutes). Skip the metrics, skip the deep project audit, skip the someday list.

It is a legitimate review, not a compromise. David Allen’s own guidance is that any review beats no review, and that when time is short you should pick the step that most has your attention. The one thing worth protecting even in a five-minute week is the waiting-for sweep, because that is where the expensive surprises live.

What do the numbers look like in practice?

Example 1: the stale list audit. A marketing manager with 120 open tasks runs the audit for the first time. She ticks 22 tasks that were finished but never closed, archives 34 items older than six months, merges 11 duplicates, and finds 9 tasks with no next action. The list drops from 120 to 53 real items. Nothing was deleted that mattered; the list simply stopped lying. The review took 55 minutes and the following week’s planning took 12 instead of the usual 40.

Example 2: carry-over rate as a capacity signal. Over four weeks, a developer commits to 38, 35, 40 and 36 tasks and completes 24, 22, 27 and 21. Carry-over runs at 37%, 37%, 33% and 42%. Two conclusions follow: the plan is consistently 35% too ambitious, and no amount of personal discipline will fix it. The correct response is to commit to 25 tasks next week, not to try harder.

Example 3: the cost of one missed commitment. An account director discovers in the Friday review that a client proposal promised “by Thursday” was never sent. It goes out Friday afternoon, four days late. The client pushes the decision to the next committee cycle, which delays $46,000 of signed work by a month. The review that caught it took 45 minutes; the miss cost a month of cash flow.

Example 4: the time budget. A 45-minute review every week for 48 working weeks is 36 hours a year — about 0.9% of a 2,000-hour working year. If it prevents two late deliverables and one lost invoice query, it has paid for itself several times over. Framed as a percentage of the year rather than an hour of the week, the math stops being a debate.

What should you do with the someday/maybe list?

Review it every two to four weeks, not every week, and give every item one of three verdicts: promote it to a project, leave it parked, or delete it. The list exists so that interesting ideas stop competing with current commitments, and it only performs that function if the parked items are genuinely parked rather than silently nagging.

A practical rule: if an item has sat on the list for a year and you have not promoted it once, it is not a someday — it is a no. Delete it. The relief is immediate, and nobody is keeping score. Keeping a list of 60 aspirational projects is not ambition; it is a queue of small disappointments you walk past every week.

Which signals should you track over time?

Four metrics are enough. More than four and you will stop recording them.

Two cautions. First, do not compare your numbers to anyone else’s; a support lead and a researcher have different throughput by design. Second, do not turn the metrics into a performance review. The moment the numbers are used against you, they stop being honest.

How do you run a weekly review for a team?

A team version takes fifteen minutes and is not a status meeting. Each person answers three questions: what did you close this week, what are you waiting on from someone in this room, and what are you dropping? The third question is the one that changes behaviour, because most teams never explicitly cancel anything.

The team lead’s job is to capture the waiting-for answers into one shared list and to name the one or two items the team will not carry. Then close the meeting. Do not turn it into planning; that belongs to a separate session where the work is actually scoped.

One structural habit makes the team version work: keep the review at the same time as the week’s last working hour. Friday at 4 pm is common because it is early enough that people are still reachable and late enough that the week’s work is visible.

What are the common mistakes?

• Turning the review into a work session. You open one email, start answering it, and forty minutes later you have done one task and reviewed nothing.
• Only planning, never reconciling. A review that starts with “what should I do next week” skips the part that makes the list trustworthy.
• Doing it on Sunday night. It works for some people, but it borrows from your rest and it puts the follow-ups 48 hours away from anyone who could answer them.
• Skipping weeks and then doing a mega-review. A three-week backlog turns a 45-minute habit into a half-day project, which is exactly why people quit.
• Keeping every list. Someday/maybe lists are useful; five of them are not. One place per type of commitment.
• Never deleting anything. A system with no discard function becomes an archive, and archives do not help you decide what to do on Monday.
• Reviewing in the tool that has the most notifications. Do it in the calmest interface you have, even if that means a paper checklist.

> Important note: if you finish a review and feel behind rather than clear, the problem is usually that you reviewed your tasks but not your commitments. The calendar sweep in phase two is the part that finds the promises you forgot you made.

How do you make the habit stick?

Book the next eight Fridays before you start the first one, and treat the slot as you would a meeting with a client. David Allen’s advice is to run at least four reviews before deciding the habit does not suit you, because the first two feel slow and the third is where the value appears.

Shrink the barrier rather than the ambition. Keep the checklist open in a document, not buried in a tool you have to log into. Start the timer before you open the first inbox, so the review has an end as well as a beginning. And if a week collapses, do the 20-minute version on Saturday morning rather than skipping — a partial review keeps the system current, while a skipped one starts the decay that makes the next review feel pointless.

Where does Doitify fit?

Doitify is our product, so treat this as a disclosure rather than a review. A weekly review needs one place where tasks, projects, due dates and the waiting-for state can be seen together, and most people assemble that from three tools that do not talk to each other.

In Doitify, the review is mostly a filter exercise rather than a data-gathering exercise: tasks by owner and status, projects without recent activity, items with overdue dates, blockers and dependencies, and a work report that already holds the weekly numbers. Because tasks, sub-tasks, checklists, meetings notes and project documents live in the same workspace, the calendar sweep does not require exporting anything. It is not a magic habit machine — the discipline is still yours — but it removes the ten minutes of assembly that usually comes before the actual review.

Conclusion

The weekly review is the least glamorous habit in productivity and the one that keeps every other habit alive. It does not make you more disciplined; it makes your system honest, and an honest system is the only kind you will actually trust on a Monday morning.

Start with the 20-minute version this Friday: empty the inboxes, sweep the calendar for promises, chase anything you have been waiting on for more than a week, and decide what you are dropping. Add the numbers and the project audit once the habit holds. The five minutes you spend on next week will feel easy, because for the first time in a while the list will be telling the truth.

If this post on weekly review was helpful, you might also enjoy Time Tracking Project Management Tool and How to Reduce Meeting Overload.