Co-occurring substance use disorder and mental illness is where diversion pathways are most likely to fail. People can present with intoxication, withdrawal, paranoia, suicidality, trauma responses, and cognitive impairment in the same encounter—yet systems often route “SUD” to one provider and “mental health” to another, with no shared plan for the first 72 hours. Counties that reduce cycling treat co-occurring presentations as a single operational pathway with integrated triage, stabilization options, and continuity rules that survive real-world volatility. This article strengthens justice-system interfaces and diversion pathway design and aligns it to community-based SUD service models that can carry people through early instability without punitive drift.
Why “dual diagnosis” is an operational risk, not a clinical label
In diversion settings, co-occurring conditions create predictable breakdowns: incomplete risk assessment, wrong placement decisions, missed medication continuity, and inconsistent follow-up ownership. The person is then labeled “noncompliant” when the system never built a workable bridge from justice contact to a stable clinical start. Effective diversion for co-occurring needs is built around workflows that answer: who conducts integrated screening, where stabilization happens if the person cannot safely engage in routine outpatient care today, and who owns proactive follow-up when the first plan fails.
Counties also have to prevent a common rights-and-safety failure mode: using custody as default “stabilization” because clinical options are fragmented. A defensible pathway creates a non-custodial stabilization route (with clear escalation thresholds) and documents decision-making so outcomes are explainable to oversight bodies and funders.
Oversight and funder expectations that shape co-occurring diversion design
Expectation 1: Demonstrable risk management and clinical governance. Counties are typically expected to show that diversion decisions involving suicidality, psychosis, or severe withdrawal risk are made through structured processes, not informal judgment. That means documented screening, clear escalation routes, and supervisory review for high-risk cases. When adverse events occur, oversight bodies look for evidence that the system applied consistent thresholds and took timely follow-up actions.
Expectation 2: Continuity across settings, not repeated re-intake. Funders and payers generally expect counties to reduce duplication and fragmentation. If people repeatedly cycle through crisis response, ED, and short appointments without a sustained plan, the pathway looks inefficient and inequitable. A defensible approach shows how information and accountability move across settings so the person does not restart from zero each time they destabilize.
Operational Example 1: Integrated screening at the diversion touchpoint with a “single narrative” handoff
What happens in day-to-day delivery. At the first diversion decision point (court-based program office, pretrial services, defense-linked clinician, or deflection hub), staff use an integrated screening workflow that covers substance use pattern, withdrawal risk, overdose history, suicidality, acute psychosis/mania indicators, trauma risk, and immediate safety needs. The workflow is designed for rapid use: short structured questions, clear scoring/flags, and a defined escalation pathway. The result is recorded as a single integrated summary (not separate SUD and mental health notes) that is shared with the receiving provider using agreed minimum-necessary fields and a named contact.
Why the practice exists (failure mode it addresses). Co-occurring presentations often fail because each system collects only what it cares about. SUD programs may miss suicidality and acute psychosis risk; mental health programs may miss withdrawal severity, overdose risk, or medication continuity needs. The integrated approach exists to prevent unsafe placements and “split brain” handoffs that create gaps in the first week.
What goes wrong if it is absent. People are routed to inappropriate settings—sent to routine outpatient intake when they cannot safely engage, or sent to crisis response without a plan for MOUD continuity. Staff then interpret missed appointments as refusal rather than incapacity. The system compensates with repeated referrals, police transports, or detention “for safety,” increasing trauma, costs, and recidivism risk.
What observable outcome it produces. Counties can evidence fewer failed placements, fewer repeated crisis transports during the first 7–14 days, and higher rates of completed first clinical contact. Quality reviews show clearer decision logic: why a placement was chosen, what risks were identified, and what follow-up was assigned when the first plan did not hold.
Operational Example 2: Stabilization routing that avoids custody as the default “safe place”
What happens in day-to-day delivery. The pathway includes a stabilization routing model with defined options: same-day crisis stabilization (when acute risk is present), short-term observation (when impairment makes outpatient engagement unsafe), and rapid outpatient start (when the person can safely attend). Diversion staff have a live directory of stabilization capacity, admission criteria, hours, and transportation options. When stabilization is used, the diversion team triggers a continuity package: medication plan, follow-up appointment scheduled before discharge, and a warm transition to a community provider with a named care coordinator. Supervisors review stabilization use weekly to ensure criteria are applied consistently.
Why the practice exists (failure mode it addresses). Without stabilization routing, counties face a false choice: outpatient referral that fails, or custody as containment. The routing model exists to prevent unnecessary incarceration and to protect against unsafe outpatient placement when the person is clinically unstable.
What goes wrong if it is absent. People bounce between crisis calls and court dates without clinical grounding. When they miss appointments, the system escalates to warrants or detention because there is no other mechanism to manage risk. This creates punitive drift, undermines engagement, and increases overdose risk after release from short custody episodes.
What observable outcome it produces. Counties can track reduced “custody for stabilization” usage, fewer short jail stays linked to missed clinical starts, and improved engagement after stabilization discharge (because a follow-up appointment and care coordinator are already in place). Documentation supports defensibility: leaders can show that clinical thresholds—not convenience—drove routing decisions.
Operational Example 3: First-week continuity protocol for co-occurring needs with escalation that stays supportive
What happens in day-to-day delivery. The pathway assigns first-week ownership to a specific role (care coordinator, peer navigator, or intensive case manager) who conducts scheduled touchpoints: day 1 confirmation, day 3 check, and day 7 review. Touchpoints are structured: medication continuity check, safety plan review, housing/contact stability, and barriers to attendance. If the person misses the first appointment, the protocol triggers same-day outreach and a re-booking sequence, plus a clinical consult for risk reassessment. Escalation options remain supportive (stabilization routing, mobile outreach, telehealth check-in) rather than immediately punitive. Supervisors audit a sample of missed-appointment cases monthly to confirm the protocol was followed.
Why the practice exists (failure mode it addresses). Co-occurring conditions make early disengagement more likely and more dangerous. The first-week protocol exists to prevent “silent failure,” where the system waits until a crisis or violation occurs. It also prevents agencies from interpreting symptoms (disorganization, paranoia, withdrawal) as willful noncompliance.
What goes wrong if it is absent. People miss early appointments and fall out of the pathway with no proactive response. They then reappear through emergency services, new charges, or technical violations. Providers experience repeated re-intake demand, and courts lose confidence because outcomes appear random and unmanaged.
What observable outcome it produces. Counties can measure first-week contact completion, re-engagement after missed starts, and reduced unplanned crisis contacts. Case review shows whether barriers were addressed (transport, phone access, symptom flare) and whether escalation remained proportionate and rights-protecting.
Implementation controls that sustain integrated diversion
- One integrated screen, one handoff summary: reduce fragmentation by design.
- Defined stabilization options: prevent custody becoming the default safety tool.
- First-week ownership: assign accountable follow-up and audit missed-start responses.
- Case review discipline: use routine reviews to prevent punitive drift and inconsistent thresholds.
Co-occurring diversion succeeds when counties treat early instability as expected and design workflows that absorb it: integrated screening, stabilization routing, and first-week continuity that stays supportive. Done well, the pathway reduces cycling, protects rights, and produces an operational record that holds up under oversight and funding scrutiny.