School-Based Behavior Support: From Whack-a-Mole to a System

“The loudest classroom gets the help.”

If you work in school-based behavior support, you may recognize the pattern. The next student added to the caseload is not always the student with the greatest need. It may be the concern that arrived in an urgent email, the teacher who caught you in the hallway, or the situation an administrator called about that morning.

Some situations truly are urgent and need an immediate safety response. But when every concern enters the system as an emergency, urgency can start making every decision for us. The result is a behavior team that spends the day reacting, teachers who are unsure what to try, and cases that stay open long after the next step has become unclear.

The answer is not simply to work faster or take on more. A sustainable school-based behavior support system helps teams match the level of support to the level of need—and makes it easier for cases to move forward.

A behavior support system should do four things

A useful system does not need to be complicated. At minimum, it should give staff and behavior teams a shared way to:

Receive concerns. Staff know where and how to bring a concern forward.
Make decisions. The team has shared ways to decide what is urgent, what needs consultation, what needs more information, and what may warrant intensive support.
Manage cases. Cases have a status, a next step, a person responsible, and a date to review progress.
Build teacher capacity. Teachers receive practical strategies and coaching they can use when the behavior specialist is not in the room.

These parts work together. A referral form without follow-up does not create a system. A caseload tracker without clear decision rules does not create a system either. The tools matter, but the team’s routine for using them matters more.

The Center on PBIS’s Tier 3 District-Level Systems Guide offers more detail on the team structures, coaching, and data systems that support intensive behavior services.

Start with observable behavior, not labels

Referrals often begin with shorthand: “defiant,” “disrespectful,” “manipulative,” or “refusing.” Those words may describe how a situation feels to an adult, but they do not tell the team exactly what the student did or what support might help.

Ask questions that help everyone look at the same thing: What did the student do? When and where did it happen? How often or how long did it last? What was happening just before? What happened afterward?

The goal is not to make teachers write a dissertation. It is to describe behavior in a way another adult could observe or recognize. That gives the team a more useful starting point for classroom support, data collection, and decision-making.

More Training & Tools for School-Based Behavior Support

Agree on what makes a concern significant

“Significant” should not mean annoying, inconvenient, different from peers, or difficult during one hard day. Teams need shared criteria so decisions do not depend on who received the referral or how urgently it was worded.

A concern may warrant more support when there is a safety risk, substantial loss of access to instruction, frequent or escalating behavior, a meaningful impact on the student or others, or a need for individualized assessment and coordinated support.

Significant does not always mean dramatic. A quiet student who spends much of the day disengaged, cannot communicate important needs, or is unable to access instruction may need support just as much as a student whose needs are more visible.

Use classroom supports as a starting point for non-urgent concerns

For many non-urgent concerns, the first step can be a practical classroom support pathway rather than automatic intensive behavior-team involvement. This is one way an MTSS approach can help teams match support to need.

That does not mean telling a teacher, “Good luck—figure it out on your own.” It means offering usable first steps, such as visual supports, choices, precorrection, reinforcement, task adjustments, environmental changes, communication supports, or coaching.

The best classroom strategy is one a teacher can use during a real school day. If a support is too complicated, takes too long to prepare, or does not fit the routine, it is unlikely to be implemented consistently. When teachers have accessible strategies and a clear way to ask for help, some concerns improve before they become intensive cases. When they do not, the team has better information about what has already been tried.

For more ideas, see these 10 proactive behavior management tips for teachers.

Collect useful information without asking for perfect data

When a concern continues, a short period of simple ABC data can help the teacher and behavior team notice patterns: when the behavior happens, where it happens, what tends to come before it, what follows it, and how often or how long it occurs.

The goal is not to turn every teacher into a perfect data collector. The goal is useful information. In my experience, coaching a teacher to collect basic data sometimes helps the teacher spot a pattern or identify a classroom adjustment without needing a more intensive case. Sometimes the concern improves enough that the teacher can manage it with the supports already in place. Both are useful outcomes.

