Behavior goals are some of the hardest to write well, because the instinct is to target what you want the student to stop doing. But "will stop calling out" tells a student nothing about what to do instead, and it gives you no skill to teach. Strong behavior goals teach a replacement behavior, define it in observable terms, and — critically — start from the function a Functional Behavior Assessment identified.
Start with function, not frequency
A Functional Behavior Assessment (FBA) answers one question: what is the behavior getting the student? Most behavior serves one of a few functions — escape (getting out of a task), attention, access to something tangible, or sensory input. The function determines the goal, because the replacement behavior has to meet the same need in an acceptable way.
If a student disrupts class to escape hard work, the replacement is a break-request or help-request — not "will stay quiet." A goal that ignores function asks the student to give up the only strategy that works for them without offering a substitute. It will fail.
Define the behavior so anyone could count it
A behavior goal is only measurable if two different observers would record the same thing. "Will be respectful" fails this test; "respectful" means different things to different adults. Define the target behavior in observable, countable terms:
- Weak: Eli will show self-control.
- Strong: Eli will begin an assigned task within 1 minute of the direction.
The strong version names something you can see and time. If you can't count it, you can't graph it, and you can't report on it honestly.
Teach the replacement behavior
The heart of a behavior goal is the replacement behavior — the acceptable thing the student will do to meet the same function. Examples by function:
- Escape: will request a break using a break card in 4 of 5 observed opportunities.
- Attention: will raise a hand and wait to be called on in 8 of 10 opportunities.
- Tangible: will use a first-then negotiation to request a preferred item in 4 of 5 opportunities.
A full example: By the end of the IEP year, when presented with a non-preferred task, Eli will request a break using his break card instead of leaving the room, in 4 of 5 observed opportunities across 2 consecutive weeks, as measured by daily frequency data.
Decide how you'll collect the data
Behavior data is the part teams most often hand-wave. Pick a method you can actually sustain:
- Frequency — count occurrences (good for discrete behaviors like call-outs or break requests).