Pretend you are the SNF ops lead and force the skilled nursing package to survive questions about who can freeze a rehospitalization ladder, how census caps are timed across units, and which override classes still lack a named owner when the live sample disagrees with the slide.
This seat sits between SNF tools and the transfer narrative leadership will quote. It asks which rehospitalization trees invent completeness the page export never measured, which census windows look crisp on a slide and soft in the live sample, and what happens when a caregiver backup rule lands because ownership is incomplete. A green SNF board does not answer those questions. The review needs the transfer map, census calendar, override packet, and the named person who can freeze a SNF path.
Bring exhibits, not slogans
Hand over the SNF tools in use, rehospitalization ladder draft, census cap review plan, override packet, last payer-visible transfer gaps, and one recent case where a delayed freeze hurt a SNF narrative. Include which SNF promises still bypass the same review. State the decision: clear the SNF change, revise specific controls, or hold until a transfer owner is named.
Boundaries matter. The SNF ops lead can challenge untested rehospitalization ladders, census windows that ignore measured lead time, exceptions without a kill switch, and override paths without logging. Clinical outcome ownership stays with treating clinicians. Spend ceilings belong in the same packet so a quiet dashboard does not hide a brittle SNF path.
Authority questions worth answering in writing
- Which critical transfer class still lacks a tested freeze path with a measured age-out, and who owns the gap?
- What must hold before a rehospitalization ladder can promote into a lasting policy, and who can waive it without a written reason?
- How does a declined census exception become visible to the requester within the claimed window?
- What is the measured time from a failed transfer finding to a human with freeze authority?
- Which shared override can ship many SNF changes without failing a single rehospitalization health check?
- Who has authority to pause exceptions or force a SNF rollback at week end without waiting for the system owner?
Require observed, inferred, or unknown labels. Observed claims need a source. Unknowns become owners and due dates. When two teams claim the same SNF authority, force one named decision before the next tool change starts.
Leave a SNF ledger
Run the role in Pingpong with the same exhibits the SNF team will use. Have the home team answer each objection in writing. The useful output is a short SNF ledger: approved transfer classes, blocked classes, freeze windows, and the person who can call a freeze.
For adjacent SNF work, pair this seat with a rehospitalization ladder, a census cap review, a home health hand-off, and the care management lead seat. The war-game decisions hub has more seats. Before approving the package, make the SNF ops lead write the exact freeze and transfer check that will decide whether the change continues.