Functional Behavioral Assessment (FBA) Form

Use this form when a student’s behavior is interfering with learning, safety, or participation and the team needs a structured record before choosing supports. It is especially useful after repeated incidents, when a behavior plan needs updating, or when staff need to compare patterns across settings. It is not a substitute for a full evaluation when a broader special education decision is being made.

The form is usually completed by a school psychologist, behavior specialist, special education case manager, or another trained team member with input from teachers and caregivers. The best results come from combining direct observation with staff reports and any relevant records. If multiple people contribute, the submission should clearly show who entered the final version for audit trail purposes.

Update it whenever the target behavior changes, the suspected function is no longer matching what staff observe, or the intervention is not working as expected. It is also worth revisiting after a major schedule change, placement change, or new trigger appears. A dated follow-up field helps the team know when to review the hypothesis again.

Describe only observable behavior, such as leaving seat, yelling, refusing work, or hitting, rather than labels like "defiant" or "unmotivated." The definition should be specific enough that two staff members would record the same behavior the same way. That makes the baseline data and consequence notes more useful when building a behavior intervention plan.

Common mistakes include writing vague behavior definitions, mixing interpretation with observation, and skipping antecedent details that explain what happened right before the behavior. Another frequent issue is listing too many suspected functions without evidence. The form works best when the team records what was seen, what happened next, and what pattern the evidence supports.

Yes. You can adjust the fields for classroom observations, recess, bus behavior, cafeteria incidents, or home-school collaboration notes. Conditional logic can hide fields that do not apply, which keeps the form shorter and easier to complete. If your district uses different terminology, rename the sections without changing the core structure of antecedent, behavior, consequence, and function.

The form captures the pattern the team needs to identify the likely function of the behavior and choose a replacement behavior and supports that match it. That makes the next step more concrete than an ad hoc incident note. The follow-up date also helps the team review whether the intervention is reducing the target behavior.

When appropriate, yes, because behavior patterns often change across settings and caregiver input can clarify setting events or triggers. The form can be shared in a way that limits unnecessary PII and keeps the focus on the behavior data needed for the team’s decision. If the process includes consent or disclosure language, it should be clear about what information is collected and why.