An ABA prior authorization checklist for an initial treatment request should verify the member's active benefit and plan rules, then assemble a consistent administrative and clinical record. That record usually includes referral or diagnosis evidence, provider and member identifiers, an assessment, individualized plan, measurable goals and baselines, service-intensity rationale, caregiver and coordination plans, signatures, required attachments, submission proof, and a dated follow-up owner.
The exact packet varies by payer, product, state, age, benefit, network, provider contract, and submission channel. Use the checklist below as a quality-control framework, then replace each general item with the current member-specific requirement.
Build a dated requirement record before assembling the packet
Begin with the member's insurance card, current eligibility response, benefit details, referral status, and the payer's controlling clinical and submission instructions. Record the exact payer legal name, plan or product, network, member ID, group number when applicable, coverage dates, servicing location, and whether the request is for an assessment or treatment. A portal screenshot, call reference, or electronic response should carry a checked date and named owner.
Benefit verification and prior authorization answer different questions. The first records the plan information available at a point in time. The second asks the payer to review a proposed service under its current rules. Keep both records in the file because eligibility, network status, benefits, authorization, and payment each have their own conditions.
For every requirement source, record its URL, version or effective date, member scope, request type, submission route, required contents, timing, and accountable owner. This creates a compact evidence trail when a form, manual, portal instruction, or phone reference changes.
The BACB ethics requirements page identifies the current code governing BCBA and BCaBA certificants. The full Ethics Code for Behavior Analysts provides the professional framework for records and responsible communication. The CASP ABA Practice Guidelines page describes its 2024 third edition as guidance for ABA assessment and treatment for autism; the full guideline requires licensed access. Payer documents control member-specific packet fields and routes.
The initial ABA prior authorization checklist
Give each line a status of complete, missing, inconsistent, expired, or inapplicable. “Complete” means the item is current, legible, internally consistent, attributable to its author, and supported by the controlling requirement.
| Packet area | Verify before submission | Evidence or control to retain |
|---|---|---|
| Benefit and plan | Active dates, plan or product, network, ABA benefit, assessment and treatment authorization rules, place-of-service limits, referral rules, and submission channel | Dated eligibility response, benefit reference, source link, representative or portal reference, and verifier |
| Referral and diagnosis | Required referral or order, qualifying diagnosis, diagnosing professional, diagnostic date, accepted evaluation or instrument, and any payer-specific certification | Signed referral, diagnostic report, certification form, and requirement citation |
| Member identifiers | Legal name, date of birth, member ID, address or responsible-party information when requested, and plan identifiers | Match the card, eligibility response, form, treatment plan, and portal entry character for character |
| Provider identifiers | Requesting, servicing, supervising, group, and facility names; credentials; National Provider Identifier; tax or payer ID when required; network status; phone; fax; and address | Current roster or credentialing record plus a cross-document comparison |
| Assessment | Assessment dates, methods, interviews, direct observation, functional and adaptive information, relevant history, strengths, preferences, risks, and clinical interpretation | Signed assessment with named instruments, data dates, informants, settings, limitations, and author credentials |
| Individualized treatment plan | Client priorities, target areas, procedures, measurement, generalization, settings, supervision, review schedule, coordination, and transition planning | One controlled plan version whose dates and labels match every form and attachment |
| Goals and baselines | Observable response, operational definition, baseline value and dates, measurement method, mastery criterion, generalization criterion, and expected review point for every goal | Goal table and graphs or source data that use the same labels and units of measurement |
| Service-intensity rationale | Functional need, assessment findings, risks, client context, proposed frequency and duration, setting, staffing model, supervision, other services, and reason the requested level fits the plan | Code-level unit calculation tied to the treatment schedule and clinical narrative, without copying licensed code descriptors |
| Caregiver plan | Caregiver priorities, baseline skills when measured, feasible participation, teaching targets, measurement, barriers, accommodations, frequency, and alternatives when a caregiver is unavailable | Individualized goals and schedule with family input documented according to the applicable requirement |
| Safety and coordination | Current safety concerns, crisis or risk procedures within scope, medical or behavioral health conditions, medication information when required, school or other therapies, consent, and nonduplication review | Coordination notes, relevant plans, releases, contacts, and documented attempts when another party cannot be reached |
| Outcome measures | Payer-named measures, administration date, respondent, score report, due date, qualified administrator, and interpretation in the treatment plan | Complete reports and a measure tracker; verify proprietary-use and qualification rules |
| Signatures and attestations | Required clinician, diagnosing professional, parent or guardian, and provider signatures; credentials; dates; and accepted electronic-signature method | Final signed versions with dates that fit the requested service period |
| Attachments and file control | Every required form, assessment, plan, graph, report, referral, schedule, credential, coordination record, and supplemental page | Numbered inventory with descriptive file names, version date, page count, and final-review initials |
| Submission proof | Exact submitted files, portal or fax destination, timestamp, confirmation number, transmission status, and request type | Receipt, fax confirmation, portal export, or API response stored with the packet inventory |
| Follow-up | Payer response target, request-for-information owner, due dates, contact route, decision status, authorized span, and escalation path | Work queue entry with next action, owner, deadline, and complete communication history |
The clinical pieces should read as one argument. Assessment findings identify functional needs, baselines quantify the starting point, and goals state what will change. The intensity rationale connects the proposed frequency, duration, setting, and staffing to assessed needs, safety, other services, caregiver context, and review points.
Run unit arithmetic outside the narrative, then compare it with every form and portal field. Document units per occurrence, frequency, expected service weeks, requested dates, and totals for each line. A clinician reviews the schedule's clinical fit; an authorization reviewer checks calculation and transcription.
Caregiver work needs a clinical purpose: skill, current level when assessed, teaching plan, feasible cadence, measurement, and relationship to client outcomes. Safety and coordination records should name the concern, responsible party, consent status, action, and unresolved follow-up.
Synthetic packet inventory and gap review
This fictional example contains no patient information and does not represent a real payer rule or coverage outcome. “Northstar Community HMO” is an invented plan used to show the review process.
The practice's dated matrix says Northstar requires an ordering referral, diagnostic report, signed assessment, individualized plan, goal table, code-level request, caregiver plan, coordination summary, one named outcome measure, clinician signature, and portal submission. The team wants treatment to begin October 5.
| Inventory item | Review finding | Required correction |
|---|---|---|
| Eligibility and benefit record | Portal response is current, but the saved record omits product name and place of service | Save the full response and record the HMO product, network, benefit, setting, checked date, and verifier |
| Referral and diagnosis | Diagnostic report is present; ordering referral names a previous group | Obtain a corrected referral or payer-confirmed remedy before submission and preserve the communication |
| Assessment | Signed assessment uses observations through August 18 | Confirm its currency under the invented plan matrix and cite August 18 as the assessment data cutoff throughout |
| Treatment plan | Plan names the correct client and provider, yet one section references an older assessment date | Correct the date, regenerate the controlled PDF, and retire the superseded copy |
| Goal table | Eight goals are listed; two lack numeric or narrative baselines with dates | Add observable baselines and dates from the assessment record, or revise the goal when evidence is unavailable |
| Intensity request | Clinical schedule shows 18 hours weekly; form arithmetic produces 19.5 | Have the BCBA confirm the intended schedule, recalculate each service line, and update all documents |
| Caregiver plan | Frequency is listed; teaching target and measurement are absent | Add an individualized skill, feasible cadence, measurement method, and review point |
| Safety and coordination | Risk plan is current; occupational therapy coordination attempt has no outcome or next step | Add the contact result, consent status, unresolved question, owner, and follow-up date |
| Outcome measure | Report and score are complete, with the required respondent and date | Mark complete and verify the same date and score appear wherever referenced |
| Signatures and attachments | Assessment is signed; final treatment plan signature is pending; inventory lists an obsolete graph | Obtain the required signature, replace the graph entry, and rerun the page-count check |
| Submission and follow-up | No transmission has occurred | Hold submission until gaps close, then save the portal receipt and create the response task |
The packet remains on hold because the referral, two baselines, requested intensity, treatment-plan signature, and attachment inventory conflict with the stated requirements. A clean review ends with a disposition: ready to submit, ready after named corrections, or escalated for payer or clinical clarification. The reviewer should never silently repair a clinical decision.
How current payer examples change the initial packet
These examples illustrate program variation. Check the member's current product and contractor before applying any item.
Nevada Medicaid and Nevada Check Up
Nevada's official provider forms library lists FA-11E, its instructions, and FA-11F as the ABA authorization materials. The FA-11E form dated June 10, 2025 collects requesting and servicing provider data, recipient data, co-occurring diagnoses and history, responsible-party information, behavioral targets, baselines, goals, treatment-plan and coordination information, discharge planning, requested services, and signatures. Review the current FA-11E.
The instructions dated November 26, 2025 say initial requests require FA-11E and FA-11F together. They also direct providers to complete the requesting, servicing, and recipient sections in full; align target dates with the portal; provide baseline, short-term, intermediate, and long-term goal information; and obtain the specified BCBA signature. The caregiver section has request-type instructions, and certain school or care-plan answers trigger attached copies. Read the current FA-11E instructions.
FA-11F is an initial-request diagnosis certification completed by one of the practitioner types named on the form. It records the diagnosis basis, diagnostic tool or criteria, and practitioner attestation. This form belongs to Nevada Medicaid and Nevada Check Up; another Nevada product may use a different process. Open the current FA-11F.
Tennessee January 2026 multi-MCO request
The current Wellpoint Tennessee forms library links a Request for Applied Behavior Analysis. The January 2026 form separates assessment, initial, and continuation request types. It provides distinct fax or portal routes for BlueCare or TennCareSelect, CoverKids, Wellpoint Tennessee, and UnitedHealthcare, and it collects member, provider, requested-date, code, modifier, weekly-unit, authorization-period-unit, and telehealth fields. Check the January 2026 Tennessee multi-MCO form.
Use that common form only for the programs it names. Verify the member's managed care organization, current route, required supporting pages, and clinical criteria before sending the packet. A shared cover form does not make each product's benefit, network, or review decision identical.
TRICARE Autism Care Demonstration
TRICARE's Autism Care Demonstration (ACD) has an enrollment and authorization sequence. In the West Region, the current enrollment page says a definitive autism diagnosis includes results of a validated assessment tool, completion of the DSM-5 checklist, and an ABA referral. Review the West Region ACD enrollment steps.
After enrollment, TRICARE West authorizes an initial ABA assessment. The provider completes the assessment, develops the treatment plan, and submits the plan and outcome measures for the treatment request. Treatment begins after written approval. Review the West Region steps to obtain ABA services, updated March 19, 2026.
TRICARE East's public workflow says the first assessment includes background information, a functional behavior assessment, caregiver interview, treatment-plan development, outcome measures, and caregiver agreement on the plan. Read the TRICARE East ABA process, updated July 28, 2025. These details are scoped to the ACD and the named regional processes. Providers should confirm current regional instructions and authorization notices.
Preserve the submission record and run the follow-up queue
Before transmission, conduct a clinical review and a packet-control review. The BCBA confirms assessment interpretation, goals, procedures, requested intensity, caregiver plan, safety, coordination, and transition logic. The authorization specialist verifies the payer source, form version, identifiers, arithmetic, signatures, attachments, and channel. Resolve each discrepancy with the accountable person and log the correction.
At submission, save the exact file inventory, destination, timestamp, confirmation identifier, and receipt status. Retain the fax result and page count, portal confirmation, or permitted application programming interface (API) identifiers. Apply the practice's privacy, security, retention, and access controls.
Create the follow-up task while the receipt is open. Include the response target, next check, owner, contact route, and escalation threshold. Log any information request, due date, files sent, confirmation, and resolution. When a decision arrives, record its status, authorized services and dates when applicable, reason, next route, and people notified.
The CMS Prior Authorization API FAQ explains that specified impacted payers' API responses may approve, deny with a specific reason, or request more information. The federal API framework has defined payer and implementation scope. It does not replace a member's current ABA policy, benefit terms, form, portal, fax path, or clinical review.
This checklist supports general education and packet quality review. Coverage and authorization depend on the member's plan and the payer's current review. Individual assessment, treatment planning, and service intensity remain clinical decisions for qualified professionals. External review by an ABA prior-authorization specialist and a BCBA clinical reviewer remains pending.
Check initial packets before submission
Finni AI Prior Auths is designed to help teams identify packet gaps and payer-specific requirements while keeping clinicians responsible for the final request. See how Finni AI Prior Auths flags packet gaps and payer-specific requirements.
Related resources
Browse the parent guide, Prior Authorization and Medical Necessity, for the complete clinical authorization library.
- How to Maintain a Payer-Specific ABA Prior Authorization Requirements Matrix
- ABA Concurrent Authorization Checklist: Progress, Barriers and the Next Treatment Period
- How to Write a Medical-Necessity Narrative for ABA Authorization
- How to Build an ABA Authorization Appeal Packet
Sources
Sources were checked August 13, 2026. Verify each payer source again for the member's current plan before submission.
- Behavior Analyst Certification Board, Ethics Codes
- Council of Autism Service Providers, ABA Practice Guidelines Version 3.0
- Centers for Medicare & Medicaid Services, Prior Authorization API FAQ
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts
- Nevada Medicaid and Nevada Check Up, Provider Forms
- Nevada Medicaid and Nevada Check Up, FA-11E ABA Authorization Request
- Nevada Medicaid and Nevada Check Up, Instructions for Form FA-11E
- Nevada Medicaid and Nevada Check Up, FA-11F Diagnosis Certification
- Wellpoint Tennessee, Provider Forms
- Tennessee Multi-MCO Request for Applied Behavior Analysis, January 2026
- TRICARE West Region, Steps to Enroll in the Autism Care Demonstration
- TRICARE West Region, Steps to Obtain ABA Services
- TRICARE East Region, How to Obtain ABA Services
