How Do I Stop ABA Sessions From Running Past the Authorized Units Before the Reauthorization Comes Through?
How to Keep ABA Units From Running Out Before the Plan Ends
The goal is simple: every client’s authorized units tracked against what has been billed and scheduled, with the reauth already moving before the units run low. Here is what does that, move by move.
1. Build a Live Unit Ledger Per Client
The root problem is that the authorization gets treated as a date range when it is really a unit budget. The first move is a live ledger per client: authorized units, minus units already billed, minus units already scheduled and in progress, equals units remaining. Update it every week. When you can see that a 600-unit, 6-month authorization is on pace to empty at week 15, you can act at week 10 instead of finding out at week 18 when the denials arrive. You cannot manage a burn rate you are not measuring.
2. Set Alerts at 75 Percent Usage and 30 Days Before Expiration
A ledger nobody looks at is a spreadsheet, not a control. The second move is two standing alerts per authorization: one when unit usage crosses 75 percent, and one at 30 days before the authorization expires. Whichever fires first starts the reauthorization clock. The 75 percent alert catches the fast burners, the caseloads scheduled heavy enough to exhaust units well before the date, and the 30-day alert catches the ones pacing on schedule. Together they mean no authorization reaches its last units without someone already working the renewal.
3. Prepare the Reauthorization Packet Early, Not at the Wall
When the alert fires, the reauth packet gets built while there are still units and days left, not in a scramble after they are gone. That means the updated treatment plan, the progress data the payer wants to see, and the clinical justification for continued care assembled and submitted with a real buffer. Payer review time is unpredictable, so the packet has to go out early enough that even a slow review lands before the current units run out. Building it early is the difference between continuous care and a denied gap.
4. Reconcile the Burn Rate Weekly So Units and Calendar Stay in Sync
The whole failure is the burn rate drifting out of sync with the calendar unnoticed. The fix is a weekly reconciliation: for each client, are the units on pace to last the authorization period, or is the schedule burning them faster than planned? When a client is ahead of pace, the specialist flags it early so the reauth or a scope adjustment moves before the units are gone. Weekly is the cadence that catches a fast burner at week 8 instead of at the denial. Anything slower lets the units run out quietly.
5. Hand Utilization Tracking to a Dedicated Team
Clinics that stop delivering sessions past their authorized units do it by handing utilization tracking to a dedicated team: remote specialists who keep the ledger, watch the alerts, and prepare the reauth packets, live in 1 to 2 weeks. The BCBAs go back to clinical work instead of guessing at unit counts, a trained backup covers every gap, and the authorization stops being the thing that quietly empties before anyone checks. Below is what it sounds like when nobody owns it yet, in providers’ own words.
Key Pain Points and Discussions by Providers
real reports from practice staff, lightly edited
“We scheduled a client at ten hours a week against a six-month authorization and never did the math on the units. They ran out around week fifteen. Three weeks of delivered sessions denied, and the payer would not authorize a single one of them after the fact.” – clinic director, ABA therapy practice
“Nobody was tracking utilization percentage. The authorization had a start and end date, so everyone assumed it covered the whole period. It did not. The units emptied months before the date, and we only found out when the claims came back denied.” – billing lead, ABA clinic
“The denials for sessions billed past the units are the worst, because the care was real and appropriate. The clinician did everything right. We just never watched the unit count, and retroactive authorization for those dates was flatly refused.” – practice administrator, behavioral health group
“Our fast burners are the problem. A client scheduled heavy exhausts the authorization way ahead of the end date, and if we are only watching the calendar we miss it completely. We need to be watching the units, not the dates, and we never had the hours.” – BCBA, ABA therapy clinic
“Every time this happens it is the same story. Reauth request goes in late because nobody flagged that units were almost gone, and the sessions in between deny. If someone had been reconciling the burn rate weekly, we would have caught it a month earlier.” – operations manager, multi-site ABA group
Our Answer
Here is what we actually do. A dedicated remote specialist keeps a live unit ledger per client, authorized units minus what is billed minus what is scheduled equals what is left, and updates it weekly so a fast burner shows up long before the units run out. Two alerts fire on every authorization: one at 75 percent unit usage and one at 30 days before expiration, and whichever hits first starts the reauth. The specialist builds the reauthorization packet, the updated treatment plan, the progress data, the clinical justification, while there are still units and days left, and submits it with a real buffer against unpredictable payer review time. Our specialists are credentialed professionals working inside your practice management and billing systems, with AI drafting the first-pass tracking and packet and a human verifying every submission. This is our prior authorization support paired with an AI-first workflow, in one paragraph.
Why This Keeps Happening
If the math is that simple, why do clinics keep running past their units? Because the authorization is treated as a date range when it is really a unit budget, and the two do not empty at the same rate. A 600-unit authorization written for 6 months does not last 6 months if the client is scheduled at 40 units a week; it is gone around week 15. When a client is delivered more units per week than the authorization was paced for, care rendered after the approved units are used up denies as authorization-exceeded, and under CMS claim adjustment reason code 198, precertification or authorization exceeded, those claims are the practice’s responsibility, not the patient’s.
The tracking gap is what makes it invisible until it is too late. Nobody is reconciling utilization percentage against the calendar week by week, so the schedule keeps running and the units keep burning with no one watching the count. ABA billing guidance is consistent on this: a live unit ledger that tracks authorized minus billed minus in-progress units, plus reauthorization lead time before the authorization expires, prevents the large majority of these denials. Without it, the first signal that units ran out is a batch of denied claims weeks after the care was delivered. Closing that gap is exactly what an AI prior authorization workflow with human oversight is built to do.
And the cost lands twice. Reauthorizations are where ABA practices lose the most revenue, because when units run out mid-plan, treatment continues, claims go out, and the payer denies everything after the exhaustion point with retroactive authorization rarely granted. But the deeper cost is clinical: a child in active ABA treatment does not benefit from an interruption while a reauthorization catches up. The tracking gap does not just cost the clinic the denied sessions, it risks a break in continuous care that the treatment plan was specifically built to avoid.
Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:
| What you tried | What actually happened | Who ended up doing the work |
|---|---|---|
| Watched the authorization end date only | Units emptied weeks before the date and nobody noticed until claims denied | The calendar, which does not count units |
| Asked the BCBA to keep an eye on unit counts | Clinical work came first; the running unit tally was guesswork between sessions | A clinician doing it in their head |
| Submitted reauth when denials started appearing | Too late; the sessions in the gap were already denied and would not be backfilled | Whoever caught the denials in billing |
| Gave utilization tracking to a dedicated remote specialist | Live ledger per client, alerts at 75 percent and 30 days, reauth packet ready before units ran out | Someone whose whole job it is |
The Solution
So what does “someone whose whole job it is” look like on a heavy caseload? The specialist keeps a live unit ledger for every client, authorized units minus billed minus scheduled equals remaining, and updates it weekly, so a client burning 40 units a week against a 600-unit authorization shows up as a week-15 exhaustion at week 8, not at the denial. Two alerts stand on every authorization, 75 percent usage and 30 days to expiration, and whichever fires first starts the renewal. Most of these losses are a tracking-and-lead-time problem, and that is exactly what dedicated prior authorization support is built to solve before it becomes a denial.
Then comes the part the schedule cannot do on its own. When an alert fires, the specialist builds the reauthorization packet while there are still units and days left: the updated treatment plan, the progress data the payer requires, and the clinical justification for continued care, submitted with a real buffer against unpredictable review time. The reauth lands before the current units run out, so the care stays continuous and no session gets delivered against units that are already spent. The clinician never has to guess whether the client still has coverage.
Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow keeps the ledger, fires the alerts, and assembles the packet; a person confirms the utilization is right, the clinical documentation is complete, and the submission goes to the correct payer entity. Every security control that protects the treatment data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving clinical and treatment records through an authorization workflow is only safe when the controls are real.
Who Actually Does This Work
Fair question: why would an outsourced team track your units better than your own staff? Because keeping the ledger, watching the alerts, and building reauth packets is their entire day, not the thing a BCBA squeezes between sessions. The people working your authorizations are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US behavioral health and prior authorization workflows. They know what a unit budget really is, how to read a burn rate against a calendar, and what a payer wants in an ABA reauthorization packet, so a fast-burning caseload gets caught weeks before the units run out instead of at the denial.
We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical clinic is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so a client’s units never quietly run out because the one person who tracks them is on vacation.
And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.
Put the routine and the people together, and a specific list of things simply stops happening.
How We Permanently Fix the Process
A person alone is not the fix, and neither is a bot alone. The fix is a documented utilization-tracking workflow: a live unit ledger per client, standing alerts at 75 percent usage and 30 days to expiration, and a reauthorization packet process that starts when the alert fires, all written down and worked the same way every week. Before we take a single caseload for a new clinic, we chart each client’s authorized units against their scheduled hours so we can see which authorizations will empty ahead of their end dates, and we build the tracking against that reality, not a generic template.
From there the workflow becomes a living playbook rather than a unit count in one BCBA’s head. It records how each payer wants a reauthorization documented, the required progress data, the review-time buffer each plan needs, and the escalation path when a client is burning units fast. It is written down, kept current as payers change their rules, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so no client’s units run out because one person was away that week.
That is the difference between fighting this month’s exhausted-unit denials and fixing the process for good, and it is what a dedicated prior authorization partner actually buys you. A coordinator leaving used to mean the ledger stopped getting updated and units started running out again. Under this model the tracking keeps running, the playbook stays, the backup steps in, and an authorization stops being the thing that quietly empties before anyone checks.
The Whole Thing in Four Sentences
ABA sessions run past the authorized units because the unit burn rate is never reconciled weekly against the authorization: 10 hours a week against 600 units over 6 months empties the units around week 15, but nobody watches utilization until claims deny, and by then retroactive authorization is refused. Watching only the end date, asking a BCBA to track units between sessions, or submitting reauth once denials appear all fail the same way. The fix is a live unit ledger per client, alerts at 75 percent usage and 30 days to expiration, a reauth packet built before the units run out, and a weekly burn-rate reconciliation that keeps units and calendar in sync. An ABA therapy group runs exactly this model with us today, names withheld, no patient data shown.
If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.
Ready to stop burning past your units? Try us risk free: two weeks, your real caseload and authorizations, a dedicated specialist tracking utilization and preparing the reauth packets, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.
One Flat Weekly Rate. 45 Hours of Coverage.
No hourly meters, no setup fees, no long-term contracts. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.
One dedicated remote specialist tracking unit utilization and preparing reauth packets across your caseload, single-site ABA therapy clinic
5+ remote specialists running utilization tracking and reauthorization across a multi-site ABA group and several BCBA caseloads
10+ remote specialists, multi-location ABA network, MSO, or PE-backed platform running authorization utilization tracking across many clinicians
45 hours of coverage for less than others charge for 40.
Standard US full-time year: 40 hrs x 52 weeks = 2,080 hours, the federal basis for computing hourly pay per the U.S. Office of Personnel Management. A Staffingly plan: 45 hrs x 52 weeks = 2,340 hours a year, that is 260 additional hours included in your flat rate. $399/week x 52 = $20,748 a year / 2,340 hours = $8.87 per hour. Typical US market rates for healthcare virtual assistants run $9.50 to $13.00 per hour for 40 hours of coverage.
Keep Every Client Inside Their Units This Month
You have seen the whole method. The pilot proves it on your own caseload, with a utilization tracker your team can watch every day.
Start My 2-Week Free TrialRequest Information
Single specialty or multi-site? One payer or many? Tell us your situation and we will map the right coverage within 24 hours.
Frequently Asked Questions
Where the Claims on This Page Come From
Sources & References
- American Medical Association Prior Authorization Physician Survey. Physician-reported data on prior authorization volume, care delays, and administrative burden across specialties. ama-assn.org
- CMS Claim Adjustment Reason Code (CARC) Reference. Standard payer adjustment and denial codes, including authorization-exceeded and authorization-absent denials relevant to unit utilization. cms.gov
- MGMA Practice Operations and Prior Authorization Resources. Benchmarks and guidance on authorization workload, utilization tracking, and patient access for medical group practices. mgma.com
- HFMA Revenue Cycle and Denials Management Resources. Guidance on authorization-related denials, utilization management, and the revenue impact of exhausted or lapsed authorizations. hfma.org
- AAPC Behavioral Health Coding and Authorization Resources. Coding and billing guidance for behavioral health and ABA services, including authorization and unit management. aapc.com