The one-page plan before the spreadsheet
| Field | Question answered | Educational example |
|---|---|---|
| Hypothesis | What are we trying to improve? | Add incline-press repetitions without losing the row |
| Review window | When do we sit down and decide? | Six weeks for scheduling, not physiological superiority |
| Anchors | Which movements must stay comparable? | Incline press, chest-supported row and squat |
| Progress variable | What changes when a set goes well? | Repetitions first, then load inside the range |
| Limits | What will not happen automatically? | No new sets merely because a week starts |
| Exit | Which signal closes or changes the block? | Goal met, persistent fatigue, pain or new context |
It is tempting to call six coloured weeks a mesocycle. The label adds little when week five cannot be compared with week two. A hypothesis fixes that: it names an improvement visible in the log and protects two or three anchors so the block produces information, not just fatigue.
- Write one hypothesis
Name an observable improvement and one limit. “More repetitions at similar RIR without adding sets” can be reviewed; “grow more” cannot.
- Protect two or three anchors
Keep movements comparable while they remain tolerable and useful so the log retains context.
- Choose one progress variable
Decide whether repetitions, load or execution moves first. Avoid pulling several levers in one exposure.
- Reserve the review date
The calendar creates a decision point; it does not prove that the block must end that day.
- Define the exit before starting
Goal met, persistent fatigue, pain or changed context should be able to close or modify the block.
A six-week example without automatic volume escalation
| Week | Main job | What may progress | Closing question |
|---|---|---|---|
| 1 — Reference | Anchor exercises and conservative volume | Nothing by obligation; log well | Which load and RIR are genuinely repeatable? |
| 2 — Repeat | Same map | One repetition when effort remains in range | Do technique and duration hold? |
| 3 — Build | Same anchors | Load only after owning the top of the range | Does the goal advance without the rest worsening? |
| 4 — Confirm | Avoid novelty | Holding can also be a decision | Was that progress or one unusually good day? |
| 5 — Last useful exposure | Repeat key conditions | One small advance if the signal is clear | Is fatigue accumulating, or are we simply bored? |
| 6 — Review | Reduce, hold or close according to context | Do not chase a record at any cost | Continue, adjust one element or end? |
The example does not require a deload in week six or added load every seven days. If week two already shows that a movement irritates a joint, the calendar does not outrank safety. If everything progresses and recovery is sound, the review may conclude that very little should change. The ending exists to make a decision, not to dramatise supposed “resensitisation”.
A well-written hypothesis
“For six weeks we will keep incline press and chest-supported row, seek more repetitions at comparable RIR, and avoid adding sets unless three exposures show room and stable recovery.” That beats “hypertrophy phase: increase volume” because it names what to observe and which action is prohibited until a signal exists.
Review traffic light: continue, adjust or exit
| Signal | Prudent reading | Smallest action |
|---|---|---|
| Repetitions or load rise at similar RIR | The exposure is progressing | Keep anchor and structure |
| One exercise stalls while others do not | A local issue, not a failed block | Review order, execution or that selection |
| Several exercises fall and recovery worsens | Fatigue or context deserves attention | Reduce demand and review sleep, stress and adherence |
| Everything works but boredom appears | A relevant preference, not proof of failure | Change only if adherence improves and comparison survives |
| Pain or symptoms | Outside editorial diagnosis | Stop the movement and seek advice |
| Goal met | The hypothesis has answered | Close, document and choose the next block |
The exercise-variation review is small: eight studies and 241 young men. It suggests deliberate variation may make sense and random rotation may compromise adaptation, but it cannot authorise a universal change calendar. Our favourite rule is less exciting: keep an anchor while it still answers a question, and replace it when a concrete reason appears.
BUSTAFIT as the block notebook, not an autopilot
| Element | Data | Future decision |
|---|---|---|
| Anchor | Load, repetitions and RIR | Hold or progress |
| Last useful reference | Recent comparable exposure | Avoid rebuilding each session from zero |
| Weekly volume | Sets actually completed | Separate the plan from execution |
| Short external note | Sleep, travel, pain or schedule change | Separate context from programming failure |
BUSTAFIT’s official listing documents routines, load, repetitions, RIR, history and practical progression context on iPhone. It does not claim to generate mesocycles, add sets by itself or prescribe a deload. We would use it as a good log should be used: so week six remembers what really happened in week one.