Change control, threshold updates and re-approval paths when performance shifts
Define how monitoring findings become controlled model changes, who approves each change and what evidence is required before production use resumes.
Sept. 7, 2026 ยท Cicrim
Performance shifts do not always require a model replacement, but they always require a controlled decision. Threshold adjustments, feature changes, recalibration and workflow changes should follow an approval path proportionate to their risk and customer impact.
Classify changes before they reach production
A clear change taxonomy prevents minor maintenance from becoming a bottleneck while ensuring material changes receive independent challenge and approval. The classification should consider model behavior, affected products, customer impact and regulatory significance.
- Routine changes: Documentation or operational updates that do not change model behavior or decision outcomes.
- Threshold changes: Adjustments to alerts, cutoffs or tolerances that can alter review volume or risk exposure.
- Material changes: Recalibration, new variables, policy changes or integrations that can affect model performance or customer treatment.
- Emergency changes: Temporary controls used to contain a material issue while full analysis and approval continue.
Make re-approval evidence explicit
Each change record should include the trigger, analysis, test results, affected controls, implementation plan, rollback criteria and approvals. Monitoring requirements after release should be established before the change is deployed.
A practical re-approval path
- Document the monitoring event or business trigger.
- Classify materiality and identify required reviewers.
- Test performance, fairness, policy alignment and operational impact.
- Approve the change, implementation window and rollback plan.
- Confirm post-release monitoring and formally close the record.