Pretend you are the utilization review lead and force the utilization package to survive questions about who can freeze a length of stay target, how prior auth delays are timed across service lines, and which review classes still lack a named owner when the live sample disagrees with the slide.
This seat sits between utilization tools and the length health leadership will quote. It asks which stay trees invent completeness the page export never measured, which length targets look crisp on a slide and soft in the live sample, and what happens when a utilization exception lands because ownership is incomplete. A green length board does not answer those questions. The review needs the stay map, prior auth calendar, exception packet, and the named person who can freeze a utilization path.
Brief the seat with evidence, not slogans
Hand over the utilization tools in use, length scorecard draft, stay target plan, prior auth packet, last payer-visible length gaps, and one recent case where a delayed stay decision hurt a utilization narrative. Include which length promises still bypass the same review. State the decision: clear the utilization change, revise specific controls, or hold until a stay owner is named.
Boundaries matter. The utilization review lead can challenge untested stay trees, length windows that ignore measured lead time, exceptions without a kill switch, and override paths without logging. Clinical outcome ownership stays with attending clinicians. Spend ceilings belong in the same packet so a quiet dashboard does not hide a brittle utilization path.
Force answers that name owners
- Which critical stay class still lacks a tested length path with a measured age-out, and who owns the gap?
- What must hold before a length of stay target can promote into a lasting rule, and who can waive it without a written reason?
- How does a declined utilization exception become visible to the requester within the claimed window?
- What is the measured time from a failed prior auth finding to a human with freeze authority?
- Which shared override can ship many utilization changes without failing a single length health check?
- Who has authority to pause exceptions or force a utilization 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 utilization authority, force one named decision before the next tool change starts.
Turn objections into a stay ledger
Run the role in Pingpong with the same exhibits the utilization team will use. Have the home team answer each objection in writing. The useful output is a short utilization ledger: approved stay classes, blocked classes, length windows, and the person who can call a freeze.
For adjacent utilization work, pair this seat with a length of stay target, a prior auth backlog cut, the claims ops lead seat, and the clinic ops lead seat. The war-game decisions hub has more seats. Before approving the package, make the utilization review lead write the exact freeze and length check that will decide whether the change continues.