Repeat crisis utilization is not primarily a âbehaviorâ problem; it is a continuity problem. When a person has a second and third crisis episode in a short period, the system is telling you something: no one owns the full pathway, handoffs are leaky, and the work that keeps people stable between episodes is unfunded, unassigned, or unevidenced. Effective prevention starts with governanceâclear cohort rules, accountable roles, escalation steps, and a shared audit trail that proves what was done between crises. For related resources, see Repeat-Crisis Utilizer Prevention and Crisis Response Models.
Define the Cohort Like You Mean It
Governance begins with a definition the system will actually use. âHigh utilizerâ is often too vague, too stigmatizing, and too retrospective. A prevention cohort should be defined by a trigger that is early enough to change the next episode, but specific enough to assign ownership. Examples include repeat crisis line contact plus ED presentation within a set window, multiple mobile crisis dispatches in a month, or repeated short stabilization stays with no documented follow-up completion. The goal is not to label people; it is to create a reliable system response once repeat risk is visible.
Once defined, the cohort definition must be operationalized: who sees the list, how frequently, and what action is required when a person appears on it. If the answer is âwe review it quarterly,â you do not have preventionâyou have reporting.
What Governance Must Control
A prevention governance model should control four things: (1) ownership (one accountable role per person), (2) the minimum continuity actions that must occur after a repeat episode, (3) escalation when actions cannot be completed, and (4) how outcomes and equity are monitored to prevent informal rationing or exclusion. Without these controls, systems default back to the loudest, most immediate work: dispatch and transport.
Operational Example 1: A Repeat-Utilizer Trigger That Generates Assigned Work
What happens in day-to-day delivery: a repeat-utilizer trigger runs on a fixed cadence (daily or several times per week) and produces a short queue owned by a prevention pathway lead. Each new entry is assigned within 24 hours to a named continuity owner (navigator, high-risk care manager, or intensive case coordinator) with a standard task set: attempt outreach, review the last crisis encounter note, confirm current risk status, and initiate a continuity plan. Assignment is recorded in a shared tracker so crisis teams, stabilization, and care coordination can see ownership immediately.
Why the practice exists (failure mode it addresses): repeat crises are often treated as unrelated incidents. The system fails to âlearnâ quickly, so the same person hits the same failure points againâmissed follow-up, medication lapse, housing instabilityâwithout any structured response beyond another emergency episode.
What goes wrong if it is absent: lists circulate without ownership, or ownership is informal (âsomeone should follow upâ). Outreach happens late, teams duplicate assessments, and the person experiences fragmented, inconsistent messaging. Operationally, this shows up as repeated transports, repeated brief holds, escalating restrictions, and staff fatigue because every episode is managed under pressure with no continuity leverage.
What observable outcome it produces: an assigned-work trigger increases early outreach attempts and creates an auditable record of follow-through. Evidence includes time-stamped assignments, documented contact attempts within defined windows, and measurable reductions in repeat crisis contacts for people who received timely continuity interventions.
Operational Example 2: The Continuity Owner Uses a âMinimum Viableâ Stability Plan
What happens in day-to-day delivery: the continuity owner executes a minimum stability plan that is practical, not aspirational. It typically includes a verified follow-up appointment within a defined timeframe, medication reconciliation with a refill bridge, a barrier check (transport, phone access, ID, benefits), and a brief crisis prevention plan written in plain language the person can keep. The owner confirms completion, not just referral, and documents the proof points (appointment date/time, pharmacy confirmation, transportation arrangement, housing step taken).
Why the practice exists (failure mode it addresses): crisis systems often rely on discharge instructions and referrals that do not translate into action. The failure mode is âhandoff evaporationââcare is recommended but not received, and barriers are discovered only after the next crisis.
What goes wrong if it is absent: stabilization becomes a temporary pause. People return to the same conditions with the same unresolved barriers, leading to rapid bounce-back. The failure presents as missed appointments, medication gaps, deteriorating safety, repeated 911 calls, and rising ED use despite âservices being offered.â
What observable outcome it produces: completion of a stability plan improves follow-up timeliness, reduces immediate returns, and strengthens defensibility of diversion decisions. Evidence includes completion rates for plan components, reduced repeat contacts within 7â30 days for engaged individuals, and QA findings showing fewer continuity failures.
Operational Example 3: A Governance Escalation Path When the Plan Cannot Be Completed
What happens in day-to-day delivery: when the continuity owner cannot complete key stability actions (cannot contact, person refuses, no capacity available, safety risk escalates), the case escalates through a defined governance path. That path includes a rapid multi-agency huddle (short, time-limited, decision-focused) and a documented decision: what the next best step is, who will do it, and by when. Escalation also triggers a capacity review if the barrier is structural (no step-down slots, no transportation, no same-week follow-up access).
Why the practice exists (failure mode it addresses): without escalation rules, âhard casesâ drift. Staff keep trying the same unsuccessful outreach while risk rises, or the system defaults to emergency pathways because no one is empowered to make a coordinated decision.
What goes wrong if it is absent: cases linger until an acute incident forces a response. Operationally, the system sees repeated ED boarding, increased involuntary interventions, more law enforcement involvement, and higher safety incidents because the pathway cannot adapt when standard steps fail.
What observable outcome it produces: escalation governance produces clearer accountability and faster, documented decision-making. Evidence includes escalation logs, time-to-decision metrics, reduced âdriftâ for high-risk cases, and capacity actions tied to recurring barriers (for example, targeted investment in step-down or bridge follow-up access).
Two Oversight Expectations You Should Design For
Expectation 1: funders and system purchasers increasingly expect evidence of continuity performance, not just crisis response volume. That means showing follow-up completion rates, timeliness measures, and repeat-utilizer trend reductions for a defined cohortâsupported by a credible audit trail of actions taken between episodes.
Expectation 2: governance must protect rights and avoid âexclusion by label.â If a repeat-utilizer cohort becomes a de facto blacklist, the system will create inequity and risk. Oversight should include equity checks (who gets flagged, what interventions they receive, whether diversion outcomes differ across groups) and a review mechanism for contested decisions.
What Success Looks Like
A functioning repeat-utilizer prevention model changes operations: the cohort is identified early, ownership is visible, minimum stability actions are completed (or escalated), and leadership can prove what happened between crises. The outcome is not just fewer repeat contacts; it is a system that learns and adapts fast enough to prevent predictable bounce-back.