Writing a Behavior Intervention Plan Staff Can Actually Follow

A behavior intervention plan is only as good as the adult who has to run it in the moment. Most plans are written well enough to pass a file review and then fail at the copier, because the person who actually needs them, the paraprofessional covering the room at 10am, cannot tell from the document what to do when the behavior starts. This guide is about writing a BIP that survives that moment. It is built around one continuous composite student so you can see each layer of a plan in context, and it ends with how to train the plan so every adult runs it the same way.

Why most BIPs fail at the copier

A plan can be technically correct and still useless. The common failure is not bad strategy. It is that the plan was written for a binder and an audit, not for the person standing next to the student when the task gets hard.

Three patterns produce this. The first is length: a fifteen-page plan is a plan no one reads twice, so the adult runs it from a half-remembered meeting instead of from the page. The second is jargon: a plan that says "implement antecedent-based interventions to reduce escape-maintained behavior" tells a behavior analyst something and tells a substitute nothing. The third is the missing response: the plan describes what to do to prevent the behavior but goes quiet on what to do when it happens anyway, which is exactly the moment the adult needs the page.

A BIP that staff can follow reads like instructions, names actions instead of concepts, and fits in a glance. The rest of this guide is how to get there.

It helps to be honest about who the real audience is. The plan will be read by the case manager who wrote it, yes, but it will be run by whoever is in the room when the behavior starts, and that person is often not in the meeting where the plan was made. It is the aide who floats between three rooms, the new hire in their second week, the substitute who got the binder ten minutes ago. Write for that reader and the plan works for everyone. Write for the meeting and it works only for the people who were there, which is the smallest and least relevant group at 10am on a Tuesday.

Meet the composite student

To keep every example concrete, we will use one composite student throughout. Composite means assembled from common patterns, not a real child.

A composite fifth grader we will call Andre. His FBA found that when Andre is given an independent writing task, he tears up the paper and puts his head down, which results in the task being paused while an adult comes over. The function is escape from non-preferred written work, heightened on days that started badly. Every section below is drawn from Andre's plan, so you can see how the layers connect to one function rather than reading four unrelated examples.

The parts that matter, taught as distinct layers

The most useful thing you can do for the adult running the plan is to separate it into layers that do different jobs. A plan that blends prevention, teaching, and response into one paragraph forces the reader to untangle it under pressure. Four layers, each labeled, each short, keep the plan usable.

The four layers are prevention (what you change before the behavior to make it less likely), teaching (the replacement behavior you build so the student has a better option), response (what every adult does both when the replacement happens and when the problem behavior happens), and a safety or crisis line (the small number of steps for the rare moment that crosses into danger). Keeping them distinct is not bureaucracy. It is what lets a reader find the one piece they need in the moment they need it.

The layers also do their work at different times, which is why blending them fails. Prevention happens before the behavior, so it lives in how the task and the room are set up. Teaching happens in calm moments away from the hard situation, so it is a schedule of practice, not a single instruction. Response happens during the behavior, so it has to be short enough to act on in real time. A safety line happens almost never, so it should be small and clearly marked. A reader under pressure does not want to read across all four jobs to find the one that applies right now. Labeling each layer lets them jump straight to the response section when the paper tears, and to the teaching section when they are planning a calm practice block. The structure is doing navigation work, and navigation is exactly what an adult needs when a student is escalating.

Layer one, prevention

Prevention is the antecedent work: the changes you make to the environment, the task, or the schedule so the behavior is less likely to start. For an escape function, prevention usually means making the task more doable, not removing it.

Notice that none of these wait for the behavior. They change the conditions that set it off, which is the quiet work prevention does before a response is ever needed.

Layer two, teaching the replacement

Prevention lowers the odds. Teaching gives the student a better way to get the same thing the problem behavior was getting. This is the layer most plans skip or rush, and skipping it is why so many plans stall. If Andre's behavior gets him out of writing, then the replacement has to get him a break too, only faster and more reliably, or he will go back to what worked.

The replacement has to be functionally equivalent, meaning it gets the student the same outcome, and it has to be lower effort than the problem behavior. A break request that takes longer or works less reliably than tearing up the paper will lose every time.

Layer three, response

The response layer is the one the adult reaches for in the moment, so it has to cover both directions: what to do when the replacement happens, and what to do when the problem behavior happens anyway. These are not the same and the plan should not blur them.

