A weekly review should not feel like another task you failed to do.
If the template asks for wins, losses, feelings, lessons, habits, priorities, and a long reflection, you may do it once. Then the week gets messy, and the review is the first thing to disappear.
A useful weekly review template should be light enough to use on the week you least want to look at.
It only needs to answer one practical question:
What should change in next week's plan?
A weekly review is planning input
The mistake is treating a weekly review as a judgment of your discipline.
If you finished everything, the week was good. If you missed tasks, the week was bad. That framing makes people avoid the review exactly when they need it most.
Use a better standard.
A weekly review should show:
- what actually moved
- what did not move
- why work slipped
- what should stay, shrink, move, or stop
- what the next dated action should be
The goal is not to feel better about the week. The goal is to leave with a better plan.
If the same goal keeps slipping for more than a week or two, use a goal review checklist instead of moving the same task forward again.
The weekly review template
Use this once a week before you make the next weekly plan.
| Question | Short answer |
|---|---|
| What moved this week? | |
| What slipped? | |
| Why did it slip? | |
| What still matters next week? | |
| What should shrink, move, pause, or stop? | |
| What is the next dated action? |
Keep the answers short. One or two lines per question is enough.
If you prefer plain text, copy this:
What moved this week?
What slipped?
Why did it slip?
What still matters next week?
What should shrink, move, pause, or stop?
What is the next dated action?
Step 1: write what moved
Start with visible progress.
Do not only list completed tasks. Connect them to the goal they moved.
Weak review:
Finished outline.
Sent emails.
Worked out.
Better review:
Content goal: finished the outline for the next SEO article.
Launch goal: sent two user interview requests.
Health goal: walked for 30 minutes twice.
This helps you see whether the week moved your goals or only kept you busy.
Step 2: write what slipped
Next, list missed work without explaining it yet.
Content goal: did not write the first draft.
Launch goal: did not test the onboarding flow.
Health goal: missed one walk.
Keep this section factual. Missed work is planning data. It shows where the plan did not match reality.
Step 3: name why it slipped
Most missed work falls into a few patterns.
| Reason | What it means |
|---|---|
| Too large | The task was not small enough to start |
| No date | The task never had a real place in the week |
| Low priority | Another goal mattered more |
| Energy mismatch | The task needed more focus than the time slot allowed |
| Goal confusion | The goal itself may need review |
Write article slipping is different from write the intro paragraph slipping.
The first may mean the task was too large. The second may mean the time slot, priority, or energy was wrong.
Step 4: decide what changes next week
Do not automatically move every missed task forward.
Use four actions:
Keep: still important and realistic
Shrink: important but too large
Move: important but poorly scheduled
Stop: no longer worth carrying
For example:
Missed:
Write first draft.
Reason:
Too large.
Change:
Shrink to "write H2 sections and first 300 words on Tuesday."
That is a better next plan than simply moving write first draft to next week.
Example weekly review
Goal:
Publish one useful SEO article.
What moved?
- Researched five competing articles.
- Chose the primary keyword.
What slipped?
- The full draft was not written.
- Friday publishing did not happen.
Why did it slip?
- The task was too large.
- Wednesday evening was the wrong energy slot.
What still matters next week?
- Publish the article, but make the draft smaller.
What should change?
- Do not plan a full draft in one sitting.
- Split outline, first sections, examples, and edit into separate days.
Next dated actions:
- Tuesday: write the outline.
- Wednesday morning: write the first two sections.
- Thursday: add one concrete example.
- Friday: edit and publish.
The review turns a vague missed task into dated next actions.
If the whole goal has already fallen behind, start with how to get back on track with goals and rebuild only the next seven days.
How Aimo makes the review less dependent on memory
Weekly reviews are hard when you have to reconstruct the week from memory.
Aimo is designed around goal-linked execution records. When today's tasks are brought into Discord, you can mark what was completed or missed in the same place where the work was shown.
That gives the weekly review better inputs:
- which goal each task belonged to
- what was completed
- what slipped
- what needs to be replanned
The review becomes less about digging through memory and more about deciding what should change.
Summary
A weekly review template should not become another long task.
Use it to answer:
- what moved
- what slipped
- why it slipped
- what should change next week
- what the next dated action is
The best weekly review does not end with reflection. It ends with a better plan.