Tool 30 of 32
Checkpoint Review
The plan faces its numbers at three set points, on agendas fixed on day 10 so they cannot be dodged later.
At roughly day 40, 70 and 100, on agendas set in writing on day 10, in a fixed order that starts with numbers.
Step 7 of 7 · Around days 40, 70 and 100
Proof
Is it working?
You execute. Then, at roughly day 40, 70 and 100, the plan faces its numbers. The agendas are set on day 10 so they cannot be dodged later.
Why this step exists
Around week six every plan turns into a story unless something measurable is keeping it honest. Deep fixes are invisible while they are happening, and invisible work loses support. The plan needs a pulse everyone can see moving, and a room that looks at numbers before anyone narrates.
What you leave with
- Three checkpoint records against written numbers, including wherever the numbers are flat
- The baseline next to today, same source, same method
- The due forecasts next to what actually happened
- At day 100, whether the numbers everyone agreed to moved, measured, with nobody having to trust anybody's story
The usual miss
Letting the review become a progress narrative, rescheduling when the numbers look bad, or omitting the flat vitals so the table can tell a kinder story.
3 tools
Tool 31 of 32
Baseline Re-Measure
Every baseline number re-run the same way and shown next to today's, including the flat ones, because omission is the misuse this tool exists to prevent.
Inside each Checkpoint Review, against the vitals captured during the diagnosis window, same source, same method.
Tool 32 of 32
Ledger Read-Back
The due forecasts read out next to what actually happened, because the gaps are the fastest way to learn what the plan got right.
Inside each Checkpoint Review, after the re-measure, read by a neutral person, never by the forecaster.