The session’s over. You collected your data, the client’s caregiver has gone back to the kitchen, and now you have ten minutes to turn two hours of work into a note your supervising BCBA can actually use.
“Client had a good session” won’t cut it. It doesn’t say what was taught, how the client responded, or whether anything needs attention.
This guide gives you complete ABA session note examples for RBTs and BCBAs, a free template you can copy without signing up, and the review checklist supervisors can use before a note moves to billing.
In this guide:
- What a good ABA session note looks like
- What ABA session notes are
- What to include
- How to write one, step by step
- Full examples for RBTs and BCBAs
- Free ABA session note template
- ABA SOAP notes
- Review checklist for BCBAs
- Common mistakes, with better versions
- Making review faster
- FAQs
All client details, names and data in this article are fictional and for education only. Documentation requirements vary by payer, state, service code and organization. Always follow your organization’s approved templates and your payer contracts.
ABA Session Note Example: What a Good Note Looks Like
A session note should describe what happened during the session using objective observations and measurable data. Here’s an example of how a vague note can be improved.
Weak note:
Client had a good session. Worked on goals. Some behaviors during transitions, but overall did well. Mom was happy with progress.
Stronger note:
Session time: 3:00 to 5:00 PM
Location: Client’s home
Implemented manding (two-word requests) and receptive identification (body parts) according to the current treatment plan. For manding, the client responded independently in 9 of 14 opportunities (64%), required an echoic prompt in 4 opportunities, and did not respond in 1. For receptive identification, the client responded independently in 13 of 20 trials (65%) and required a gestural prompt in 7.
During transitions, dropping to the floor, as defined in the behavior intervention plan (BIP), occurred twice across five transitions, lasting 40 seconds and 1 minute 10 seconds. A visual timer and first-then board were used before each transition, as outlined in the BIP. The caregiver reported that the client woke up early that day. No safety concerns were observed, and no criteria for supervisor notification were met.
What Makes the Stronger Note Better?
- Specific goals: It identifies the programs addressed rather than simply stating that goals were worked on.
- Measurable progress: It includes trial counts, percentages, and prompt levels instead of subjective phrases such as “did well.”
- Observable behavior: It describes the behavior, frequency, duration, and context rather than vaguely mentioning “some behaviors.”
- Relevant caregiver input: It documents the caregiver’s report without presenting it as a direct observation by the provider.
- Clear follow-up: It records safety concerns and whether supervisor notification was needed.
A strong ABA session note does not need to be lengthy. It needs to be specific, objective, consistent with the treatment plan, and supported by the data collected during the session.
What Should an ABA Session Note Include?
Most ABA session notes cover the elements below. Exact requirements depend on the payer, state, service code and your organization’s policy, so treat this as a starting point, not a compliance standard.
Element | What to record | Watch for |
Client identifier | The identifier your organization requires | Use only what’s required; don’t add extra personal details |
Date and location | Date of service and setting (home, clinic, school, community, telehealth) | Location should match the place of service on the claim |
Start and end times | Actual times, including any breaks | Times must be internally consistent and match the schedule |
Rendering provider | Name and credential (RBT, BCaBA, BCBA) | Other people present, such as a supervising BCBA, if your policy requires it |
Service type | The service delivered, using the code your payer requires | The adaptive behavior CPT code set changes January 1, 2027; confirm current coding |
Goals addressed | Programs and targets from the current treatment plan | Targets should match the authorized plan |
Interventions | Procedures used (DTT, NET, prompting, reinforcement, BIP strategies) | Describe what was actually done, not what was planned |
Objective data | Counts, percentages, durations, latency, prompt levels | Narrative must match the data entered |
Client response | What the client did, in observable terms | Avoid labels and guesses about feelings |
Caregiver input | Relevant information a caregiver reported | Label it as reported, not observed |
Events and barriers | Illness, schedule changes, environmental factors, safety events | Describe objectively and briefly |
Follow-up | Supervisor notification, if criteria were met | Follow your BIP and organizational protocols |
Signature and review | Provider authentication; co-signature or review if required | Sign within your organization’s and payer’s timeframe |
How to Write ABA Session Notes, Step by Step
- Confirm the session details. Check the date, actual start and end times, location and who was present before you write anything else. Mismatched times are easy to catch and easy to miss.
- Pull goals from the current treatment plan. Name the programs or targets you ran, in the plan’s own wording.
- Describe what you actually implemented. If you planned DTT but switched to NET because the client was engaged in play, say so.
- Add the measurable responses. Trials, opportunities, percentages, prompt levels, frequency and duration.
- Record relevant context. Include only what helps a reader understand the data, such as a schedule change or a caregiver report about sleep.
- Summarize within your role. RBTs describe what happened and how the client responded. Clinical interpretation, program changes and medical-necessity statements belong to the BCBA.
- Complete the follow-up fields. If anything met your notification criteria, document who you told and when.
- Reread before you submit. Check that narrative numbers match the data sheet, the times add up, and nothing was carried over from a previous note.
The BACB’s RBT Ethics Code (2.0) is direct about this. Standard 2.02 says RBTs follow their supervisor’s direction and accurately complete all required documentation, including client data and billing records.
ABA Session Note Examples for RBTs and BCBAs
Each example below is fictional, uses invented data, and is meant for training. Your organization’s fields and wording will differ.
Example 1: RBT session note for skill acquisition
Client: Fictional client “A.R.” Date / time: 10/05/2026, 9:00–11:00 AM Location: Clinic Provider: RBT (name, credential) Service: Direct treatment by technician following the established protocol (code per current payer guidance)
- Manding: During natural environment teaching (NET), the client had 18 opportunities to request preferred items. The client independently used two-word requests in 12 opportunities (67%), required an echoic prompt in 5, and did not respond in 1.
- Tacting: During discrete trial training (DTT), the client completed 20 trials involving target set B using a zero-second prompt delay. The client responded independently and correctly in 8 trials (40%) and gave prompted correct responses in 12. Most errors involved the targets “goat” and “sheep.”
- Following one-step instructions: During group play with two peers, the client followed 7 of 10 instructions within five seconds without prompting. The remaining 3 required a gestural prompt.
Session context: Client arrived on time. Session included a 10-minute snack break at 10:00 AM.
Notes for supervisor: Tacts set B has been at 35–45% independent across the last three sessions (data in program graph). Flagged for BCBA review; no changes made.
Signature: RBT signature, date/time
Why it works: Every program ties to the plan, every claim has a number, and the flat tact data is reported honestly. The RBT flags it without changing the program, which keeps the decision with the BCBA.
Example 2: RBT session note with transitions and a behavior-reduction target
Client: A.R. (fictional)
Date: October 8, 2026
BCBA observation time: 9:30 to 10:15 AM, during the RBT’s scheduled 9:00 to 11:00 AM session
Location: Clinic
Provider: BCBA (name and credential); RBT present
Service: Adaptive behavior treatment with protocol modification, subject to applicable payer requirements and coding guidance.
Reason for the session: The RBT reported that independent responses for tacting target set B had remained between 35% and 45% across recent sessions. The BCBA reviewed this concern to determine whether changes to the teaching procedure were warranted.
Direct observation: The BCBA observed the RBT conduct 10 tacting trials. The RBT correctly implemented the existing zero-second prompt delay in all 10 trials. The client responded independently in 4 of the 10 trials.
Protocol modification: Based on the clinical assessment, the BCBA changed the prompt delay from zero to two seconds and reduced the active target set from six animals to three. The program documentation was updated to reflect the revised procedure.
RBT training and implementation: The BCBA modeled the revised prompt-delay procedure across five trials. The RBT then conducted six trials with feedback and implemented all required steps correctly in all six trials.
Plan: Review the data after three sessions to assess whether independent responding improves. If progress remains limited, the BCBA will consider additional assessment, including a preference assessment to evaluate appropriate reinforcers for DTT.
Authentication: BCBA signature and date/time.
Why this note works: The documentation identifies the clinical concern, describes what the BCBA directly observed, explains the protocol changes, and records the training and implementation results. It also establishes a clear follow-up plan to evaluate the effectiveness of the changes.
Documentation reminder: When the BCBA observes an RBT during an ongoing session, the notes should accurately reflect the actual observation period, providers present, services delivered, and work performed. Overlapping session times alone do not establish whether services can be billed separately. Documentation and billing must follow the applicable payer’s requirements, authorization, and rules for concurrent services. Confirm service codes and requirements with the billing team before submitting claims.
Free ABA Session Note Template (Copy and Customize)
Copy this into your documentation system or a document. It’s original to Caretap and isn’t based on any proprietary template. Delete fields your payer doesn’t require and add any your payer or state does.
text
ABA SESSION NOTE
SESSION INFORMATION
Client identifier: ______________________
Date of service: ____/____/______
Start time: ________ End time: ________ Breaks (times): ____________
Location / place of service: ☐ Clinic ☐ Home ☐ School ☐ Community ☐ Telehealth
Rendering provider + credential: ______________________
Others present (name, role): ______________________
Service delivered (code per current payer guidance): ______________________
GOALS ADDRESSED (use treatment-plan wording)
- ______________________
- ______________________
- ______________________
PROCEDURES USED
☐ DTT ☐ NET ☐ Task analysis ☐ BIP antecedent strategies
☐ BIP response procedures ☐ Other: ______________________
Prompting used (type / level / delay): ______________________
Reinforcement used (type / schedule): ______________________
DATA AND CLIENT RESPONSE (one line per target)
Target: __________ Opportunities/trials: ____ Independent: ____ Prompted: ____ %: ____
Target: __________ Opportunities/trials: ____ Independent: ____ Prompted: ____ %: ____
Behavior (per BIP definition): __________ Frequency: ____ Duration(s): ____
Context (antecedent / setting): ______________________
OBSERVED EVENTS AND BARRIERS (what you saw, objectively)
______________________________________________
CAREGIVER-REPORTED INFORMATION (label as reported)
______________________________________________
SAFETY
☐ No safety concerns ☐ Safety event (describe objectively and follow protocol):
______________________________________________
SUPERVISOR COMMUNICATION
☐ No notification criteria met
☐ Supervisor notified — who: ________ when: ________ how: ________
Reason: ______________________________________________
NOTES FOR SUPERVISOR (RBT: describe patterns; don’t change programs)
______________________________________________
AUTHENTICATION
Provider signature: ______________________ Date/time signed: __________
Supervisor review / co-signature (if required): __________ Date: ______
How to customize it:
- Match your payer. Some payers require specific fields, such as caregiver signatures or particular identifiers. Check each contract.
- Mirror your treatment plan. Pre-fill goal names from the plan so RBTs aren’t retyping them.
- Keep the data and narrative together. If your system already captures trial data, link it rather than asking staff to retype numbers.
- Train before you roll it out. The Council of Autism Service Providers makes the same point about its own session note templates: templates aren’t a substitute for training, they may not meet every payer’s requirements, and they don’t guarantee audit results.
ABA SOAP Notes: Format and Example
SOAP stands for Subjective, Objective, Assessment and Plan. It’s a way to organize a note, not a requirement every payer uses.
- Subjective: What the client or caregiver reported. Label it as reported.
- Objective: What you observed and measured.
- Assessment: Interpretation of what the data means. This is clinical judgment, so in most organizations it belongs to the BCBA.
- Plan: What happens next.
If your organization uses SOAP for RBT notes, consider limiting the “A” section to a factual summary against program criteria (“Target met criterion for the session”), and leave interpretation and plan changes to the BCBA.
Example: BCBA SOAP note for a caregiver guidance session (fictional)
Client: Fictional client “M.T.” Date / time: 10/09/2026, 6:00–6:45 PM, telehealth Provider: BCBA (name, credential). Caregiver present; client present for the last 15 minutes. Service: Family adaptive behavior treatment guidance (code per current payer guidance)
S: Caregiver reported 3 elopement attempts at a store over the weekend and said the visual timer “doesn’t work when we’re out.” Caregiver stated mornings before appointments are the hardest.
O: BCBA reviewed the transition and elopement data from the last 6 sessions with the caregiver. In session, the caregiver practiced the 2-minute timer warning and first-then board in 3 role-plays; the caregiver completed 9 of 12 procedural steps in the first role-play and 12 of 12 in the third. During the final 15 minutes, the caregiver ran 2 transitions with the client; both were completed within 60 seconds.
A: Transition data in sessions show 4–5 of 7 transitions completed within 60 seconds over the last 6 sessions. The caregiver demonstrated accurate implementation after feedback. Community settings aren’t yet represented in the data.
P: Caregiver to use a portable first-then card on two planned errands this week and log transitions on the provided sheet. BCBA to add a community transition target to the plan for review at the next supervision session.
Signature: BCBA signature, date/time
Notice what’s in each section. The weekend store incident is in S because the BCBA didn’t see it. The role-play performance is in O because it was observed and counted. The interpretation stays in A, written by the BCBA.
ABA Session Note Review Checklist for BCBAs
Use this checklist to review RBT session notes before approving them for billing. It helps maintain consistent documentation, but completing the checklist alone does not establish compliance or guarantee reimbursement.
Clinical Accuracy
- Treatment plan alignment: Goals and targets match the client’s current treatment plan.
- Data consistency: Numbers in the narrative match the recorded session data.
- Behavior documentation: Behaviors are described objectively using the operational definitions in the behavior intervention plan (BIP).
- Progress reporting: Stable, limited, or declining progress is documented accurately without overstating improvement.
- Scope of practice: The RBT documented the procedures implemented and any concerns requiring review without making unauthorized program changes.
Documentation Completeness
- Session times: Start and end times are accurate and consistent with other relevant documentation, including any overlapping BCBA session.
- Place of service: The documented location matches where the service was delivered.
- Caregiver input: Information provided by caregivers is clearly identified as reported rather than directly observed.
- Supervisor notifications: Required notifications and follow-up actions are documented.
- Originality and accuracy: The note reflects the actual session and has not been copied from a previous note without appropriate updates.
Billing Readiness and Approval
- Service and coding: The documented service matches the service delivered, and the billing code follows current payer guidance.
- Authorization: The service falls within the applicable authorization, including any limits on service type, units, or provider.
- AI-assisted documentation: Any AI-generated content has been verified against the actual session data and corrected where necessary.
- Review and authentication: The responsible professional has completed the required review and signed the note within the applicable timeframe.
Final Review Outcome
Every note should receive one of three outcomes:
- Approved: All required checks are complete, and the note is ready for the next billing step.
- Returned for correction: Missing information, inconsistencies, or documentation errors must be resolved by the author.
- Escalated for BCBA review: Clinical concerns, questionable data, or issues requiring supervisory judgment need further review before approval.
A note should move forward only when all applicable requirements are met. Return incomplete or inaccurate notes to the author for correction, and escalate clinical or supervisory concerns to the BCBA before proceeding with billing.
Common ABA Session Note Mistakes
ABA session notes should describe what happened during a session using objective observations and measurable data. The following examples show how to replace vague or subjective statements with clearer documentation.
Common Mistakes and How to Correct Them
Vague praise: Instead of writing, “Client did great today,” document what the client accomplished: “Followed one-step instructions independently on 8 of 10 opportunities.”
Labels instead of observable behavior: Instead of writing, “Client was aggressive,” describe the specific action: “Hit the RBT’s arm with an open hand twice during transitions to table work, consistent with the behavior’s operational definition in the BIP.”
Assumptions about feelings: Instead of writing, “Client was frustrated,” document what was observed: “Client said ‘no’ and pushed the materials off the table.” Avoid presenting an inferred emotional state as an observed fact.
Missing prompt information: Instead of writing, “Completed 10 trials correctly,” specify the level of independence: “Across 10 trials, the client responded independently on 6 and required a gestural prompt on 4.”
Unsupported progress claims: Instead of writing, “Client is improving with tacts,” report the actual results: “Tacting target set B was 40% independent, consistent with performance across the previous three sessions.”
Repeated or copied narratives: Avoid using the same session summary throughout the week. Each note should reflect the actual session, including its specific data, interventions, client responses, and relevant events.
Recommendations outside the writer’s role: Instead of having an RBT write, “Recommend increasing hours,” document the concern and refer it appropriately: “Caregiver asked about increasing service hours. The question was forwarded to the BCBA at 5:40 PM for review.”
How to Make ABA Session Note Review Less Time-Consuming?
A consistent documentation template helps, but much of the review burden comes from missing information, inconsistent data, and corrections identified after the session. These issues can delay the billing process.
When evaluating ABA documentation software, consider five questions:
- Does session data flow into the note? Manually retyping information from data sheets can introduce inconsistencies.
- Are notes linked to the treatment plan? Goal names and targets should reflect the current authorized plan.
- Can supervisors track pending reviews? Reviewers should be able to identify notes awaiting approval and return them with specific correction requests.
- Is AI-assisted drafting reviewable? Clinicians should be able to verify, edit, and approve drafts before finalizing notes.
- Can billing staff check documentation status? The workflow should make outstanding documentation issues visible before claims are submitted.
How Caretap Supports ABA Documentation Workflows?
Caretap’s ABA software brings key clinical and administrative workflows together, including treatment plans, programs and targets, session data collection, session notes, BCBA review, authorization tracking, and documentation checks before billing.
Its data collection capabilities include frequency, duration, latency, trial-based recording, interval recording, task analysis, ABC data, and percentage correct. Authorization tracking helps practices monitor units used against units remaining.
Caretap also offers AI-assisted documentation. Supported BCBA and RBT conversations can be used to generate draft notes, which clinicians must review, edit, and approve before finalization.
Pricing starts at $99 per month for up to five users. Practices switching from another system can also receive free standard migration and staff onboarding, subject to the provider’s terms.
For practices building their documentation workflows from the ground up, read What Software Does a New ABA Practice Actually Need?.
If your notes, authorizations, scheduling, and billing currently sit in separate tools, explore How One Platform Connects Scheduling, Documentation, Billing, and Authorizations.
