Referral-to-placement workflow
Every stage has an owner, a next action, and a definition of done, from referral source through placement or a recorded lost reason.
Lost referral opportunities, slow intake movement, and disconnected handoffs are workflow problems. Solvhaus maps how referrals move through your team today, then implements ownership rules, tracking, authorization visibility, and the pipeline view admissions leaders can run every week.
Solvhaus implements referral management for behavioral health programs and the admissions software workflow around it: intake ownership, speed-to-contact rules, VOB and authorization visibility, bed allocation, and a pipeline admissions directors can run every week. Every referral source gets a record, an owner, and a closed loop back to the partner who sent it.
Admissions directors know the feeling: a strong referral, a slow first call, a missing VOB, a partner who never heard back, a bed that was open yesterday. The work is real. The system around it is not, so opportunities leak between stages and nobody can see where.
The workflow below is the one every treatment center runs, whether or not it is written down. The failure points are where manual versions lose referrals. Each stage needs an owner, a next action, and a record.
Five-stage admissions workflow: referral source, inquiry and intake, verification of benefits and clinical review, bed allocation, then CRM and EHR sync. Each stage lists where the manual version breaks.
Every stage needs an owner, a definition of done, and a place the outcome is recorded. That is the system BedFlow and the surrounding architecture are built to hold.
Set your monthly inquiries and the share that advances at each stage today, then the version with owners and next actions. The difference is arithmetic on your inputs, not a claim.
Five stages from referral source to CRM and EHR sync. For each stage you set the share of records that advance, once for how it runs today and once for the version with owners and next actions. Bars show how many records enter each stage in each scenario, and the difference in placements per month at your volume.
| Stage | Today · enter | Today · leak | Target · enter | Target · leak |
|---|---|---|---|---|
| Referral source | 60 | 9 | 60 | 5 |
| Inquiry / intake | 51 | 15 | 55 | 10 |
| VOB / clinical review | 36 | 9 | 45 | 7 |
| Bed allocation | 27 | 5 | 38 | 4 |
| CRM / EHR sync | 21 | 2 | 35 | 1 |
| Placed | 19 | 34 |
This model runs on the numbers you enter. Defaults are illustrative placeholders, not client results, and nothing here is a forecast or a promise.
Every stage has an owner, a next action, and a definition of done, from referral source through placement or a recorded lost reason.
Routing, coverage, and escalation so the first human response is not a matter of luck.
Partners, channels, and campaigns attributed at the inquiry, and the loop closed back to the partner.
VOB and auth status on the same record as the person, with dates the team can act on.
Open beds visible to admissions and BD by program and house, so a bed is not promised twice.
A board admissions, UR, and leadership look at together, plus the weekly cadence to use it.
Where the admissions pipeline is configured and adopted.
The wider operating model this workflow sits in.
Referral queue, bed availability, and authorization tracking in one working system.
How referral sources and paid inquiries end up in the same pipeline.
A systems conversation is a working discussion with someone who owns admissions, operations, or growth. Bring the messy version.