Skip to content
MegAligna

Free template

Free ABA session note template that survives a payer audit

An ABA session note documents one billed session: client, date, start and end times, place of service, CPT code, the programs run, a narrative tied to treatment-plan goals, and the rendering provider's credential and signature. Download the free template, or generate payer-ready notes from MegAligna with the session data already filled in.

Start free trial See pricing

What auditors actually check

A session note exists to support the claim that was billed against it. In a post-payment review, the auditor reads the note next to the claim line and asks: do the times support the units billed, does the credential match the code, does the narrative show the authorized service actually happened? A note can be clinically thoughtful and still fail all three.

Identification

  • Client name and date of birth
  • Date of service, with start and end times, not a duration
  • Place of service, matching what was billed
  • Rendering provider name, credential and signature, with supervising BCBA where required

Billing linkage

  • CPT code for the session
  • Units, consistent with the recorded times
  • The authorization the session was delivered under

Clinical content

  • Programs and targets run, tied to treatment-plan goals
  • Data summary for the session
  • Behavior incidents and any protocol modifications
  • Plan for the next session

The two failures that cost money

Times that do not support the units. Four units of 97153 is one hour. A note reading “2:00-2:45” under a four-unit claim line is a recoupment in waiting, and it is the single most common documentation finding.

Credential mismatches. A code delivered by a technician, noted by a technician, but signed only by an unnamed supervisor, or the reverse, fails the who-rendered-this question. The note must name the person the claim says rendered the service.

What the blank note gives an RBT to fill in

Download the ABA session note template (CSV)

The file follows the order an RBT works in. A session block comes first: client, date, start and end times, total minutes, place of service, rendering and supervising provider, and the service code. Then a programs-run grid with a row per program or target (trials or minutes, correct or independent, prompted, percent), a behaviour grid with antecedent and consequence, and a narrative block covering presentation, interventions, response, caregiver contact and the plan for next session. It ends with delivered-by and co-signed-by lines.

Two things are deliberately left to you. The service code is a blank you fill in, because CPT descriptors are licensed by the AMA and the file ships none. And the total-minutes line is there so the RBT does the arithmetic the auditor will do: if the minutes do not support the units on the claim, the note is the place to catch it.

Filled from the session instead of by hand

In MegAligna the note pulls its own session data: times from the session, programs and trial data from collection, and the code and units from the charge. What remains for the RBT to write is the narrative, which keeps the structured fields consistent with the claim while leaving the clinical account to a person.

What fills this in on a live caseload is ABA data collection, and the note surface it becomes is described in clinical notes. A signed session note is also the charge: see ABA billing.

Session note questions from RBTs and BCBAs

How soon after the session should the note be written?
Same day is the defensible norm, and some payers state a deadline in their provider manual. A note dated days after the session invites the question of what it was reconstructed from.
Does every 97153 session need its own note?
Yes. One note per billed service line, with its own times and signature. A weekly summary covering five sessions cannot support five claim lines.
Can the supervising BCBA sign instead of the RBT?
The rendering provider documents and signs their own service. Co-signature requirements for RBT-delivered sessions are payer-specific and state-specific, so treat the co-sign rule as configuration, not doctrine.

Collect a test session and see the note it writes

14 days, no card required. Use made-up patients while you evaluate: real patient information waits until a business associate agreement is in place.