War-game a case mix freeze by proving each case weight class has a named owner, a measured age-out, and a reverse path before draft weights start governing every service-line claim.
Case mix freezes fail when "frozen" means a status without a decision artifact, when teams dual-count a draft weight as both approved and live, and when high-risk service lines still pin to one thin coder because the weight inventory is incomplete. The review needs one written inventory of weight classes, one owner who can deny a risky shortcut, and a documented consequence when a failed freeze ages past the deadline.
Name what the freeze actually changes
State which case families the freeze covers, the effective date, which case weights change, how versions are stored, and what happens to encounters already in flight. Name the service lines that feel it first and the cash promises that depend on coherent case mix handling. If the memo mixes a case mix freeze with a DRG validation ladder and a charge capture audit, split them.
Write the decision you will make if the war game finds nothing new. Also write the reverse criteria: the missed weight, cash gap, or payer deadline that would force a freeze rollback within a stated window.
What breaks first under load
- A high-dollar case class stays soft while the aggregate case mix dashboard stays green.
- Two teams claim the same weight ownership and neither can force a freeze at week end.
- A restore has already left an encounter without a trusted case weight state.
- The primary case mix export lags beyond the planned observation window.
- An operator skips a freeze gate because a month-end cutoff is near.
For each break, require detection time, cash impact, containment, and the authority to force a freeze rollback. Commands and export links belong in the runbook, not in a verbal promise that monitoring will catch it.
Evidence gate before commit
Feed Pingpong the freeze memo, the weight exhibits, and seating briefs for revenue integrity, coding, finance, and utilization review. First pass steelmans the freeze. Later passes attack from those seats. Final pass turns surviving objections into phased weight rules, mitigations, or a changed recommendation. Agreement across passes is not proof. Keep the objections that still have evidence gaps.
Pair with the revenue integrity lead seat, a DRG validation ladder, a charge capture audit, and a coding query backlog stress test. More operating decisions live in the war-game decisions hub.
Ship the freeze only when approved and blocked weight labels can be reproduced from stored case mix exports without a verbal override.