ABA Reauthorization Checklist for Clinicians

An ABA reauthorization checklist should prove three things with one consistent record: what happened during the current authorization, why the client still needs the proposed services, and how the next treatment period will respond to the data. The packet should connect goal-level progress, barriers, clinical modifications, delivered and requested units, caregiver work, transition criteria, and every payer-required attachment.

Requirements vary by payer, product, state, age, benefit, and authorization cycle. Confirm the member's current plan instructions before using this checklist. The examples below show how several programs ask for similar clinical facts in different forms.

Build one clinical argument across the packet

A concurrent request works best when each section advances the same clinical argument. The prior period supplies evidence, the reassessment explains what that evidence means, and the next-period plan turns the interpretation into measurable care.

Start with the client, rather than the form. Review current functional needs, safety concerns, communication and adaptive skills, treatment response, preferences, assent when applicable, family priorities, co-occurring care, and the environments where skills matter. Then map that clinical record into the payer's fields. The BACB ethics requirements page identifies the current code governing BCBA and BCaBA certificants, and the full Ethics Code for Behavior Analysts provides the professional framework for accurate records, effective treatment, client protection, and responsible communication.

The CASP ABA Practice Guidelines page describes its 2024 third edition as consensus guidance for planning, implementing, and evaluating ABA assessment and treatment for autism. Access to the complete guidelines is licensed. This checklist uses the public summary as a standards reference and relies on current payer documents for program-specific submission rules.

Before drafting prose, write a one-sentence decision for every active goal: continue, revise, fade, generalize, place on hold, or close. Add the evidence and date behind that decision. This step keeps the treatment plan, progress report, graphs, units table, and cover form aligned.

The ABA reauthorization checklist

Use the checklist as a clinical review record. Add each payer's named form, lookback period, submission window, and attachment rules in the practice's payer matrix.

Review areaEvidence to place in the packetControl question before submissionAuthorization identityMember and plan identifiers, requesting and servicing provider information, current authorization number, approved dates, request type, and proposed datesDo the member, provider, plan, and date fields agree in every file and portal field?Goal-level progressOriginal baseline, current level, measurement definition, relevant graph, observation dates, treatment exposure, and status for each goalCan a reviewer trace every continue, revise, or close decision to current data?Limited or uneven progressBarrier, dates, amount of treatment affected, clinical effect, action taken, and response after the actionDoes the packet explain the data pattern without treating a barrier as a substitute for clinical analysis?Treatment modificationsProtocol, teaching, measurement, setting, or caregiver-support changes; rationale; implementation date; and post-change dataIs each modification tied to a clinical observation and reflected in the next plan?Service delivery and utilizationApproved and delivered units by code, weeks available, cancellations, staffing gaps, setting, supervision, and other servicesDoes utilization reconcile with schedules and claims, and does any gap have a specific explanation?Ongoing medical necessityCurrent functional impairment or risk, response to treatment, remaining needs, coordination, and reason for the requested level and settingDoes the narrative explain why the proposed services fit the client's current needs?Next-period goalsCurrent baseline, observable response, mastery criterion, measurement method, generalization plan, target date, and responsible clinicianAre new and continuing goals measurable from the first day of the requested period?Requested intensityCode, modifier when required, units per day or week, frequency, duration, setting, supervision, and total unitsDoes the arithmetic reproduce the total request, and does the clinical rationale support the schedule?Caregiver involvementTraining offered and delivered, skills addressed, caregiver response, barriers, preferences, and next-period planDoes the record show an individualized role that fits the family and the payer's requirement?Transition and dischargeStep-down triggers, generalization criteria, natural and community supports, aftercare, coordination, and estimated review pointCan the team explain what data would support lower intensity, transfer, or discharge?Packet integrityCurrent forms, required assessments, graphs, plans, signatures, credentials, attachment names, and source page referencesCan an authorization specialist find each required item without guessing which version controls?

Progress belongs at the goal level. A program-wide statement such as “the client made progress” hides the decision a reviewer must evaluate. Use the same operational definition and compatible measurement for baseline and current status. If measurement changed, state when, why, and how the clinician interpreted the two series.

