Why Your ABA Authorization Renewal Workflow Needs Its Own Countdown

Start an ABA authorization renewal from your own recorded payer turnaround plus a buffer, not a universal number. Use a countdown with four markers (start, documentation complete, submit, escalate), a named owner for each, and a lapse plan. The federal CMS timeframes apply only to named payer types.

Short answer: start from your payer's recorded turnaround

An ABA authorization renewal workflow should start the renewal far enough ahead that a normal payer turnaround, plus a buffer, still ends before the current authorization does. The right lead time is not a universal number. It is your own recorded turnaround for each payer, plus a buffer for missing paperwork. Until you have that data, the countdown below is a sensible default to adjust.

The point of a workflow is ownership. Every step needs a named person and a date, so a renewal never depends on someone remembering. This post goes deep on renewals: what the federal rule does and does not change, a countdown template with owners, a worked example with numbers, a decision table, a lapse playbook and the mistakes to avoid. For the whole lifecycle, see ABA prior authorization tracking.

What the evidence says, and what it means for you

Three published sources frame this topic. Each one comes with what it means for an operator, because none of them tells you your own payer's turnaround.

The CMS rule sets decision timeframes for named payer types. In January 2024, CMS finalized a rule on interoperability and prior authorization. Per the CMS press release, impacted payers must decide expedited requests within 72 hours and standard requests within seven calendar days, with the timeframes beginning primarily in 2026. They must also give a specific reason when they deny a request. CMS moved the API compliance dates from generally January 1, 2026, to January 1, 2027. What it means: ask each payer whether the rule applies to your plan, and use the answer to ask better questions. Do not use the rule to set your lead time.

Three limits matter to a clinic:

  • Who is covered. The impacted payers are Medicare Advantage organizations, Medicaid and CHIP fee-for-service programs, Medicaid managed care plans and CHIP managed care entities, plus qualified health plan issuers on the federal exchanges. CMS says the 72-hour and seven-day timeframes do not apply to those exchange issuers.
  • Who is not listed. The page does not describe employer-sponsored commercial plans as covered. Do not assume it applies to them.
  • What it does not tell you. It does not tell you your payer's actual practice, your state's rules, or the clinical criteria a payer uses.

Medicaid details vary by state. Medicaid.gov describes EPSDT as Medicaid's comprehensive and preventive benefit for enrollees under 21, and says states determine medical necessity case by case. What it means: for a Medicaid-enrolled child, treat the state's process as its own process, and record it per payer rather than copying another state's workflow.

Demand makes delay costly. The CDC's ADDM Network estimated that about 1 in 31 eight-year-olds was identified with autism spectrum disorder in its 2022 sample from 16 US communities. This is context for demand, not a measure of any one clinic. What it means: when a lapse interrupts a family's schedule, the clinic carries both the disruption and the pressure to restart quickly. Prevention is cheaper than recovery.

Use the rule to ask each payer, "What is your current turnaround for a continued-stay request, and how do we see the status?" Record the answer and the date.

The Renewal Runway

The Runway is a countdown with four markers. The day counts below are our suggested defaults, labeled as such. Replace them with your payer's recorded turnaround plus a buffer.

Marker Suggested default What happens Owner
Start 60 days before end date Pull the case, confirm the payer's current requirements and submission method Billing / authorization lead
Documentation complete 45 days before Clinical documents requested, received and checked for completeness Clinical coordinator
Submit 30 days before Request submitted; confirmation number and date logged Billing / authorization lead
Escalate 14 days before, if no decision Call the payer, tell the scheduler, alert the owner Operations director

Keep the Runway on one board that shows every case by its next marker. Sort by date, review it every week in the same meeting, and treat a missed marker as the signal to escalate, not as a reason to wait.

Who owns each markerSuggested defaultsStart: confirm requirementsAuthorization leadDocumentation completeClinical coordinatorSubmit and log confirmationAuthorization leadEscalate if no decisionOperations directorDay counts are defaults. Use your own payer data.
Each of the four markers has one named owner, so no renewal depends on someone remembering.

