RBT Session Note Examples: What the Documentation Domain Tests
RBT session notes document what happened during a behavior-analytic service session: the date, time, and duration, what procedures were run, the data collected, the client’s response, and anything unusual an RBT Supervisor needs to know. This is the practical, day-to-day version of the Documentation and Reporting domain, which makes up 13% of the scored RBT exam (10 of 75 scored questions). We’re covering the general structure and purpose these notes serve here for exam-prep and study purposes; your actual employer’s specific note format, EHR system, and clinical documentation standards always govern what you write on the job, not this page.
People searching for session note examples are usually either studying for the Documentation domain specifically, or newly on the job and looking for a sense of what a complete note actually includes. Both land on the same underlying structure, since the exam domain and the real documentation task are testing the same underlying skill: capturing what happened clearly enough that someone who wasn’t there can understand it. This domain is one piece of the broader RBT certification exam, and it pairs closely with the study approach in our RBT exam study guide.
(RBT HQ is not affiliated with the BACB. We use “RBT” the way the field does, to name the exam domain, not to claim we administer clinical documentation standards, which vary by employer and jurisdiction.)
What does the Documentation and Reporting domain actually cover on the exam?
10 of the 75 scored questions, 13% of the exam, the second-smallest of the six domains, ahead of only Behavior Assessment at 11% (RBT Test Content Outline, 3rd ed.). It sits alongside Data Collection and Graphing as one of the two domains most directly about record-keeping rather than direct client interaction, which is exactly why the two get confused with each other, data collection is capturing numbers during a session, documentation and reporting is writing up what happened around and alongside those numbers.
What does a complete session note structure typically include?
Six core elements, in roughly this order:
| Element | What it captures |
|---|---|
| Session identifiers | Date, start and end time, location, RBT and client identifiers |
| Procedures implemented | Which programs or interventions ran during the session |
| Data summary | Key data points or trends from the session (often referencing a separate data sheet) |
| Client response | How the client responded to procedures, including any notable behavior |
| Anything unusual | Incidents, changes in presentation, or anything a supervisor should know about |
| RBT signature/attestation | Confirmation of who wrote the note and when |
This structure reflects common documentation conventions across ABA settings generally; your specific employer’s required fields and format always take precedence, and this page isn’t a substitute for that internal training.
Why does documentation quality actually matter beyond the exam?
Because a supervisor reviewing your written materials, including session notes, is one of the listed activities inside your ongoing supervision requirements. A note that’s vague about what actually happened doesn’t just look sloppy; it limits what your supervisor can actually evaluate about your service delivery during the parts of the month they’re not directly observing you. Clear documentation is functionally part of how supervision works, not a separate administrative chore layered on top of it.
What’s a common mistake in how people write these notes?
Recording the outcome without recording the procedure. A note that says a client “did well with reinforcement” tells a reader almost nothing useful: which procedure, what schedule of reinforcement, what “did well” actually measured against. The stronger version names the specific procedure, the specific data point or trend, and the specific observed response, the same specificity the exam’s Documentation domain questions are checking whether you understand the purpose of.
How does this connect to what the competency assessment checks?
Directly. Practicing for the competency assessment often includes producing a sample note or data summary that meets basic format expectations, since documentation is one of the few Documentation-domain skills that’s naturally demonstrable hands-on rather than purely knowledge-based. If you’re rehearsing for that assessment, writing a full practice note after a mock session, not just discussing what one should contain, is a more useful rehearsal than reading examples alone.
Should I study real note examples from my job, or generic ones?
Both, for different reasons. Your actual employer’s format and required fields are what you’ll be graded against day to day, and that’s what to study for the job itself. Generic structural examples, like the six-element breakdown above, are more useful for understanding why the Documentation domain exists as 13% of the exam, connecting the abstract task-list language to something concrete you can picture, rather than memorizing your specific employer’s exact template as if it were universal.
Run the free RBT HQ practice exam and pay attention specifically to Documentation and Data Collection questions together, since in practice the two domains reinforce each other more than most people expect going in.
The free RBT HQ Exam Prep Cheat Sheet keeps all six domains, including Documentation and Reporting, on one page, a fast reference while you’re comparing your own note-writing habits against what the exam is actually checking.
FAQ
Is writing session notes tested directly on the RBT exam? The exam tests your knowledge of documentation principles and the Documentation and Reporting domain generally, worth 13% of scored questions, rather than having you write a live note during the written exam itself.
What’s the difference between data collection and documentation on the exam? Data Collection and Graphing (17% of the exam) covers recording and graphing numeric data during a session. Documentation and Reporting (13%) covers the broader written record of what happened, including but not limited to that data.
Do all RBT employers use the same session note format? No. Formats vary by employer, EHR system, and funder requirements. The BACB tests general documentation principles on the exam; your specific job dictates the exact template you’ll use in practice.
Can a poorly written session note affect my supervision? Indirectly, yes. Your supervisor reviewing written materials like session notes is a recognized supervision activity, so unclear notes can limit how effectively that supervision actually functions, even if it doesn’t directly fail you on anything.
Is documentation practice part of the competency assessment? Often, yes, in the form of producing a sample note or data summary that meets basic expectations, though the exact format depends on your specific assessor and organization.
Bottom line: RBT session notes and the Documentation and Reporting exam domain test the same underlying skill, writing clearly enough that someone who wasn’t in the room understands exactly what happened. Study the domain’s purpose generically; follow your actual employer’s format on the job.