Use this one-page template to replace vague planning with a repeatable weekly check. Use it when your to-do list grows but results stay noisy.
The template is not a lifestyle doctrine. It is a practical audit loop: collect, filter, decide, assign, and carry forward.
Why this tool exists
A weekly review is different from a to-do cleanup. A cleanup only reduces backlog. A review changes quality by testing assumptions:
- Did I do what I thought mattered?
- Did I protect my attention or only increase surface busyness?
- Which commitments are still connected to my priorities, and which were added out of pressure?
When the answer is unclear, small weekly shifts become larger than they need to be.
Who should use it
Use this template if you:
- juggle multiple projects and always feel behind;
- keep resetting motivation but not priorities;
- over-collect tasks and under-complete outcomes;
- feel mental fatigue from undefined next steps.
If your environment is unstable, use a simplified version and keep this session to 5 minutes.
Fast start setup (5 minutes)
Before filling the template, complete these three actions:
- Open one list of commitments for the last 7 days.
- Set a timer for 20 minutes.
- Turn off notifications for the next 20 minutes.
Then copy the template below.
Weekly review template
```text 1) Week in one line What was the main result I wanted this week? Was it achieved? yes / no / partly
2) Completed commitments List 3 outcomes completed and 1 thing you did not expect to happen. For each: which action made it possible?
3) Not finished / postponed List 3 tasks still open. For each, choose one cause:
- too large
- unclear prerequisite
- waiting on someone else
- no longer valuable
- blocked by energy / health
4) Friction points What repeatedly blocked progress?
- context switching
- unclear decisions
- emotional overload
- unclear standards
5) Priority filter For the next week, choose 3 priorities only. For each: why does it matter this week and what is the cost of not doing it?
6) Choose one anchor action For each priority, define the smallest visible action for next week. Example format:
- Priority: finalize proposal
- Anchor action: draft executive summary (40 minutes)
7) Weekly commitments Name the commitments you keep and the one you drop.
- Keep: __________
- Keep: __________
- Drop: __________
8) Risks and boundaries What should not be promised next week?
- I cannot meet timeline X without extra support.
- I should limit late-night work because it reduces clarity.
- I will not start major new projects during this cycle.
9) Attention check Rate 0-10 each:
- focus stability
- decision clarity
- stress baseline
- relationship friction
- practical output
10) Carry-over and stop condition If one area is still messy, define the stop condition that ends work on it for now. ```
How to use the template
Step 1: collect without judgment
At first pass, do not edit. Just write facts, including failures.
Step 2: group by signal
Move each line under one of three signals:
- energy drain,
- impact,
- relational cost.
Step 3: reduce
Keep only 3 priorities and 3 anchor actions.
Step 4: protect the anchor
Give each anchor action one fixed slot on your calendar. If it moves, it is no longer an anchor.
Step 5: review in 10-minute chunks
At mid-week and week end, check only the top 3 anchors and one risk boundary.
Template adaptations
Use lighter versions depending on your operating mode:
- Starter version: only Sections 1, 2, 3, 5, 6, 7, 9.
- Team version: add collaborator name and dependency next to each blocked task.
- Creative version: add "idea quality" in section 1 and "idea quality blockers"
in section 4.
- Recovery version: cut anchors to one, add sleep and health boundaries in section 8.
Common mistakes and how to fix them
Too much logging
If you are writing 40 lines and never deciding, you are in data-gathering mode. Stop at "drop one commitment" and "keep one." Then return to action.
Mistaking urgency for importance
Urgent entries are often temporary. Importance is linked to your goals and values. Create a one-sentence reason for each of the three priorities.
Using review as emotional punishment
If review becomes self-criticism, switch the language from "failures" to "signals." You are auditing a system, not measuring your worth.
Ignoring blockers
If an item is repeatedly postponed due to external dependency, schedule a dependency conversation instead of repeating private "plan to do better."
Safety and boundaries
Use a gentler review when symptoms of overload are high. Stop the template and use a basic anchor action if you notice:
- sharp anxiety spike,
- sleep collapse,
- compulsive checklist behavior,
- isolation during review.
For high emotional load, add one more column called "support needed" and use it without delay.
If this work repeatedly increases shame or hopelessness, this is a sign to reduce the method rather than trying harder.
Suggested weekly rhythm
Monday: capture and classify. Wednesday: first anchor audit, no new priorities. Friday: final review of completed outcomes. Saturday/Sunday: no full review; optional 10-minute carry-over check only.
A concrete use example
You run a week with three parallel requests and one family commitment.
- 2 anchors selected: prototype review, client call prep, invoice follow-up.
- 7 pending tasks were grouped by cause.
- 1 commitment dropped because it depended on unavailable data.
- 1 risk boundary added: no email after 9:30 PM.
After one cycle, output stayed smaller, but completion clarity improved because the review had a real limit.
Final instruction
Use this template every week for 4 weeks. If you are not improving signal-to-effort after 4 cycles, switch to a simpler anchor-only review and return to this full template only when your system expands. No version is a magic move.