Crisis continuums are frequently judged on utilization: calls answered, visits completed, beds occupied. But utilization is not the same as capacity reliability. If contracting only pays for encounters, systems will underfund readiness, supervision, surge staffing, and barrier removal—exactly the mechanisms that keep capacity usable when demand rises. The result is predictable: “paper capacity,” ED overflow, and staff burnout. Crisis continuum capacity planning must be paired with contracting that funds readiness and throughput as explicit deliverables, aligned to crisis response models so the model can actually operate at scale rather than collapsing into emergency default pathways.
Funding is not a separate topic from operations. Funding logic shapes operations every day: how many staff are on shift, whether supervision exists, whether follow-up is protected, and whether surge protocols are real. If you want reliable diversion and stabilization, you must pay for the operating conditions that make it possible.
Two oversight expectations contracting must meet
Expectation 1: Evidence of readiness, not just activity. Funders and system leaders increasingly expect that crisis services can demonstrate readiness across peak hours, weekends, and seasonal surges—supported by staffing plans, governance triggers, and measurable response capacity. Contracts should specify readiness requirements and how they will be verified.
Expectation 2: Accountability for outcomes and safety under pressure. Oversight partners expect contracts to include performance expectations that reflect safety and stability: reduced avoidable ED use, reduced repeat crises, and consistent decision quality. They also expect mechanisms to detect and correct drift (for example, unplanned restriction of access or reduced follow-up) rather than rewarding volume alone.
Why “pay per encounter” undermines capacity reliability
Encounter-based models push providers to maximize billable units while minimizing non-billable readiness work: training, supervision, QA, surge drills, discharge coordination, and barrier removal. In a crisis continuum, these “overheads” are not optional; they are the controls that prevent failure. A stable contract model therefore separates three things: (1) readiness and baseline coverage, (2) variable response delivery, and (3) performance/outcome incentives that reinforce the crisis model.
Practical contracting also accounts for the system nature of crisis work. A mobile visit may prevent an ED admission; a follow-up call may prevent a repeat crisis contact. If the contract only pays for what is easily counted, it underpays the work that prevents avoidable escalation.
Operational example 1: A readiness retainer tied to coverage and competency controls
What happens in day-to-day delivery
A county contract includes a monthly readiness retainer that funds baseline coverage: minimum staffing by role across specified hours, on-call supervision response times, and competency maintenance (required training hours and sign-offs for high-risk decision roles). The provider submits a monthly readiness packet: coverage rosters, vacancy/absence reports with mitigation actions, training completion logs, and supervision access audits (including response-time sampling). Readiness payments are not reduced because demand is low; they exist to ensure the system can absorb demand when it spikes. If readiness standards are not met (for example, repeated shifts below decision-safe minimums), a corrective action plan is triggered rather than silently tolerating drift.
Why the practice exists (failure mode it addresses)
This exists to prevent “staffing to volume,” where providers cut coverage during quiet periods and cannot surge safely when demand rises. Without a readiness-funded baseline, services become brittle, response times degrade, and the system defaults to ED/law enforcement because the community continuum cannot reliably staff the model.
What goes wrong if it is absent
If there is no readiness retainer, providers are pressured to minimize staffing and supervision. Training and QA are treated as luxuries. The failure presents as inconsistent triage and placement decisions, limited weekend coverage, and rapid staff turnover because working conditions are unstable. When surges occur, the service cannot scale safely, and system partners lose trust in community diversion pathways.
What observable outcome it produces
A readiness retainer produces measurable reliability: fewer shifts operating below minimum safe coverage, faster supervisor response times, and reduced variance in decision-making across shifts. Over time, systems see fewer surge-related failures and more stable response capacity during peaks, supporting oversight expectations for readiness evidence rather than retrospective excuses.
Pay for throughput controls that keep beds and teams usable
Contracts often fund “beds” but not the discharge coordination and barrier removal needed to turn those beds over safely. Similarly, they fund mobile dispatch but not the cross-agency work needed to ensure placement pathways and follow-up are real. A capacity plan without throughput funding creates a holding pattern: beds fill, stays extend for non-clinical reasons, and access collapses upstream.
Operational example 2: A throughput payment component tied to barrier removal and discharge coordination performance
What happens in day-to-day delivery
A managed care plan and county agree a throughput component that funds discharge coordination infrastructure: a transition coordinator role, a daily barrier review process, and defined escalation authority to convene cross-agency resolution calls. The contract specifies required practices (day-one transition plan, barrier log, defined discharge readiness checklist) and performance measures (percentage of discharges with confirmed follow-up, median time-to-barrier-resolution, and reduced avoidable extended stays). The provider reports monthly on delay reasons (housing, transport, pharmacy, authorization) and shows corrective actions for persistent bottlenecks. Payment is structured so the provider is not punished for taking complex cases, but is accountable for actively managing the barriers that prolong stays.
Why the practice exists (failure mode it addresses)
This exists to prevent “capacity erosion,” where stabilization capacity becomes unavailable because discharge is unowned and barriers are normalized. Without throughput funding, providers cannot sustain the coordination work that keeps beds and teams usable, and the system ends up paying far more through ED utilization and inpatient escalation.
What goes wrong if it is absent
Absent throughput funding, discharge coordination becomes intermittent and dependent on individual heroics. Barriers persist without escalation authority, stays extend, and admissions are delayed. The failure presents as upstream congestion (988/mobile backlogs), ED boarding, and pressure to discharge unsafely when the system is congested. Over time, providers may gatekeep admissions to protect themselves from becoming a holding environment.
What observable outcome it produces
Throughput funding produces measurable improvements: shorter and more predictable length of stay, fewer avoidable extended stays, and higher follow-up confirmation rates. The system gains a clear picture of bottleneck causes and can invest strategically (for example, transport solutions or pharmacy access agreements) rather than repeatedly expanding bed counts that will simply become stuck again.
Incentivize outcomes without creating perverse incentives
Outcome incentives can backfire if they reward avoidance (turning away complex cases) or superficial compliance (checking boxes). The safest approach is to use balanced measures that reflect both access and stability: timely response, continuity completion, repeat crisis contacts, and ED utilization—paired with audit protections that detect gaming. Contracts should also include explicit protections for rights-based practice and non-punitive approaches, so providers are not incentivized to shift risk to law enforcement or restrictive settings.
Operational example 3: A balanced scorecard with governance triggers and drift safeguards
What happens in day-to-day delivery
A region implements a contract scorecard combining access, continuity, and stability measures: call answer performance, time-to-mobile response, percentage of stabilization discharges with confirmed follow-up, 7-day repeat crisis contacts, and avoidable ED utilization following crisis contact. The contract includes governance triggers: if repeat contacts rise above a threshold or follow-up completion falls, a joint performance review is convened within a defined timeframe. The review examines operational causes (staffing gaps, barrier delays, allocation drift) and requires a remediation plan. Drift safeguards are built in: the provider must report any changes to eligibility or operating rules during surges, and a sample audit checks that decisions remained consistent and rights-respecting. Incentives are paid for improvement and stability, not for volume alone.
Why the practice exists (failure mode it addresses)
This exists to prevent two common failures: (1) paying for volume that does not reduce crises, and (2) paying for outcomes in ways that encourage gatekeeping or unsafe shortcuts. A balanced scorecard links funding to the system’s real objective: stable community-based crisis response that prevents repeat escalation.
What goes wrong if it is absent
Without balanced incentives and governance triggers, performance management becomes reactive. Providers may be blamed for system failures they cannot control, or rewarded for activity that does not create stability. The failure presents as repeated cycles of surge collapse, ED overflow, and contract disputes—without real redesign. In the worst cases, services tighten access quietly to protect metrics, undermining equity and trust.
What observable outcome it produces
A balanced scorecard with triggers produces visible system learning: performance issues are identified early, analyzed operationally, and corrected through agreed actions. Measures improve in ways that matter—lower repeat contacts, better follow-up completion, and reduced avoidable ED use—while audit safeguards preserve defensibility and rights-respecting practice.
What to include in contracts so capacity planning is real
At minimum: readiness standards (coverage, supervision, competency), throughput controls (transition planning, barrier removal, follow-up ownership), and governance triggers (how drift is detected and corrected). Include reporting that reflects constraints (role coverage gaps, follow-up bottlenecks) rather than activity alone. When funding aligns with these controls, crisis capacity planning becomes operational reality rather than a slide deck.
Reliable crisis continuums are built through operations and paid for through contracting. If you fund readiness and throughput, the model can hold under pressure—and the ED stops being the default safety net for predictable system constraints.