Study guide
9.4 Supervision Documentation, Audit Readiness, and Record Retention
RBT Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: RBT Orientation, Official Sources, and 2026 Transition
1.1 What the RBT Credential Does and Does Not Authorize 1.2 Official Source Control and 2026 TCO Transition 1.3 Eligibility, Application, Fees, and Competency Assessment 1.4 Exam Format, Domain Weights, and Question Strategy 1.5 Results, Retakes, and Historical Passing Data 1.6 Supervisor-Supported Study Map
2 Chapter 2: Measurement, Data Collection, and Graphing
2.1 Observable Definitions and Session Readiness 2.2 Continuous Measurement: Frequency, Duration, Latency, and IRT 2.3 Discontinuous Measurement: Interval Recording and MTS 2.4 Permanent Product Recording and Data Source Selection 2.5 Data Entry, Graph Updates, and Visual Display 2.6 Rate, Mean Duration, Percentage, and Summary Calculations 2.7 Trend Identification, Data Quality, and Fidelity Risks
3 Chapter 3: Behavior Assessment and Preference Assessments
3.1 Assessment Role Boundaries for RBTs 3.2 Preference Assessment Formats: MSWO, Paired, and Free Operant 3.3 Skill Assessment Participation and Strength-Deficit Observation 3.4 Functional Assessment Support: Descriptive and Functional Analysis 3.5 ABC Observation, Context, and Objective Reporting 3.6 Assessment Case Lab: From Preference to Supervisor Report
4 Chapter 4: Behavior Acquisition Core Teaching Procedures
4.1 Reinforcement Procedures: Positive, Negative, and Schedules 4.2 Conditioned Reinforcers and Token Economies 4.3 Discrete-Trial Teaching Implementation 4.4 Naturalistic Teaching and Incidental Teaching 4.5 Discrimination Training and Stimulus Control 4.6 Maintenance Versus Acquisition Decisions 4.7 Behavior Acquisition Case Lab
5 Chapter 5: Prompting, Chaining, Shaping, and Generalization
5.1 Stimulus and Response Prompts 5.2 Prompt Fading, Errorless Learning, and Time Delay 5.3 Task Analysis and Forward, Backward, and Total-Task Chaining 5.4 Shaping Successive Approximations 5.5 Generalization Across Settings, People, and Stimuli 5.6 Procedural Fidelity, Error Correction, and Supervisor Feedback 5.7 Teaching Procedure Case Lab
6 Chapter 6: Behavior Reduction and Crisis Protocols
6.1 Common Functions of Behavior and Supervised Interpretation 6.2 Antecedent Interventions: NCR, High-Probability, and Demand Fading 6.3 Differential Reinforcement: DRO, DRA, DRI, DRL, and FCT 6.4 Extinction Procedures and Secondary Effects 6.5 Punishment Procedures and Time-Out Scope Controls 6.6 Crisis and Emergency Protocol Implementation 6.7 Behavior Reduction Case Lab
7 Chapter 7: Documentation, Reporting, and Session Communication
7.1 Objective Session Notes and Observable Language 7.2 Communicating Intervention-Team Concerns to Supervisors 7.3 Seeking Clinical Direction and Following Chain of Command 7.4 Reporting Variables That Affect Progress 7.5 Legal, Regulatory, and Workplace Documentation Rules 7.6 Documentation and Reporting Case Lab
8 Chapter 8: Ethics, Scope, Confidentiality, and Professional Conduct
8.1 Core Principles: Dignity, Compassion, and Integrity 8.2 Competence and Scope of RBT Services 8.3 Ongoing Supervision and Effective Feedback Practices 8.4 Confidentiality, Privacy, and Information Handling 8.5 Public Statements, Social Media, and Credential Representation 8.6 Multiple Relationships, Gifts, and Boundary Risk 8.7 Cultural Humility, Professional Communication, and Ethics Case Lab
9 Chapter 9: Supervision, Maintenance, and Workflow Readiness
9.1 RBT Supervisor and Requirements Coordinator Structures 9.2 Monthly 5% Supervision and Face-to-Face Contacts 9.3 Client-Specific Oversight and Supervisor Listing 9.4 Supervision Documentation, Audit Readiness, and Record Retention 9.5 Recertification, Transition, Reentry, and Inactive Status 9.6 Workplace Readiness for New RBTs
10 Chapter 10: Integrated RBT Session Scenario Labs
10.1 Home Session Data and Caregiver Communication Lab 10.2 School Classroom Antecedent and Reinforcement Lab 10.3 Clinic DTT, Prompting, and Token Economy Lab 10.4 Community Generalization and Safety Lab 10.5 Behavior Reduction and Crisis Documentation Lab 10.6 Data Irregularity and Supervisor Escalation Lab 10.7 Ethics, Supervision, and Boundary Simulation
11 Chapter 11: Final Review, Exam Day, and Recertification Plan
11.1 Final 30-Day RBT Study Plan 11.2 Domain-Weighted Review and Remediation Map 11.3 Timed Practice Pacing and Question Reading 11.4 Common RBT Distractor Patterns 11.5 Pearson VUE Test-Day Readiness 11.6 Retake Remediation and Application Window Planning 11.7 First-Month RBT and Recertification Readiness Plan
9.4 Supervision Documentation, Audit Readiness, and Record Retention
Key Takeaways Explain This Topic AI
Supervision documentation must be maintained for 7 years and be ready for BACB audit.
Audit readiness depends on accurate, timely records of service hours, supervision contacts, participants, dates, formats, and content.
RBTs should never create, backdate, exaggerate, or sign inaccurate supervision records.
Good documentation links supervision to actual service delivery, feedback, client-specific issues, and follow-up tasks.
Last updated: May 2026
Documentation as evidence of supervision
The source brief states that supervision documentation must be maintained for 7 years and be ready for BACB audit. That requirement should shape how an RBT thinks about records from the first month of practice. A supervision log is not a memory aid to fill in later when someone asks. It is evidence that required supervision occurred, with enough detail to show who participated, when it happened, what service delivery it related to, and whether the monthly requirements were met.
If an audit or internal review happens later, vague statements like "we talked often" or "the supervisor was usually around" are not the same as accurate documentation.
The RBT may not be the only person responsible for official records, but the RBT participates in their accuracy. The RBT may sign or acknowledge a supervision form, enter service hours, confirm contact dates, upload documentation, or respond to coordinator questions. Whenever the RBT is asked to confirm a record, the RBT should read it carefully. If the date is wrong, the duration is inflated, the contact type is inaccurate, or a meeting is listed that did not occur, the RBT should report the discrepancy through the chain of command. Correcting records promptly is professional.
Signing inaccurate records because "everyone knows what happened" creates ethical and maintenance risk.
Record element Why it matters RBT quality check
Calendar month Supervision is calculated monthly Does the record match the correct month of service hours?
Service hours The 5% minimum depends on them Do the direct-service totals match scheduling and time records?
Supervision duration Shows the amount of supervision received Is the duration realistic and not rounded in a misleading way?
Contact format Supports face-to-face and individual-meeting requirements Is a group meeting, individual meeting, or observation labeled accurately?
Participants Shows appropriate supervision relationship Was the contact with the correct supervisor or approved person?
Content and feedback Connects supervision to service quality Does the note describe data review, observation, training, feedback, or client-specific issues?
Signatures or acknowledgments Confirms review Did the RBT review before signing or acknowledging?
Scenario: An RBT receives a supervision form on the last day of the month. It lists two face-to-face contacts, but one of the listed dates was a day the RBT was absent. The supervisor may have made a clerical error, but the RBT should not sign the form as written. The correct action is to report the discrepancy, ask for correction, and document the objective fact that the RBT was absent on that date. If pressure continues to sign inaccurate records, the RBT should follow the chain of command and consider BACB reporting obligations as described in current official ethics resources and workplace policy.
Scenario: A Requirements Coordinator asks each RBT to upload supervision records to a shared system. The RBT notices that one observation note says the supervisor reviewed a behavior reduction protocol, but the meeting actually covered only data-entry problems. The RBT should ask for the content note to be corrected. This is not nitpicking. Audit records should reflect what occurred because supervision content demonstrates whether the RBT received feedback relevant to service delivery.
Audit readiness checklist:
Service hours are entered promptly and match the calendar month.
Supervision contacts are documented close to the time they occur.
The record shows at least the required 5% supervision, two face-to-face contacts, and one individual meeting when applicable to the month.
Contacts identify the supervisor or approved participant accurately.
Notes include practical content such as observation, data review, modeling, rehearsal, feedback, protocol questions, or follow-up tasks.
The RBT reviews records before signing or acknowledging them.
Discrepancies are reported immediately and corrected through the official system.
Records are retained according to the 7-year requirement and workplace policy.
Good supervision documentation also improves clinical continuity. Suppose an RBT is struggling with a client's escape-maintained behavior during transitions. A useful supervision note might say that the supervisor observed transition implementation, modeled the visual-timer sequence, had the RBT rehearse the response to refusal, reviewed latency data, and asked the RBT to report back after three sessions. That note is far more useful than "supervision completed." It tells a future reviewer what support occurred and helps the supervisor follow up. It also helps the RBT remember exactly what direction was given.
RBTs should avoid common record risks. Do not wait weeks to reconstruct supervision from memory. Do not count social conversation, scheduling texts, or general staff announcements as clinical supervision unless the current rules and workplace documentation support that classification. Do not copy last month's notes into this month. Do not sign forms with blank sections that someone says they will complete later. Do not store records in a way that violates confidentiality or workplace policy.
If client names or identifiers are included in supervision notes, those records must be protected according to confidentiality rules.
For exam preparation, audit-readiness scenarios often test integrity under pressure. A supervisor may ask the RBT to sign a late form, a coworker may say everyone rounds hours up, or a record may omit a required contact. The best answer is not to accuse people or ignore the problem. The RBT should communicate objectively, seek correction, follow the chain of command, and maintain accurate documentation. The RBT's ethical role includes behaving with integrity, protecting client interests, and representing professional activities accurately.
The 7-year retention requirement also means RBTs should understand where records live. Some organizations keep records centrally. Some require RBTs to retain copies. The RBT should follow the current RBT Handbook and employer policy for exact procedures. If leaving a job, the RBT should ask how supervision records will be accessed later and what the RBT is responsible for keeping. The time to ask is before access to the workplace system ends, not after an audit notice appears.