9.1 RBT Supervisor and Requirements Coordinator Structures

Supervision as the operating structure

The RBT credential is built around supervised service delivery. That means the RBT is not simply employed by an agency or assigned to a classroom; the RBT must be connected to an appropriate supervision structure in BACB records and in day-to-day practice. The source brief for this guide summarizes the current expectation plainly: active RBT practice requires an RBT Supervisor and/or RBT Requirements Coordinator in BACB records. The names matter, but the functions matter more.

The RBT needs clinical direction, performance feedback, client-specific oversight, documentation systems, and a clear path for asking questions when the written plan, data system, or session context does not answer the problem.

An RBT Supervisor is the person who provides the supervision needed for behavior technician services. The supervisor must meet BACB requirements and must have enough knowledge of the client and service arrangement to provide useful direction. A supervisor who has never reviewed the behavior plan, never observed the RBT's implementation, and cannot answer questions about a client's procedures would not be functioning as meaningful oversight for that client.

The RBT's job is not to judge the supervisor's credential qualifications independently, but the RBT should notice practical warning signs: no one can identify the supervisor, the listed supervisor is unavailable for client questions, supervision contacts are not occurring, or the RBT is being asked to implement procedures without training or feedback.

An RBT Requirements Coordinator is a BACB-recognized role that may support an organization with requirement tracking, documentation, and oversight. In many workplaces, the coordinator helps ensure that RBTs are properly listed, supervision records are complete, renewals are monitored, and organizational processes match BACB requirements. The coordinator role can be very helpful in larger agencies where one person tracks due dates and records across many RBTs. However, a coordinator is not a shortcut around clinical supervision.

If the RBT needs direction about a client's prompting hierarchy, a behavior reduction protocol, a data irregularity, or whether a procedure should pause, the RBT needs the clinically responsible supervisor or the chain of command identified by the organization.

Scenario: Jordan is hired by a clinic and is told that the company has a Requirements Coordinator. On the first day, Jordan receives a schedule with three clients but no clinical supervisor name next to two of them. The correct RBT response is not to assume the coordinator can answer every clinical question. Jordan should ask, before providing behavior technician services, who the RBT Supervisor is for each client, how to contact that person, where supervision will be documented, and what to do if an urgent plan question comes up during a session.

If the workplace cannot identify appropriate supervision, Jordan should not treat the schedule as enough authorization by itself.

Scenario: A supervisor is listed in the BACB account, but a new school client has been added and the RBT has only received a one-page schedule. The RBT should verify client-specific direction before implementing services. Questions might include: Have I been trained on this client's programs? Where is the behavior plan? What data sheets are used? Who observes me with this client? If a teacher asks me to change the procedure, who do I contact? These questions are professional, not resistant. They protect the client, the supervisor, and the RBT.

A useful supervision structure checklist for RBTs is simple:

1. I know the RBT Supervisor and, if applicable, the RBT Requirements Coordinator connected to my services.
2. I know which supervisor has client-specific knowledge for each client I serve.
3. I know how monthly supervision contacts are scheduled and documented.
4. I know the chain of command for clinical questions, data irregularities, safety concerns, confidentiality concerns, and caregiver or stakeholder requests.
5. I know where to find written protocols and where to record objective notes.
6. I know how to report if supervision is missed, records are incomplete, or I am asked to work outside my competence.

This structure also matters for exam preparation because many scenario questions test the same professional discrimination: the RBT implements written procedures, collects objective data, seeks clinical direction in a timely manner, and does not independently design or revise services. When a question describes confusion about supervision, the best response usually involves identifying the correct supervisor relationship, following the chain of command, and documenting objective facts.

The least appropriate responses usually involve improvising clinical decisions, hiding missed supervision, relying on informal coworker advice, or continuing services when the RBT does not have appropriate oversight.

The deeper point is that supervision is not a monthly formality. Good supervision includes observation, modeling, rehearsal, feedback, and problem solving tied to real service delivery. The RBT should come prepared with data questions, examples of unclear responses, notes about variables that may affect progress, and willingness to accept feedback. A supervisor relationship is strongest when the RBT treats it as a practice system: bring accurate information, receive direction, implement the direction, and report back with data. That habit turns BACB maintenance requirements into better client care.