The ROI of referral intake automation for a multi-location practice on Elation Health comes from two sources: staff hours recovered (minutes per referral × monthly referral volume × loaded staff cost) and revenue recovered from referrals that used to leak before scheduling (leakage reduction × referral volume × average downstream value per new patient). For most multi-location practices, recovered revenue outweighs labor savings by a wide margin, and payback typically lands within the first few months.
Why is ROI the right question for referral intake automation?
Every vendor will tell you their product saves time. That's not enough to get a CFO or a practice owner to sign. The real question is whether the dollars you recover — in staff time and in patients you'd otherwise lose — exceed what the software and implementation cost, and how fast.
Multi-location practices on Elation are where this math gets most interesting. Each location usually has its own fax line, its own front desk, and its own way of handling referrals. That fragmentation creates two kinds of waste at once: duplicated labor across sites, and inconsistent follow-up that lets referrals slip. A Becker's survey on patient leakage found that leakage costs nearly half of healthcare organizations 10% or more of annual revenue. Referral intake is one of the most direct places to recover some of it.
The framework below lets you plug in your own numbers. Every assumption is labeled so you can swap it for your data.
Where does the labor savings come from?
Labor savings is the easier half to measure, so start there. The formula:
Monthly labor savings = referrals per month × minutes saved per referral ÷ 60 × loaded hourly cost
Referrals per month. Count every inbound referral across all locations, including ones that arrive by Direct or portal. Most multi-location practices undercount because nobody aggregates across sites.
Minutes per referral today. Time a sample. Include opening and classifying the fax, searching for or creating the patient in Elation, keying demographics and insurance, filing and tagging, requesting missing records, and handing off to scheduling. Practices that time it honestly usually land somewhere between 8 and 15 minutes for a clean referral, and far longer for incomplete ones that require back-and-forth.
Minutes saved. With automation handling routine referrals end to end, staff time drops to review of exceptions. A reasonable planning assumption is a 70–80% reduction in hands-on time per referral.
Loaded hourly cost. Use wage plus benefits, payroll taxes, and overhead — commonly 1.25–1.4× base wage for front-office staff.
Worked labor example
Assumptions for a hypothetical four-location practice: 600 referrals a month, 12 minutes each today, 75% time reduction, $28 loaded hourly cost.
- Current time: 600 × 12 = 7,200 minutes = 120 hours a month
- Hours recovered: 120 × 0.75 = 90 hours a month
- Monthly labor value: 90 × $28 = $2,520, or about $30,000 a year
That's roughly half of a full-time employee's hours. Useful, but rarely enough on its own to drive the decision.
How do you calculate recovered referral revenue?
This is the bigger number, and the one most ROI models skip. The formula:
Monthly recovered revenue = referrals per month × percentage-point reduction in leakage × average downstream value per new patient
Current leakage rate. Measure the share of referrals that never result in a scheduled first visit within 30 days. Industry analysis summarized in a Becker's whitepaper puts the share of referrals that never result in completed care at roughly half. Your number may be better, but most practices that measure it for the first time are surprised.
Leakage you can actually recover. Not all leakage is fixable. Some patients choose not to proceed, go out of network, or get better. Focus on process-driven leakage: referrals that sat in the inbox, waited on missing records, or got one callback attempt. A conservative planning assumption is a 5–10 percentage-point improvement.
Downstream value per new patient. Use 12-month collections per new referred patient, not just the first visit. For procedural specialties, this includes imaging, procedures, and follow-up visits. Pull it from your own billing data.
Worked revenue example
Same four-location practice. Assumptions: 600 referrals a month, a 6-point leakage reduction, and $400 average 12-month collections per new referred patient.
- Additional patients: 600 × 0.06 = 36 new patients a month
- Monthly recovered revenue: 36 × $400 = $14,400, or about $173,000 a year
Even with conservative inputs, recovered revenue is more than five times the labor savings in this example. That ratio is typical, which is why referral intake ROI conversations should lead with revenue, not headcount.
What other benefits matter for multi-location practices?
Some benefits are real but harder to put a precise number on. Include them in your business case as qualitative or loosely estimated items.
- Centralized intake. Automation lets you run referral intake from one team instead of a part-time role at every location. That makes coverage for vacations and turnover much easier.
- Faster days-to-schedule. Patients booked within a couple of days are far less likely to go elsewhere. Faster scheduling also improves the referring provider's experience.
- Fewer incomplete referrals reaching the schedule. Automated completeness checks reduce day-of-visit surprises like missing authorizations or imaging.
- Less overtime and temp staffing. Referral backlogs after holidays or staff departures often get cleared with overtime. Automation absorbs those spikes.
- Referrer retention. Closed-loop acknowledgments protect your relationships with the offices that send you the most patients.
- Standardization across sites. One set of rules across every location makes performance comparable and problems visible.
How sensitive is the ROI to your assumptions?
A good business case shows what happens when the assumptions are wrong. Run three scenarios using the same four-location example and see where the decision holds.
Conservative. Leakage improves by only 3 points, downstream value is $250 per patient, and time savings are 60%. Recovered revenue drops to 18 patients × $250 = $4,500 a month, and labor savings to 72 hours × $28 = about $2,000. Combined, roughly $78,000 a year.
Base case. The worked examples above: about $14,400 in recovered revenue and $2,520 in labor savings a month, or roughly $203,000 a year.
Optimistic. Leakage improves by 10 points and downstream value is $600 per patient for a procedure-heavy specialty mix. Recovered revenue reaches 60 × $600 = $36,000 a month.
The useful insight is which variable moves the answer most. In nearly every multi-location model, it's downstream value per patient and leakage reduction — not minutes saved. That tells you where to spend your measurement effort: get your 12-month collections per referred patient right, and measure your true baseline leakage before go-live. If the conservative scenario still clears your cost hurdle, the decision is low-risk.
What does referral intake automation actually cost?
An honest ROI model counts every cost, not just the license.
Software. Pricing models vary: per referral, per page, per location, per provider, or platform fees. Ask vendors to quote against your actual volume and location count.
Implementation. Expect a few weeks of project time covering the Elation API connection, document type and tag mapping, completeness rules, and staff training. Some vendors include implementation; others charge separately.
Elation integration setup. API access is configured at the practice level. Your Elation admin will need to authorize the connection and confirm permissions.
Internal time. Someone has to own the project: defining rules, reviewing the parallel run, and managing change at each location. Budget 2–4 hours a week from an operations lead for the first two months.
Change management. Staff whose jobs shift from keying referrals to working exceptions need clear new responsibilities. Practices that skip this step see slower adoption and lingering manual workarounds.
Using the example above, if total first-year cost lands around $40,000–$60,000, combined labor and revenue benefits of roughly $200,000 would pay it back within the first quarter or two. Your numbers will differ, which is why the inputs matter more than the outputs.
What should you measure in the first 90 days to prove it?
The fastest way to lose executive support is to launch and not measure. Capture a baseline for at least four weeks before go-live, then track the same metrics monthly afterward.
- Referral volume by location. Confirms you're capturing every channel.
- Staff minutes per referral. Time samples before and after.
- Percent of referrals handled without human touch. Shows automation coverage.
- Days from receipt to scheduled. Usually the first metric to improve.
- Referral-to-scheduled rate within 30 days. Your leakage number.
- New patient visits from referrals. The revenue driver.
Report these to leadership at 30, 60, and 90 days. By day 90, you should be able to replace the assumptions in your model with actual results.
How does Honey Health fit into the model?
Honey Health builds the kind of automation modeled above. Its Referral Intake agent works inside Elation to capture, classify, extract, and file referrals across every location, request missing records automatically, and hand complete referrals to scheduling. For multi-location practices, it also makes centralized intake practical, since one team can manage exceptions for every site from a single queue. When you run your ROI model, use your own baseline data and ask any vendor, Honey Health included, to show results against it.
Frequently Asked Questions
What is a typical payback period for referral intake automation?
It depends on volume, current leakage, and downstream value per patient. Practices with high referral volume and meaningful process-driven leakage often see payback within a few months, because recovered patient revenue usually exceeds software cost quickly. Lower-volume practices may see payback closer to a year.
Should we count recovered revenue or only labor savings?
Count both, but present them separately. Labor savings are easier to verify and appeal to cost-focused stakeholders. Recovered revenue is usually larger and is the strategic case. Use conservative leakage assumptions so the revenue estimate holds up to scrutiny.
How do we measure referral leakage before automation?
Pull every referral received over one to three months, then check how many resulted in a scheduled first visit within 30 days. Tag reasons for non-scheduling where possible, such as unreachable patient, incomplete referral, or patient declined, to separate fixable process leakage from unavoidable losses.
Does referral intake automation reduce headcount?
It can, but most multi-location practices use it to absorb growth, avoid backfilling open roles, and shift staff to higher-value work like patient outreach and referrer relationships. Plan around redeployment rather than layoffs; it makes adoption smoother and preserves institutional knowledge.
Is the ROI different for multi-location practices than single sites?
Usually it's higher. Multi-location practices have more referral volume, more fragmented intake processes, and more duplicated effort across sites. Centralizing intake through automation captures labor savings and consistency gains that a single location can't realize to the same degree.
