Part 2 of a three-part series
Net collection rate, denial rate, days in A/R, and aging A/R are all metrics most RCM teams report on, and they are useful. Each one tells us whether revenue moved the way we expected it to. What they cannot do is tell us in time.
A payer may take 14 to 45 days to adjudicate a claim, and sometimes as long as 60. So the denial rate reviewed on any given day is often describing an operational pattern from six to eight weeks earlier. By the time the number moves, the activity that produced it has had time to repeat itself hundreds of times.
Those are lagging indicators. They report a decision the payer has already made. Leading indicators show whether the work behind a claim is functioning while there is still time to act on it. I spent a good portion of my session at the SUD Business Summit on this idea...
Why lagging revenue cycle metrics fall short
Here is the piece that tends to land hardest: a claim getting paid does not guarantee you keep that money.
A payment is the clearest lagging indicator there is. It reflects how a payer adjudicated a claim based on the information in front of them at that moment, and that decision can be revisited. Takebacks and recoupments arrive months later, pull back revenue that was already recognized, and send the claim back to a team that had closed it. What gets reported as collected this quarter is not always what you keep.
Eligibility gives us an even clearer example. A patient receives care, and the claim eventually comes back because there was no active coverage on the date of service. By the time the team has worked through the process and reached the answer, three months may have passed. The patient has already received care. They may no longer be an active patient. The likelihood of collecting that balance has changed dramatically.
The denial eventually reports that there was a problem. A stronger eligibility process creates the chance to catch it before the service is ever delivered. That is the difference between measuring an outcome and watching the conditions that produce it.
What leading indicators look like in revenue cycle management
There is no universal set of leading indicators that every organization should adopt. A more useful approach is to look at the activities that make up the revenue cycle and ask what evidence would show that an activity is working before the payer weighs in.
That question opens up a very different set of things to measure:
Touches per claim before payment. How many times does a biller handle a claim before it results in payment? Rework volume says something about efficiency and something about what is happening upstream. When the same claims keep coming back, that pattern usually points to a condition earlier in the process that is worth investigating.
Eligibility verification audits. What share of patients had correct eligibility verification completed before services were provided in a given period? That number is available right now. It does not require a payer to weigh in, and it surfaces a problem well before that problem becomes a denial.
Denial categorization tracked over time. Read it the way you read payer mix. Pull denials by category each month, look at each category as a share of total denials rather than a raw count, and watch the direction of travel. If eligibility denials fall, that movement can be connected back to a specific change. If coordination of benefits denials climb, there is something to get ahead of. The movement carries more information than the total.
Time to payment by payer. Track average days from submission to payment for each payer, then watch for the one sitting well outside the rest. When a payer consistently takes far longer, the cause is sometimes a configuration issue hiding inside a performance number. A 68-day average traced back to remittances arriving by mail rather than electronically. On a dashboard, it reads as a payer problem. In practice, it was a setup that could be corrected.
These are examples, not a prescribed scorecard. The way of thinking behind them is the part worth borrowing.
How to build leading indicators around the work
Instead of starting with a fixed list of KPIs, start with what your revenue cycle needs to accomplish. The right metrics follow from there.
Start by mapping the core activities in your revenue cycle: scheduling, intake, eligibility, authorization, documentation, charge capture, contracting, credentialing, and claim submission. Take them one at a time and ask what evidence would show that this job is being done well.
Eligibility has an answer. So does credentialing. So does scheduling, even though most people would not think to put scheduling on a revenue cycle map. When a patient picks up the phone to schedule an appointment, they are already participating in the revenue cycle.
Defining the jobs-to-be-done first makes the metrics easier to identify. It also makes the gaps easier to see, which is usually the more valuable outcome. You start to see where ownership is unclear, where a process depends on manual intervention, or where no one is measuring whether a critical step is working at all.
And when a number does move, keep going. If you have little humans in your life who ask “why?” constantly, you already know the technique. Ask why the metric changed. Then ask why that happened. Keep following the thread until you reach something your organization can actually act on.
A metric should get you to the question. Investigation gets you to the answer.
How leading indicators support denial prevention
Watching leading indicators gives your team a chance to act before a problem reaches the denial queue.
When the denial queue is the primary thing generating work, it sets the agenda. The team appeals, resubmits, and closes claims while the conditions that produced those denials may still be in place upstream, creating the next wave.
A common response to growing denial volume is to add capacity. More people move the queue faster, and that capacity goes into reworking claims that have already been touched once. The volume arriving each week stays where it was, because the conditions creating it are still occurring earlier in the revenue cycle.
Leading indicators give you another place to intervene. If an eligibility audit shows that verification accuracy is slipping, that becomes a conversation with the team responsible for the process today. If documentation turnaround begins moving in the wrong direction, those encounters can be investigated before they turn into delayed claims. If one denial category starts climbing, the pattern can be followed while it is still forming.
That is where preventative RCM becomes practical. It shortens the distance between the moment a problem begins and the moment someone can do something about it.
The goal is not to eliminate the need for downstream metrics. Denial rate, days in A/R, and collections will always matter. The goal is to pair those outcomes with signals that describe how the system is behaving before the financial impact fully arrives.
Let’s get tactical: setting up leading indicators
Pick one job. Eligibility is a useful first choice because the activity happens early and the connection to downstream revenue is easy to trace.
Define the one metric that would show that job is working. Measure it for 30 days before changing anything, so you know what normal looks like before you react to movement. When the number moves, investigate the why before deciding the fix. Then take the next job.
Over time, those signals give an organization a way to read how the revenue cycle is behaving while there is still time to influence the outcome.
In Part 3, I'll take on another assumption worth examining. What AI genuinely does well in revenue cycle work, where human judgment still does the reading, and how to tell the difference.
Separating a staffing problem from a payer, technology, or process problem is its own diagnostic. Our 3-Question Triage walks through the questions that point you toward where to investigate first. Download it here.
