ROSC success depends less on how many partners are “at the table” and more on whether partners are accountable to the same performance expectations. In Recovery-Oriented Systems of Care (ROSC) design, governance must translate partnership language into enforceable standards—aligned with community-based SUD service models that operate across multiple entry points, risk levels, and funding rules.
This article sets out a practical ROSC governance model: what gets governed, how accountability is evidenced, and what counties do when a partner’s delivery fails people in real time.
Why ROSC governance fails in practice
Many systems invest heavily in steering groups and multi-agency meetings, but avoid the hard parts: defining minimum operational standards, setting shared metrics, and creating consequences for repeated failure. When governance is primarily relational, the system becomes inconsistent across geography, populations, and access points.
ROSC governance needs three things: (1) clear standards, (2) shared performance measurement, and (3) escalation routes that protect individuals when partners miss critical steps.
Expectation: funders and oversight bodies expect documented system accountability
Counties are increasingly expected to show not only “who provides what,” but how they assure the system functions safely and consistently. That means governance evidence: decision logs, corrective action processes, performance reporting, and mechanisms for addressing repeated pathway failures (missed follow-up, unsafe discharge, delayed engagement, or poor continuity for high-risk individuals).
What governance must cover in a real ROSC
Governance should explicitly cover: access and timeliness standards; cross-setting transitions (detox, ED, inpatient, jail release); peer and recovery support quality; housing and employment stabilization integration; medication continuity; incident and overdose review processes; and equity monitoring (who is not being served, and why).
Operational Example 1: Minimum pathway standards with auditable checkpoints
What happens in day-to-day delivery
The county defines “minimum pathway standards” for key workflows (e.g., post-ED follow-up within 24–48 hours for high-risk referrals; warm handoffs at discharge; re-entry without full re-intake; housing risk screening at intake). Each standard includes specific auditable checkpoints: who documents the contact, where it is recorded, and what constitutes completion. Providers submit monthly pathway compliance data, and care teams can see missed checkpoints in near real time.
Why the practice exists (failure mode it addresses)
This addresses the failure mode where partners describe good practice but deliver inconsistently. Without explicit checkpoints, “we tried” becomes an acceptable substitute for evidence that a person was actually reached, engaged, and supported.
What goes wrong if it is absent
Inconsistent follow-up becomes normalized. High-risk individuals are lost during transitions, and the system cannot identify whether the failure occurred in ED discharge, referral transmission, outreach capacity, or documentation gaps.
What observable outcome it produces
Counties can evidence improved timeliness, reduced missed transitions, and fewer “unknown outcome” cases. Audits show clear traces of engagement attempts and escalation actions when standards are missed.
Expectation: governance must include an escalation pathway that protects the person
Oversight expectations increasingly focus on what happens when the system fails. A ROSC governance model should specify escalation when a partner repeatedly misses critical actions—especially for overdose risk, medication continuity, or post-release follow-up.
Operational Example 2: A standing “system rescue” function for failed handoffs
What happens in day-to-day delivery
The county funds a small system rescue team (often within the lead agency) that activates when a critical handoff fails. If a person is discharged from detox without confirmed follow-up, or a justice release referral is not contacted within the time standard, the rescue team intervenes: confirms location, assigns a peer, coordinates transportation, and reissues referrals to alternative providers if needed. Rescue actions are logged and reviewed in governance meetings to identify partner failure patterns.
Why the practice exists (failure mode it addresses)
This exists to address the failure mode where the system knows a handoff failed but no one is empowered to fix it. Without rescue capacity, the system tolerates failure until the person returns through crisis.
What goes wrong if it is absent
Missed handoffs become repeat overdoses, repeat incarceration, or repeat ED use. The system’s only “correction” is a future crisis event—too late to prevent harm.
What observable outcome it produces
Counties can evidence reduced time-to-engagement for high-risk transition cases and fewer repeated crisis re-entries attributed to failed follow-up.
Operational Example 3: Corrective action plans tied to measurable improvement
What happens in day-to-day delivery
When a partner repeatedly misses standards (e.g., low follow-up rates, poor documentation, high “unable to contact”), governance triggers a corrective action plan (CAP). The CAP defines the failure pattern, root causes, and a time-bound improvement plan: staffing adjustments, workflow redesign, training, or technology fixes. The partner provides fortnightly progress updates with metric movement. If improvement is not evidenced, the county escalates to contract remedies or shifts volume to alternative providers.
Why the practice exists (failure mode it addresses)
This addresses the failure mode where governance identifies problems but never changes delivery. Without CAPs, the same issues recur indefinitely.
What goes wrong if it is absent
Chronic underperformance persists. High-risk people are exposed to preventable delays and inconsistent quality, while the system lacks defensible oversight evidence.
What observable outcome it produces
Governance meetings move from narrative updates to measurable improvement. Counties can show trend improvement in pathway compliance, timeliness, and engagement outcomes.
Design takeaway: governance is a safety function, not a meeting structure
ROSC governance is credible when it can answer: What standard was missed? How do we know? What did we do immediately to protect the person? What changed to prevent recurrence? When governance can evidence those answers, system performance becomes real.