RBT Supervision Requirements Explained

Supervision is not a formality attached to the RBT credential. It is a structural part of it: an RBT is by definition a supervised practitioner, and the requirement exists because you implement clinical programs you did not design for people who cannot always advocate for themselves.

Here is how it works, and how to get something out of it beyond a signature.

The core requirements

Two clarifications that resolve most confusion:

The percentage is of your service hours, not your paid hours. Administrative time, drive time, and training hours are generally not counted in the base. Ask your supervisor how your agency calculates it.

Monthly means monthly. Supervision does not roll forward or backward. A month with no supervision contact is a deficient month permanently, even if you receive double the next month.

What actually counts

Counts:

• Direct observation of you with a client, in person or via approved live video
• Individual supervision meetings discussing your clients and performance
• Small-group supervision within the allowed limits
• Structured feedback and skill training tied to your work

Does not count:

• Casual hallway conversations
• Team meetings with no supervision content
• General staff trainings unrelated to your clinical work
• Anything undocumented

If a contact is not documented, it did not happen from a compliance standpoint. This is worth being slightly pedantic about.

Group versus individual

Group supervision is permitted within limits, and it has genuine value — hearing how other technicians handle situations is instructive. But it cannot replace individual contact, and if your entire supervision experience is a weekly group call, raise it. That arrangement is usually out of compliance and always thin on development.

Documentation: keep your own

Your supervisor documents supervision. So should you.

Keep a personal record with:

• Date and duration of each contact
• Format (individual, group, direct observation)
• Which clients were discussed
• What feedback you received
• What you agreed to change

That last column is the valuable one. It is also useful evidence in a performance review, and if you later pursue BCaBA or BCBA fieldwork, the habit of contemporaneous documentation will already be established.

Store copies somewhere you control. Not only in the agency's system — agencies change platforms, and you are the one who needs the records years later.

How to make supervision worth the hour

Most technicians treat supervision as an evaluation to survive. The ones who advance treat it as free consultation from an expert who is contractually obligated to answer their questions.

Come with three items.

One thing that went well and why, one thing you are unsure about, one clinical question about a program you run. Sending them the day before makes the session dramatically more useful.

Ask "why" questions, not just "how" questions.

"How do I run this DTT program?" gets you a procedure. "Why did we choose backward chaining for this task analysis?" gets you the reasoning — and the reasoning is what transfers to the next client.

Ask to be observed on hard things.

The instinct is to schedule observation for your smoothest session. That is a wasted hour. Ask your supervisor to watch the program you struggle with; the feedback is worth far more than a clean report.

Write down the feedback and implement it before the next contact.

Nothing builds a supervisor's confidence faster than seeing their feedback appear in your practice within a week.

Responding to feedback

Responding well to feedback is itself an assessed RBT skill, and the exam tests it. In real life it also determines how much your supervisor invests in you.

The four-part response:

1. Acknowledge it without defending — "Got it, thank you"
2. Ask one clarifying question if you need one
3. Implement it in the next session
4. Report back on how it went

What not to do: explain why you did it your way, cite a different supervisor's instruction, or apologize at length. All three shift the conversation away from the work.

When supervision is not happening

Sometimes the requirement is not being met and it is not your fault. A supervisor leaves, caseloads spike, a month gets away from everyone.

Handle it in this order:

1. Email your supervisor requesting a contact, with dates you are available. Email creates a record.
2. If there is no response within a few days, escalate to a clinical director or manager. This is not going over anyone's head — supervision is a compliance obligation for the agency, not a favor.
3. Document your attempts. Save the emails.
4. Understand the exposure. Providing services without required supervision is a problem for your certification, not only for your employer.

If a pattern persists across months despite escalation, that is meaningful information about the agency. Supervision quality is the single biggest determinant of whether your first years make you good at this work, and it is the right reason to change employers.

What supervision is not

It is not a performance review, though performance is discussed. It is not a punishment for underperforming. And it is not optional once you feel competent — the requirement continues for the entire life of the credential, at every experience level.

The technicians who get the most out of it are the ones who stop thinking of it as oversight and start thinking of it as the only regularly scheduled hour where an expert clinician is focused entirely on making them better.