In almost every clinical note, the person writing it is the person who made the decisions. They assessed, they decided, they treated, and then they wrote it down.

An Applied Behavior Analysis (ABA) session note is not like that. The Registered Behavior Technician (RBT) writing it executed a protocol somebody else designed. They did not choose the programs, set the targets or write the plan.

That one difference changes what the note is for, and no guide to writing these notes mentions it. Here are three blank templates, three worked examples, an honest answer to the SOAP question, and the reason your note has a specific reader.

Key Takeaway: An ABA session note records what happened during a treatment session delivered by a Registered Behavior Technician under the direction of a supervising behavior analyst. It is structurally unlike other clinical notes because the writer did not design the treatment. Medicaid coverage for these services commonly runs through pathways where non-licensed practitioners furnish the service under supervision, and guidance from the Centers for Medicare & Medicaid Services (CMS) sets the condition that the state's scope of practice act requires the licensed practitioner to "assume professional responsibility for the patient and the service furnished by the unlicensed practitioner under their supervision" [1]. The session note is how that supervision actually happens. It should record whether the protocol ran as written, what deviated from it, and what the supervisor needs in order to decide something. Sully.ai drafts the session note from what the technician describes, so the context survives the drive home.

What an ABA Session Note Is For

The Note Has a Reader, and It Is Not the Chart

Here is the part no competing page states.

A physician's progress note is written by the person who decided the plan. If they want to know what they were thinking last visit, they read their own reasoning back.

An RBT session note is the opposite. The technician carried out a plan written by a Board Certified Behavior Analyst (BCBA) who was not in the room. The note is not a record of a decision. It is a report to the person who will make the next one.

Follow that through and it changes what matters in the note.

The most valuable sentence in an ABA session note is usually the one describing what did not go to plan. Not because problems matter more than progress, but because the deviation is the only thing the supervisor cannot get from anywhere else. The data system already tells them the trial percentages. It does not tell them the session ran in the kitchen because a sibling was ill in the living room.

Why the Data and the Note Are Different Documents

The second structural point, and the one costing technicians the most time.

Trial-by-trial responses, frequency counts, duration data, antecedent-behavior-consequence (ABC) records and percentage correct all live in the data system. They were entered during the session, on a tablet, as it happened.

The session note is not a second copy of that.

A note that paraphrases the data adds nothing a supervisor could not already see, and it takes twenty minutes per session to produce. That is the single biggest source of wasted documentation time in ABA, and it comes from nobody ever saying out loud that these are two documents with two jobs.

What the note carries instead is context the numbers cannot: what the environment was like, what the technician changed inside the protocol, what a caregiver mentioned on the way out, what the supervisor should look at before the next session.

Why SOAP Fits ABA Badly

This deserves a direct answer, because a lot of agencies mandate SOAP (Subjective, Objective, Assessment, Plan) and the people using it did not choose it.

SOAP was built for an autonomous clinician. They gather the subjective report, record objective findings, form an assessment, and write a plan. Each letter assumes the writer has the authority to do that step.

A technician has that authority for two of the four.

The Assessment field asks for a clinical judgment the technician is not the one making. The Plan field asks for a treatment plan that already exists and was written by the analyst. Filling those two boxes honestly is genuinely difficult, which is why so many ABA SOAP notes read as vague.

If your agency requires SOAP, map it rather than fight it.Subjective becomes presentation on arrival plus caregiver report. Objective becomes programs run, where the data sits, and observed behavior. Assessment becomes observations for the supervisor, explicitly not a clinical judgment. Plan becomes what you will do differently next session inside the existing protocol, plus anything escalated.

That mapping keeps the form your agency wants and puts the right content in it.

What Governs ABA Session Documentation

The Supervision Structure the Note Has to Serve

CMS guidance on Medicaid coverage of services to children with autism describes several pathways states use. One runs through Other Licensed Practitioner (OLP) services, defined at 42 CFR 440.60 as "any medical or remedial care or services, other than physicians' services, provided by licensed practitioners within the scope of practice as defined under State law" [2].

Under that pathway, services can be furnished by people who are not themselves licensed. CMS sets conditions, and one of them is the reason this article exists:

