Many counties design ROSC pathways with strong clinical intent but weak financial architecture. Funding streams pay for episodes, not continuity; contracts reward volume, not re-engagement; and accountability is spread across multiple providers with no single owner for the outcomes the county cares about. When that happens, the ROSC becomes fragmented by design, regardless of how committed partners are. Counties with durable systems align procurement and payment with continuity: they pay for the work that prevents relapse and crisis—follow-up, barrier removal, re-engagement, and stabilization routing. This article strengthens ROSC design and governance foundations and aligns them with community-based SUD service models that must operate under fluctuating demand while remaining accountable for real-world outcomes.
Why financing determines whether ROSC is a system or a patchwork
Counties can mandate collaboration, but contracts still shape daily behavior. If providers are paid only for scheduled sessions, they will deprioritize outreach after missed appointments. If housing coordination is unfunded, it becomes sporadic. If performance measures are vague, the county cannot correct drift. A ROSC financing model must explicitly fund continuity functions and require measurable completion events that reflect how recovery actually stabilizes over time.
Financing also determines equity. When payment models assume stable attendance and easy engagement, they inadvertently select for lower-complexity clients and leave higher-need populations under-supported, increasing crisis utilization and worsening outcomes.
Oversight and funder expectations that shape ROSC contracting
Expectation 1: Clear accountability for measurable outcomes, not just service volume. State agencies, managed care entities, and county leadership increasingly expect counties to demonstrate performance improvement with defensible metrics such as retention, reduced crisis utilization, and continuity after transitions. Contract language must specify what “success” looks like operationally and how it will be verified.
Expectation 2: Procurement integrity, equity, and auditable governance. Funders and oversight bodies typically expect transparent procurement processes, consistent performance reporting, and corrective action when providers underperform. Counties need audit-ready documentation showing that dollars are tied to defined functions and that equity is monitored rather than assumed.
Operational Example 1: Paying for continuity through defined “completion events” rather than only encounters
What happens in day-to-day delivery. The county defines a set of continuity completion events that are payable and reportable, such as: verified first appointment attended within a target window, first-week follow-up contacts completed after high-risk transitions, successful re-engagement after a missed start, medication continuity confirmed where relevant, and barrier resolution actions documented (transport arranged, phone access restored, benefits reactivated). Providers submit claims or invoices tied to these completion events with required evidence fields. A county contract manager runs monthly validation checks to ensure evidence quality and to prevent gaming.
Why the practice exists (failure mode it addresses). Encounter-only payment underfunds the work that keeps people connected when attendance is unstable. The completion-event approach exists to prevent the failure mode where systems “do care” only when clients show up on time, then label missed attendance as client failure rather than a continuity gap the system should manage.
What goes wrong if it is absent. Providers prioritize scheduled billable visits and deprioritize outreach, rebooking, and barrier removal. Clients with unstable housing or co-occurring needs drop out early, and the ROSC experiences churn. The county then spends heavily on crisis services and repeated re-intake while reporting high activity but limited stability outcomes.
What observable outcome it produces. Counties can measure improved first-visit attendance, higher re-engagement rates after missed starts, and better retention at 30–90 days. Audits show consistent documentation of continuity actions, allowing leaders to defend spending as targeted risk reduction rather than general service volume.
Operational Example 2: Braided funding model with a single operating model and shared performance scorecard
What happens in day-to-day delivery. The county maps funding streams (county general funds, grants, Medicaid/managed care, justice reinvestment, housing resources) to a single ROSC operating model. Instead of allowing each funding source to create a separate program, the county uses a unified service specification that assigns roles and workflows across the pathway (access, navigation, peer support, housing coordination, stabilization routing). Providers are contracted under compatible requirements, and all partners report into a shared scorecard with consistent definitions. Monthly governance meetings review the scorecard and assign corrective actions across agencies, not just within one provider.
Why the practice exists (failure mode it addresses). Braided funding often becomes fragmented funding: multiple initiatives with different rules and different metrics. That produces duplication in some places and gaps in others. The unified model exists to prevent the failure mode where ROSC looks coherent on paper but functions as disconnected grant projects in practice.
What goes wrong if it is absent. Clients are moved between programs with different eligibility criteria and documentation requirements. Staff spend time translating between funding rules rather than supporting continuity. Providers protect their own contract metrics and may resist shared accountability. The county cannot explain outcomes because performance measures are inconsistent across contracts.
What observable outcome it produces. Counties can demonstrate clearer pathway ownership, reduced duplication, improved timeliness of access, and more consistent continuity performance across providers. Governance records show that the county used performance data to manage the system, strengthening defensibility to funders and oversight bodies.
Operational Example 3: Contract enforcement and improvement cycle that prevents drift and protects equity
What happens in day-to-day delivery. Contracts include explicit thresholds for key continuity measures (for example, time-to-first-contact, first-week follow-up completion, re-engagement after missed starts, and retention). When a provider falls below threshold, the county triggers a structured improvement cycle: root-cause analysis, workflow changes, staff coaching, and a time-bound corrective action plan. The county verifies completion through data audits and file sampling, not self-attestation alone. Equity checks are built in: performance is reviewed by geography, population subgroups, and pathway entry points to ensure high-need clients are not being indirectly excluded.
Why the practice exists (failure mode it addresses). Without enforcement and improvement discipline, performance problems persist and become normalized. Providers may unintentionally “cream-skim” toward easier-to-serve clients to protect metrics. The improvement cycle exists to prevent drift and to ensure the ROSC remains accountable for the populations it is designed to serve.
What goes wrong if it is absent. Underperformance becomes chronic, and the county lacks leverage to fix it. Equity gaps widen quietly. After an adverse event or public scrutiny, leadership cannot show that it monitored performance, identified failures, and implemented corrective action, increasing reputational and funding risk.
What observable outcome it produces. Counties can evidence narrowing performance variation across providers, improved continuity measures over time, and documented corrective actions with owners and deadlines. Equity reporting shows whether improvements are reaching high-need populations, strengthening the county’s defensibility and long-term sustainability.
Practical contracting controls that support real-world ROSC delivery
- Write the workflow into the specification: define continuity tasks and completion evidence, not just service categories.
- Fund re-engagement explicitly: pay for outreach, barrier removal, and rapid re-entry, not only attendance.
- Standardize measure definitions: one scorecard across providers prevents metric drift and gaming.
- Use audit-ready verification: combine data checks with file sampling and supervision evidence.
Financing and contracting are not administrative details; they are the operating logic of a ROSC. Counties that pay for continuity functions, braid funding into a single operating model, and enforce performance through structured improvement cycles build systems that sustain recovery engagement under real-world conditions—while producing defensible evidence for funders, oversight stakeholders, and the public.