Re-authorization is a revenue event, not an admin task
An authorization expires on the 9th. The renewal is approved on the 30th.
In between, one of two things happened, and both of them cost you.
The two versions of a gap
You paused. The clinical team held sessions until the approval came through. Three weeks of nothing. The clinician was on payroll, the family lost continuity, and the client came back with regression that will take longer to recover than the gap itself.
You continued. Sessions were delivered on the assumption that the renewal would be retroactive. Sometimes it is. Often it is not, or it is retroactive to the approval date rather than the expiry date, which is the same thing as not. Full cost incurred, no revenue, and no appeal because there was nothing to appeal against.
Practices tend to have a default. Whichever yours is, it is being applied without anybody costing it.
The cost of one gap
One client, 15 hours a week, blended agreed rate $75.
Illustrative arithmetic, not a client engagement.
Six gaps a year across forty clients is not a lot. It is 15 percent of your book having one interruption each, which is well within normal for a practice with no early-trigger process.
Twenty-eight thousand dollars is not a rounding error, and it is entirely avoidable, because the expiry date was known six months in advance.
Why it belongs on the cash forecast
Every other predictable revenue interruption gets forecast. Seasonality gets forecast. Holiday closures get forecast. A clinician’s parental leave gets forecast.
An authorization expiring is more predictable than any of those. The date is in your system. The approval turnaround for each payer is knowable from your own history. The client’s weekly hours are known.
So the forecast line writes itself: for each authorization ending in the forecast period, the expected gap in days multiplied by the client’s weekly revenue. It will be wrong on individual clients and close in aggregate, which is what a forecast is for.
Doing this once tends to change behaviour faster than any amount of process documentation, because the number lands in front of the person who cares about cash rather than the person who cares about paperwork.
The trigger date is not the expiry date
The most common fix — “submit the renewal 30 days out” — is usually not enough, and it is not enough for a boring reason: 30 days is the same for every payer, and payers are not the same.
Work backward instead. Take your median approval turnaround for that payer from your own last twelve months. Add the time your BCBA needs to write the request, which is real and is usually a week. Add a buffer equal to half the turnaround, because the median is not the worst case.
A payer with a 21-day median turnaround needs a trigger at 21 plus 7 plus 10, which is 38 days. A payer at 45 days needs 45 plus 7 plus 22, which is 74. Same practice, two triggers, because the constraint is not yours.
And if you do not know your median turnaround by payer, that is the thing to go build. It is one query against approvals you already have.
The conversation with the family
Worth a line, because it is the part that gets skipped.
If you are going to pause during a gap, the family should hear it from you two weeks before it happens, not on the morning of. A gap explained in advance is an administrative inconvenience. A gap discovered on arrival is a reason to look at another provider.
Five checks you can run this week
1. Pull your median approval turnaround by payer for the last twelve months. Not the number the payer quotes. Yours.
2. Set a trigger date per payer using turnaround plus writing time plus half the turnaround as buffer. One number per payer, not one for the practice.
3. List every authorization expiring in the next 90 days and check whether the renewal has been submitted against that payer’s trigger date. Anything past it is already late.
4. Count the gaps in the last twelve months and multiply by the affected clients' weekly revenue. That is the number for the forecast and for the partner meeting.
5. Decide the default, in writing. Pause or continue. Whichever you pick, the clinical team and the billing team should not be picking differently on the same day.
The number to actually track
Median approval turnaround by payer, and the number of authorization gap days in the period.
Pair it with gap days multiplied by the affected client’s weekly revenue. That figure belongs on the cash forecast, not in an admin report.
A single practice-wide trigger date is not a control, because the constraint belongs to the payer and payers differ.
Where this sits
This is the second of eight stages where ABA revenue leaves. Stage 01 is the reservoir — what a client will realistically receive. Authorization burn is what happens when delivery and authorization stop lining up.
A gap is the most predictable revenue interruption in the business, which is what makes leaving it unforecast hard to defend.
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.
