Repeat-crisis utilization is most visible in the field: the same addresses, the same public locations, the same transport decisions made under time pressure. Prevention here is not achieved by telling responders to âdivert more.â It is achieved by building a governed field pathway that makes the safer, lower-intensity option practicalâclear criteria, rapid access to continuity owners, and follow-up that resolves the barrier that triggered the call. For related resources, see Repeat-Crisis Utilizer Prevention and Crisis Response Models.
Start With Reality: âHot Spotsâ Are Usually Continuity Failures
Hot spots are not just geography; they are patterns of unmet need. Repeated calls at a shelter, a supportive housing site, or a known public location often reflect the same breakdown: no reliable engagement pathway, inconsistent medication access, unstable routines, or staff uncertainty about when and how to escalate. Field prevention requires the system to respond to patterns, not just incidents.
Transport Avoidance Is a Safety Practice, Not a Cost Play
In repeat-utilizer prevention, avoidable transport reduction must be governed like a safety intervention. That means: the alternative pathway must be available in real time; criteria must be clear and defensible; and every non-transport decision must generate continuity work (ownership, follow-up, and barrier resolution). If the system cannot do that reliably, transport becomes the default for good reason.
Operational Example 1: Hot-Spotting That Produces Actionable Work, Not Just Maps
What happens in day-to-day delivery: the system identifies hot spots using recent call patterns (for example: repeated EMS dispatches or mobile crisis responses to the same location or individual). A small joint operations team (EMS liaison, mobile crisis lead, and prevention pathway manager) reviews the list on a fixed cadence and assigns action: on-site staff coaching, targeted outreach visits, or rapid linkage clinics. For individuals, the continuity owner is confirmed and the field plan is updated with practical instructions responders can use.
Why the practice exists (failure mode it addresses): systems often notice hot spots but treat them as inevitable. The failure mode is passive awarenessâeveryone knows the pattern, but no one owns an intervention to change what keeps generating calls.
What goes wrong if it is absent: hot spots become normalized. Responders cycle through the same high-intensity interventions, the same transports, and the same brief holds. Operationally, it presents as rising unit hours, ED pressure, deteriorating relationships with community sites, and higher risk incidents because staff rely on emergency escalation rather than early stabilization steps.
What observable outcome it produces: action-based hot-spotting reduces repeated dispatches and improves field confidence. Evidence includes reduced call volume from targeted sites, increased use of alternative pathways (where safe), and documented completion of assigned actions (staff coaching delivered, outreach completed, linkage established).
Operational Example 2: Street-Level Follow-Up That Fixes the Trigger Condition
What happens in day-to-day delivery: after a repeat crisis episode, a field-capable continuity team performs a structured follow-up within a defined window. The follow-up is practical: confirm where the person is staying, whether they can be reached, whether medications are accessible, and what immediate barrier triggered the crisis (lost phone, missed benefits appointment, conflict at a site, withdrawal symptoms, lack of food/transport). The team resolves one or two barriers on the spot (transport voucher arranged, pharmacy bridge coordinated, shelter coordination call made) and documents the actions as proof points.
Why the practice exists (failure mode it addresses): many repeat crises are driven by basic instability that is not resolved by clinical advice alone. The failure mode is expecting office-based follow-up to succeed for people who cannot reliably access phones, transport, or safe environments.
What goes wrong if it is absent: âfollow-upâ becomes a missed appointment. The system continues to respond only when crises erupt, and the person learns that emergency access is the only reliable access. This shows up as repeated 911 calls, repeated ED presentations, and escalating frustration among responders who feel they are doing the same job repeatedly with no change.
What observable outcome it produces: street-level follow-up increases real engagement and reduces near-term repeat contacts. Evidence includes documented barrier resolutions, higher follow-up completion rates for hard-to-reach individuals, and measurable reductions in repeated dispatches for those receiving field-based continuity support.
Operational Example 3: A Governed Non-Transport Pathway With Real-Time Backup
What happens in day-to-day delivery: responders have access to a governed non-transport pathway when criteria are met. Criteria are operational (orientation, medical red flags screened, immediate risk assessed, safe environment confirmed, and a continuity owner reachable). If criteria are met, responders can connect the person to mobile crisis, a stabilization alternative, or a scheduled rapid follow-up without automatic ED transport. The decision is documented with required proof points and a defined escalation plan if risk changes.
Why the practice exists (failure mode it addresses): responders default to transport because the alternative is uncertain and risky to defend. The failure mode is lack of real-time supportâno one to consult, no clear criteria, and no proof that follow-up will happen if transport is avoided.
What goes wrong if it is absent: transport becomes the only defensible choice, even when it is not clinically necessary. EDs become crowded with repeat presentations that could have been managed through structured community pathways, and responders lose time that could be spent on higher-acuity emergencies.
What observable outcome it produces: a governed pathway increases appropriate non-transport decisions while maintaining safety. Evidence includes documentation compliance, follow-up completion after non-transport, reduced repeat calls for individuals who receive continuity support, and QA reviews showing that criteria were applied consistently.
Two Oversight Expectations You Should Design For
Expectation 1: oversight stakeholders expect non-transport pathways to be defensible and auditable. That means clear criteria, documentation standards, and QA sampling that reviews whether safety screening and follow-up occurred as required.
Expectation 2: field prevention models must avoid âdisplacementâ (reducing ED use by shifting risk to shelters, families, or law enforcement). Governance should monitor adverse events, equity impacts, and site-level burden, and should include mechanisms to add capacity where hot spots reflect structural gaps rather than individual choices.
What to Measure (Beyond âTransports Downâ)
Track leading indicators that prove prevention work is happening: hot-spot action completion, field follow-up completion within the defined window, barrier resolution documentation, real-time continuity owner reachability, and QA outcomes for non-transport decisions. When these are strong, transport reduction becomes a byproduct of safer continuityânot the goal that compromises trust.