Teaching RBTs to Think Clinically: Training In-the-Moment Decision Making

RBTs Make Clinical Calls in the 80 Percent You Never See

Plans look clean on paper. Sessions do not. Motivation shifts inside a single hour. Problem behavior can climb with no clear warning. A reinforcer (something the learner will work for) can stop working by Thursday. Noise, transitions, and interruptions show up all day long.

Now do the supervision math. Say you supervise 20 percent of a client's direct hours. That leaves 80 percent you never watch. You may be in the building and still be focused on another child. In a home, you may only be reachable by text. A quick message is not the same as coaching.

So the technician cannot pause the session and wait for you. They respond. That happens whether or not you taught them how. Skipping decision training does not stop decisions from happening. It only leaves those decisions untrained. In effect, you hand over clinical judgment with no guardrails on it.

most RBT sessions happen independently, right?

From the talk — Dr. Jessica Osos & Tauren Keels

The Decision Points That Show Up in Almost Every Session

Four moments come up again and again. First, the reinforcer stops working. That can be satiation (the reward has lost its pull). Second, the learner stops engaging, or starts to leave the area. Third, problem behavior begins. It may be familiar, or it may be brand new. Fourth, the setting changes. A sibling comes home. A peer walks in. A different technician runs the session.

The talk followed one case example named Jordan. Jordan is an RBT with about a year of experience. He is reliable and runs programs well, especially when watched. His sessions are heavy on naturalistic teaching (teaching during play and daily routines) and happen in the home. His BCBA supervises about 20 percent of the direct hours.

In one week, the snack that worked last week gets pushed away. Problem behavior rises when demands are folded into play. The house gets louder in the afternoon once siblings are home. None of this is dramatic. That is the point. The case is ordinary on purpose, and so is the drift that follows it.

These are likely happening across an RBT's week just naturally

From the talk — Dr. Jessica Osos & Tauren Keels

Why Checklist-Only Training Breaks Down

Look at a typical fidelity checklist (a list that scores whether the plan was run as written). It may say follow the learner's lead during naturalistic teaching. It may say deliver reinforcement for the right responses. Both are fine items. Neither tells Jordan what to do when the learner checks out completely.

The checklist also cannot sort the cause. Is this a skill the learner does not have yet? Is it low motivation? Is it something in the room? You can often read that from the back of the room. Jordan is inside the moment, not watching it from outside.

There is a second cost. Training only to the script can punish good clinical instincts. Take an intraverbal program (answering a spoken question with words). The target on the data sheet is bird. The child says airplane. The technician says no, try again, birds fly in the sky. The answer was correct and spontaneous.

Over-standardizing carries its own risks. It can de-skill the technician, because rules without reasons do not transfer. It can create automation bias (trusting the tool over what you see). It can create a false sense of safety, since following a protocol is not the same as helping the client. Our ethics code still asks for independent professional judgment.

that just took away an opportunity to reinforce a new response

From the talk — Dr. Jessica Osos & Tauren Keels

What Clinical Thinking Means at the RBT Level

Be precise about the target, or this drifts out of scope fast. Clinical thinking for an RBT is not assessment. It is not diagnosis. It is not treatment design. It is a small set of observable, teachable behaviors. Those behaviors help the technician respond when the session goes sideways.

The first is discrimination (telling two situations apart). Can the technician tell a skill problem from a performance problem? Maybe the response is not in the repertoire yet. Maybe motivation dropped, the effort went up, or ratio strain set in (too much work for too little reward).

The second is noticing patterns instead of single trials. Engagement drops late in the session. Errors rise during one activity. Behavior shifts by setting. The third is adjusting approved variables. Many plans already allow choices or a denser reinforcement schedule. Others allow a high probability request sequence (easy requests before a hard one). The skill is knowing which dials are theirs to turn.

The fourth is escalating well. Strong thinking shows up when a technician sees that a situation is above their authority and says so clearly. That is not the same as freezing. It is also not a play-by-play report of every minute. You are shaping a judgment about what deserves your attention.

the RBT is not expected to determine which it is, but only to recognize that the difference matters

From the talk — Dr. Jessica Osos & Tauren Keels

