Stress-test an appointment no-show spike by proving that each hold window and restore rule can place open slots inside the planned lane, survive override pressure, and avoid trapping schedulers inside a green fill-rate slide that hides long-lived empty chairs.
Appointment no-show spikes often list a surge plan while leaving restore behavior, override authority, and abort ownership implicit. Those edges decide whether a late cancellation stays inside the spike packet or leaves a broken access path live under peak load. The exercise should follow actual clinic timelines, slot maps, and escalation paths rather than a clean fill-rate deck.
Map the spike path
List every appointment class with its hold window, waive rule, override behavior, owners, and notification channels. Mark paths that cannot reverse without a manual amendment. Attach the last three appointment no-show incidents with raw timelines and any waivers. Include the source of truth for open slot counts during the observation window.
Define the phases for detect, hold, divert, abort, and restore. Each phase needs an owner and an exit condition. Write the point after which a stuck empty chair would require a different procedure, then review whether that action is still permitted. Capture maximum acceptable dwell in measurable units, including which clinics are excluded from the spike path and why.
Include the calendar of known events for the next two quarters: flu season peaks, provider leaves, and credential freezes that shrink the usable hold window. A spike budget that ignores those dates will look calm until the week they land.
Break drills
- A minority high-volume clinic keeps a side-channel while the aggregate no-show dashboard stays green.
- A restore has already left a slot surface without a trusted appointment state.
- The primary no-show dashboard lags beyond the planned observation window.
- An operator skips a hold gate because a patient cutoff is near.
- Automated and human divert messages collide under the new spike rule.
- Abort authority is unclear at week end and the update lands on the wrong amendment.
For each drill, identify detection time, access impact, containment, and the authority to force a spike rollback. Require commands and dashboard links in the runbook. A claim that monitoring will catch it does not establish which alert fires or who receives it.
Show timing and ownership
Run the package in Pingpong with clinic, scheduling, patient access, and finance seats. Ask clinic which access decision becomes unsafe first if holds still stick after the claimed window. Ask scheduling whether slot macros can absorb a forced override. Ask owners to show the exact appointment version or export used as the exit condition.
Related reviews include the clinic ops lead seat, a room utilization freeze, a provider credential ladder, and a healthcare ops change stress test. Browse the war-game decisions hub for adjacent controls.
Authorize the published appointment no-show spike path only after a timed drill restores usable slot hygiene inside the documented budget without an undocumented manual step.