The last stage you can fix without a payer on the phone

Draw a line under this chapter.
Above it — the reservoir, authorizations, cancellations, session conversion, getting the claim out the door — everything is yours. Your schedule, your clinicians, your notes, your queue.
Below it — clean claims, rate integrity, recoupments — you are dealing with a payer. You can be right, be documented, be on time, and still be waiting on somebody else’s adjudication cycle.
That line is the most useful thing on the Leak Map, and it is the reason to work the stages in order.
Why order matters more than size
The instinct is to go after the biggest leak first. Usually that is wrong, for two reasons.
The first is dependency. A denial at stage 06 frequently originates at stage 02 — the authorization was wrong, or expired, or for the wrong code. If you attack the denial rate without fixing the authorization process, you are reworking the same error forever. The downstream leak is a symptom and you are treating it as a diagnosis.
The second is control. Fixing something that requires a payer to agree takes a quarter, minimum, and it takes a person with the patience to sit on hold. Fixing something inside your own building takes a decision and a fortnight. If you have limited management attention — and every practice does — spending it on the things you control returns faster.
What “you control it” actually buys
Illustrative arithmetic, not a client engagement.
Add the four stages you control outright and it is $10,400 a week, fixable inside a month, requiring nobody’s permission.
Stage 06 is bigger per week than stage 04 and stage 05 individually. It is also a quarter of work with a dependency on somebody else’s process. Start there and you will be four weeks in with nothing to show, which is how revenue cycle projects die.
The sequencing argument in one sentence
Fix upstream first, because the downstream leaks are partly made of the upstream ones, and because you will need the early wins to keep the room’s attention for the slow work.
That is not a productivity aphorism. It is the difference between a project that finishes and a project that becomes a standing agenda item.
What to do in the month
Week one: build the converted-and-unbilled report and the completed-and-unconverted report. Two queries. You now have both of the stages you control end to end.
Week two: work the stuck piles. Not the queue — the piles. Every practice has two or three causes sitting under most of the aged rows, and clearing those is a morning’s work once you can see them.
Week three: set the cadence. Daily for unconverted, daily for unbilled. A weekly check finds the problem four days after it stopped being cheap to fix.
Week four: write down who owns each report and what number they are aiming at. An owned report with a target is a control. An unowned report is a file.
Then start on stage 06, with a clean upstream and a room that has watched you release $45,000 of working capital without asking anyone for anything.
The one thing not to do
Do not announce a revenue cycle initiative. Do not build a deck.
Build the two reports, work the piles, and let the cash show up. The argument for stage 06 will be much easier to make from a position of having already delivered something than from a position of having a plan.
Five checks you can run this week
1. Draw the line on your own Leak Map. Mark every stage by who has to act. If you cannot say, that is the first thing to settle.
2. Total the leaks above the line. That is your controllable number and it is the only one worth putting in front of a partner meeting this quarter.
3. Build the two reports — completed and unconverted, converted and unbilled. Nothing above the line is manageable without them.
4. Find the two or three causes under the oldest rows in each. It is almost never a hundred separate problems.
5. Name an owner and a target for each report before you touch stage 06. Without those, the leak reopens the week attention moves on, and you will get to have this conversation again next year.
The number to actually track
Total weekly leak across the four stages you control outright, held against the four you do not.
Pair it with an owner and a target per report. An unowned report is a file, not a control.
A single practice-wide leak number hides the thing that matters most, which is who has to act.
Where this sits
This is the fifth of eight stages where ABA revenue leaves, and the last one you can fix without a payer on the phone. Everything downstream needs somebody outside your building to act.
Sequence matters more than size here, because the downstream leaks are partly made of the upstream ones.
A Leak Map Assessment measures all eight — the reservoir, authorization burn, cancellations, session conversion, conversion to billed, clean claims, rate integrity and recoupments. A claims audit is a different instrument. It starts once a session has been converted and billed, and reconciles the back half of the cycle to cash.
Aimline closes the books, oversees the revenue cycle, and sits in the CFO seat for ABA practices. We run claims audits scoped to a payer book, and Leak Map Assessments that measure the full cycle — three weeks, $7,500 fixed. Either one gives us a verified number to run oversight against, and the report is yours whether or not you engage us to fix what it finds.