âRecovery-Oriented System of Careâ (ROSC) is often treated as a values statement. In practice, a ROSC is a system design problem: how a county or region ensures people can enter care quickly, move between levels of support without falling through gaps, and sustain recovery in the presence of relapse risk, housing instability, trauma, and co-occurring conditions. A credible ROSC has to behave like a real operating modelâdefined pathways, accountable handoffs, and evidence that the system is improving. This article supports recovery-oriented systems of care (ROSC) design and depends on strong community-based SUD service models to deliver the work on the ground.
The core ROSC mistake is assuming ârecovery-orientedâ means âmore services.â A real ROSC means fewer dead ends: the person does not have to re-explain their story at every door, withdrawal and cravings are treated as predictable clinical and operational risks, and every program knows what happens next if engagement slips. Below is an operational blueprint counties can implement and govern.
What a ROSC must accomplish at system level
A ROSC is the way a system delivers continuity across prevention, harm reduction, treatment, and long-term recovery supports. It must work for people at different stages and with different goals, including those who are not ready for abstinence but still need stabilization. A ROSC must also be legible to funders and oversight bodies: who is responsible for outcomes, what capacity exists, and how the system detects and fixes failure patterns.
Two oversight expectations counties should assume
Expectation 1: A ROSC must show accountable governance, not ânetwork languageâ
State agencies, Medicaid authorities, and county leadership will expect named ownership for pathway performance, clear escalation routes, and an audit trail that shows decisions are made consistently. A ROSC without governance is a collection of providers with inconsistent practice.
Expectation 2: Outcomes must be reported in a way that is comparable and defensible
Funding bodies will expect measurable indicators (access timeliness, retention, overdose trends, jail/ED utilization, housing stability signals) and defined measurement logic. âRecoveryâ cannot be a vague outcome; it must be evidenced through observable system markers and client-centered goals.
Operational example 1: A single front door with triage, warm handoffs, and booking authority
What happens in day-to-day delivery
A ROSC front door is not a phone number on a flyer; it is an operating function with triage capability and booking authority. Counties run a centralized access hub (virtual or physical) staffed by trained navigators and clinicians who can complete initial screening, identify overdose risk, assess withdrawal needs, and book appointments directly into partner programs. The hub uses a shared capacity viewâreserved intake slots, real-time availability, and agreed referral rulesâso it does not ârefer and hope.â
Warm handoffs are operationalized: the hub schedules the appointment, confirms transport where needed, and sends the receiving provider a standardized referral packet (minimum necessary data, consent status, risk flags, and contact plan). The hub then executes a follow-up workflow: same-day confirmation text/call, day-before reminder, and a post-appointment check to confirm attendance or rebook rapidly if missed.
Why the practice exists (failure mode it addresses)
The failure mode is the referral cliff. People in acute need are given lists, told to call multiple places, or wait weeksâduring which withdrawal, overdose risk, or legal/housing crises worsen. The system loses people before care starts.
What goes wrong if it is absent
Access becomes provider-dependent and inequitable. High-motivation individuals navigate the system; others disengage and return via ED, jail, or crisis response. Providers blame ânoncomplianceâ when the true failure is the absence of booking authority and follow-up infrastructure.
What observable outcome it produces
Observable outcomes include reduced time-to-first-appointment, higher show rates, and fewer repeated crisis contacts. Evidence includes access dashboards (median time to intake), missed appointment recovery rates, and documented handoff completion.
Operational example 2: Recovery navigation that stays with the person across settings
What happens in day-to-day delivery
A ROSC assigns recovery navigation as a longitudinal role, not a short-term referral task. Navigators (often peers with supervision, or mixed teams with clinical support) maintain contact through transitions: detox discharge, outpatient entry, housing moves, probation check-ins, or relapse episodes. They use a shared care plan framework that includes recovery goals, risk triggers, medication plan status (including MAT), and practical barriers (ID, benefits, transport).
Navigation is governed through structured cadence: weekly contact during early phases, step-down frequency when stable, and rapid escalation when risk indicators appear (missed visits, loss of housing, overdose event, medication interruption). Navigators document contacts in a system-wide workflow tool or shared platform with defined minimum data elements, enabling supervision, QA, and continuity when staff change.
Why the practice exists (failure mode it addresses)
The failure mode is fragmentation during transitions. People often leave detox or ED with vague plans, lose appointments, or experience medication interruptions. Each transition becomes a reset, and the system repeatedly ârestartsâ rather than stabilizing.
What goes wrong if it is absent
Engagement becomes episodic. People repeatedly re-enter at higher acuity, relationships with providers weaken, and relapse events trigger punitive responses instead of stabilization. Providers operate in silos and do not see the full risk picture.
What observable outcome it produces
Outcomes include improved retention, fewer failed transitions, and measurable increases in continuity indicators (kept appointments after discharge, fewer gaps in medication, fewer repeat ED visits). Evidence includes transition follow-up metrics and care-plan completion audits.
Operational example 3: ROSC governance that detects failure patterns and drives corrective action
What happens in day-to-day delivery
A functional ROSC runs governance like a performance system. The county establishes a ROSC steering group with clear membership: Medicaid/behavioral health authority representatives, provider leadership, peer workforce leadership, ED/detox partners, housing partners, and justice interface representatives where relevant. This body owns a defined set of indicators and meets on a fixed cadence (monthly is common) with pre-read dashboards.
Governance meetings are not updates; they are problem-solving sessions. If time-to-intake rises, the group identifies whether the bottleneck is capacity, authorization, transport, or referral quality. If overdose spikes appear among people recently discharged, the group examines discharge processes, naloxone distribution reliability, and MAT continuity failures. Corrective actions are assigned to named owners with deadlines, and progress is tracked to closure. Quality assurance includes chart audits, pathway fidelity reviews, and incident learning loops (e.g., overdose fatality review integration where available).
Why the practice exists (failure mode it addresses)
The failure mode is unmanaged drift. Without governance, services slowly diverge from intended practice, gaps expand, and recurring failures (missed follow-up, inconsistent MAT access, poor linkage to housing) remain unaddressed.
What goes wrong if it is absent
The ROSC becomes a brand, not a system. Providers optimize for their own contracts, handoffs break down, and stakeholders cannot explain why outcomes are not improving. Funding renewals become vulnerable because the system cannot evidence improvement mechanisms.
What observable outcome it produces
Observable outcomes include improved pathway fidelity, reduced access delays, and measurable improvement in defined indicators over time. Evidence includes action logs, audit results, and documented remediation cycles that show the system learns and adapts.
Design principle: recovery orientation must be engineered into daily operations
A ROSC is not âmore meetingsâ or âmore partners.â It is an engineered set of pathways that make stabilization and sustained recovery more likely: a real front door, longitudinal navigation, and governance with teeth. Counties that treat ROSC design as an operational blueprintârather than a mission statementâare the ones that can show defensible outcomes and sustain funding over time.