RBT Documentation & Reporting: What to Know for the Exam

Notes should be facts a supervisor can act on

Documentation items punish vague storytelling. The exam wants observable facts the supervisor can act on. Practice choosing the note that reports what was seen → rather than the note that explains the client’s personality. Domain E is 10 scored items (13%)—enough to matter, easy to ignore if you only drill DRA and DTT.

Write what happened, when, and what you did from the plan. Leave motive out. “Client was lazy” is not data. “Client completed 2 of 10 independent trials; coughed frequently; temperature reported by caregiver as 101°F” is a note plus a variable that may affect progress.

What to communicate, and to whom

Seek supervisor direction when the plan is silent, a procedure is untrained, or session conditions changed in a way that affects implementation. The chain of command is the supervisor, not a coworker’s group chat and not the client’s neighbor.

Report illness, medication changes you were told about, missing materials, and setting events the plan asks you to capture. Do not wait for a monthly recap if the handbook and workplace rules say notify now. The ethics guide overlaps: withholding relevant session information is not a documentation style. It is a professional problem.

Do not change targets, prompt levels, or reinforcement schedules on your own to make a graph look better. That is both documentation fraud and an unauthorized plan change.

When a stem offers a dramatic narrative option and a dry observation option, pick the observation and keep practicing that habit →.

Overlap with data collection, without duplicating Domain A

Domain A owns measurement method and graphs. Domain E owns how those facts travel: session notes, objective language, and asking for direction. A perfect frequency count that never reaches the supervisor is still a reporting failure. See data collection.

Competency assessments also require accurate demonstration records. That is a different event from Pearson VUE, but the same honesty rule. See competency.

If you keep missing items that look like “be a team player and just handle it,” use the rationale to name the supervisor step →. Helpfulness without direction is a frequent distractor.

How to study Domain E in small sessions

Collect five bad notes and rewrite them as observable. Then mix a few Domain E items into Acquisition-heavy sets so you still recognize them. The what-to-study guide shows the weight.

Do not write a novel. The examination is four options. The skill is choosing the report that is accurate, timely, and inside role.

When the note versus story distinction is stable, put Documentation into mixed RBT practice →. Graphs without communication are only half of what this domain tests.