Next steps with owners, dates and a checkpoint

Implementation lives inside stage 4

The SAF process ends at communicate; there is no stage called implement. OpenStax's problem-solving steps end with implementation and feedback, and Smith's with follow-up — the same work, but in this course it is the next-steps section of stage 4, and the sixth R-psp-4 line marks it: next steps with owners and dates. Three things make a next step real: an action (a verb someone can do), an owner (a name, not a department), and a date. A fourth makes the list complete: a first checkpoint — the day on which a named measure is reviewed to see whether the recommendation is working, and by implication the day on which it could be changed.

Worked example — Lakeshore's list

1. Priya approves the lease route — Priya — by 22 November.
2. Wren requests three lease quotes, specifying a 3-year term with an upgrade clause and a service-level agreement — Wren Advisory — by 29 November.
3. Priya selects a vendor and signs — Priya — by 13 December.
4. Press installed and both operators trained by the vendor — the vendor and the operators — first fortnight of January.
5. Checkpoint: on-time delivery percentage reviewed against the 96 % benchmark — Priya and Wren — end of February.

Read the list against the risk table from L7.4: the upgrade clause and the SLA appear as specifications inside step 2, and the training window is step 4. That is what it means for mitigations to have owners — they become steps. And read it against the memo's deadline: the memo is due 15 November, the first step is a week later, and the checkpoint is six weeks after installation, long enough for the on-time figure to mean something.

What is not a next step

"Monitor the situation." No action a person can do on a day, no owner, no measure — it fails the line outright, and it is the sentence most stage-4 responses end with. "Implement the recommendation." An action, but the whole recommendation rolled into one step with no owner or date; the list exists to unroll it. "Ongoing review." A checkpoint that never arrives. The test for each line: could a reader, on the date named, ask the owner whether it was done and get a yes or a no?

The checkpoint is a promise to revisit

A checkpoint does two things. It fixes the measure the recommendation was made to move — on-time %, no-show %, average turnaround in days — so that success is not a matter of impression. And it fixes the date on which the analysis could be reopened: if on-time delivery is still under 90 % at the end of February, the memo has already said what happens next. A recommendation without a checkpoint is one the client can never know was right.

Write the clinic's

1. The dentists approve the move to online booking with reminders — the dentists — by 28 March. 2. Tomas obtains written quotes from the two shortlisted vendors, declining the referral bonus in writing — Tomas — by 11 April. 3. The dentists select and sign — the dentists — by 25 April. 4. Vendor onboarding for the receptionists in a quiet week; go-live the following Monday — Tomas and the receptionists — week of 12 May. 5. Checkpoint: no-show % and double-bookings per month reviewed against the 12 % and two-a-month baselines — Tomas to the dentists — 15 August.

Type the skeleton cold

The snippet is the shape: numbered lines, each action — owner — by date, and a final Checkpoint: measure reviewed on date. Once it is automatic, "monitor the situation" will look as incomplete to you as it does to the marker.