RBT Exam PrepThe short answer: Great RBT documentation is objective, observable, and on time. Describe what you saw in measurable terms, leave out opinions and guesses about feelings, report data exactly as collected, and communicate important changes to your supervisor promptly. Your notes are a legal and clinical record: write them like someone who was not there needs to understand exactly what happened.
Objective vs subjective: the golden rule
This distinction drives most documentation questions. Objective language describes observable, measurable facts. Subjective language adds opinions, interpretations, or guesses about internal states.
- Subjective: "He was frustrated and refused to work." Objective: "He pushed the worksheet away, said 'no,' and put his head on the table for 3 minutes."
- Subjective: "She had a great session." Objective: "She completed 8 of 10 trials independently and earned 12 tokens."
- Subjective: "Mom seemed upset." Objective: "Mom stated she was concerned about homework completion."
If a reader cannot picture exactly what happened from your words, rewrite them. Opinions about why someone did something belong in a conversation with your supervisor, not in the permanent record.
What goes in a session note
Follow your employer's required format, but most session notes include: the date, time, and location; the goals or programs addressed; objective data on performance; the procedures you implemented; any significant events or changes (illness, injury, new behaviors, environmental changes); and communication with caregivers or the supervisor. Sign and date your notes. Complete them promptly, ideally the same day, while the details are fresh. Memory fades fast, and late notes are vague notes.
Reporting data honestly
Report what you actually observed: no rounding up, no filling gaps from memory, no copying yesterday's numbers. If a session was cut short or data is missing, document that plainly. If you made an error in a written record, follow employer policy, typically a single line through the error with your initials and the date, never erasing or obscuring it. Electronic systems have their own correction procedures; learn them. Data integrity is not just ethics, it is what keeps clinical decisions safe.
Confidentiality in documentation
Session notes contain protected health information. Store them only in authorized systems, never on personal devices or personal email, and share them only with authorized team members. Leaving a data sheet on a car seat or texting a photo of it to a coworker is a confidentiality breach, and the exam will present exactly that scenario.
Data sheets: your in-session scratch paper
Session notes are the polished record; data sheets are where the numbers live during the session. Fill them in as the behavior happens, not from memory at the end, because memory invents data. Know your sheet before the session starts: which columns, which codes, what counts as a correct response. If the plan changes mid-session per supervisor direction, note the change and the time. Messy sheets lead to messy notes, and messy notes lead to clinical decisions built on sand. Treat the data sheet like the cockpit checklist it is: boring, exact, and non-negotiable.
Quick-fire review
- Objective = observable facts; subjective = opinions and guesses
- Same-day notes, signed and dated, in the required format
- Never alter records; correct errors per policy
- Urgent changes go to the supervisor directly, not just in the note