What a session note is for
A note has three readers. The payer or auditor needs to see that the billed service was delivered by the right person, for the time billed, against goals in an authorized treatment plan. The care team needs to know what was worked on, how the learner responded, and what should happen next. And the record itself needs to hold up years later, when nobody remembers the session.
Writing for all three at once is what separates a note from a diary entry. "Great session, worked on lots of goals" serves none of them; a note that names the targets, gives the data, and states the plan serves all three.
What every note should include
Requirements vary by payer and state, so check the documentation policy of each payer you bill. The elements below are common to most of them.
| Element | What to record |
|---|---|
| Identification | The learner, the date, start and end times, the service location, and everyone present. |
| Service | The CPT code, the rendering clinician and their credential, and units that match the times recorded. |
| Goals addressed | The treatment-plan targets worked on, named the way the plan names them. |
| Data | Each target's results in its own units: percent independent, counts, durations, prompt levels. |
| Behavior | Behaviors of concern that occurred, with frequency or duration, and the plan procedures used in response. |
| Interventions | The procedures delivered: teaching formats, prompting, reinforcement, and behavior plan strategies. |
| Response and progress | How the learner responded, compared with recent sessions and with the goal. |
| Plan | What happens next session, and anything that needs the supervising BCBA's attention. |
| Signature | The rendering clinician's signature and date, plus a co-signature where the payer or organization requires one. |
The SOAP format
Many ABA providers structure notes as SOAP: Subjective, Objective, Assessment, and Plan. Subjective is what was reported rather than measured - a caregiver's report of poor sleep, a new medication, the learner's own statements. Objective is what was measured: the session's data for each target and each behavior, with times, location, and code. Assessment is the clinician's interpretation - progress against goals, trends across sessions, barriers. Plan is what happens next.
Some providers use variants such as DAP (Data, Assessment, Plan), which folds reported information into the data section. The structure matters less than the discipline it enforces: keeping what was observed separate from what was concluded, so a reader can check one against the other.
A worked example
The note below is for a fictional two-hour session of one-to-one treatment. It is written to be checked: every figure can be traced to the session's data, and every conclusion points back to a figure.
| Section | Example |
|---|---|
| Subjective | Caregiver reported the learner slept about 6 hours, less than usual, and ate little breakfast. |
| Objective | 97153, 2:00-4:00 PM, home, 8 units; RBT and caregiver present. Manding for items: 14 of 20 opportunities independent (70%). Receptive colors (DTT): 8 of 10 trials independent (80%). Handwashing task analysis: 6 of 8 steps independent, partial physical prompts on steps 3 and 4. Elopement: 2 occurrences, 15 and 40 seconds, blocked and redirected per the behavior plan. |
| Assessment | Manding is up from 55% last session and continues an upward trend across five sessions. Receptive colors met the 80% criterion for the second consecutive session. Both elopements occurred during transitions, consistent with the escape hypothesis in the behavior plan. |
| Plan | Continue the current manding protocol. Probe receptive colors with a second therapist. Flag transition elopement for review at the next supervision visit. |
Writing objectively
Describe what was observed, not what it is assumed to mean. "Was frustrated" and "had a good day" are conclusions a reader cannot check; "pushed the materials away and said 'no' three times" and "completed 9 of 10 trials independently" are observations. The same discipline that makes ABC data useful makes notes defensible.
Write the note as soon as possible after the session, from the data recorded during it. Every number in the narrative should match the recorded data and the graph built from it; a note that says 80% when the data say 70% is a finding in an audit. Avoid cloned notes: reusing a structure is fine, but notes that repeat the same narrative session after session are a common audit flag, because they suggest the note was not written about the session it describes.
The problems auditors find most often
The same issues recur: missing or late signatures, start and end times that do not support the units billed, a code that does not match the service or the clinician's credential, goals that do not appear in the authorized treatment plan, and notes with no data at all. A 97155 note that does not say what protocol was modified or how the technician was directed is a frequent example of a code the note does not support; the ABA CPT codes guide covers what each code requires.
Corrections are the other common problem. Once a note is signed, it should be corrected with a dated addendum that leaves the original visible, not edited in place. An edited note with no trail of what changed reads, to an auditor, as a record that cannot be trusted.
RBT notes and supervisor co-signature
RBTs commonly write the notes for the sessions they deliver; the BACB's RBT Handbook lists generating session notes among the activities an RBT may perform. Many payers and organizations also require a supervising BCBA to review or co-sign an RBT's notes, and reviewing notes and data sheets is one of the supervision activities the BACB recognizes - see the RBT supervision requirements guide.
A co-signature means the supervisor has read the note and stands behind it. Routing notes to the supervisor as they are signed, rather than in a batch before an audit, keeps that review meaningful and catches problems while the session is still fresh.
How Cadence drafts session notes
Cadence drafts a SOAP note from the session's committed data, with the data attached, for the clinician to review, edit, and sign. Every figure in the draft is checked against the committed measurements, and a percentage that does not match is flagged before signature. A required-element checklist blocks sign-off while something a payer will ask for is missing, such as the service location or the session's CPT code.
A note signed by an RBT is routed to their supervising BCBA for co-signature, and signed notes can be amended only through tracked addenda, so the record shows what changed and when.