Cross-Agency Accountability in Crisis Diversion: Defining Decision Rights Across 911, Law Enforcement, ED, and Community Providers

Crisis diversion collapses when responsibility is implied rather than defined. When dispatch assumes law enforcement will decide, law enforcement assumes the ED will assess, and community providers assume someone else owns follow-up, gaps emerge that default back to arrest, ED boarding, or system bounce-back. Effective crisis diversion governance requires explicit decision rights across agencies, aligned with broader crisis response models, so that eligibility, risk ownership, and escalation authority are operationally clear at every step.

Two oversight expectations drive this work. First, system leaders and funders expect diversion pathways to measurably reduce unnecessary ED use and justice involvement, not simply shift the burden. Second, regulators and public safety partners expect defensible decision-making—clear criteria, documented handoffs, and auditable accountability when outcomes are reviewed.

Why decision-right ambiguity is a predictable failure mode

Most crisis systems are multi-agency by design. That strength becomes a liability when no one can answer three basic questions in real time: Who decides eligibility? Who owns the risk once diversion occurs? Who authorizes escalation or transfer? Without formal answers, frontline staff improvise under pressure. Improvisation increases inconsistency, increases perceived risk, and pushes systems toward the most defensible default—often ED or arrest.

Operational Example 1: Dispatch-to-Field Diversion Eligibility Protocol

What happens in day-to-day delivery
Dispatch uses a structured triage script that distinguishes medical emergency, imminent violence risk, behavioral health crisis, and social distress. If criteria indicate behavioral health crisis without active violent threat, dispatch assigns a co-response or mobile crisis unit under defined eligibility parameters. Law enforcement retains scene safety authority but does not determine clinical disposition unless explicit exclusion criteria are met. Eligibility decisions are recorded in a shared system, visible to crisis teams and supervisors.

Why the practice exists (failure mode it addresses)
The failure mode is defaulting to traditional police-led or ED-based responses because dispatch lacks clarity on when diversion is appropriate. Without protocol clarity, risk-averse decisions override diversion intent.

What goes wrong if it is absent
Calls that meet diversion criteria are routed to law enforcement or ED unnecessarily. Field officers may spend extended time on scenes awaiting unclear guidance, increasing frustration and reinforcing the belief that diversion is unreliable.

What observable outcome it produces
Systems see improved alignment between call type and response model, reduced inappropriate ED transports, and measurable adherence to eligibility criteria through call audits and supervisory review.

Operational Example 2: Clear Risk Ownership After On-Scene Diversion

What happens in day-to-day delivery
When diversion is initiated on scene, a named role—typically the crisis team lead—assumes documented risk ownership. Law enforcement documents scene clearance, and responsibility formally transfers via shared documentation. The crisis team records safety plan elements, observation needs, and contact information for follow-up services. If the person is transported to a crisis receiving or stabilization site, that site acknowledges receipt and assumes defined monitoring responsibilities.

Why the practice exists (failure mode it addresses)
The failure mode is “shared but owned by none” risk. When no explicit handoff occurs, agencies assume others are monitoring, leading to missed follow-up and unmanaged deterioration.

What goes wrong if it is absent
Post-scene deterioration may not trigger timely review because no agency recognizes ongoing responsibility. Repeat 911 calls or ED visits occur within hours or days, reinforcing skepticism about diversion effectiveness.

What observable outcome it produces
Systems can track continuity ownership, demonstrate documented handoffs, and show reduced short-interval repeat calls following diversion events.

Operational Example 3: Escalation Authority and Transfer Threshold Governance

What happens in day-to-day delivery
Each diversion setting operates under explicit transfer thresholds—medical deterioration, escalating violence risk, inability to maintain safety plan engagement. A named clinical supervisor or on-call authority confirms transfer decisions when feasible. Documentation includes objective indicators, actions attempted, and rationale for transfer. Supervisors review transfer patterns monthly to identify threshold drift or systemic gaps.

Why the practice exists (failure mode it addresses)
The failure mode is inconsistent escalation—either delaying necessary transfer due to uncertainty or escalating prematurely because staff lack confidence in their authority.

What goes wrong if it is absent
Staff rely on individual judgment, producing variability across shifts and agencies. Transfers become harder to defend in post-incident review, undermining interagency trust.

What observable outcome it produces
Programs demonstrate consistent application of transfer criteria, improved timeliness when escalation is necessary, and fewer avoidable transfers triggered by ambiguity.

Governance Mechanisms That Sustain Accountability

Cross-agency dashboards should track eligibility adherence, handoff documentation completion, repeat utilization within defined intervals, and transfer rationale patterns. Joint governance forums—including dispatch leadership, law enforcement, behavioral health providers, and ED partners—must review data regularly. When accountability is designed rather than assumed, crisis diversion becomes operationally reliable rather than dependent on goodwill.