War-game a menu allergy rewrite by proving each allergy lane has a named owner, a measured age-out, and a reverse path before draft labels start governing every tray.
Menu allergy rewrites fail when "allergy-safe" means a status without a decision artifact, when teams dual-count a draft label as both aspirational and live, and when high-risk allergen families still pin to one thin production desk because the lane inventory is incomplete. The review needs one written inventory of allergy lanes, one owner who can deny a risky shortcut, and a documented consequence when a failed label ages past the deadline.
Freeze the allergy inventory
State which allergen classes the rewrite covers, the effective date, which label lanes change, how versions are stored, and what happens to trays already in flight. Name the units that feel it first and the safety promises that depend on coherent allergy handling. If the memo mixes a menu allergy rewrite with a trayline backup rule and an NPO status mismatch, split them.
Write the decision you will make if the war game finds nothing new. Also write the reverse criteria: the missed lane, allergen gap, or meal deadline that would force a menu allergy rewrite rollback within a stated window.
| Allergen lane | Owner | Age-out | Reverse path |
|---|---|---|---|
| Common allergen set | Named dietary charge | Measured minutes | Documented hold |
| High-risk dual path | Dietary ops | Measured minutes | Documented restore |
| Cross-contact bridge | Quality lead | Measured minutes | Documented re-route |
Fill the table from stored exports, not from memory. Empty cells are blockers, not notes for later.
Allergy break points
- A high-risk allergen class stays soft while the aggregate menu dashboard stays green.
- Two teams claim the same lane ownership and neither can force a freeze at week end.
- A restore has already left a tray without a trusted label state.
- The primary allergy export lags beyond the planned observation window.
- An operator skips a label gate because a meal cutoff is near.
- Allergy claims lack a stored exhibit at release time.
For each break point, require detection time, unit impact, containment, and the authority to force a menu allergy rewrite rollback. Commands and export links belong in the runbook.
Hostile seats on the allergy labels
Feed Pingpong the rewrite memo, the lane exhibits, and seating briefs for dietary, nursing, quality, and infection control. First pass steelmans the rewrite. Later passes attack from those seats. Final pass turns surviving objections into phased lane rules, mitigations, or a changed recommendation. Agreement across passes is not proof. Keep the objections that still have evidence gaps.
Pair with the dietary ops lead seat, a trayline backup rule, an NPO status mismatch stress test, and the quality ops lead seat. More operating decisions live in the war-game decisions hub.
Ship the rewrite only when approved and blocked allergy labels can be reproduced from stored allergy exports without a verbal override.