Checkpoint calendars that vendors actually follow

Vendors respond to rhythms. We coach teams to publish a twelve-week checkpoint calendar with three speeds: read-only reviews, evidence submissions, and joint working sessions. Each speed has a default response window so nobody invents SLA language on the fly.

We also separate commercial threads from control threads. Mixing them creates ambiguous email chains. The calendar carries control threads only, with a footnote pointing procurement to their own system.

During workshops, teams rehearse declining out-of-band requests politely. The phrase bank is short and boring on purpose. Boring language keeps tone steady when schedules slip.

We close with a retrospective template that asks what to keep, not what went wrong. Morale matters for long programs, and retrospectives should not become blame sessions.