Change Management for Models
What This Requires
Implement change management process for model updates: require change ticket, peer review, testing evidence, and approval before deployment. Maintain change log with rationale, impact, and rollback plan.
Why It Matters
Uncontrolled model changes cause outages and regressions. Change management ensures accountability, traceability, and coordination across teams.
How To Implement
Change Ticket
Require ticket (Jira, ServiceNow) for all model changes. Include: change description, rationale (bug fix, performance improvement), impact assessment (affected systems, users), testing summary, rollback plan.
Peer Review
Require peer review for change ticket. Reviewer verifies: testing adequate, rollback plan clear, approval obtained, deployment window appropriate.
Approval Authority
Define approvers by change risk: low (team lead), medium (manager + ops), high (director + CISO). Emergency changes allowed with post-facto approval.
Change Log
Maintain change log (spreadsheet, wiki) with: date, version, description, approver, deployment status. Review log during post-incident reviews.
Evidence & Audit
- Change management policy document
- Sample change tickets with all required fields
- Peer review records and approvals
- Change log with recent entries
- Deployment records tied to change tickets