The checking loop
Two new meetings, and what changed because of them.
When something new arrives, the loop checks it against every page before anything is sent. One fact changes in one place, and every page follows. This is what happened between Friday 22 January and Friday 29 January 2027.
The loop at a glance
Drop it in, and every page follows
1New input arrives
Drop in transcripts, emails and documents
T4Business banking workshopTranscript, Tue 26 Jan T5Steering catch-upTranscript, Thu 28 JanAlready in: three transcripts, four emails and three process documents.
2The Change Partner works
- Ingest the new input
- Extract facts, decisions and questions
- Check against every artefact
- List what changes
- Update the artefacts
- Update the changelog and actions
- Delete answered questions
- Run the checks
All eight checks passed
3Every affected output updates
- Stakeholder listRichard Vance moves to ConditionalUpdated
- Risk register12 risks become 14Updated
- Go/no-go checklist14 criteria become 16Updated
- Action list23 actions become 28Updated
- Open questionsQ-05 answered, Q-07 addedUpdated
- Training scheduleEarly, late and make-up sessionsUpdated
- Comms planBankers message addedUpdated
- Learning planMatches the new trainingUpdated
- Change on a pageGate moves to Fri 9 AprUpdated
- Phased rolloutGate moves to Fri 9 AprUpdated
- UAT scheduleNew dependency before UATUpdated
- Detailed change planRaised to v0.2Updated
- Weekly status reportA new report for the weekUpdated