The reason the response layer honors the replacement instantly and keeps the task present after the problem behavior is the same reason: both protect the function logic. Honoring the break makes the good option pay off. Keeping the task present means the old option no longer pays off. Reverse either one and the plan teaches the wrong lesson.

Layer four, the safety or crisis line

Most plans should have a short safety line even when the behavior is not dangerous, because the rare bad day is exactly when adults improvise. Keep it to a few steps and a name to call. If the behavior is not a safety concern, say so, so no one escalates a torn worksheet into a crisis response.

A safety line that names what is not authorized is as valuable as one that names what is. It keeps a minor behavior from being met with a major response by an adult who does not know the student.

The plain-language test

Once the four layers are drafted, run every line through one test: would the adult who has never met this student know exactly what to do? Jargon fails that test. The fix is to write the action, not the concept. Here are common phrasings from real plans next to what the staff member actually does.

The left column is not wrong. It is just written for a different reader. The plan that the paraprofessional runs should live in the right column, with the technical language moved to an appendix if it needs to exist at all.

The two-page rule and what belongs in appendices

A working BIP should fit on two pages: the four layers, the function in one line, and the data plan. Everything else is reference material that belongs behind the working plan, not inside it.

Push the FBA summary, the full data history, the consent and meeting notes, the detailed reinforcement schedules, and the legal procedural language into appendices. They matter, and they should exist, but they are not what the adult reads at 10am. The two-page front matter is the plan. The appendices are the file. Separating them is the single change that does the most to make a plan followable, because it lets the working document stay short without losing the documentation a review needs.

A useful check: if your two pages do not fit on a clipboard or a single laminated card, they are not yet two pages. Cut until they do.

There is a second reason the two-page rule matters, beyond readability. A short working plan is easier to keep accurate. Long plans accumulate stale instructions, because no one wants to reread fifteen pages to update one step, so the document slowly drifts from what the team actually does. A two-page plan can be reread in a minute and corrected on the spot, which means it stays true to practice. The appendices can hold the history that should not change. The front matter holds the practice, which should change whenever the team learns something, and stay short enough that updating it is never a chore.

A common worry is that a short plan looks thin to a reviewer or a parent. It does not, if the appendices carry the depth. A reviewer reading the file sees the full FBA, the data, and the procedural language behind the working plan. A parent reading the two pages sees a plan they can understand and reinforce at home, which is worth far more than a plan they cannot finish. Short is not the same as incomplete. Short means the part that has to be run is separated from the part that has to be filed.

Training the plan in 15 minutes

A plan that lives only in the document gets run differently by every adult. A 15-minute training before the plan goes live makes every adult run it the same way. This is short on purpose, because a training that needs an hour will not happen for the substitute or the new aide.

Fifteen minutes spent here saves the weeks a plan loses when half the adults run it one way and half run it another. Run the same training with any substitute or new staff member before they cover the room.

If it helps to keep the daily logging consistent across every adult who runs the plan, a simple printable slip for marking break requests and problem-behavior instances keeps the data clean enough to review later.

A quick audit before the plan goes live

Before you hand the plan out, run it past a short audit. These are the checks that catch the problems that otherwise surface three weeks in, after the plan has already been delivered inconsistently. A few minutes here saves a wasted month.

A plan that answers yes to all six is a plan that can be run. A plan that answers no to even one of them has a known failure point you can fix before it costs you a month of muddy data.

Review cadence and who owns it

A plan without a review date is a plan that drifts. Set the cadence when you finish the plan, and name an owner so review is someone's job rather than everyone's good intention.

A practical cadence: check fidelity weekly for the first month using a short five-item check, review the behavior data every four to six weeks, and hold a fuller team review each grading period or sooner if the data calls for it. The case manager or behavior lead owns the calendar and the data, the classroom teacher owns the daily logging, and the team owns the decision to keep, change, or fade the plan. Tie the review to the function the FBA named, so the question at each review is always whether the plan is still addressing the right thing, not just whether the numbers moved.

When you finish writing, do one last pass for the reader who matters most. Hand the two pages to the paraprofessional who will run the plan and ask them to tell you, line by line, what they would do. The lines they hesitate on are the lines to rewrite. A BIP staff can actually follow is not the one that reads best in a meeting. It is the one that holds up at the copier at 10am.