Functional Behavioral Assessment Basics: Move From “What Happened?” to “What Is the Behavior Doing?”

A functional behavioral assessment is a process for understanding why a behavior occurs so support can address its function rather than merely suppress its appearance. U.S. Department of Education guidance emphasizes function-based thinking as a way to create supportive learning environments. An FBA is not simply a behavior tally, and “the student wants attention” is not a function hypothesis unless data support it.

Define the behavior so observers can agree

Replace “aggressive” with the action being measured: “hits, kicks, or pushes another person with enough force to move the person or produce an audible impact.” Replace “off task” with a definition tied to the task. Include examples and nonexamples when staff disagree. A behavior definition is useful when two adults observing the same event would count roughly the same occurrence.

Collect antecedent-behavior-consequence data without assuming causation

ABC notes capture what happened immediately before, the observable behavior, and what followed. Example: antecedent—teacher presents an independent writing task after lunch; behavior—student tears worksheet and places head on desk; consequence—task is removed for ten minutes and adult talks one-to-one. One event does not prove function, but repeated patterns can reveal conditions associated with behavior.

Look beyond the immediate trigger

Setting events and broader context can matter: sleep disruption reported by family, schedule changes, medication changes when appropriately shared, a substitute teacher, missed breakfast, noisy assemblies, or a difficult peer interaction earlier in the day. Teams should handle private health and family information carefully while recognizing that behavior does not occur in a vacuum.

Possible functions are hypotheses, not labels

Behavior may help a student access attention, a tangible item or activity, sensory stimulation, or escape/avoidance of a demand, among other functional descriptions depending on the assessment framework. The same visible behavior can serve different functions for different students, or multiple functions for one student. Data must drive the hypothesis.

Test the hypothesis against patterns

Suppose task-tearing occurs primarily during extended handwriting, rarely during oral discussion, and is usually followed by work removal. Work samples show the student can explain answers orally but writes slowly and reports hand fatigue. A plausible hypothesis is that tearing produces escape from a high-effort writing demand. That hypothesis points toward different support than an assumption that the behavior is maintained by adult attention.

Measure frequency, duration, latency, or intensity as appropriate

Pick dimensions that match the behavior. A 40-minute shutdown once a week may be more important to capture by duration than by frequency. For task initiation, latency from direction to first action can show improvement. Intensity scales require clear anchors; “mild/moderate/severe” is unreliable unless each level is behaviorally defined.

Ask what skill could meet the same need more safely or efficiently

If the function is escape from an overwhelming writing demand, a replacement response might be requesting a short break, asking to dictate the first sentence, or using an agreed help signal. The support plan should also examine task difficulty and access accommodations. Teaching “sit quietly” does not provide a functional alternative to escape.

Prevention is part of function-based support

Change predictable antecedents where possible: adjust task chunking, clarify visual expectations, build choice, schedule supports before known difficult periods, or ensure communication tools are available. Prevention is not “giving in.” It can remove unnecessary triggers while the student learns the replacement behavior.

Know when the process belongs with the IEP Team

Behavior assessment can have legal and procedural implications, particularly for students with disabilities and disciplinary situations. Follow IDEA, state rules, and district procedures for when an FBA is conducted, who participates, consent or notice requirements where applicable, and how findings are incorporated into the IEP or behavior plan. Classroom data can inform the process, but teachers should not create a quasi-clinical FBA outside required procedures and present it as official.

Judge the FBA by the plan it makes possible

The final question is whether the hypothesis leads to support that can be tested. A strong FBA makes the next steps specific: prevent the triggering condition where appropriate, teach a functionally equivalent response, change adult consequences so the replacement works, and monitor both the target behavior and the new skill.

Test the hypothesis against events that do not produce the behavior

If disruption is believed to escape difficult writing, compare writing periods in which the behavior occurs with equally difficult tasks where it does not. Perhaps adult proximity, task length, peer attention, or the way directions are delivered differs. A good functional hypothesis should explain both occurrence and nonoccurrence reasonably well. If it predicts every behavior in every setting, it is too broad to guide intervention.

Use direct observations alongside interviews and record review; staff recollection alone can overrepresent the most memorable episodes.

Record the consequence immediately after the behavior as carefully as the antecedent. Adult attention, peer reaction, task removal, delay, sensory change, or access to an item can each strengthen a different hypothesis.