PrerequisiteCompleted Module 6 (Evaluation), with a complete evaluation report and confounder disclosure
0 / 2 completed
Learning objectives
Actually drill disable, recovery, and revocation, recording how long each takes and any gaps found.
Design an exception-handling process: who can approve an exception, and how its scope and expiry are recorded.
Judge whether the governance review confirms the pilot has the governance foundation needed to enter the Adoption Gate discussion.
Drill disable, recovery, and revocation
60 min
Three governance drills
Module 1 defined stop authority, and Module 5 may already have drilled an anomaly response once during the pilot. Human-AI governance review requires the team to systematically drill three governance actions and record actual timing, rather than merely claiming in a document that "it can be disabled anytime."
Three governance drills and what to record
Drill type
Drill content
What to record
Disable
Immediately stop AI auto-replies, fully revert to the manual workflow
Time from the command to it actually taking effect; whether any cases got stuck mid-state
Recovery
Restore AI assistance from a disabled state, confirming data and state consistency
Whether a version re-verification is needed after recovery; any data loss or duplicate processing
Revocation
Revoke access for a specific account or tool
Time for revocation to take effect; whether access is still possible through another path
Warning
Common mistake: only ever drilling "how to turn it on" and never actually drilling "how to turn it off." Disable and revocation often involve cross-system operations, and the first real drill frequently reveals a gap between what the process document says and what actually happens in the system: which is exactly the point of drilling.
Key takeaway: A disable, recovery, or revocation mechanism that has never actually been drilled cannot be counted as ready; the drill itself is the evidence governance review needs.
Exception handling and the governance conclusion
60 min
Exception handling and the governance conclusion
Every governance system needs a way to handle "this situation is outside the original design, but it is urgent." A system with no explicit exception process is often quietly bypassed exactly when an exception is genuinely needed, which defeats its governance purpose.
Required fields for exception handling
Field
Description
Approver
A named person or specific role, and never the same person who requested the exception
Exception scope
Precisely which cases or which functions the exception applies to: never a blanket "relax everything"
Expiry
The exception must have an explicit expiry date and lapse automatically, requiring re-approval to continue
After-the-fact review
The governance reviewer re-checks after the exception ends, confirming it stayed within the approved scope
1Exercise: governance review summary (using SYN-CS-001) Complete a governance review summary as a precondition for entering Module 8's adoption redesign.
2Step 1: fill in the three drill results Write one real drill record for disable, recovery, and revocation, each including timing and any gap found.
3Step 2: draft an exception scenario Assume "during a peak-time system delay, the customer-service supervisor temporarily requests loosening the confidence threshold," and write a full record following the required exception-handling fields.
4Step 3: governance conclusion Based on the drill results, judge whether the current governance mechanism is sufficient to support entering the Adoption Gate discussion, or whether blocking gaps still need to be closed first.
Info
The governance review's conclusion is not a binary pass/fail: it should clearly state which governance capabilities have been validated and which remain gaps, so Module 9's executive briefing can honestly present risk instead of hiding unresolved governance issues.
Check yourself
A customer-service supervisor temporarily requests, during a peak-time delay, "let's loosen the confidence threshold for now so the AI can handle more cases." Per this module's exception-handling principles, which approach is most appropriate?
Key takeaway: Exception handling without scope, expiry, and after-the-fact review becomes a back door around the governance system.