Services are furnished directly by non-licensed practitioners who work under the supervision of the licensed practitioners ... the state's Scope of Practice Act also requires the licensed practitioners to assume professional responsibility for the patient and the service furnished by the unlicensed practitioner under their supervision ... and the licensed practitioners bill for the service. [1]

Read the middle clause again. Somebody who was not in the room carries professional responsibility for what happened in it.

That is an unusual arrangement, and it is only workable if information travels reliably from the room to the responsible person. The session note is that instrument. It is not paperwork attached to the service. In this structure it is part of how the service is delivered safely.

What the Service Has to Be Doing

The service definitions CMS cites sit at 42 CFR 440.130. Preventive services are those recommended by a physician or other licensed practitioner "to prevent disease, disability, and other health conditions or their progression", to prolong life, and to promote physical and mental health and efficiency. Rehabilitative services are those recommended "for maximum reduction of physical or mental disability and restoration of a beneficiary to his best possible functional level" [3].

Every one of those definitions describes a change in direction.Progression prevented. Disability reduced. Function restored.

A session note listing activities without indicating direction of travel does not speak to that standard. It does not have to contain a progress claim on every line, and a single session often shows no measurable change at all. But across a run of notes, somebody should be able to see which way things are going.

A caveat worth stating plainly.Medicaid coverage pathways for these services vary by state, and which authority your agency bills under determines the precise documentation requirement. The principle above holds across them. The specifics are in your state plan, not in a blog post.

Where the Certification Standards Sit

The Behavior Analyst Certification Board (BACB) publishes the ethics codes governing behavior analysts and technicians [4], and the RBT Handbook covering certification and supervision requirements [5].

Both documents get revised. Rather than paraphrase their current contents here, the honest instruction is to read the version current for your certification cycle, because a session note has to satisfy the standard in force now rather than the one in force when a guide was written.

The ABA Session Note Templates

Three blocks. Each is complete as written, so you can paste it straight into a chart.

The RBT Session Note Template

RBT SESSION NOTE

• Client, date, session times: (start and stop, plus total session minutes, recorded the way any timed clinical entry should be)

• Location and who was present: (home, clinic, school, and which caregivers were there)

• Programs run this session: (named exactly as they appear in the treatment plan, not paraphrased)

• Data recorded in: (which system, so the supervisor can find it; do not copy the numbers here)

• Protocol fidelity: (did each program run as written, stated per program)

• Deviations and reason: (anything that did not run as written, and why, or "none")

• Behaviors of concern: (what preceded it, what the behavior was, what followed, described without interpretation, using the same quote-the-client, observe-the-behavior discipline that keeps attribution clear)

• Environmental context: (anything unusual about the setting that affected the session)

• Caregiver contact: (what was discussed, and what the caregiver reported)

• For the supervisor: (what you need them to decide, look at or change, or "nothing this session")

• Signature and credentials: (the technician who delivered the session)

Two lines are doing the real work here. Protocol fidelityand deviationsare the fields that exist in no other note format in healthcare, and they are the fields your supervisor reads first.

The SOAP Mapped to ABA Template

For agencies that require SOAP. Same content, mapped honestly. The Assessment and Plan fields below are deliberately narrower than in a standard SOAP note, for the reasons given earlier.

ABA SESSION NOTE, SOAP FORMAT

• Client, date, session times: (start and stop, plus total session minutes)

• S, Subjective: (how the client presented on arrival, plus what the caregiver reported, in their words where useful)

• O, Objective: (programs run as named in the treatment plan, where the data was recorded, and observed behavior)

• A, Assessment: (your observations for the supervising analyst; this is not a clinical judgment and should not read like one)

• P, Plan: (what you will do differently next session inside the existing protocol, plus anything escalated to the analyst)

• Signature and credentials: (the technician who delivered the session)

If the A field tempts you to write a conclusion about why the client behaved as they did, that is the moment to write an observation and hand the conclusion to the analyst.

The Supervision and BCBA Session Note Template

For the supervising analyst's own sessions. This is what the technician notes feed into.

BCBA SESSION NOTE

• Client, date, session times: (start and stop, plus total minutes)

