War-game an audit evidence pack by proving each control class has a named collector, a measured sample window, and a reverse path before the calendar starts governing every audit claim.
Audit evidence packs fail when "complete" means a checkbox without a decision artifact, when teams dual-count a draft sample as both collected and live, and when high-risk control paths still pin to one thin roster because the map is incomplete. The review needs one written inventory of control classes, one owner who can deny a risky shortcut, and a documented consequence when a failed sample ages past the deadline.
Map the pack before seating
List control classes by system, sample window, collector roster, last skip reason, owner of record, and evidence required to keep the claim. Attach open findings, overdue samples, and any emergency waiver in the last quarter. Name which classes are out of scope and why. If a production control class is omitted, show the residual risk in the same packet.
Decide allow, revise, or hold in advance. Include the fields that compute overdue-sample status so two reviewers reach the same label from the same exports.
Decision gates
- Roster proof. Every critical class has at least two named collectors who completed a timed dry run in the last quarter.
- Sample proof. Exports show when each sample expires and who receives the overdue alert.
- Exception proof. Logged exceptions list owner, expiry, and restore path; shared overrides fail the gate.
- Conflict proof. No collector certifies their own standing control without a second set of eyes.
- Abort proof. A named person can freeze samples at week end without waiting for the system owner.
Run four cases in Pingpong: a system still pinned to one overloaded collector, a sample that left partner evidence live without compliance review, a class that mixed interactive and service controls, and a request to skip a production class because volume is rare. Start from the documented pack language. Ask who can extend a sample window and which export proves completion. Any step that depends on an unnamed person becomes a freeze condition.
Replay one prior audit incident under the proposed rules. If the incident would still age without a reverse owner, revise the rules before calling the pack ready.
Pair with the compliance ops lead seat, a control owner map review, and a policy exception ladder stress test. More operating decisions live in the war-game decisions hub.
Close only when approved and blocked labels can be reproduced from stored exports without a verbal override.