A worked example with numbers

Example (illustrative; not a real clinic or payer). A group has 150 active clients. Authorizations run six months, so about 25 renewals come due each month. The authorization lead has logged turnaround for a quarter and finds the slowest recorded decision per payer:

  • Payer A: 10 calendar days (10 renewals a month)
  • Payer B: 21 calendar days (10 renewals a month)
  • Payer C: 30 calendar days (5 renewals a month)

The group's formula, our suggestion: Submit marker = slowest recorded turnaround + a 14-day buffer before the end date. Documentation-complete is 10 days before Submit. Start is 15 days before that.

Payer Slowest turnaround Submit (days before end) Documentation complete Start
A 10 days 24 34 49
B 21 days 35 45 60
C 30 days 44 54 69

The takeaway is that a single default does not fit. The 60-45-30 defaults happen to suit payer B, start payer A earlier than needed, and fail payer C: submitting 30 days before the end date leaves only 30 days for a payer whose slowest case took 30, with no buffer. Under a single default, the 5 payer C renewals a month, 20 percent of all renewals, are at risk of a gap.

Here is one case worked through. A payer B authorization ends on December 31. Submit is 35 days before: November 26. Documentation complete is 10 days earlier: November 16. Start is 15 days before that: November 1. If no decision has arrived by December 17, 14 days before the end, the operations director escalates.

Now the lapse side. Suppose that despite this, 6 clients' authorizations lapse for two weeks, and each would have had 2 sessions a week: 6 × 2 × 2 = 24 sessions in the gap. At an average of 3 hours that is 72 hours of scheduled care to rebook or hold, and 6 families to call. Every number is invented to show the method; do not read it as typical for any payer.

One default for allSame 60-45-30 for every payerSlow payers get no bufferFast payers start too earlyPer payer countdownSlowest recorded turnaroundPlus a buffer for paperworkMarkers reviewed each month
One default countdown fits a single payer, while a countdown built on recorded turnaround fits each payer.

Decision table: where is the case, and what do we do?

Situation Action Owner Timing What the family is told
Documents not complete at the documentation marker Chase the BCBA with a due date; flag in the weekly review Clinical coordinator Same day Nothing yet; no change
Submitted, no decision at the escalate marker Call the payer; confirm receipt and status; alert the scheduler Authorization lead, then operations director Within 1 business day That the request is pending and who is following up
Payer asks for more information Route the request to the right owner with a due date Authorization lead Same day That one more item is being gathered
Denied Record the stated reason; route to the clinical and billing leads Operations director Within 1 business day What is pending next, without promising an outcome
End date reached, no decision Confirm with the payer whether services may continue; follow the lapse plan Operations director Same day Honest status and next contact date

The handoff checklist between clinical and billing

Most late renewals are handoff failures, not payer failures. Use this checklist, which covers logistics only and leaves clinical content to the clinical team.

  1. Clinical coordinator confirms the assigned BCBA has finished the documents the payer asks for.
  2. The authorization lead checks them against the payer's list. Missing items go back to the owner with a date.
  3. Billing logs the submission date, method and confirmation.
  4. The scheduler is told the end date, the status and the plan if it lapses.
  5. The case stays on the Runway board until a decision is recorded.

See how this connects to the front of the funnel in an intake handoff.

The playbook: who does what, and when

  1. Authorization lead, weekly: refresh the Runway board and list every case reaching a marker in the next two weeks.
  2. Authorization lead, at Start: confirm the payer's current requirements and submission method, and open the case.
  3. Clinical coordinator, Start to Documentation complete: collect documents from the BCBA; confirm complete by the marker.
  4. Authorization lead, at Submit: submit, then log date, method and confirmation within the same day.
  5. Scheduler, from Submit onward: see remaining authorized hours and the end date on the schedule; book accordingly.
  6. Operations director, at Escalate: call the payer, inform the owner and decide on the lapse plan.
  7. Authorization lead, within 2 business days of a decision: record the decision date and update the turnaround log.
  8. Operations director, monthly: review the turnaround log and adjust the markers per payer.

