Where Margin Leakage Hides in Healthcare Field Services
Six simultaneous leaks – each small enough to ignore individually, large enough in aggregate to represent the difference between a comfortable business and a struggling one.
$200K–$500K
annual margin erosion from six simultaneous operational leaks
Category
Teardown
Published
March 2025
Read Time
8 min read
Overview
If you operate a healthcare field services company – mobile imaging, home health, hospice, mobile diagnostics – your margin is leaking. Not catastrophically. Incrementally. In five or six places simultaneously, each small enough to ignore individually, large enough in aggregate to represent the difference between a comfortable business and a struggling one.
I install operational AI infrastructure inside companies like yours. Here is where I consistently find the leaks.
Leak
1. The Billing Classification Gap
Your techs complete work in the field. Someone classifies that work for billing. The classification is wrong more often than you think.
In a mobile imaging company performing 500+ exams per month, we found 58 completed exams in a single month tagged "Do Not Send" at facilities with active billing contracts. That's $10,100/month – exams performed, never invoiced. The billing team didn't make an error in the traditional sense. They followed the process. The process had no validation step.
Where It Hides
Between the dispatch/worklist system (what actually happened) and the billing system (what gets invoiced). Nobody cross-references them. The gap compounds monthly.
Diagnostic Question
When was the last time someone compared your completed worklist count against your billing export count, facility by facility? If the answer is "never" or "I'm not sure," you have this leak. Every mobile healthcare company I've audited does.
Leak
2. Expired Contracts with Active Billing
You have facilities that still order from you under contracts that expired six months ago. You may not know which ones.
In one audit of 375 facility relationships, we found 16 facilities actively billing under expired agreements. Services delivered, payments collected – but at rates set years ago, with no mechanism to update them. Meanwhile, 76 additional facilities were ordering with no contract at all. Not expired contracts – no contracts. Ever.
Where It Hides
In the gap between your contract records and your billing activity data. Contract status is a static field in a spreadsheet. Billing activity is dynamic. Nobody connects them.
Diagnostic Question
If you wanted to raise prices by 5% next quarter, how many facilities could you do that for today, with a signed agreement that permits rate adjustments? Most operators cannot answer this without a week of manual research.
Leak
3. Manual Eligibility and Verification Waste
For insurance-billed exams, verification happens before or after the exam. When it happens after, and eligibility was wrong, you've deployed a tech, consumed supplies, used vehicle time – and the claim will be denied or underpaid.
The cost isn't just the denied claim. It's the tech-hour that produced zero revenue, the rebilling labor, and the 60–90 day delay before you find out the claim was rejected.
Where It Hides
In your denial rate and your average days to payment. High denial rates aren't a billing team problem – they're a verification timing problem. Every denied claim has an embedded field cost that never appears on the denial report.
Diagnostic Question
What percentage of your insurance claims are denied on first submission, and what is the average time between exam completion and denial notification?
Leak
4. Routing Inefficiency Compounding
Your techs drive the routes they've always driven. Those routes were designed by whoever was dispatching when the facility was added – not by geographic optimization.
The compounding effect is subtle. One extra 15-minute drive per tech per day across 15 techs is 3.75 hours of windshield time daily. That's 975 hours annually – roughly half a full-time employee worth of labor spent driving instead of completing exams. At a blended cost of $35/hour, that's $34,000/year in direct labor waste. Add fuel, vehicle wear, and the exams not completed because the tech ran out of shift hours, and the number doubles.
Where It Hides
In your dispatch system's lack of geographic analysis. Most dispatch systems track orders by facility and time – not by driving distance between stops. Without that data, you cannot know whether routes are optimized or habitual.
Diagnostic Question
Do you know the average drive time between stops for each tech, and has anyone analyzed whether resequencing routes would reduce total daily drive time?
Leak
5. Reporting Lag as a Cost Center
Your accountant closes the books 30 days after month-end. Your billing company sends AR reports monthly. Your operational data lives in a dispatch system that only exports CSVs.
The lag between "something happened" and "leadership knows about it" is the most expensive gap in your business – because every other leak on this list persists longer when reporting is slower.
The billing classification gap runs for months because nobody has a monthly validation report. Expired contracts accumulate because nobody reconciles contract status against billing activity. Routing inefficiency compounds because nobody can see facility order volume by geography.
$31,700 discrepancy between QuickBooks balance and actual bank balance – not an error, but reconciliation lag.
Where It Hides
In the assumption that reporting speed is a nice-to-have rather than a margin lever. It's not.
Diagnostic Question
How many hours per week does someone in your organization spend pulling data from systems and assembling it into reports for leadership? If the answer is more than zero, that time is both a direct cost and a compounding cost – because every hour spent assembling reports is an hour not spent acting on what the reports reveal.
Leak
6. Overtime as a Symptom
High overtime in field services is rarely a staffing problem. It's a routing problem, a scheduling problem, and a visibility problem wearing a staffing costume.
When techs regularly exceed shift hours, the reflex is to hire another tech. But if the overtime is caused by inefficient routing (Leak #4), late-add orders that could have been batched, or poor geographic clustering of assignments, another tech just distributes the same inefficiency across more people.
Where It Hides
In your overtime line item. The dollar amount is visible. The root cause is not – because your dispatch system doesn't tell you whether overtime was caused by high volume (legitimate) or poor routing (fixable).
Diagnostic Question
When a tech works overtime, do you know whether it was because they had too many exams or because they drove too far between them?
The Pattern
These leaks share three properties:
They exist between systems, not inside them. Your dispatch system works. Your billing system works. Your accounting system works. The leaks live in the gaps – where data should be cross-referenced but isn't.
They compound silently. No single month's leak triggers an alarm. A $10K billing gap doesn't show up on a P&L review. An expired contract generating $2K/month in services at the old rate doesn't cause a crisis. But twelve months of six simultaneous leaks at $5K–$20K each adds up to $200K–$500K in margin erosion.
They're fixable with infrastructure, not heroics. The solution to every leak on this list is the same: build an automated check that runs periodically, compares what should be true against what is true, and surfaces the discrepancies for human review. Not AI magic. Not enterprise software. Validation pipelines, cross-reference reports, and dashboards that update faster than monthly.
Takeaway
The first step is always a diagnostic: pick any two systems in your operation that should agree, and compare them. Field completions vs. billing. Contracts vs. billing activity. Dispatch times vs. actual drive times. Cash in QBO vs. cash in the bank.
If they match perfectly, you're the first operator I've met where they do.
Brian Truax is the founder of Actional, an AI Systems Operator that installs operational infrastructure inside founder-led service companies. Based in Houston.
These patterns exist in your operation