Functional behavior assessment (FBA): the practical guide

#What an FBA is actually for

An FBA answers one question with surgical precision: why is this behavior happening right now? Without that, every intervention is a guess. Payers, schools, and supervisors all expect one before a behavior plan.

The deliverable is a written report with operational definitions, data, a hypothesized function, and a linked intervention plan. Everything else is scaffolding.

#The three methods, when to use each

Indirect methods (interviews, FAST, QABF) are fast, cheap, and biased. Use them to narrow the search space.

Descriptive methods (ABC recording, scatterplots) get you closer to real-world triggers. They are the default for most cases.

Experimental methods — the functional analysis — are the gold standard but require training, IRB-level care, and safety planning. Reserve for cases where descriptive data is ambiguous or risk is high.

The FBA is the backbone of every good treatment plan. Here is how to run one that actually changes what you do next.

#A tight FBA report outline

Use the same structure every time. Consistency is how you catch what you missed last time.

• Referral question and background
• Operational definitions (topography, onset, offset, examples, non-examples)
• Data collection summary (who, when, how)
• Results with at least one graph per target behavior
• Hypothesized function(s) with supporting evidence
• Proposed intervention plan linked to function
• Limitations and data collection continued under the BIP

#The mistakes that make FBAs useless

Writing "attention-maintained" without data is the #1 issue. Payers and supervisors want the evidence chain, not the conclusion.

Another common miss: not linking each recommendation back to the identified function. If the intervention plan would read the same regardless of function, the FBA didn't do its job.