Who owns what

Name roles, not just tasks, so a vacation or a resignation does not break the process.

Role Owns Backup
Authorization lead The Runway board, submissions, payer contact Billing lead
Clinical coordinator Collecting documents from BCBAs on time Clinical director
Scheduler Booking against remaining authorized hours; flagging cases near the end date Operations director
Operations director Escalations, weekly review, payer turnaround data Owner

If an authorization lapses

Sometimes a renewal slips or a decision arrives late. Have the lapse plan ready before it happens.

  • Stop and check. Confirm with the payer what the status is and whether services may continue. Do not assume. What applies depends on the payer, so do not guess.
  • Tell the scheduler. Remaining authorized hours should be visible when sessions are booked; see backfill when hours are limited.
  • Tell the family honestly. Say what is pending and who is following up. Do not promise outcomes or dates you do not control.
  • Record the cause. Missed deadline, missing document, late payer decision. This feeds the next review.
Lapse plan: first dayMaya K.Same dayConfirm status with the payerSame dayTell the scheduler the end dateSame dayCall the family with honest statusAfterRecord the cause for review
A lapse plan lists the first four moves in order, before anyone needs it.

Common mistakes and how to fix them

  1. Starting at the end date minus the payer's average. Averages hide the slow cases. Plan against your slowest recorded turnaround.
  2. Waiting for a perfect packet. Teams hope one more document will arrive. Set a documentation-complete marker and escalate if it is missed, rather than letting a case drift.
  3. Keeping the end date in billing only. Schedulers and clinical coordinators need to see it too, so the schedule never runs past the authorization unnoticed.
  4. No record of the submission. Without a date and confirmation number, you cannot show what happened if a payer disputes it.
  5. Treating the federal timeframes as your payer's promise. They apply to named payer types; check what applies to each of your payers.

Track turnaround, and what good looks like

Each submission gives you a data point: submitted date, decision date, payer. After a quarter you have a real turnaround range per payer and can tighten or lengthen the Runway. Put the share of renewals submitted on time into your ABA practice KPIs.

We have no independent benchmark for renewal performance, so set your own targets. As our recommendation, not a standard, good looks like this:

  • Every active authorization has an owner and a next marker on the board.
  • Nearly every renewal is submitted by its Submit marker, and every miss has a recorded cause.
  • No authorization reaches its end date with nobody having escalated 14 days earlier.
  • Turnaround is logged per payer and the markers are reviewed monthly.

This article is for informational purposes and is not legal, billing or clinical advice.

Questions

How far ahead should an ABA clinic start a reauthorization request?
Start far enough ahead that your recorded turnaround for that payer, plus a buffer, still ends before the authorization does. The 60-45-30-14 day markers in this post are suggested defaults; replace them with your own data.
Who should own authorization tracking in an ABA clinic?
One named authorization lead owns the board and submissions, with a backup. Clinical coordinators own getting documents on time, and schedulers own booking against remaining hours.
What happens operationally when an ABA authorization expires mid-treatment?
Confirm the status and what applies with the payer rather than assuming, tell the scheduler, and tell the family honestly what is pending. Then record the cause so the next renewal does not repeat it.
Does the CMS prior authorization rule apply to my payer?
It applies to Medicare Advantage, Medicaid and CHIP fee-for-service, and Medicaid and CHIP managed care. CMS says the 72-hour and seven-day timeframes do not apply to exchange issuers, and the page does not describe employer plans as covered. Ask each payer.

Sources

  1. CMS: Interoperability and Prior Authorization final rule press release
  2. Medicaid.gov: Early and Periodic Screening, Diagnostic and Treatment (EPSDT)
  3. CDC: Autism Data Visualization Tool (ADDM, 1 in 31 eight-year-olds, 2022)

New posts, by email.

One short note when we publish. Unsubscribe any time.

Your email app should open with a note to us. Send it and we’ll add you.