ABA Prior Authorization Tracking: A Complete Operations Guide
ABA prior authorization tracking means knowing, for every client, what was approved, how much has been used and when it ends. Give each of six lifecycle stages one owner, show remaining hours wherever sessions are booked, run a 60/30/14-day renewal countdown, and catch denial causes before submission with a second-person check.
What ABA prior authorization tracking means
ABA prior authorization tracking is the work of knowing, for every client, what the payer approved, how much of it has been used, and when it ends, so sessions never run past approved hours and renewals never lapse. It sounds like a billing task. In practice it touches four teams: intake collects the plan's rules, the BCBA writes the clinical request, billing submits and follows up, and scheduling books against the approved hours.
Most authorization problems happen at the handoffs between those teams, not inside any one of them. A renewal date that lives only in a payer portal. Approved units that never reach the scheduler. A reassessment booked a week too late to support a renewal. Each is a small gap. Together they lead to unbillable sessions, interrupted services and frustrated families.
This guide gives you a way to close those gaps. It covers:
- The Authorization Lifecycle Map: six stages, each with one owner and a clear handoff
- How to show remaining hours at the moment of booking
- The Renewal Countdown: a 60/30/14-day rhythm so renewals never lapse
- How to prevent denials before submission
- What is changing in 2026 and 2027, including federal prior authorization rules and new billing codes
- How to keep families informed while a decision is pending
- The weekly authorization review
It is written for owners, billing and revenue cycle leads, and intake coordinators at US ABA centers. It covers operations, not payer-specific rules: every payer's requirements differ, so check each one directly.
The Authorization Lifecycle Map
The Authorization Lifecycle Map breaks one authorization into six stages. Each stage has one owner, a clear output, and a handoff to the next stage. The owner is not the only person who works on the stage; it is the person who notices when it stalls.
| Stage | Owner | Output | Hands off to |
|---|---|---|---|
| 1. Requirements | Intake | The plan's authorization rules for ABA, written in the file | BCBA and billing |
| 2. Request package | BCBA, with intake | Assessment, treatment plan and supporting documents, complete and checked | Billing |
| 3. Submission and follow-up | Billing or authorization coordinator | Request submitted, reference number logged, follow-ups on a fixed rhythm | Billing |
| 4. Decision and setup | Billing | Approved codes, units, date range and conditions entered where scheduling can see them | Scheduling and the BCBA |
| 5. Utilization | Scheduling, with billing | Hours used vs. approved, reviewed weekly | BCBA and billing |
| 6. Renewal | BCBA and billing | Reassessment done and renewal submitted before the end date | Back to stage 3 |
Stage 1: Requirements
At intake, record how the family's plan handles ABA: whether prior authorization is needed, what it requires (for example a diagnostic report, a referral or a letter of medical necessity), how long approvals usually last, and how the payer wants requests submitted. Write it in the client file, not in someone's memory. Our guide to the ABA intake process from referral to first session covers how to collect these documents early.
Stage 2: Request package
The BCBA writes the assessment and treatment plan. Before anything goes to the payer, someone other than the author checks the package against the plan's requirements: every required document present, dates current, signatures in place, requested hours matching the treatment plan. A second check catches most of the gaps that lead to requests being sent back.
Stage 3: Submission and follow-up
Submit, log the date and reference number, and set the first follow-up date before you move on. Follow up on a fixed rhythm, not when someone remembers. Record every contact with the payer: date, person or channel, and what was said.
A simple rhythm works for most centers: check status a few business days after submission, then on a fixed interval until a decision arrives, with a named escalation step if the wait runs well past the payer's usual timeframe. When a payer asks for more information, treat it as a new deadline, not a pause: tell the BCBA the same day and agree who will send what by when.
Stage 4: Decision and setup
When the decision arrives, enter the details where scheduling will see them at the moment of booking: approved codes, units for each code, start and end dates, and any conditions. If the approval differs from the request, tell the BCBA the same day. A partial approval changes the treatment plan, not just the schedule.
Stage 5: Utilization
Track hours used against hours approved every week. Under-use and over-use are both problems. Over-use creates sessions you cannot bill. Under-use means care the family was approved for is not being delivered, and it can make the next renewal harder to support.
Stage 6: Renewal
Renewal starts long before the end date. It needs a reassessment, an updated treatment plan and a new submission, and each of those takes time. The Renewal Countdown below sets the rhythm.
Who owns each stageLifecycle mapIntakePlan's rules written in the fileBCBARequest package complete and checkedBillingSubmitted, decision enteredSchedulingHours used vs. approved, weeklyBCBARenewal with billing, before endShow remaining hours at the moment of booking
The single most useful change most centers can make is to show remaining authorized hours wherever sessions are booked. A scheduler who can see "12 hours left, authorization ends March 14" makes different decisions from one who cannot.
Translate units into hours
Authorizations are usually written as units for specific billing codes over a date range. Schedulers think in hours and weeks. Translate once, at setup, using the payer's unit definitions: approved units for each code, what that means in hours, and what that means per week for the rest of the period.
A simple weekly pace check
For each authorization, compare two numbers every week:
- Expected use to date: approved hours × share of the period that has passed
- Actual use to date: hours delivered so far
If actual use is well below expected, look for cancellations, staffing gaps or a schedule that no longer fits the family. If it is above, slow down or talk to the BCBA about whether the plan needs updating. Both conversations are easier in week six than in the last week of the period.
An illustrative example
The numbers below are made up to show the method.
| Item | Value |
|---|---|
| Approved | 520 hours over 26 weeks (20 hours a week) |
| Weeks passed | 13 (half the period) |
| Expected use to date | 260 hours |
| Actual use to date | 214 hours |
| Gap | 46 hours behind pace |
At 13 weeks, the client is about two and a half weeks behind. The scheduling team checks the cancellation log, finds a recurring Tuesday conflict, and moves the standing block. The gap is visible in time to act, and the BCBA has the utilization data ready for the renewal discussion. Our guide to ABA scheduling best practices covers fixing cancellation patterns like this one.
The Renewal Countdown
Lapsed authorizations interrupt care and create sessions you cannot bill. The Renewal Countdown is a fixed rhythm that starts well before the end date:
| Days before end date | What happens | Owner |
|---|---|---|
| 60 | Flag the renewal; book the reassessment; confirm the plan's renewal requirements haven't changed | Billing flags, BCBA books |
| 30 | Reassessment and updated treatment plan complete; package checked; submit | BCBA, then billing |
| 14 | No decision yet: escalate with the payer; tell the family what is happening | Billing |
| 0 | Still no decision: follow your written policy on continuing services, agreed in advance | Owner or operations lead |
Adapt the numbers to your payers. Some take longer, and some limit how early you can submit. One practice management vendor suggests starting renewals 30–45 days before expiry; the 60-day flag gives the reassessment time to happen before that. The point is that every renewal follows the same countdown, so none depends on someone noticing.
Renewal countdownSofia L.60 days outFlag it and book the reassessment30 days outUpdated plan checked and submitted14 days outNo decision yet: escalateEnd dateFollow the written policyPreventing denials before submission
Most requests that are denied or sent back for more information share a few causes: missing or outdated documents, a treatment plan that does not support the hours requested, mismatches between the request and the plan's rules, and calculation errors in units. All of them can be caught before submission.
A pre-submission checklist
- [ ] Every document the plan requires is attached and current
- [ ] Diagnostic report meets the plan's requirements
- [ ] Treatment plan goals and requested hours support each other
- [ ] Requested codes and units match the treatment plan and are calculated correctly
- [ ] Client and provider details match the payer's records exactly
- [ ] Signatures and dates are present
- [ ] A second person has reviewed the package
Feed every denial back upstream
When a request is denied or returned, record the reason in a short coded form: missing document, insufficient clinical detail, unit error, eligibility, other. Review the codes monthly. If the same reason appears twice, fix the step that produced it, whether that is the intake checklist, the treatment plan template or the review step.
Before the request goes outPre-submissionRequired documents attachedAll currentHours match the treatment planCheckedCodes and units calculatedRecountedSecond-person reviewWaitingLog every denial reason and fix the step that caused it.What is changing in 2026 and 2027
Two changes are worth tracking. Neither replaces the basics above, but both affect how you plan.
Federal prior authorization rules for some payers
Under the CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F), impacted payers, including Medicare Advantage organizations and state Medicaid and CHIP programs, must:
- Send prior authorization decisions within 72 hours for urgent requests and 7 calendar days for standard requests, starting January 1, 2026
- Give a specific reason for denied requests
- Publicly report prior authorization metrics each year, with the first report due by March 31, 2026
- Implement a Prior Authorization API, starting January 1, 2027
The rule does not cover every plan. Most employer-sponsored commercial plans are outside it, and the decision timeframes do not apply to qualified health plans on the federal exchanges. Map which of your clients' plans are covered. For those payers, a decision that takes longer than the rule allows is worth escalating, and the specific denial reasons can feed your denial log directly.
New adaptive behavior billing codes for 2027
The AMA released the 2027 CPT code set in September 2026. It includes six new codes in the adaptive behavior services code set, which apply from January 2027. The ABA Coding Coalition, which led the application for the changes, has published guidance and held webinars for providers, billers and payers. Each payer will decide how it handles existing authorizations and new requests under the new codes, and Medicare's final 2027 payment rule is expected in November.
For authorization tracking, the practical step is preparation: list every authorization that runs past December 31, 2026, watch for payer communications about how those authorizations will be handled, and be ready to update codes and units in your tracking once payers confirm their approach.
How intake, clinical, billing and scheduling hand off an authorization
Every stage in the lifecycle ends with a handoff, and most lapses start there. A handoff is complete only when the receiving team has what it needs to act without asking a question. Write each handoff down as a short list and check it every time.
| Handoff | From | To | Must include |
|---|---|---|---|
| Plan requirements | Intake | BCBA and billing | Whether authorization is needed, required documents, typical approval length, submission method |
| Request package | BCBA | Billing | Assessment, treatment plan, requested codes and hours, supporting documents, second-person check done |
| Submission status | Billing | Intake (for the family) | Date submitted, reference number, expected decision window |
| Decision | Billing | Scheduling and BCBA | Approved codes and units, hours per week, start and end dates, conditions, any difference from the request |
| Pace alerts | Scheduling | BCBA and billing | Clients more than two weeks behind or ahead of pace, with the likely reason |
| Renewal trigger | Billing | BCBA | End date, renewal requirements, reassessment due date |
Make one person responsible for the whole client
Stage owners handle their stage. Someone should also own the client's authorization end to end, usually an authorization coordinator or a billing lead. That person does not do every step. They make sure no step is waiting on someone who does not know it is their turn.
Keep one source of truth
Approvals often live in several places: the payer portal, an email, the billing system, a scheduler's spreadsheet. Pick one place where the current approval lives, and make every other copy point to it. When an approval changes, update that one place first.
Running authorization tracking across locations
Multi-site centers face the same stages with more people involved. Two practices help:
- One process, one set of definitions. Every site uses the same lifecycle stages, the same countdown and the same denial codes, so you can compare sites and spot the one that needs help.
- Central visibility, local action. An operations or billing lead reviews all authorizations ending in the next 60 days across sites each week. Local teams still book reassessments and adjust schedules.
If one site consistently has more returned requests or late renewals, look at its handoffs first. The cause is usually a missing step, not a missing person.
Keeping families informed while a decision is pending
Waiting on an authorization is stressful for families, especially for a first authorization. Silence makes it worse.
- Tell them what was submitted and when, and roughly how long a decision usually takes for their plan.
- Update them at every change: submitted, more information requested, decision received.
- Never promise an approval or a start date that depends on one.
- For renewals, tell families early if a decision is delayed and what your policy is for continuing services.
Keep updates short and free of clinical detail, and use the contact method each family chose.
The weekly authorization review
Hold a 15-minute weekly review with billing, scheduling and a clinical lead. Look at the same list each week:
| List | What to do |
|---|---|
| Requests pending more than your follow-up interval | Follow up today; log the contact |
| Decisions received this week | Confirm setup is complete and scheduling can see it |
| Authorizations ending in the next 60 days | Check each one's countdown stage |
| Clients behind or ahead of pace | Agree an action with scheduling or the BCBA |
| Denials and returns this week | Code the reason; spot repeats |
Add two numbers to the owner's weekly scorecard: authorizations at risk of lapsing in the next 30 days, and hours delivered as a share of hours approved. See the weekly scorecard for clinic owners for the rest.
What software can and cannot do
Practice management and authorization tools can store approvals, show remaining units at booking, run countdown alerts and track pace. They cannot write a strong treatment plan, judge medical necessity, or decide what to do when a payer is late. Set up the lifecycle stages, owners and countdown first. Then choose a tool that shows each of them clearly.
When you evaluate a tool, load a few of your real authorizations and ask to see four things: remaining hours on the booking screen, the pace check for a client who is behind, the alerts for an authorization 60 days from its end date, and how a denial reason is recorded and reported. Ask how the tool will handle authorizations that span the 2027 code changes once payers publish their guidance. If the answers depend on someone remembering to check a separate report, the tool will not close the gaps this guide describes.
Where to start on Monday
- List every active authorization with its end date and hours approved.
- Flag every one ending in the next 60 days and put it on the Renewal Countdown.
- Add remaining hours to the booking screen, or to a shared list schedulers check before booking.
- Run the pace check for every client and act on the biggest gaps.
- Start a denial log with coded reasons.
- List authorizations that run into 2027 so you are ready for payer guidance on the new codes.
This article is for informational purposes and is not legal, billing or clinical advice.
