Chapters0/28 ▾
Chapter 5 · Lesson 2 of 4
Accurate records, corrections and missing data
1 min read
Documentation is the proof that a service happened, so it must match reality. If a session was scheduled from 1:00 to 4:00 pm but the client went home sick at 2:30 pm, the record shows 1:00 to 2:30 pm, which is 1.5 hours, with an objective note on why it ended early.
Recording scheduled hours that were not worked is falsification. Copying yesterday's note and changing the date is also false, because two different sessions cannot have identical true accounts.
- Record data as the behavior happens or immediately after. Memory at the end of the day distorts counts and order.
- Fix a paper error with a single line through it, the correct value, your initials and the date. Never erase, white out or scribble over an entry.
- If a submitted note is wrong, tell the supervisor and correct it through the official process instead of quietly deleting or replacing it.
- If an interruption such as a fire drill meant no data were taken, record only what was collected and note the gap and its cause. Averages and estimates are fabricated data.
Why it matters: the supervisor decides whether a program continues, changes or ends from these records. Invented or inflated numbers can keep an ineffective program running or stop one that was working.
Check yourself
1. An RBT notices that a tally was written in the wrong column on a paper data sheet earlier in the session. What is the appropriate way to fix it?
2. When should an RBT record data during a session?
Facts checked 2026-11-15 · Sources: BACB: RBT Test Content Outline (3rd ed.), BACB: RBT Ethics Code (2.0)
RBT cheat sheet: every key fact on one page →