Compliance Supervision Versus Empowerment Supervision

Compliance-oriented supervision asks one main question. Was every step run correctly? Accuracy matters, so this is not worthless. The trouble starts when accuracy is the only thing that earns praise. Technicians stop reporting. They stop escalating. Feedback starts to feel like a scolding each time, and burnout follows.

Run Jordan through that system. He gets reinforced for running programs quietly and correctly. He hears nothing back when he flags that a reinforcer is fading. So he learns the cheapest safe move.

Empowerment supervision reinforces more than fidelity. It reinforces noticing a pattern, saying it out loud, and making a reasonable in-scope call. That holds even when the call is not the one you would have made. Freezing is the outcome you least want. A discussed decision beats a frozen technician almost every time.

In that system, Jordan reports that engagement drops during longer naturalistic sessions. The BCBA treats that as clinical information, because Jordan is there every day and you are not. He is not changing treatment. He is noticing, reporting, and naming what he tried.

In this structure, Jordan learned the safe option is just follow the plan as written, say as little as possible.

From the talk — Dr. Jessica Osos & Tauren Keels

A Structured Framework for Coaching the Thinking

Give technicians a short set of questions to run in the moment. Do I need to respond at all right now? What does the data suggest? If the trend is going the right way, stay the course. If it is flat or falling, something needs to change. What variables might be driving what I am seeing?

That last question is where antecedent hunting (looking at what happened right before) belongs. Technicians often say the behavior came out of nowhere. Teach them to scan the room instead. There may be no obvious trigger, but that is not the same as no trigger. Ask them to name one hypothesis and report it.

Variability needs limits, too. If airplane counts as correct for what flies in the sky, the technician also needs the edges. A thrown chair does not fly. Teach the range and teach where it stops. That keeps structure in place while still building judgment.

Back to Jordan. He checks recent data, then lists possible variables. Maybe the train set is no longer motivating. Maybe a ten minute teaching block is too long for this learner. Maybe a show in the next room is competing for attention. He reports the pattern and what he tried. He does not redesign the plan.

We know that there is always an antecedent to all behavior.

From the talk — Dr. Jessica Osos & Tauren Keels

Coaching Without Taking Over the Session

Most of us jump in too fast. It feels supportive. It quietly teaches the technician to wait for rescue. Then challenging behavior starts and they sit back and look at you. The session may look great while you are in the room. The data from the days you were gone tell a different story.

One better move is a question in real time. A technician was cycling through reinforcer after reinforcer with an upset three year old. Each new offer just restarted the crying. The supervisor waited, then asked what he was thinking. He said none of this is working. The answer was to switch strategies, not to hand him a script.

There is a related trap. If you always come in and fix it, you can become the person the child listens to. The technician turns into an S-delta (a signal that nothing good is coming). You want the reverse. The technician should be the child's main source of reinforcement and teaching.

When you do step in, do not step in silently. Say what you are thinking as you do it. I think this is a motivation issue, so I am running a five stimulus preference check. I think this is ratio strain, so I am thickening the schedule. Then debrief away from the client, and ask what they observed you do.

All the time that I sit on my hands because my natural inclination is to get up and help.

From the talk — Dr. Jessica Osos & Tauren Keels

Keeping It In Scope: Escalation Rules and Written Reasons

Empowerment without limits turns into overconfidence. This deserves extra care with technicians who are also students in the field. They know more, so they may reach further. Be explicit about which calls are theirs and which are yours. Give the why behind each one, so the rule can transfer to the next case.

Escalation itself has to be trained and made safe. Many of us define escalation well inside behavior plans. We define it poorly for skill programs. A previously mastered skill that no longer holds up is a clear escalation point. Say that out loud, and make clear that asking is not a sign of failure.

Documentation carries a lot of this weight. If your team reads supervision notes, use them. Add a bullet for each program you changed, with the reason and the exact next step you want. Technicians can then find your instructions during prep time. Feedback also has to be received well, so treat clarifying questions as engagement, not defensiveness.

defining for them very clearly when they should be escalating things to you

From the talk — Dr. Jessica Osos & Tauren Keels