War-game a pipeline definition freeze by testing whether stage capacity, review gates, and freeze deadlines still shrink soft renames when several sales surfaces share one schema and the next board forecast is close.
Pipeline definition freezes fail when "approved" means a checkbox without a decision artifact, when teams dual-count a draft as both reviewed and live, and when money-adjacent stage paths still pin to one thin glossary because the map is incomplete. The review needs one written inventory of stage classes, one owner who can deny a risky rename, and a documented consequence when a failed review ages past the deadline.
Assemble the freeze packet
List stage classes by surface, weekly rename volume, review gate, last freeze-skip reason, owner of record, and evidence required to keep the rule. Attach open findings, overdue drafts, and any emergency rename waiver in the last quarter. Name which classes are out of scope and why. If a finance-adjacent stage class is omitted, show the residual risk in the same packet.
Decide allow, revise, or hold in advance. Include the fields that compute overdue-review status so two reviewers reach the same label from the same exports.
Claim matrix
| Claim | Evidence required | Fail condition |
|---|---|---|
| Class is staffed | Named reviewer roster and measured time-to-freeze check | Roster is empty or still points to a single untested operator |
| Definition is complete | Schema export showing approved state for the claimed fields | Ticket closed while export still shows open |
| Priority is unique | Sample deals proving no double-booked stage | Priority invents uniqueness the glossary never enforced |
| Override is controlled | Logged use with time-bound restore of review | Shared override or unlogged use |
Walk four cases in Pingpong: a surface still pinned to one overloaded glossary, a rename that left a partner forecast live without revenue review, a class that mixed batch and interactive stages, and a request to skip a finance stage because volume is rare. Start from the documented freeze language. Ask who can extend a freeze window and which export proves review. Any step that depends on an unnamed person becomes a freeze condition.
Replay one prior rename incident under the proposed rules. If the incident would still age without a reverse owner, revise the rules before calling the freeze ready.
Pair with the revenue ops lead seat, a pipeline SLA review, and a pipeline 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.