Referral workflow
- 01
Confirm current service status
Review whether the requested service is active, enrolling, in development, or readiness-gated.
- 02
Use the approved secure channel
Clinical information and records move through the contracted secure system—not WordPress or ordinary email.
- 03
Acknowledge ownership
A named access role confirms receipt, records the referral source, and communicates the next expected step.
- 04
Screen and assess
Reach One reviews safety, consent authority, eligibility, level of care, clinical need, and operational fit.
- 05
Admit, redirect, or complete a handoff
The outcome is documented and communicated. When another service is needed, Reach One applies the completed-handoff standard.
What referral partners should be prepared to confirm
Identity and authority
Who is referring, relationship to the person, consent/ROI authority, guardian/custody status when applicable.
Reason for referral
Observable needs, functioning, urgency, requested assistance, and known safety concerns—through the secure workflow.
Current providers and systems
Relevant treatment, medical, school, court, child welfare, housing, peer, or other involved systems with consent.
Access needs
Language, disability, transportation, technology, schedule, caregiver, location, and financial barriers.
Coverage and authorization
Coverage information through the secure system and any known authorization/referral requirements.
Communication plan
Who receives status updates, within what consent boundary, and what constitutes closure.
Source and publication control
Designed from Reach One’s controlled planning record
This page is generated from the Reach One website/strategic planning package, SPW readiness baseline, executive decision register, program-design materials, and website build charter. Production publication still requires current evidence, named approval, workflow testing, and a rollback path for any claim that can change.