Treatment centers and recovery housing operators lose admits to spreadsheets, inboxes, and memory. bedflow connects referral partners, referrals, bed matching, and follow-up in one operational layer, then shows which sources actually fill beds. It runs alongside your EMR, which stays the clinical record.
The walkthrough maps your referral, bed-visibility, and follow-up bottlenecks on your own setup. The demo is a read-only sample workspace you can open right now.
From referral partner to filled bed, on one track.
Five steps every program already runs by hand. bedflow gives each one an owner, a status, and a record, so the handoffs stop depending on who remembers.
- Step 1 of 5
Referral partner
Hospitals, clinicians, interventionists, alumni, and web inquiries live in one partner directory with contacts, visit history, and send-versus-receive tracked.
Prevents: A partner goes quiet and nobody notices for a month.
- Step 2 of 5
Referral
Every inquiry lands as a referral with an owner, a stage, and a clock. Stage time limits flag anything that stalls before it goes cold.
Prevents: An inquiry sits in an inbox until the family has moved on.
- Step 3 of 5
Bed match
Match against a live bed board that shows open beds, holds, planned discharges, and the waitlist across every house and program.
Prevents: Promising a bed that is already held or still occupied.
- Step 4 of 5
Admissions follow-up
Callbacks, insurance verification, clinical review, and accept or decline decisions queue as owned tasks on the right person's day.
Prevents: Follow-through that only exists in someone's head.
- Step 5 of 5
Outcome and source visibility
Every admit, decline, and discharge ties back to the partner and channel that sent it. Reports show which sources actually fill beds.
Prevents: Spending time and money on sources that never convert.
Each step is a live surface in the product: the partner directory, the referral board, the bed board, the follow-up queue, and the source and partner reports. Open the demo workspace
Referral relationships, open beds, and follow-up are fragmented by default.
Most programs run admissions across a spreadsheet, three inboxes, house-manager texts, and an EMR built to document care, not to fill beds. Partners go quiet, holds get forgotten, and nobody can say which source produced last month's admits.
Referral work is scattered across tools that were never built for admissions.
- Referral spreadsheet
Updated when someone remembers. No owner, no clock, no stage.
- Inboxes and text threads
Partner sends and callbacks buried across three people's phones.
- Bed counts by phone
Admissions calls each house manager to learn what is actually open.
- EMR notes and memory
Source of the admit lives in an intake note, if it was written down.
One front office for referrals, beds, and follow-up. Your EMR stays the clinical record.
- One referral board
Every inquiry has an owner, a stage, and a time limit that flags stalls.
- Live bed board
Open beds, holds, planned discharges, and the waitlist across every house.
- Follow-up queue
Callbacks, verifications, and decisions land on the right person's day.
- Source reporting
Admits tie back to the partner and channel. Reports show what fills beds.
bedflow is the right fit if
- You run residential, detox, PHP, IOP, or recovery housing
- Referrals are tracked in spreadsheets, email threads, or someone's memory
- Nobody can see live open beds, holds, and planned discharges across every house
- You cannot say which partners or channels produced last month's admits
- If that is you, a walkthrough on your own partner list and bed count shows what changes in week one. Book a walkthrough
Runs alongside your EMR. No records migration.
bedflow is the front office: referral partners, referrals, beds, follow-up, and source attribution. Your EMR stays the clinical record. During onboarding we import a census export, map houses and beds, and load the workspace. From there, the EMR sync keeps it current: referrals, admissions, discharges, and census events from KIPU, Sigmund, BestNotes, or any EMR that can push to a webhook land in intake, follow-up, and the bed board automatically, with every sync logged. No write-back to the EMR, ever.
Patient and census events sync in as referrals, admits, discharges, and bed status. Census export mapped during onboarding.
Admission and discharge events pushed from Sigmund workflows; roster export mapped during onboarding.
Client status and program changes sync on update; roster export mapped to your beds.
Share a census export from your EMR. No custom engineering on your side.
Our team maps clients, programs, houses, and beds to bedflow. You approve, we load. Typical turnaround is 3 to 5 business days.
Admissions, BD, and operations work in bedflow. Clinical staff stay in the EMR. Connect the EMR sync and admits, discharges, and census update the bed board on their own; every run is logged and reviewable.