6.7 Behavior Reduction Case Lab

Integrated session reasoning

Behavior reduction sessions rarely present one clean concept at a time. A client may have an escape-maintained behavior, an NCR schedule for attention, an FCT program for breaks, an extinction component for dropping materials, a response cost for a different behavior, and a crisis protocol for elopement. The RBT must know which procedure applies to which behavior, when the procedure begins and ends, what data are required, and when to call the supervisor. This case lab uses integrated scenarios to practice RBT-level judgment without stepping into independent treatment design.

Case background: Jordan is a nine-year-old receiving supervised ABA services in an after-school clinic. The supervisor's assessment summary says table refusal is most often followed by escape from writing tasks, grabbing art supplies is followed by access to materials, and loud comments during group activities are often followed by peer and adult attention. Jordan also has a crisis protocol for elopement past the clinic hallway door. The RBT has been trained on the behavior plan, data sheet, FCT prompts, and crisis communication chain.

Scenario one: writing starts, and Jordan says no, pushes the paper away, and looks toward the break card. The plan says to present one sentence, prompt the break card after five seconds of refusal, provide a 30-second break for card use, and return to the same sentence after the break. The RBT should not remove writing for the whole session or require five sentences to make up for refusal. The RBT prompts the card as written, provides the break after the communication response, returns to the one-sentence demand, and records refusal duration, prompt level, break card use, and task completion.

Scenario two: Jordan grabs markers from a peer. The plan says to block access to the markers if safe and trained, prompt Jordan to say marker please, and provide a marker for 20 seconds after the request. It also says not to provide marker access following grabbing alone. The RBT should implement the DRA and tangible extinction exactly. If the peer hands over the marker after grabbing, the RBT should not blame the peer. The RBT records that access occurred from a peer after target behavior and reports the fidelity barrier to the supervisor.

Scenario three: during group, Jordan makes loud jokes when the RBT is helping another client. The plan includes NCR attention every two minutes and DRI for raising a hand before commenting. The RBT realizes the last scheduled attention delivery was missed during cleanup. The best action is to resume the NCR schedule, reinforce hand raising when it occurs, and record the missed delivery. The RBT should not deliver extra attention immediately after the loud joke unless the plan says to respond that way. Missed antecedent procedures are important data, not facts to hide.

Scenario four: Jordan runs past the hallway door toward the lobby. The crisis protocol activation criterion is met. At that moment, the RBT stops ordinary teaching procedures and follows the elopement protocol: call the site lead, maintain visual contact, keep other clients safe according to site procedures, and use only trained safety steps. The RBT does not continue the extinction procedure for table refusal, does not lecture Jordan in the lobby, and does not invent a new loss of privileges. Afterward, the RBT documents the event and participates in supervisor debriefing.

Integrated decision workflow:

1. Identify the behavior by its written definition, not by emotion or staff frustration.
2. Match the behavior to the plan component already assigned by the supervisor.
3. Implement antecedent, teaching, reinforcement, extinction, punishment, or crisis steps exactly as written.
4. If two procedures appear to apply, follow the hierarchy in the plan and prioritize safety.
5. Record target behavior, replacement behavior, prompts, reinforcement, consequences, and fidelity barriers.
6. Preserve dignity by using neutral language and limiting unnecessary audience attention.
7. Escalate when behavior changes, safety risk increases, data are irregular, or the plan is unclear.
8. Wait for supervisor direction before changing criteria, schedules, consequences, or restrictions.

A strong RBT note after this session might say: Writing refusal occurred twice during one-sentence demands; Jordan used the break card once independently and once with a gestural prompt. Grabbing markers occurred once; RBT blocked access and prompted request, but peer provided a marker before staff could redirect. Loud comments occurred four times during group; one scheduled NCR attention delivery was missed during cleanup. Elopement criterion was met at 4:18 p.m.; site lead was called, visual contact maintained, and Jordan returned to the clinic room after two minutes.

This note gives the supervisor actionable information without blaming, interpreting motives, or hiding implementation barriers.

The exam-relevant lesson is that behavior reduction is not a menu of tricks. Each procedure has a function, timing, safety condition, and data requirement. RBTs show competence by knowing the difference between observing a possible function and declaring a function, between preventing behavior and reinforcing behavior after it occurs, between extinction and ignoring, between punishment and personal discipline, and between a behavior plan and a crisis protocol. When uncertain, the RBT protects safety, follows the chain of command, and gives the supervisor clean data.