Understanding healthcare revenue leakage

The short version

Revenue leakage is money your health system should earn but does not, because required work was not completed or documented in time.

It is not only a billing issue.

Many leakage drivers start upstream in execution: missing prerequisites, stalled follow ups, incomplete documentation, and unclear ownership between teams.

If you want to reduce leakage, you need to find the workflow steps where work stalls, assign ownership, verify completion, and prove outcomes.

Why this is getting worse

Two forces are increasing the pressure.

First, prior authorization volume is high and decisions are not always aligned with clinical reality. In Medicare Advantage alone, there were nearly 50 million prior authorization requests in 2023, and millions were denied. [4]

Second, claims denials and payer audits create expensive rework. In one industry survey, a significant share of providers reported denial rates at or above 10 percent. [5]

That means leakage is no longer a back office problem. It is now a leadership level operating problem.

Where leakage really starts

Leaders often first see leakage as denials or write offs. That is late in the chain.

Earlier in the chain, leakage looks like this:

• A referral is placed, but scheduling never completes.
• A prior authorization requires documents or labs, but a requirement is missing.
• A patient needs a follow up after discharge, but it is not completed inside the window.
• Documentation is incomplete at the moment it is needed.

These are execution failures.

You can spend money fighting denials, or you can prevent upstream failures that create denials.

The common upstream drivers

1) Missing prerequisites

Most workflows have prerequisites: documentation, criteria, labs, imaging, insurance details.

If a prerequisite is missing or expires, the entire care path stalls.

2) Unclear ownership

Work crosses teams. Access, specialty clinics, nursing, revenue integrity, and patients all play a role.

If no one owns the next action at each stage, work will sit.

3) Time windows

Many steps have deadlines. Some are clinical. Some are payer driven.

If you cannot see time windows in real time, you discover misses late.

4) Documentation gaps

Documentation is often produced after the fact.

The problem is timing. If the right document is not present at the moment it is needed, claims are delayed, denied, or appealed.

A CFO friendly way to think about leakage

Treat leakage like a pipeline with proof gates.

Every workflow has a small set of gates that must be true.

Examples:

• Referral gate: scheduled within X days.
• Prior authorization gate: prerequisites complete before submission.
• Care gate: service performed.
• Documentation gate: required note and codes present.

Leakage happens when gates are missed.

Your job is not to chase every claim. Your job is to make gate misses visible and preventable.

What to measure

Start with a small set of measures that finance and operations can both trust.

• Leakage exposure: count of open work items past a deadline, by workflow
• Exception rate: percentage of cases with a prerequisite miss, missing documentation, or stalled scheduling
• Time to completion: signal to verified completion
• Rework burden: touches per case, by workflow
• Denial related queues: volume of rework created by missing information and medical necessity requests

Then tie measures to owners.

No owner means no change.

A practical method: Detect, route, verify, prove

If you can only implement one framework, implement this.

• Detect signals and constraints as soon as they exist
• Route the next action to a clear owner
• Verify completion with evidence
• Prove outcomes with a timestamped audit trail

That audit trail matters in procurement, audit readiness, and finance trust.

How to improve leakage without new headcount

Most systems try to solve leakage by adding people.

A better starting point is to reduce avoidable rework.

Start where financial exposure is highest and most visible.

Common first picks:

• prior authorization readiness
• referral completion
• post discharge follow up

Run a short cycle:

1. baseline the exception rate and time to completion
2. surface stalls early with an owner
3. verify prerequisites and documentation
4. prove the delta

Then expand.

Common questions

Is revenue leakage only an RCM problem

No. Billing and claims are downstream. Upstream execution determines whether downstream work is clean.

What is the relationship between prior authorization and leakage

Prior authorization is a dependency with time windows and prerequisites. High volume and denial risk make it a major source of avoidable rework if prerequisites are not tracked and verified. [4]

Does this require replacing systems

No. The EHR, scheduling system, and billing system remain systems of record. The missing layer is workflow proof across systems.

References