War-game a territory map freeze by proving each boundary class has a named owner, a measured age-out, and a reverse path before draft maps start governing every coverage claim.
Territory map freezes fail when "frozen" means a status without a decision artifact, when teams dual-count a draft boundary as both approved and live, and when high-risk territories still pin to one thin planner because the map inventory is incomplete. The review needs one written inventory of boundary classes, one owner who can deny a risky shortcut, and a documented consequence when a failed boundary ages past the deadline.
Freeze the map under review
State which territories the freeze covers, the effective date, which boundaries change, how versions are stored, and what happens to routes already in flight. Name the regions that feel it first and the coverage promises that depend on coherent map handling. If the memo mixes a territory map freeze with a route density cut and an area developer dispute, split them. A war game needs one move under fire at a time.
Write the decision you will make if the war game finds nothing new. Also write the reverse criteria: the missed boundary, coverage gap, or customer deadline that would force a freeze rollback within a stated window.
Seat the territory room
- Field ops. Boundary timing, age-out math, and what the coverage forecast hides if exceptions soften after the policy.
- Franchise ops. Owner lag, dual-counted maps, and the message that would leave orphan territories open past lock.
- Sales ops. Quota capacity, pipeline load, and relationship damage with area developers when maps jump overnight.
- Finance. Commission load, forecast promises that break in process, and the first ninety days of thinner remedies after a soft freeze.
- Skeptic. The claim that looks strongest and is least sourced.
Give every seat the same exhibits: open maps, boundaries in flight, protected territories, coverage commitments, and the age-out policy you intend to use. Private data for one seat invents agreement that will not survive the real room.
Pressure the soft boundaries
Feed Pingpong the freeze memo, the map exhibits, and the seating briefs. First pass steelmans the freeze. Later passes attack from field, franchise, sales, and finance seats. Final pass turns surviving objections into phased boundary rules, mitigations, or a changed recommendation. Agreement across passes is not proof. Keep the objections that still have evidence gaps.
Pair with the field ops lead seat, a route density cut, an area developer dispute stress test, and the franchise ops lead seat. More operating decisions live in the war-game decisions hub.
Ship the freeze only when approved and blocked boundary labels can be reproduced from stored map exports without a verbal override.