An unchanged goal needs a current reason. Continued improvement toward a criterion may support continuation. Minimal exposure after an access disruption may support more observation. A flat or worsening pattern calls for analysis of treatment integrity, motivating variables, task design, measurement, health or setting changes, and other plausible clinical factors. Record the resulting change and the data that will test it.

Separate treatment response from treatment access

Barriers become useful when the packet shows their clinical effect. Name the event, its duration, the portion of planned care affected, and the response. Examples include hospitalization, school or housing changes, clinician turnover, repeated cancellations, caregiver availability, transportation, competing appointments, restricted access to a treatment setting, and missed supervision.

Keep access and response measures distinct. Delivered units show exposure. Goal data show response during the exposure that occurred. Treatment-integrity or fidelity data show whether the intervention was implemented as planned. A request becomes easier to audit when these measures sit beside one another.

For utilization, calculate each code separately:

utilization percentage = delivered units / approved units × 100

Show the numerator, denominator, authorization dates, and data source. Reconcile the result with scheduling and claim records. A lower percentage can reflect a short authorization, delayed staffing, cancellations, illness, payer processing, or a planned reduction. The explanation should state what happened and how the next request accounts for it.

The requested intensity comes from the next-period clinical plan. Show weekly or monthly frequency, expected weeks, unit length, and total units. Then test the total against the form, schedule, treatment plan, staffing model, and requested dates. Keep code descriptions within the practice's licensed coding resources.

A synthetic packet review

This example is fictional and uses rounded figures for training. The payer, code rules, and individual clinical decision in a real request may differ.

A client had 1,560 units of code 97153 approved for a 26-week period. The practice delivered 1,248 units, for 80% utilization. A seven-week technician vacancy reduced direct-treatment availability. During weeks with planned treatment, independent transitions increased from a 20% baseline to 55% across two settings. A dressing goal remained near baseline after limited exposure and inconsistent materials across homes.

The BCBA revised the transition protocol after a three-week stable period, documented the change date, and saw improvement in the next six observations. For dressing, the clinician standardized materials, added caregiver practice at a feasible time, and reset the next review point. The next plan requests 54 units of 97153 per week for 26 weeks, or 1,404 units, with separate code-level calculations for supervision and caregiver guidance.

Packet itemGap found in reviewCorrection before submissionProgress graphTransition graph showed current data but omitted the 20% baseline labelAdd baseline value, dates, setting labels, and the unchanged measurement definitionBarrier narrative“Staffing issues” gave no period or treatment effectState the seven-week vacancy, missed planned units, available services, and restoration dateModification recordProtocol change appeared in a note but had no date in the treatment planAdd the implementation date, clinical rationale, and planned evaluation measureUtilization tableDelivered units were combined across codesCalculate 97153 utilization from 97153 units and reconcile other codes separatelyRequested intensityWeekly schedule and total units produced different totalsUse 54 units × 26 weeks = 1,404 units in the form, plan, and scheduleTransition planPlan named a future reduction without a measurable triggerAdd the sustained performance, generalization, and support criteria that would prompt review

This packet explains why 80% utilization occurred, what the client learned during available treatment, how the clinician responded, and why the new schedule is lower than the prior approval. It also makes the dressing-goal uncertainty visible. The example does not assume that low utilization, progress, or a staffing gap determines coverage by itself.

How current payer examples differ

Payer forms can ask for the same decision in different ways. Treat each example as a scoped implementation, then verify the current member product and submission channel.

Nevada Medicaid and Nevada Check Up

Nevada's FA-11E form was updated July 13, 2026. For continued services, it asks the provider to quantify progress or regression over the previous 90 days, report services and responsiveness during the prior period, explain parent or guardian training and response, address care coordination, and describe discharge criteria and aftercare. It also collects requested codes, dates, units, delivery model, and school or care-plan coordination. Review the current Nevada Medicaid FA-11E form.

