Crisis systems can be clinically strong and still fail because the contract design pushes the wrong behavior. If funding rewards occupancy, programs hold people too long. If payment is contact-based without continuity requirements, âreferralsâ replace real follow-up. If authorizations are slow or criteria are vague, the ED becomes the default waiting room. A workable model funds what actually stabilizes people: timely access, executable discharge readiness, and 7â30 day continuity with defined escalation routes. This article sits within Crisis Stabilization & Step-Down Pathways and applies Risk Management and Controls so contracts align incentives with safe flow and defensible outcomes.
Oversight expectations you have to design around
Expectation 1: Demonstrable system impact and appropriate level-of-care decisions. State agencies, counties, and Medicaid plans generally expect crisis investments to reduce avoidable ED use, reduce inpatient admissions that are not medically necessary, and improve time-to-follow-up after discharge. They also expect level-of-care decisions to be defensible and consistent, not driven by payment quirks or bed pressure.
Expectation 2: Audit-ready evidence that discharges were safe and continuity occurred. When a return, incident, or complaint happens, oversight looks for proof: what criteria were met, what controls were applied, who owned follow-up, and whether medication and safety actions were executed. Contracts that only require narrative reporting tend to fail under scrutiny.
Where funding models most commonly distort the pathway
Three distortions show up repeatedly. First, per-diem models without readiness gates can reward longer stays even when risk could be managed in step-down. Second, fee-for-service contact models can reward volume over completion, encouraging superficial follow-up. Third, authorization rules can create operational delay (waiting for approvals, unclear criteria), which pushes people into ED boarding or unnecessary inpatient admission. A strong contract anticipates these distortion points and funds the controls that prevent them.
Operational Example 1: Defining a crisis-to-step-down âbundleâ with required control completion
What happens in day-to-day delivery
The payer/commissioner defines a crisis episode bundle that begins at admission (or mobile diversion acceptance) and runs through a 30-day stabilization period. Payment is not just for the bed or the contact; it is contingent on completion of defined controls: (1) a documented triage and level-of-care rationale, (2) a discharge readiness bundle with verified appointment(s) and medication access plan, and (3) a stabilization cadence with minimum contact requirements and closed-loop escalation for missed follow-up. Providers submit a small set of auditable proof points (timestamps, appointment confirmations, medication verification, contact logs) rather than lengthy narrative reports.
Why the practice exists (failure mode it addresses)
This bundle exists to prevent âpayment for presenceâ without continuity. Crisis stabilization can look successful in the moment (symptoms reduce, discharge occurs), but without funded step-down controls, the system produces predictable short-interval returns. Bundling forces design attention toward the handoff and the first month, which is where most operational failure occurs.
What goes wrong if it is absent
Without a bundle definition, providers optimize for what gets paid. Per-diem pressures can extend stays; contact-only pressures can inflate low-value follow-ups; and the first-week post-discharge period becomes under-resourced. The ED and inpatient units then absorb the cost and risk of the failure, while crisis services appear âbusyâ but ineffective.
What observable outcome it produces
A well-specified bundle produces measurable outcomes: higher rates of verified follow-up, fewer 7â30 day returns, reduced ED boarding linked to slow step-down, and stronger audit defensibility. Evidence includes bundle completion rates and trend improvements in return rates and time-to-follow-up.
Operational Example 2: Authorization and eligibility rules designed for real-time decision-making
What happens in day-to-day delivery
The contract establishes real-time authorization rules for crisis stabilization and step-down. For example: presumptive eligibility for a short stabilization stay with retrospective review, a defined set of triage criteria that staff can apply 24/7, and a rapid escalation route for exceptions. Rather than requiring multiple prior authorizations, the model uses standardized documentation (risk formulation, medical screen results, disposition rationale) that can be reviewed quickly. Contracts specify response times for payer decisions and clarify what happens if response times are missed (e.g., automatic temporary authorization to prevent ED boarding).
Why the practice exists (failure mode it addresses)
This practice exists to prevent operational delay becoming a clinical event. In crisis, time is part of safety. Slow approvals and unclear criteria lead to holding people in the wrong setting, missed opportunities for safe diversion, and unnecessary escalation to inpatient because it is administratively easier.
What goes wrong if it is absent
Without real-time rules, staff waste time chasing authorizations, people wait in ED, and crisis units fill with âpending approvalâ cases. The system becomes risk-averse and defaults to the setting with the least administrative friction, not the best clinical match. This increases cost and worsens outcomes while eroding trust between providers and payers.
What observable outcome it produces
Real-time authorization design produces measurable outcomes: reduced ED boarding days, faster access to crisis stabilization, fewer inappropriate inpatient admissions, and clearer evidence for retrospective review. Evidence includes authorization turnaround metrics and decreased âadministrative delayâ findings in case audits.
Operational Example 3: Pay-for-performance tied to control reliability, not raw volume
What happens in day-to-day delivery
The contract includes a small performance component tied to reliability of key controls: 72-hour follow-up completion, verified medication access, confirmed first outpatient appointment attendance (or documented recovery actions when missed), and reduced 7/30-day returns adjusted for risk banding. Providers meet targets through operational changesâbooking follow-up before discharge, implementing missed-contact recovery sequences, and using early warning thresholdsânot by increasing superficial contact counts. Performance reporting uses clear definitions and requires a sample-based audit right so payers can validate that âcompletedâ means completed.
Why the practice exists (failure mode it addresses)
This approach exists to prevent gaming and to focus improvement on execution. If incentives are tied to raw volume, providers can increase contacts without improving outcomes. Tying incentives to reliability of controls pushes the system toward the practices that actually reduce returns and incidents.
What goes wrong if it is absent
Without performance tied to controls, underperformance persists because there is no structured financial reason to invest in follow-up infrastructure, data capture, or after-hours escalation. Commissioners then respond with heavier reporting requirements, which increases burden without improving outcomes because the underlying design incentives remain misaligned.
What observable outcome it produces
Control-based performance measures produce measurable outcomes: improved follow-up timeliness, fewer medication-related returns, and reduced short-interval re-presentations. Evidence includes verified KPI trends and audit samples showing that documentation matches reality.
Assurance mechanisms that make contracts defensible
High-functioning contracts are built for audit. They specify clear definitions (what counts as follow-up, what âverifiedâ means), require small proof points (timestamps, confirmations), and embed the right to sample and validate. They also require a learning loop: monthly review of returns and pathway failures, with documented changes and re-testing. When these mechanisms exist, performance conversations become specific and constructive rather than adversarial.
Funding does not just buy capacity; it shapes behavior. When payment design funds readiness, continuity, and accountable step-down, crisis stabilization becomes a true pathway and the ED stops functioning as the backstop for contract misalignment.