Keep the process realistic. If data collection is too complicated to fit into classroom life, the system needs to change. And a routine data-collection process must never delay an immediate safety response. Safety concerns follow the school or district’s urgent-response procedures; the referral system helps the team decide what sustained support is needed afterward.

My guide to behavior data collection in special education walks through ABC data and other classroom measurement options.

Make referrals a starting point for a conversation

When a concern needs team review, a behavior support request can bring together the information needed to begin thoughtfully: a clear description of the concern, basic data if available, supports already tried, relevant context, and the teacher’s question or request.

The form should not become a gate that blocks help because every box is not perfect. It should help the team begin with more than “This student is having behaviors. Please come.” A useful referral moves the conversation away from assumptions and toward problem-solving.

It can also make the process more equitable. The student whose teacher writes the most persuasive email should not automatically receive more support than the student whose teacher is new, overwhelmed, or less comfortable asking for help.

Normalize “not yet”—and make the next step clear

Not every referral needs to become an active, intensive behavior case. Some students may need classroom resources, a consultation, a check-in, short-term coaching, or another team member’s perspective. Others may need assessment, a behavior plan, or more coordinated support.

One useful phrase a team can normalize is “not yet.” It does not mean “no support.” It means the team needs more information before making an intensive decision. Perhaps the team needs an observation, a clearer picture across settings, or time to see whether a strategy is being used consistently.

But “not yet” needs a follow-up plan. Decide who will do what, what support will happen in the meantime, and when the team will review the concern again. Without those details, “not yet” can become a polite way for a concern to disappear.

Give every case a next step—and a way forward

Cases should move through a lifecycle. A case may begin with a referral, move into consultation or monitoring, require assessment or active support, receive regular review, and eventually fade or close when appropriate.

Sometimes a student needs more support again later. That is okay. But cases should not stay open forever simply because nobody has built a routine for reviewing them. If a caseload only grows, it can start to feel like a waiting room with no exit.

Before a team finishes a decision meeting, identify who owns the next step, when it will happen, what information will guide the next review, and what progress might allow support to fade, shift, or close. A scheduled follow-up protects the student from getting lost in the shuffle—and saves the team from recreating the plan every time someone asks for an update.

Build teacher capacity instead of building dependence

Teacher coaching is one of the ways behavior teams can extend their impact. A teacher does not need to become a BCBA. They need a few practical supports they can use consistently, a way to notice when something is not working, and a clear path for asking for more help.

The goal is not to make the behavior specialist unnecessary. It is to make the classroom less dependent on the specialist being present for every hard moment. When teachers can use effective supports with confidence, students have more consistent access to help throughout the day—and the behavior team can focus its time where it is most needed.

Measure whether the system is working

Behavior teams are usually good at measuring student behavior. It can also help to look at how the support system itself is working. For example:

How long do referrals wait for review?
How many concerns are supported through consultation or coaching?
How many become active cases?
How long do active cases stay open?
How often are cases reviewed, faded, or closed?
Where do referrals or follow-ups tend to get stuck?

These questions are not about proving that a team is busy. They help the team see where the process needs attention. Maybe referrals wait too long, cases rarely close, the same classroom keeps asking for help, or there is no protected time for follow-up. If we do not look at the system, it is hard to improve it.

You do not need to rebuild everything at once. Choose one bottleneck and make that part of the process clearer or easier to use. Improving one stuck point can create more breathing room for the rest of the team.

This flowchart is one example of how a behavior support request process might work. Use it as a starting point, then adapt the steps and decision points to fit your school or district. You’ll find this example and other practical tools in my Behavior Team Case Management resource.

From whack-a-mole to a working system

School teams will always have urgent situations, unpredictable days, staffing changes, and students who need intensive support. A system will not eliminate those realities. It can keep them from determining the entire service model.

Good referrals need useful information, not perfect paperwork. Not every concern needs the same level of service. Teachers deserve practical support and coaching. Cases need regular review and a path forward.

The goal is not to do more for the sake of doing more. It is to help the right students, at the right time, with the right level of support—while building capacity in the people around them.