Hub-and-spoke community SUD networks are attractive because they can scale access quickly: spokes deliver local care while hubs concentrate specialist prescribing, supervision, and higher-complexity support. But many systems collapse in practice because roles are vague, escalation is informal, and data flows do not match day-to-day delivery. The result is predictable failure: people are “referred to the hub” and disengage, spokes feel unsupported, and commissioners see inconsistent quality across sites. This guide strengthens community-based SUD service models and aligns with harm reduction and overdose prevention systems by setting out an operational hub-and-spoke design that is scalable, accountable, and auditable.
What hub-and-spoke must deliver (beyond a diagram)
In operational terms, a hub-and-spoke model must deliver three things simultaneously: (1) consistent clinical quality regardless of where a person enters, (2) fast access close to home, and (3) rapid escalation support when complexity rises. This requires more than referral pathways. It requires standardized “what happens next” workflows, shared protocols, and a clear accountability model so responsibility does not drift between hub and spoke at the moments of highest risk.
Good hub-and-spoke models also recognize that the person’s journey is not linear. People move between engagement levels and settings—clinic, outreach, ED, detox, jail release, shelter. The model must handle that movement without breaking continuity.
Oversight expectations this model must satisfy
Expectation 1: Equity and consistency across locations. Counties, states, and Medicaid plans typically expect that a network model does not create “good care in one place and thin care elsewhere.” Hub-and-spoke should produce measurable consistency in access, initiation, follow-up, and overdose prevention practices across sites.
Expectation 2: Clear accountability and safe escalation. Oversight also expects that escalation pathways are defined, time-bound, and documented. In a serious incident review, “we thought the hub was managing it” or “the spoke didn’t tell us” is treated as a governance failure.
Core design choices that determine whether the model works
Role clarity by function, not job title. Define who owns: intake and triage, MOUD initiation, stabilization follow-up, harm reduction delivery, peer navigation, and re-engagement after missed visits. Assign ownership at both hub and spoke levels.
Escalation pathways with thresholds. Specify what triggers hub involvement (polysubstance sedation risk, pregnancy, repeated overdoses, complex comorbidity, non-response to treatment, safeguarding concerns) and how quickly the hub must respond.
Shared clinical governance. Hubs must provide protocols, supervision, and audit sampling that support spokes without undermining local autonomy. Spokes must adhere to minimum standards while retaining flexibility for local context.
Information flows designed for speed and auditability. Data sharing must be minimum necessary, role-based, and traceable. It must support real-time decisions, not just reporting.
Operational Example 1: Spoke-led same-day starts with hub backup for complex presentations
What happens in day-to-day delivery. A spoke clinic offers walk-in and rapid slots for MOUD starts. The spoke clinician uses a standardized initiation protocol and completes a brief risk screen. If predefined complexity triggers appear—recent overdose with polysubstance use, pregnancy, severe mental health risk, or prior failed inductions—the spoke initiates a “hub consult” workflow. The hub provides same-day or next-day clinical consultation (virtual or phone), confirms the pathway (standard vs micro-induction, follow-up cadence, harm reduction plan), and documents the consult outcome in a shared, auditable record. The spoke remains the primary delivery site, and the hub’s role is to strengthen decision-making, not take over care unless criteria are met.
Why the practice exists (failure mode it addresses). Hub-and-spoke often fails when spokes refer complexity out instead of being supported to manage it. That creates drop-off because referral becomes a barrier. A consult-based model keeps care local while ensuring specialist input is available quickly.
What goes wrong if it is absent. Spokes either attempt complex starts without support (risking unsafe variation) or refer people to the hub with delays. People disengage during the wait, overdose risk rises, and the system sees repeated crisis contacts. Oversight then finds inconsistent initiation practice and weak evidence of escalation support.
What observable outcome it produces. A consult-based model improves same-day access while reducing unsafe variation. Evidence includes consult response times, reduced “referred but never attended hub” rates, improved early retention across spokes, and audit samples showing consistent protocol use with documented hub input when triggers were present.
Operational Example 2: Mobile team as a spoke with defined handoff into stabilization and ongoing care
What happens in day-to-day delivery. A mobile team engages people in shelters and on the street. The team can complete rapid triage, provide harm reduction supports, and initiate MOUD through a governed pathway (direct prescribing where available or immediate connection to a spoke prescriber). The mobile team logs minimum necessary data: identity confirmation method, risk triggers, MOUD status, naloxone status, and next appointment. A “handoff to stabilization” workflow routes the person to a spoke site for follow-up within 24–72 hours. If the person misses the follow-up, the mobile team triggers the retention ladder: outreach attempts, rebooking, and escalation if high-risk indicators are present.
Why the practice exists (failure mode it addresses). Mobile teams often become parallel engagement services, generating contacts but not stable treatment pathways. Without a defined handoff and retention workflow, the system expends effort without achieving sustained engagement.
What goes wrong if it is absent. People receive naloxone and brief support but do not convert into treatment. The mobile team cannot confirm whether prescriptions were filled or follow-up occurred. Spokes receive incomplete information, and care becomes fragmented. Oversight reviews then question whether outreach funding is producing measurable clinical engagement and harm reduction outcomes.
What observable outcome it produces. A governed mobile-spoke pathway improves conversion from outreach contact to treatment engagement and reduces “touch but no hold” patterns. Evidence includes closed-loop handoff completion, follow-up attendance rates, and reduced repeat outreach contacts without progression. Systems can also show improved overdose prevention coverage among high-risk populations engaged by mobile teams.
Operational Example 3: Hub-led quality management that supports spokes without burdening them
What happens in day-to-day delivery. The hub operates a lightweight quality management cycle: monthly sampling of initiations, follow-ups, and escalation events across spokes; quarterly supervision cohorts; and rapid protocol updates based on findings. Spokes submit only minimum necessary audit artifacts (template completion fields and outcome indicators), avoiding long narrative reporting. The hub produces practical feedback: where the pathway breaks, what training is needed, and which protocols require clarification. Corrective actions are tracked with owners and due dates, and improvements are re-tested through the next sample cycle.
Why the practice exists (failure mode it addresses). Hub-and-spoke models often fail because quality is assumed rather than measured. Alternatively, they fail because governance becomes heavy and spokes drown in reporting, reducing time for care. Sampling-based quality management balances assurance with feasibility.
What goes wrong if it is absent. Spokes drift into local variations that grow over time—different induction instructions, inconsistent naloxone practices, uneven follow-up. When oversight scrutiny occurs, the network cannot evidence consistent standards or improvement activity. If governance becomes overly burdensome, staff focus on paperwork, access slows, and engagement drops.
What observable outcome it produces. Lightweight hub-led quality management increases consistency across sites while protecting access. Evidence includes improved protocol adherence rates, reduced variation in key measures (time-to-initiation, early follow-up), documented corrective actions, and improved commissioner confidence because the network can demonstrate active learning and control.
Practical governance and data flow rules that keep the model stable
Define a minimum shared dataset. Agree the essentials that must move across hub/spoke: MOUD status, risk triggers, naloxone status, follow-up schedule, escalation contacts, and critical safety notes. Keep it minimum necessary.
Use closed-loop referrals internally. Internal handoffs must behave like closed-loop referrals: acknowledged, accepted, scheduled, attended, outcome recorded. “We sent them to the hub” is not a completion state.
Set service-level response expectations. Hub consult response times and escalation windows should be explicit and measurable. This prevents hub support from becoming aspirational.
Hub-and-spoke networks succeed when they operate as an integrated system: local access with specialist backup, consistent governance, and reliable data flows. When designed this way, hubs amplify spokes rather than absorbing them—and the network becomes scalable, auditable, and defensible.