ABA SOAP note template: examples for session notes and supervision

#When SOAP works for ABA documentation

SOAP is useful when a session note needs a predictable clinical order without becoming a long story. The format separates caregiver report, objective session data, clinical interpretation, and next-step planning.

For ABA, the Objective section should carry the note. Payers and supervisors need measurable client response, not only a description that therapy occurred.

#The ABA SOAP note template

Use the template as a prompt set, not a script. The headings can repeat every session, but the final wording should reflect the actual session, current treatment plan, and provider scope.

A technician note should keep the Assessment section limited to observable response and supervisor-review items. A BCBA note can include clinical interpretation, protocol changes, and plan updates when those activities are within the service billed.

• Subjective: caregiver report, setting context, client presentation, or relevant handoff
• Objective: goals addressed, procedures implemented, data collected, prompt level, behavior data, and duration
• Assessment: progress, barriers, treatment-plan fit, or supervisor review need
• Plan: targets to continue, data to monitor, caregiver follow-up, or BCBA action item
• Signature: provider name, credential, date, and required attestation when applicable

SOAP notes work well for ABA when the format stays data-led: what was reported, what was measured, what it means clinically, and what happens next.

#RBT SOAP note example

Subjective: Caregiver reported the client slept poorly and had difficulty transitioning from breakfast. Client entered session alert and accepted the first transition with one gestural prompt.

Objective: RBT implemented DTT and NET targets for manding, imitation, and listener responding. Client completed 42 of 50 acquisition trials independently, required model prompts on 5 trials, and emitted three instances of task refusal during table work. Refusal episodes resolved within 30 seconds using the behavior plan's demand-fading and differential-reinforcement procedures.

Assessment: Client maintained high response accuracy despite increased transition support needs. Task refusal was limited to table-work demands and should be reviewed by the BCBA if the pattern continues.

Plan: Continue current manding and listener-responding targets. Flag transition and table-work refusal data for supervisor review at the next overlap.

#BCBA SOAP note example

Subjective: RBT reported increased latency during transitions from NET to table work. Caregiver confirmed a similar pattern at home during cleanup routines.

Objective: BCBA observed 30 minutes of direct treatment, reviewed acquisition and behavior data from the prior two sessions, and modeled revised transition prompts for the RBT. Client transitioned within 20 seconds on 4 of 6 opportunities after the revised prompt sequence.

Assessment: Transition latency appears sensitive to abrupt activity changes. The current protocol remains appropriate with a modified transition-warning step and clearer differential reinforcement for independent transitions.

Plan: Update transition protocol, train RBT on revised prompting sequence, monitor latency for the next three sessions, and review caregiver generalization plan at the next caregiver-training contact.

#Checklist before the note is signed

Before signing, check whether each SOAP section has a job. If the same sentence could appear in every session, rewrite it with session-specific data.

The note should reconcile with the billed time and service code. If a note reads like direct implementation only, do not use it to support a protocol-modification code without adding the clinical analysis and modification that actually occurred.

• Start and end times match the units billed
• Goals and procedures match the treatment plan
• Objective data is present and understandable
• Assessment language fits the provider's scope
• Plan identifies a next clinical or documentation action
• The note is not cloned from a previous session