SECAI Core · phase 15 of 15
Change control system
A collection of formal, documented procedures for changing official project documents and how project deliverables will be controlled, changed, and approved.
The Explain card
- Plain English
- A change control system is the formal, documented set of procedures for proposing, reviewing, approving and recording changes to project documents and deliverables, so nothing changes without a record.
- Example
- A team wants to swap their production model for a newer version. Change control requires a risk assessment, safety evaluation results, a rollback plan and sign-off from security before the switch is scheduled.
- Why it matters
- Model swaps, prompt edits and data source changes can alter behaviour dramatically. Change control keeps these reviewed, traceable and reversible, and helps investigators answer "what changed?" after an incident.
- Hook
- No change without a paper trail.
Where it sits in the deck
Phase 15: MLOps, Continuous Delivery, and Operational Resilience
Close the loop — operational practices, drift management, and delivery discipline that keep deployed AI systems healthy, current, and continuously improving.
