War-game a headcount freeze rule by proving each role class has a named owner, a measured exception window, and a reverse path before the calendar starts governing every hiring claim.
Headcount freeze rules fail when "frozen" means a status without a decision artifact, when teams dual-count a draft exception as both approved and live, and when high-risk role paths still pin to one thin roster because the map is incomplete. The review needs one written inventory of role classes, one owner who can deny a risky shortcut, and a documented consequence when a failed exception ages past the deadline.
Map the rule before seating
List role classes by team, exception window, owner roster, last skip reason, owner of the line, and evidence required to keep the claim. Attach open findings, overdue backfills, and any emergency waiver in the last quarter. Name which classes are out of scope and why. If a production role class is omitted, show the residual risk in the same packet.
Decide allow, revise, or hold in advance. Include the fields that compute overdue-exception status so two reviewers reach the same label from the same exports.
Decision gates
- Roster proof. Every critical class has at least two named owners who completed a timed dry run in the last quarter.
- Exception proof. Exports show when each exception expires and who receives the overdue alert.
- Backfill proof. Logged backfills list owner, expiry, and restore path; shared overrides fail the gate.
- Conflict proof. No hiring manager certifies their own standing exception without a second set of eyes.
- Abort proof. A named person can freeze exceptions at week end without waiting for the system owner.
Run four cases in Pingpong: a team still pinned to one overloaded hiring manager, an exception that left an offer live without people review, a class that mixed contractors and full-time roles, and a request to skip a production class because volume is rare. Start from the documented rule language. Ask who can extend an exception window and which export proves completion. Any step that depends on an unnamed person becomes a freeze condition.
Replay one prior freeze incident under the proposed rules. If the incident would still age without a reverse owner, revise the rules before calling the freeze ready. Compare with the broader headcount freeze war game when the rule sits inside a company-wide pause.
Pair with the people ops lead seat, a comp band rewrite stress test, and an equity refresh ladder review. 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.