• Purpose of this session: (direct treatment, protocol modification, caregiver training, technician supervision, or a combination)

• Observations of protocol implementation: (what you saw when the protocol was run, if you observed a session)

• Treatment plan modifications: (what changed, and the clinical rationale for changing it)

• Technician feedback delivered: (what you fed back, and how it was received)

• Caregiver training provided: (what was taught, and what the caregiver demonstrated, recorded against the goals in the behavioral health record)

• Next review date: (the date, and anything that would trigger an earlier review)

• Signature and credentials: (the supervising analyst)

Where Sully.ai Fits in ABA Documentation

Technicians finish one session and frequently start the next immediately, or drive to the next home and write both notes at the end of the day.

What survives that gap is the data, because it was entered on a tablet during the session. What does not survive is precisely the material this article has argued the note is for: the environment, the improvisation inside the protocol, the thing the caregiver mentioned at the door.

Sully.ai's AI scribe for behavioral health teams drafts the session note from what the technician describes, so that context is captured while it is still accurate rather than reconstructed six hours later. It runs on a single integration across Epic, Cerner, Meditech and Athenahealth.

Two boundaries, and the second one matters more than the first.

It does not judge protocol fidelity.Whether a program ran as written is a technical judgment made by the person running it, against a protocol they were trained on. No tool reading a description makes that call.

It cannot tell you what would surprise your supervisor. The entire purpose of the note is to convey what the supervisor does not already know, and that is a judgment about someone else's state of knowledge. A drafted note that reads smoothly and contains no deviation is not evidence that nothing deviated. It may only be evidence that nobody said so out loud.

Sully operates across 5,000+ providers, has delivered 50M+ hours of work, and prices each role 80 to 90 percent below the human equivalent [6].

Three Worked Examples

A Routine In-Home Session

Everything ran to protocol. Notice how short this is.

Client A, 14 September, 1530 to 1730. Total 120 minutes. Home, mother present throughout.

• Programs run: Manding for preferred items, Receptive identification of household objects, Tolerating delay of reinforcement, Independent hand washing.

• Data recorded in: Agency data system, entered live during session.

• Protocol fidelity: All four programs run as written.

• Deviations and reason: None.

• Behaviors of concern: None observed this session.

• Environmental context: Session ran in the usual work area. No disruptions.

• Caregiver contact: Mother reported the client used the mand for "outside" spontaneously twice at the weekend, which is the first time she has heard it outside of session.

• For the supervisor: The spontaneous weekend manding may be worth a generalization target.

That caregiver line is the whole value of the note. It is not in the data system, it happened outside a session, and it may change the plan.

A Session Where the Protocol Did Not Run

Client B, 15 September, 0900 to 1100. Total 120 minutes. Clinic, no caregiver present.

• Programs run: Matching to sample, Vocal imitation, Toilet training protocol. Fine motor program not run.

• Data recorded in: Agency data system, entered live during session.

• Protocol fidelity: Three of four programs run as written. Fine motor program not run.

• Deviations and reason: Fine motor program requires the pincer grip materials, which were not in the clinic kit. Substituted additional matching to sample trials rather than introducing an untrained activity.

• Behaviors of concern: None. Client was cooperative throughout.

• Environmental context: Clinic room change to Room 3 because of a scheduling overlap. Client took roughly ten minutes to settle, longer than usual.

• Caregiver contact: None, client transported by service.

• For the supervisor: Fine motor materials need replacing in the clinic kit before Thursday. Also flagging that the room change cost about ten minutes of session time, in case that is worth planning around.

Two deviations, both ordinary, both recorded with a reason. The technician also stated what they did instead, which is the part most notes leave out and the part that shows a judgment was made rather than a program simply skipped.

A Session With a Behavioral Incident

Client C, 16 September, 1600 to 1800. Total 120 minutes. Home, father present in adjacent room.

• Programs run: Tolerating transitions, Functional communication training, Joint attention.

• Data recorded in: Agency data system. ABC data recorded for the incident below.

• Protocol fidelity: All programs run as written until the incident at approximately 1705, after which the session moved to the behavior plan.

• Deviations and reason: Joint attention program discontinued after the incident, per the behavior intervention plan, which directs a return to low-demand activity following escalation.

