Personnel Rotation (6–12 Month Cycles) Personnel responsible for daily oversight tasks (reviewing dashboards, triaging alerts, conducting operator oversight) rotate on a 6–12 month cycle. A new person brings a fresh perspective: they notice anomalies the previous person had normalised, ask questions about processes the previous person had stopped questioning, and identify documentation gaps the previous person had worked around. The AI Governance Lead plans the rotation schedule in advance, with a handover period including knowledge transfer and a documented handover checklist. The handover prevents knowledge loss while ensuring the incoming person approaches the system with fresh eyes. Key outputs

• 6–12 month rotation cycle for oversight personnel
• Planned handover with documented checklist
• Fresh perspective counteracting normalisation of deviance
• Module 7 AISDP documentation

Quarterly Threshold Drift Checks Quarterly threshold drift checks compare current operational thresholds (in monitoring configuration, CI pipeline gates, and alert rules) against the values documented in the AISDP. Over time, teams may informally adjust thresholds upward to reduce alert volume, with each adjustment individually reasonable but cumulatively reducing sensitivity to genuine problems. Any discrepancy must be either reverted to the documented threshold or formally approved by updating the AISDP with the new threshold and the rationale. Threshold drift checks are conducted by a person who was not involved in the threshold adjustments, providing independent verification. Key outputs

• Quarterly comparison of operational thresholds against AISDP values
• Discrepancies reverted or formally approved with AISDP update
• Independent verification by non-involved personnel
• Module 7 and Module 12 AISDP evidence

“Fresh Eyes” Reviews Scheduled “fresh eyes” reviews bring personnel not involved in daily operations into a periodic deep-dive. An internal auditor, a team member from a different system, or an external consultant reviews the monitoring data, evidence repository, non-conformity register, and governance meeting minutes with no prior context. Fresh eyes reviewers often reveal systemic issues that the operational team has normalised: thresholds that have drifted, non-conformities that have been open for months without remediation, documentation that no longer matches the deployed system’s configuration, or governance processes that have become perfunctory. Findings are documented and entered into the Non-Conformity Register. Key outputs

• Periodic deep-dive by non-operational personnel
• No-prior-context review of monitoring, evidence, and governance
• Normalised systemic issues surfaced
• Findings entered into Non-Conformity Register