The companion instructions say a continued-services request must arrive 5 to 15 days before the last authorized date. They also require current progress for goals carried forward from the prior 180 days and a BCBA signature from the clinician charged with service coordination. Those details belong to the Nevada Medicaid and Nevada Check Up FA-11E workflow. A provider serving a managed-care member should confirm whether the member's plan uses this form or another process. Read the July 2026 FA-11E instructions.

Tennessee multi-MCO ABA request

The Tennessee ABA resource page says Wellpoint worked with BlueCare Tennessee, UnitedHealthcare Community Plan, and community experts on a common ABA request form. Check the current Tennessee ABA resource page before selecting a portal or destination.

The January 2026 form names BlueCare or TennCareSelect, CoverKids, Wellpoint Tennessee, and UnitedHealthcare submission routes. For continuation, it requests code-level weekly and period units, measurable progress, standardized assessments, service breaks, graphs, achieved goals, treatment barriers, caregiver proficiency and training volume, utilization of 97153 units, justification for an increase, and a fading plan. Its form-specific control asks for an explanation when 97153 utilization is under 90%. That threshold belongs to this Tennessee multi-MCO form and should not be applied to another plan. Open the January 2026 Tennessee Request for ABA.

TRICARE Autism Care Demonstration

Under TRICARE's Autism Care Demonstration (ACD), ABA treatment is authorized in six-month periods, the ABA provider requests reauthorization every six months, and specified outcome measures recur on six- or twelve-month schedules. The authorized ABA supervisor updates the treatment plan before the next period. Confirm the current ACD steps and ongoing requirements.

TRICARE's public questions page says the six-month update leads to a continuation request or a transition or discharge plan. Its West Region clinical-necessity page says TriWest reviews goals, requested hours, service location, and outcome-measure results and may request missing information. Read the ACD questions and answers and TriWest's clinical-necessity review description. These requirements belong to the ACD and its contractor process.

Run packet controls before the clinical signature

Complete a two-person review after the clinical content is stable. The BCBA owns the clinical decisions. A trained authorization reviewer checks the payer matrix, form version, dates, units, attachments, and submission route. Resolve discrepancies with the clinician before signature.

Use four final controls:

Source control: Record the payer, product, policy or form name, version or effective date, URL, date checked, and submission window.
Cross-document control: Compare member, provider, diagnosis, dates, goal labels, baseline and current values, code-level units, settings, and requested schedule across every file and portal field.
Attachment control: Use descriptive file names, current signatures, legible graphs, page references, and one approved version of each document.
Receipt control: Save the submission confirmation, track requests for information, assign an owner and due date, and record the final decision and authorization span.

The CMS Prior Authorization API FAQ says an impacted payer's API response must state approval and duration or denial and a specific reason, and it may request more information. Those federal API rules apply to specified impacted payers and do not replace an ABA payer's clinical policy, portal, fax route, or form. A practice still needs a complete packet and a follow-up queue.

Set the internal workflow backward from the payer's actual deadline. Give the clinician time to interpret data, discuss changes with the client or caregivers as appropriate, complete reassessment work, and review requested intensity. Let the authorization team run arithmetic and attachment checks before the permitted submission window opens. Escalate missing signatures, stale assessments, unresolved unit conflicts, and unclear medical-necessity language while correction is still possible.

This checklist supports quality review and general education. It does not determine coverage, replace a payer's current requirements, or substitute for individualized BCBA judgment. External review by an ABA prior-authorization specialist and a BCBA clinical reviewer remains pending.

Check reauthorization packets before submission

Finni AI Prior Auths is designed to help teams find payer-requirement gaps, cross-document conflicts, and missing packet elements while keeping a clinician in control of the final request. See how Finni AI Prior Auths checks reauthorization packets before submission.

Related resources

Browse the parent guide, Prior Authorization and Medical Necessity, for the full clinical authorization library.

Sources

Sources were checked August 13, 2026. Confirm payer and program instructions again before submission.

ABA Concurrent Authorization Checklist: Progress, Barriers and the Next Treatment Period