• Behaviors of concern: At approximately 1705, following a transition instruction away from a preferred tablet activity, the client dropped to the floor, screamed for approximately 90 seconds, and struck the floor with an open hand four times. No contact with people or property. Behavior ceased following the planned response of neutral waiting with the tablet removed from view. Client accepted a break and returned to a low-demand activity within four minutes.

• Environmental context: Session ran later than usual because of a schedule change. Father noted the client had not napped.

• Caregiver contact: Informed the father immediately after the incident, described what happened and the response. He reported the same behavior twice at home this week, both times around transitions from the tablet.

• For the supervisor: Two caregiver-reported instances at home this week, both tablet transitions. May warrant review of the transition protocol or a function check.

Note what the technician did not write. No sentence explaining why the client escalated. Antecedent, behavior and consequence, factually and in order, plus the caregiver report. The interpretation is the analyst's, and the note gives them what they need to make it.

What Gets an ABA Session Note Sent Back

A note that restates the data. If the supervisor can see it in the data system, it does not need retyping. Point at the data and spend the words on context.

No deviation recorded on a session where something clearly changed. If the room changed, the materials were missing or the session ran late, that is a deviation even when the programs still ran. Silence reads as either nothing happened or nothing was noticed.

Interpretation written by the technician. "The client was seeking attention" is a hypothesis about function. Describe what happened and let the analyst draw it.

No program named from the treatment plan. A note describing a session without naming the programs cannot be matched to the plan it was supposed to deliver.

FAQ

What should be included in RBT session notes?

Session times and location, the programs run as they are named in the treatment plan, where the data was recorded, whether each program ran as written, any deviation with its reason, behaviors of concern described without interpretation, caregiver contact, and anything the supervising analyst needs to act on. The note is a report to the supervisor, not a second copy of the data.

Do ABA session notes use SOAP format?

Some agencies require it and it can be made to work, but the fit is imperfect. SOAP assumes the writer assessed the client and then wrote a plan. A Registered Behavior Technician does neither, because the treatment plan was written by the supervising analyst. Mapped honestly, Assessment becomes observations for the supervisor and Plan becomes what changes next session inside the existing protocol.

Why do ABA session notes matter for billing?

Because somebody who was not in the room carries responsibility for what happened in it. CMS guidance on Medicaid coverage for children with autism describes pathways where non-licensed practitioners furnish services under supervision, with the licensed practitioner assuming professional responsibility for the service and billing for it [1]. The session note is the record that supervision relies on.

How long should an ABA session note be?

Shorter than most people write. A routine session where everything ran to protocol needs the times, the programs, a pointer to the data, and a line confirming fidelity. Length should track how much the supervisor does not already know, which on an uneventful day is very little.

Can an AI scribe write ABA session notes?

It can draft them from what the technician describes, and Sully.ai does exactly that. What it cannot do is judge whether a program ran as written, or know which detail would surprise the supervisor. A smooth note with no deviation in it is not evidence that nothing deviated.

Sources

[1] Centers for Medicare & Medicaid Services — CMCS Informational Bulletin, Clarification of Medicaid Coverage of Services to Children with Autism, 7 July 2014. https://www.medicaid.gov/federal-policy-guidance/downloads/cib-07-07-14.pdf

[2] U.S. Government Publishing Office — 42 CFR 440.60, Medical or other remedial care provided by licensed practitioners. https://www.govinfo.gov/content/pkg/CFR-2023-title42-vol4/xml/CFR-2023-title42-vol4-sec440-60.xml

[3] U.S. Government Publishing Office — 42 CFR 440.130, Diagnostic, screening, preventive, and rehabilitative services. https://www.govinfo.gov/content/pkg/CFR-2023-title42-vol4/xml/CFR-2023-title42-vol4-sec440-130.xml

[4] Behavior Analyst Certification Board — Ethics Codes. https://www.bacb.com/ethics-information/ethics-codes/

[5] Behavior Analyst Certification Board — RBT Handbook. https://www.bacb.com/rbt-handbook/

[6] Sully.ai — AI Medical Scribe. https://www.sully.ai/medical-scribe