A weekly review checklist that repairs trust in your plans

A planning system becomes stressful when it stops telling the truth. The inbox contains things you never clarified. Projects have no visible next action. The calendar is treated like a wish list. Old commitments remain active because closing them feels like failure.

A weekly review restores trust by bringing the system back into contact with reality. It is not the only time you process work, and it does not need to include every life category. It is a protected interval for seeing the whole field before another week begins.

Why a weekly review works in ordinary weeks

Daily planning happens too close to the pressure of the day. A weekly view makes different problems visible: a project with no owner, three deadlines competing for Thursday, a customer promise hidden in meeting notes, or a task you keep rescheduling because you no longer intend to do it.

The review also creates permission to renegotiate. A trustworthy system includes not now, waiting, delegate, and stop. If every captured idea becomes an active promise, the system is not organized; it is accumulating guilt.

Use the 25-minute RESET framework

Minutes 0–5: Recover

Collect the sticky note, meeting follow-up, browser tab, voice memo, and unfinished daily note. Do not complete everything. Put it in one place so you can decide with the whole set visible.

Minutes 5–12: Evaluate

Review the previous and upcoming calendar, active projects, waiting items, and recent notes. Close what is complete. Update what changed. If a project has no next action, decide whether it is active or merely interesting.

Minutes 12–18: Select

Choose one to three meaningful outcomes for the week and a handful of smaller commitments. An outcome describes a changed state, such as “proposal sent with pricing approved,” not a vague activity such as “work on proposal.”

Minutes 18–22: Expose

Look for collisions and uncertainty. Which item is blocked? Which meeting needs preparation? Which promise lacks an owner? Which deadline is invented? Write the uncomfortable answer while there is still time to renegotiate.

Minutes 22–25: Time-box

Protect time for the work that requires concentration and add preparation or travel around fixed commitments. Leave slack. A calendar filled to capacity assumes nothing will take longer, nobody will interrupt, and you will never need to think.

# Weekly review — [date]

## Recover
[ ] Empty loose captures into the inbox
[ ] Process recent meeting and journal notes
[ ] Capture anything still being held in memory

## Evaluate
[ ] Review last week and the next two weeks of calendar
[ ] Review waiting-for items and promises to other people
[ ] Check every active project for a next action
[ ] Close, defer, delegate, or delete stale work

## Select
1. Weekly outcome:
2. Weekly outcome:
3. Optional outcome:

## Expose
Blocked:
Overcommitted:
Decision needed:
Conversation to have:

## Time-box
[ ] Protect focus blocks
[ ] Add preparation around fixed commitments
[ ] Leave unscheduled capacity

## End note
Monday's first visible action:

Adapt the review to the work you actually do

For software developers

Review open investigations, pull requests waiting on you, technical decisions that need a record, release risks, and one learning note worth promoting into project documentation. Keep the official status in the repository or tracker.

For product managers

Review customer evidence, decisions awaiting an owner, initiative risks, stakeholder promises, and the difference between your private follow-through list and the team roadmap.

For founders and business owners

Review customer commitments, cash-sensitive dates in the appropriate financial system, operating projects, hiring or vendor decisions, and the few conversations only you can move forward.

For writers and journalers

Review fragments worth developing, deadlines, research questions, revision lists, and patterns in the week’s journal. Do not turn every reflection into a task. Some writing is allowed to remain writing.

Use views to answer different review questions

A table is useful for missing fields and stale projects. A board shows work that is blocked or overloaded in one stage. A calendar makes genuine dates visible. A timeline shows collisions across longer work. These should be views of the same project records, not four separate plans that require manual reconciliation.

Cal Newport’s weekly productivity template video below offers a more calendar-centered perspective. The useful contrast is that a review and a schedule do different jobs: the review decides what deserves commitment; time blocking gives selected work a place to happen.

How to keep the review sustainable

• Use a timer. A review can surface deeper work without becoming the time to complete all of it.
• Keep a parking area. Interesting ideas do not need to become active projects.
• End with a restart point. Name Monday’s first visible action so the week begins with movement instead of another planning session.
• Miss without debt. If you skip a week, resume with the current reality. Do not recreate history to make the system look complete.

Mind Marshal can combine the Inbox, daily journal, project pages, task lists, and database views used in this review. It is strongest as a personal workspace. Team commitments should still be updated in the shared source of truth your colleagues rely on.