ABA documentation requirements, billing codes and audit defense
ABA documentation requirements are the elements a payer expects to find before it pays a claim: who was seen, when, for how long, by whom, what was delivered, what the data showed, and why the service was medically necessary.
Read more about payer requirements ＋
There is no single national ABA documentation standard. Commercial payers, TRICARE contractors, and state Medicaid programs publish their own requirements, and each clinic is responsible for meeting the strictest rules that apply. CliniScripts drafts documentation from the session and preserves review, signature, and edit history while the treating clinician remains the author of record.
Last updated: 23 August 2026
Required elements are connected to the session record.
Time & serviceMatches scheduled session
VerifiedGoals & dataLinked to treatment plan
ConnectedClinical narrativeSession-specific response
ReviewedSignature trailAuthor and reviewer recorded
CompleteWhat documentation do ABA payers actually require?
Payers require a note that identifies the client, fixes the session in time and place, names and credentials whoever delivered the service, records the behavior in observable terms with its data, and states in narrative form how the client responded and how that relates to treatment plan goals.
That list is a synthesis, not a rule you can quote back at a reviewer. The honest position no vendor states plainly: there is no single national ABA documentation standard. Requirements are set payer by payer and state by state, and the clinic has to confirm its own. What helps is that several payers publish theirs openly, and the lists overlap.
Read more ＋
Humana Military, the TRICARE East contractor, requires an ABA progress note to carry the beneficiary's full name; the date with start and end times and session length; the place of service; the names and relationship of participants; and the name, credentials and dated signature of the rendering supervisor, assistant behavior analyst or behavior technician. It defines clinical status as "the specific, observable and measurable behavior displayed," and requires narrative content for the session summary, response to treatment and progress toward goals — stating that data alone does not meet this requirement.
State Medicaid programs add conditions. MO HealthNet requires documentation to be completed within five business days to be timely, and a licensed behavior analyst to co-sign notes for services rendered by behavior technicians or RBTs. It warns that using a published template — even the CASP templates it recommends — "does not guarantee immunity from audits." Two payers, two rule sets, both explicit: read yours before you design your note template.
The adaptive behavior CPT codes and what each one has to show
The adaptive behavior codes are 97151 and 97152 for assessment and 97153–97158 for treatment, plus Category III codes 0362T and 0373T for clients with severe destructive behavior treated by two or more technicians under on-site oversight. All are reported in 15-minute units.
Descriptors are quoted from the ABA Coding Coalition billing codes reference; presence, direction and concurrent-billing rules from the ABAI supplemental guidance on the adaptive behavior codes. The final column is our summary of what payers commonly look for, not part of the CPT descriptor — confirm it against your payer's policy.
| Code | Service | Who delivers it | What the note has to demonstrate |
|---|---|---|---|
| 97151 | Behavior identification assessment | Physician or other qualified health care professional (QHP) | The assessment activity, including the non-face-to-face time this code allows — reviewing past data, scoring and interpreting, preparing the report and plan. A treatment plan on its own is not a note. |
| 97152 | Behavior identification supporting assessment | One technician under the direction of a QHP | Which supporting assessment procedure was run, on whose direction, and the data it produced. |
| 97153 | Adaptive behavior treatment by protocol | Technician under the direction of a QHP | The protocol run as written, the targets, the data, the client's response, and the time delivered. The highest-volume code, and the one most often sampled in an audit. |
| 97154 | Group adaptive behavior treatment by protocol | Technician under the direction of a QHP | That the service was delivered in a group, each client's own targets and data, and group composition matching what was authorised. |
| 97155 | Adaptive behavior treatment with protocol modification | Physician or other QHP | The modification itself. Humana Military requires the note to define the protocol modification clearly; supervision or observation alone is not enough. |
| 97156 | Family adaptive behavior treatment guidance | Physician or other QHP | Who received the guidance, what was taught, and how it maps to the client's goals. This service may occur with the client absent. |
| 97157 | Multiple-family group adaptive behavior treatment guidance | Physician or other QHP | The multi-family group format and each family's participation. The guidance states this service occurs without the patient present. |
| 97158 | Group adaptive behavior treatment with protocol modification | Physician or other QHP | The group format and the protocol modification made during it, with per-client data. |
| 0362T | Behavior identification supporting assessment (severe destructive behavior) | Two or more technicians, QHP on site | The customised environment, the number of technicians, and QHP presence on site — defined in the guidance as immediately available and interruptible at the same location. |
| 0373T | Adaptive behavior treatment with protocol modification (severe destructive behavior) | Two or more technicians, QHP on site | The same staffing and on-site conditions, plus the protocol modification. Direction is bundled into this code rather than billed separately. |
Changing soon. The ABA Coding Coalition has announced that the AMA CPT Editorial Panel accepted its code-change application in September 2025: new codes, revised guidelines, and deletion of the existing Category III T codes, effective 1 January 2027. The new numbers stay confidential until the AMA publishes them, so treat today's templates as due for review in late 2026.
What "medical necessity" means in an ABA note
Medical necessity in an ABA note is not a sentence you add at the end. It is the property of a note a reviewer can read once and understand why this client needed this service, at this intensity, from this person, on this day.
Four things carry it, and all four have to be visible in the note itself rather than inferable from a treatment plan in another file.
- The behavior described in observable terms. "Dysregulated" and "had a hard morning" are not clinical status. "Three instances of elopement from the table, each 20–40 seconds, during demand presentation" is.
- The link from the target to the treatment plan goal. A target that does not obviously trace to an authorised goal reads to a reviewer as unauthorised service. Name the goal, not just the target.
- The data supporting progress, or the reasoning where there is none. Flat data is not a problem; flat data with no clinical comment is. A note that says a target has not moved in six weeks and what changes next is far stronger than one that reports the same numbers silently.
- Why this service level. A session billed as 97155 has to show a protocol modification, not a BCBA in the room. A session billed as 97153 has to show the protocol being run by the technician and the time it took.
The compact test: strip the client's name out, and could a reviewer still tell which client this was and why the service was needed? If not, the note describes a service rather than justifying one.
Why ABA claims and notes get flagged
Most flags are not clinical disagreements. They are inconsistencies a reviewer spots without knowing anything about the client — times that do not match, notes that repeat, signatures missing, goals that never change.
| What the reviewer finds | What usually caused it | What a clean note looks like |
|---|---|---|
| Session times in the note do not match the schedule or the units billed | The note was written later from memory, or the scheduled block was copied in instead of actual start and end times | Times captured from the session as it happened, matching the units billed, with any variance from the schedule explained |
| Notes across sessions read as near-identical | Template reuse, copy-forward, or a generated draft signed without editing | Session-specific detail in every note: what happened, what varied, what the data showed that day |
| Technician-delivered service with no supervising clinician documentation | Co-signature workflow not enforced, or direction recorded in a system the auditor never sees | The technician's name, credentials and dated signature, plus the supervisor's co-signature where the payer requires it |
| Narrative with no data, or data with no narrative | Data lives in the collection tool and the note is prose, or raw trial data is exported with no interpretation | Both in one document: the numbers, and a summary of the response to treatment and progress toward goals |
| Goals unchanged across a whole authorization period | Mastery criteria never revisited, or plan updates made verbally and never written down | Visible progression — targets mastered and retired, criteria adjusted, or a stated rationale for holding a goal |
| 97155 billed for a session that reads as observation | The BCBA was present and supervising, but the note describes no change to the protocol | The modification named: what changed, why, and what happened after |
Recovery costs more than people expect: the payer requests a sample, someone pulls it by hand, the clinical director reads every note in it, and the clinic pays for that time twice. Clinical directors overseeing multi-site ABA operations usually find the cheapest fix is upstream, in what the note captures at the point of care.
How AI-drafted notes hold up under audit
An AI draft is not the audit risk; an unreviewed note is. A note drafted by software, read and corrected by the clinician and signed by them is a signed clinician note — the same as one dictated into a phone or typed from a template.
What makes it defensible is the trail behind it. CliniScripts records the attestation chain on each note: who drafted it, who reviewed it, who signed it, when each happened, and what changed between the draft and the signed version. If a reviewer asks how a note came to exist, the answer is a record rather than a policy statement.
- The clinician is the author of record. The signature asserts the content is accurate. Software drafts; a person signs.
- Edits after signature are addenda, not rewrites. The originally signed content stays retrievable, and every change is attributed and timestamped.
- CliniScripts does not determine coverage and does not submit claims on a clinician's behalf without review. The platform assembles documentation and prepares billing information; a human approves what leaves the building. Coding is a clinical and billing decision; coverage is the payer's.
That is why supervisor review workflows for BCBAs sit between the draft and the claim rather than beside them. A review step that can be skipped is not a review step.
Cloned notes: the specific risk of any generated documentation
Cloned notes — sessions that read the same week after week — are among the first things a reviewer looks for, and any system generating text from a template drifts toward sameness unless something pushes against it.
The mechanism is worth naming. A model drafting from a fixed structure, for a client whose program is stable, in a service where many sessions genuinely do resemble each other, will produce similar sentences. Add a clinician who signs at 6pm without reading, and you get notes that are individually plausible and collectively indefensible. The risk predates AI — the copy-forward button has been producing it for twenty years — but generated text produces it faster and at volume, which is why it is worth engineering against.
- The draft comes from the session, not the last note. The source is what was recorded or entered that day, not the previous note copied forward.
- Session data is bound into the note. ABA data collection and trend graphs feed the note, so the numbers in each note are that day's numbers.
- Clinic memory carries context, not text. Continuity keeps goals and history correct rather than reproducing prior wording.
- Review is a distinct, stamped step. "Signed instantly, unedited, across forty notes" is visible to you internally before a payer ever sees it.
None of that removes the clinician's obligation. If two sessions genuinely read the same, the fix is clinical: either the sessions were not meaningfully different, or the note is not capturing what made them different.
Questions ABA billing and compliance staff ask
Are AI-generated notes allowed for ABA billing?
No payer rule we can find prohibits a note that was drafted with software, and clinicians have used templates, dictation and transcription for decades. What payers require is that the note is accurate, specific to the session, and signed by the rendering clinician, with a co-signature where a technician delivered the service under direction. An AI draft that the clinician reads, corrects and signs is a signed clinician note. An AI draft nobody read is the problem, and it would be the same problem from a paper template.
What has to be in a 97153 note?
CPT 97153 is adaptive behavior treatment by protocol delivered by a technician under the direction of a physician or other qualified health care professional, billed in 15-minute units, so the note has to show the protocol being run as written and the time actually spent doing it. In practice: client name, date, start and end times, place of service, who was present, the technician's name, credentials and dated signature, the targets with their data, the client's response, and a narrative summary rather than data alone. Confirm the exact element list with your own payer and state Medicaid program.
How long must ABA records be retained?
There is no single national number, and any vendor who gives you one is guessing. The U.S. Department of Health and Human Services states that the HIPAA Privacy Rule does not include medical record retention requirements and that state laws generally govern how long they are kept; separately, 45 CFR 164.316(b)(2)(i) requires HIPAA-mandated documentation such as policies and procedures to be retained for six years. Your period comes from your state, your licensing board and your payer contracts — retain at least as long as the longest of the three.
What is a reauthorization packet?
A reauthorization packet is the documentation a payer asks for before approving the next authorization period of ABA services: an updated assessment or progress report, the current treatment plan with goals and mastery criteria, graphed data, caregiver training participation, and the clinical rationale for the hours requested. It is assembled from session notes already in the record, which is why note quality across the period decides how hard it is to build. Each payer publishes its own requirements and windows.
Can a note be edited after signing?
Yes, but the edit has to be an addendum or a tracked correction, not a silent rewrite of the signed record. The defensible pattern is that the original signed content remains retrievable, the change is attributed to a named user with a timestamp, and a reason is recorded. In CliniScripts, edits after signature are captured in the note's history rather than overwriting what was signed, so a reviewer can see the original, the change and who made it.
Who is the author of record?
The clinician who reviews and signs the note is the author of record, and that does not change because a draft was generated by software. CliniScripts produces a draft from the session; the BCBA, BCaBA or technician reads it, corrects anything wrong, and signs it, and the signature asserts the content is accurate. The attestation trail records who drafted, who reviewed, who signed, when, and what changed between draft and signed version.
Does CliniScripts submit claims?
No. CliniScripts does not determine coverage and does not submit claims on a clinician's behalf without review. The platform can surface documentation and prepare billing information for a human to check, but a person approves what goes out. Coverage decisions belong to the payer and coding decisions belong to the clinician and the practice's billing staff.
Are the adaptive behavior CPT codes changing?
Yes. The ABA Coding Coalition has announced that the AMA CPT Editorial Panel accepted six new CPT codes, revisions to codes 97151 to 97158, revised guidelines, and deletion of the existing Category III T codes, effective 1 January 2027 and published in the 2027 CPT Professional code book late in 2026. The new code numbers are confidential until the AMA releases them. Plan a template review in late 2026 rather than assuming current templates carry over.
Where this page sits in the CliniScripts structure
Billing and audit defense is downstream of everything else in ABA documentation. If the note is right at the point of care, the claim is usually right too — so this page links back to the people who write the notes and the hub that covers the clinical work.
See what your notes would look like before an audit does
Bring one authorization period of real documentation to a call and we will walk through what a reviewer would look for, what your current notes show, and what CliniScripts would capture differently. No coverage advice, no claim submission — just the documentation.
All Rights Reserved