School BCBA Systems Letter

Research that leads to a practical next step

Communication before compliance

The trap

A student is already escalating or avoiding the room. The team writes a plan that stacks demands: token board, visual schedule, three easy tasks, then a reinforcer.

That plan looks organized. It is still a demand stack, not a skill plan. The student already has a fast way out of the hard moment. The plan asks for more work before it teaches a low-effort request that would work faster than the behavior does.

The better question

What will the student say instead, and will saying it work faster than the behavior does?

That question forces the first move. Teach a low-effort request for a break, for help, or for a preferred reset. Honor it reliably while the response is still easy. Increase demands and thin the schedule later. Compliance is a later layer. Communication is the first one.

The research points to two checks that keep that order intact.

Prompt the request when the student is already indicating

Frampton, Axe, Davis, Meleshkevich, and Li reviewed indicating responses in mand training and offered a definition plus practice recommendations. They define an indicating response as a response that identifies or rejects a reinforcer (for example, gesturing toward, looking at, approaching, touching, or pushing away the item), is evoked by a motivating operation, and is maintained by specific reinforcement from another person. In short, it is an observable sign that motivation is in effect.

Their core recommendation is simple: observe an indicating response before you prompt the request. If a student points to the truck, run the request for the truck. If the student does not indicate for the blocks, do not prompt "blocks" as another demand. Wait, or arrange motivation for something the student is already indicating. Prompting a request when motivation is not in effect can produce a compliance response instead of a request that will work when the moment is actually hard.

For a school BCBA, that is the first check on a demand-stack plan. A token board and three easy tasks asks the student to work before anyone has confirmed what the student is trying to get or get away from. Watch for one indicating response, prompt the low-effort request then, and honor it. Use the indicating response as the start of the teaching trial, not as a reason to add more demands.

The limitation matters because this is a tutorial that organizes existing literature rather than a new classroom experiment, indicating responses can be observed only when the relevant item or condition is present, and later work is still needed to fade that presence so the student can request when the item is not in view. Do not treat every reach or protest as a finished communication plan. Treat the paper as a reason to stop prompting requests on the adult's schedule and start prompting them when the student has already shown motivation.

Frampton, S. E., Axe, J. B., Davis, C. R., Meleshkevich, O., & Li, M.-H. (2024). A tutorial on indicating responses and their importance in mand training. Behavior Analysis in Practice, 17(4), 1238-1249. https://doi.org/10.1007/s40617-024-00965-7

Read the full-text article on PubMed Central

After the request works, thin it with clear signals

Greer, Fisher, Saini, Owen, and Jones summarized 25 consecutive applications of functional communication training schedule thinning across 20 cases. After the communication response was established, they thinned reinforcement using signaled compound schedules (multiple schedules, response restriction, or chained schedules) so the learner could tell when a request would and would not produce reinforcement.

Across applications, destructive behavior fell by a mean of 96% from baseline after thinning. Discriminated communication stayed high (mean 92%). Reinforcement deliveries dropped by a mean of 82% from early FCT sessions to the final sessions. In 88% of applications, learners tolerated periods of at least four minutes with reinforcement unavailable without large increases in destructive behavior. Supplemental procedures were needed in only 28% of applications.

For a school BCBA, that is the second layer, not the first. Once the student uses the request and adults honor it, make the plan livable for a real classroom: signal when a break request will work, signal when it will not, and gradually lengthen the periods between honored requests. Thinning is how communication stays available without requiring an adult to deliver a reset after every ask all day. It is also how work requirements enter the plan without replacing the skill you just taught.

The limitation matters because these applications came from a specialized clinical setting, not ordinary classrooms, and implementers were clinical staff rather than teachers or paraprofessionals. Do not copy a four-minute terminal interval into every BIP. Use the study as a reason to thin only after the request is fluent, to pair thinning with clear signals, and to judge success by whether communication stays discriminated while the day becomes workable for staff.

Greer, B. D., Fisher, W. W., Saini, V., Owen, T. M., & Jones, J. K. (2016). Functional communication training during reinforcement schedule thinning: An analysis of 25 applications. Journal of Applied Behavior Analysis, 49(1), 105-121. https://doi.org/10.1002/jaba.265

Read the full-text article on PubMed Central

What to do this week

1. Pick one student whose current plan stacks demands during escalation (token board, three tasks, then a reinforcer). Write the replacement request the student will use instead, in the lowest-effort form they can already approximate.
2. Make that request pay: define the preferred reset, deliver it immediately when the student uses the request, and check that the reset is faster and better than what still follows problem behavior.
3. Prompt the request only after you see an indicating response (a reach, look, approach, or reject) for several days before you add work requirements, delay, or denial.
4. Only after the request is consistent, add a simple signal for when the request will and will not be honored, then lengthen the wait in small steps while you keep honoring discriminated communication.

Build the system around the decision

The goal is not to remove every demand from the day. The goal is to stop asking for compliance before the student has a request that works, then thin that request until the plan fits an ordinary classroom.

That is the work inside the School BCBA Transformation Program: turning escalation moments into teachable communication first, then building the systems that keep the plan usable when the schedule has to thin. The January 2027 cohort is an intensive, live, small-cohort six-week program designed to help you develop the systems you are missing. Learn about the School BCBA Transformation Program

Until next week,

Rob Spain, BCBA, IBA