# Weekly Review Template

A review is not a verdict. It gives next week a more accurate starting point. Reserve 20 minutes, inspect evidence before explaining causes, and change one variable only. Do not include passwords, client data, sensitive health information, or unauthorised third-party details.

## Weekly Review — YYYY-Www

### Main Question

- Goal:
- One question this week:
- Acceptance criteria:
- Constraints (time, energy, responsibility):

### Evidence Inventory

- Completed:
- Work/recording/test location:
- First, assisted, and delayed-retest locations:
- External reader/user feedback:

| Evidence | What it shows | What it does not show yet |
| -------- | ------------- | ------------------------- |
|          |               |                           |

### Four Checks (0–2)

| Item                                             | Score | Reason and evidence |
| ------------------------------------------------ | ----: | ------------------- |
| Completion: was the task done?                   |       |                     |
| Quality: did it meet the standard?               |       |                     |
| Retention: can it be reproduced days later?      |       |                     |
| Transfer: does it work under changed conditions? |       |                     |

### Errors and Causes

| Error/barrier | Evidence | Likely cause | Next test |
| ------------- | -------- | ------------ | --------- |
|               |          |              |           |

### Energy and Recovery

- Effect of sleep/stress on performance:
- Unsustainable arrangement:
- What needs pausing or support:

### Change One Variable

- Keep:
- Stop:
- Adjust:
- Most important task and acceptance criteria:
- Next review date:

### Write Back Without Duplicating Records

Write back only what can change a decision. Do not copy the same paragraph into four files. Choose the file by its job:

- [Evidence Chain Template](https://byoungd.github.io/up/en/templates/evidence-chain): compare baseline, immediate performance, delayed retention, and transfer;
- [Rhythm Ledger](https://byoungd.github.io/up/en/templates/rhythm-ledger): keep this week's rhythm, capacity versions, repeated resistance, and next condition to change;
- [Learning State](https://byoungd.github.io/up/en/templates/learning-state): keep cross-session handover, unconfirmed facts, boundaries, and the smallest next task;
- [90-Day Cycle Map](https://byoungd.github.io/up/en/templates/90-day-cycle): keep phase gates, twelve weekly questions, and the direction of the cycle.

Evidence Chain updated: yes / no / not applicable\
Rhythm Ledger updated: yes / no / not applicable\
Learning State updated: yes / no\
90-Day Cycle Map updated: yes / no / not applicable\
Evidence location for the smallest next task:

## Handover Links

After the review, open only the files whose jobs apply: the [Evidence Chain Template](https://byoungd.github.io/up/en/templates/evidence-chain) compares four time points; the [Rhythm Ledger](https://byoungd.github.io/up/en/templates/rhythm-ledger) records this week's rhythm; [Learning State](https://byoungd.github.io/up/en/templates/learning-state) carries cross-session handover; the [90-Day Cycle Map](https://byoungd.github.io/up/en/templates/90-day-cycle) carries cycle gates.

Do not redesign the whole system after one poor week. Separate random variation from a pattern repeated at least three times; when a pattern persists, change the environment, task size, or support network first.

---

Source: [Life Level-up Guide](https://byoungd.github.io/up/en/templates/weekly-review) · Manuscript updated: 2026-09-01. Content: [CC BY-NC 4.0](https://creativecommons.org/licenses/by-nc/4.0/).