Functional Behavior Assessment

What an FBA is, the para's role in data, and how the output drives the BIP

For paraprofessionals participating in or implementing the results of FBAs

Why this brief

Functional Behavior Assessment — FBA — is the structured process behind every legitimate Behavior Intervention Plan. It's how a team figures out what a behavior is doing for the student before deciding what to do about it. Brief 05.01 covers function-based thinking; brief 05.03 covers reading and running a BIP; this one bridges the two: how does the team actually conduct an FBA, what does the para contribute, what does the FBA output look like, and how do its conclusions become the plan?

Paras are usually the most important data source for an FBA — you're the person closest to the student across the day. The quality of an FBA depends heavily on the quality of the data the para provides. Knowing the framework helps you collect data that's actually useful, not just lots of data.

| |

| :-: |

| FBA principleBehavior is communication. Even behaviors that look chaotic, dangerous, or pointless are usually doing something for the student — getting attention, escaping a demand, accessing a tangible, or producing a sensory experience. The FBA's job is to find that something so the BIP can address it. |

Who this brief is for

Paras participating in FBA data collection (most behavior-support paras)

Paras implementing BIPs that came out of FBAs

Supervising teachers and BCBAs running FBAs and coordinating with paras

Anyone trying to make sense of a behavior they don't understand yet

What an FBA is

Definition

A Functional Behavior Assessment is a systematic process to identify the function (purpose) of a target behavior and the conditions under which it occurs. The output is a hypothesis about why the behavior happens, which then guides intervention.

When required

FBAs are required by IDEA in specific situations:

When a student's behavior is interfering with their learning or others' learning and the IEP team decides to address it

Before certain disciplinary removals (when removal is for behavior that is or may be a manifestation of disability — see brief 02.08 planned)

When a BIP needs to be developed or substantially revised

As part of consideration of placement changes related to behavior

FBAs are also done proactively in many schools whenever a behavior is a significant concern, regardless of legal requirement.

Who conducts FBAs

Varies by district. Common configurations:

School psychologist or school behavior specialist

Board Certified Behavior Analyst (BCBA) — when the district employs or contracts one

Special education teacher with training

Outside consultant for complex cases

Paras don't conduct FBAs — but they are crucial data sources. Brief 13.06 covers scope of practice; FBA design is outside scope, FBA participation is squarely inside it.

The FBA process

Real FBAs vary in formality and depth depending on the case and the assessor's training. A typical sequence:

Step 1: Define the target behavior

The team operationally defines the behavior — what specifically is being measured. This is critical and surprisingly hard. "Disruption" is not operational. "Speaking out without raising hand, defined as audible verbal output when not called on, lasting 1+ second" is.

Common patterns: define the behavior so two observers would record the same thing; specify what counts and what doesn't; include severity if relevant.

Step 2: Indirect assessment

Interview teachers, paras, family

Review records — incident reports, IEP, prior data

Use formal questionnaires (FAST, MAS, QABF) — common formal tools

Gather hypotheses — what does the team currently think is happening?

Step 3: Direct observation

This is where paras are most often involved. The assessor or team conducts:

ABC narrative recording (see brief 06.04) — antecedent, behavior, consequence for each occurrence

Scatter plots — when the behavior occurs across the day/week to detect patterns

Frequency or duration counts (see brief 06.01) — getting a baseline rate

Setting events identification — what conditions make the behavior more likely (lack of sleep, certain peers, low blood sugar, transitions)

Step 4: Functional analysis (sometimes)

In more complex cases, especially with severe behavior, the assessor may conduct a functional analysis — systematically presenting different conditions (attention, escape, tangible, alone) and observing which conditions trigger the behavior. This is technical work conducted by trained behavior analysts. Paras may assist with logistics (running materials, recording data) but don't design or interpret it.

Step 5: Hypothesis development

The team synthesizes the data into a function-based hypothesis. A common format:

"When \[setting events / antecedents\], the student \[behavior\], in order to \[function\], maintained by \[consequence\]."

Example: "When given a multi-step writing task, especially after lunch, Marcus rips up his paper and crawls under the desk, in order to escape the writing demand, maintained by removal of the work."

Step 6: BIP development

The hypothesis informs the Behavior Intervention Plan. See brief 05.03. The connection is direct: the BIP is the team's response to what the FBA found.

The four functions — quick recap

Brief 05.01 covers function-based thinking in depth. The four functions are typically labeled:

| Function | What the student is getting | Common signs |

| :-: | :-: | :-: |

| Attention (social positive reinforcement) | Adult or peer attention | Behavior happens when others are nearby; stops when ignored (sometimes); often escalates if attention is initially withheld |

| Escape / avoidance (negative reinforcement) | Removal from a demand or unpleasant situation | Behavior happens during demands; stops when the demand is removed; tied to specific tasks or settings |

| Tangible / access (social positive reinforcement) | Access to an item or activity | Behavior happens when access is denied or restricted; stops when the item/activity is provided |

| Sensory / automatic (automatic reinforcement) | A specific sensory experience | Behavior happens regardless of who's around; doesn't stop based on social response; often happens during downtime |

Multiply-maintained behaviors

Many behaviors serve more than one function — sometimes attention, sometimes escape, sometimes both at the same time. A good FBA captures this complexity. "He yells out for attention from peers AND to escape difficult tasks" is a real and common finding.

Why function matters

Two students might do the same thing — say, throwing a chair — for entirely different reasons. The FBA-driven plan looks different in each case:

Throwing chair to escape work → reduce or modify the demand, teach functional communication for breaks

Throwing chair for attention → reduce attention to the throwing, increase attention to alternative behaviors

Throwing chair to access an item → teach asking for the item, use a schedule of access

Throwing chair for sensory feedback → provide sensory alternatives, environmental modifications

Without function, interventions are guesswork. With function, they're targeted.

The para's data role

Most of what an FBA team needs comes from the people who watch the student most closely — typically paras. What you contribute and how to contribute it well:

ABC narrative data (brief 06.04)

Most useful single tool. For each occurrence of the target behavior, record:

Antecedent: what was happening immediately before (what task, what demand, what said by whom, what setting)

Behavior: specifically what the student did

Consequence: what happened next (what the adults did, what the peers did, what the student got or escaped)

Quality matters more than quantity. Five well-written ABC entries beat fifty vague ones.

Scatter plot data

Often the FBA assessor will give you a scatter plot — a grid with time blocks across the day and dates. You mark when the behavior occurred. Patterns emerge: "Always around 11:15. Almost never on Wednesdays. Common during math but rare during reading." These patterns guide hypotheses.

Frequency or duration counts

Establishes baseline before intervention

Helps confirm changes after intervention

Track on agreed schedules — every period, certain time blocks, etc.

Setting events

Conditions that aren't immediate antecedents but make the behavior more likely. Pay attention to and document:

Sleep, breakfast, medication compliance

Mood at arrival, at handoffs

What happened at home (when family shares)

Schedule changes, substitutes, special events

Sensory environment (loud, bright, crowded)

Interview information

If the FBA assessor interviews you, prepare:

Specifics, not generalities — "On Tuesday at 11:15 he" not "he often"

Honest information about what doesn't work — interventions that haven't helped

Your hypotheses — what you think is happening

Patterns you've noticed that might not be in formal data

| |

| :-: |

| Be honest about adult responsesFBA data should accurately reflect what adults do in response to the behavior. If the student gets out of work when they melt down, even if that's not the intent, the data should reflect that. The FBA can't help if it doesn't capture reality. |

Good FBA data versus bad FBA data

Good FBA data

Operational definitions — clear, specific, observable

Recorded in real time as behavior occurs

Specific antecedents and consequences, not just "he got upset"

Notes setting events when relevant

Captures the full sequence including what adults did

Honest about what reinforces the behavior, even when adult response was unintended

Covers different times of day, settings, and people

Sufficient quantity — usually 1–2 weeks minimum, sometimes longer

Bad FBA data

Vague — "disrupted again," "acting out"

Filled in from memory at end of day

Only covers one setting (e.g., only what the para sees, not what other adults see)

Only the bad days — selection bias

Inconsistent across observers — different definitions in use

Editorializing about character ("he was being defiant") instead of describing behavior

Skips the consequence — what happened after

Too much editorializing about probable function — that's the assessor's job

What an FBA report looks like

A typical FBA written report includes:

Demographic and educational context

Reason for referral

Operational definition of target behavior(s)

Methods used (interviews, observations, formal tools)

Summary of findings

Hypothesis statement(s)

Recommended intervention strategies (often summarized; the BIP develops them)

Some FBAs are more detailed; some are more brief. The hypothesis statement is the heart of it.

Reading the hypothesis

A clear hypothesis statement gives you the four pieces:

Setting events: what makes it more likely

Antecedents: what immediately triggers it

Behavior: what specifically the student does

Function: what's reinforcing it

Example: "When transitioning from a preferred activity to a non-preferred academic task, particularly after morning recess, Mariana drops to the floor and refuses to move, in order to delay or avoid the academic task, maintained by adult attempts to coax her back and the resulting reduction in task time."

Reading multiple hypotheses

Some FBAs identify multiple functions. The BIP then needs to address each. Don't be surprised if a behavior turns out to serve more than one purpose — that's common and not a flaw in the FBA.

Limits of FBAs

FBAs are hypotheses, not certainty

Even a well-conducted FBA produces a probable explanation, not a proven one. The BIP is a test of the hypothesis. If the BIP based on the FBA hypothesis isn't working after a fair trial, the team should revisit the FBA — maybe the function is something else, maybe there are multiple functions, maybe the conditions have changed.

FBAs can miss things

Setting events that happen outside school (sleep, family stress, hunger)

Medical conditions causing or contributing to behavior

Trauma history that's not visible in current observations

Sensory conditions that the team isn't trained to see

Slow-developing changes that need longer observation

Communication needs underlying the behavior

FBAs can be biased

Assessors bring assumptions; data should counterbalance them

Cultural mismatch between assessor and family/student can color interpretation

Stigma about certain disabilities can shape what's seen as the problem

Boys are over-referred for FBAs compared to girls; students of color over-referred compared to peers — equity issues to be aware of

FBAs can be rushed

Districts under pressure sometimes do FBAs in 1–2 days that should take 2 weeks. A rushed FBA produces unreliable hypotheses, which produce unreliable BIPs. If the FBA seems too fast, that's worth flagging — though usually through the supervising teacher, not directly.

Consent and ethics

FBAs in schools generally require:

Parent notice (always)

Parent consent (typically yes, especially for formal FBAs tied to BIPs and IEPs; varies by state)

Functional analysis (the experimental version) usually requires more explicit consent because it deliberately sets conditions to evoke the behavior

Paras don't manage consent — that's the case manager and admin. But know that FBAs aren't done in secret; families have the right to be informed and involved, and you may be asked to brief families about what data is being collected and why (refer them to the case manager for the substantive answers).

Ethical considerations

Don't do anything during data collection that worsens the student's day for the sake of data

Don't deliberately escalate to "see what happens" — that's not your call and is generally wrong

If you're asked to participate in something that doesn't sit right ethically, consult — see brief 16.07

Maintain confidentiality of the data and findings

Pitfalls

| Try this | Watch out for |

| :-: | :-: |

| Use operational definitions everyone agrees on | Use vague terms like 'disruption' or 'tantrum' |

| Record ABC data in real time as behaviors occur | Reconstruct from memory at end of day |

| Capture what adults did, including unintended reinforcement | Edit the data to make adult responses look better |

| Document setting events, not just immediate antecedents | Focus only on what happened in the last 30 seconds |

| Use scatter plots to find patterns over time | Rely only on impressions about when behaviors happen |

| Bring honest hypotheses to the FBA team — what you think is happening | Wait passively for the assessor to figure it out |

| Recognize FBA hypotheses as testable, not proven | Treat them as the final word |

| Trust function-based BIPs over generic 'consequence' approaches | Default to punishment when prevention isn't working |

| Flag if behavior reappears or worsens after BIP — FBA may need revisiting | Stay quiet when the plan stops working |

| Maintain confidentiality of FBA data and findings | Discuss FBA results with people who don't have a need to know |

Scenarios

Scenario 1: A new FBA assignment with no training

The supervising teacher hands you an ABC data sheet for a student you support. "Take this for the next two weeks; the BCBA is doing an FBA."

Ask for a brief orientation: what behaviors should I record (operational definition), what's the threshold (every instance? only when above a certain intensity?), how should I write antecedents and consequences (what level of detail?). Ten minutes of clarification at the start saves two weeks of unusable data. Brief 06.04 ABC Narrative Recording covers the technique in depth.

Scenario 2: An FBA hypothesis you don't agree with

The FBA report says your student's hitting is attention-maintained. You think it's escape-maintained — you've watched her do it specifically when faced with hard work.

Your observations are valuable. Bring them to the team — supervising teacher, BCBA, case manager: "I want to flag a concern about the FBA hypothesis. Here's what I've been seeing." Specific data wins arguments. The BIP based on a wrong function won't work; better to raise it now than to find out after a month of failed intervention. The team can revisit, get more data, or refine the hypothesis.

Scenario 3: Multiple paras producing inconsistent data

You and another para take ABC data on the same student. Your data shows demand-related behavior; theirs shows random outbursts.

Either you're seeing different things at different times (legitimate — bring both), or you're using different definitions (need calibration). Sit with the supervising teacher and review side by side. Often the issue is the operational definition; tighten it. Take inter-observer agreement data on a few sessions until you match. This is what brief 06.01 (Data Types Overview) calls inter-observer agreement work.

Scenario 4: A behavior changing function over time

A student who was clearly escape-maintained six months ago is now showing the same behavior in attention-rich contexts where there's no demand. The BIP is based on the original FBA.

Function can shift. Bring this to the BCBA and team. The BIP may need revision based on current function. This is especially common when behaviors get reinforced inadvertently in new ways — a student who originally hit to escape may now hit because hitting reliably gets a big adult response.

Scenario 5: An FBA that was rushed

The FBA was completed in three days. The BIP is now in place but doesn't seem to fit the student you actually see.

Three days is fast for an FBA, especially for a complex behavior. Document what you're seeing now that suggests the BIP isn't fitting. Bring it to the supervising teacher and case manager. Don't simply abandon the BIP unilaterally; raise the concern through the right channel and let the team decide whether to revisit the FBA, gather more data, or modify the BIP.

Scenario 6: A family disagreeing with the FBA findings

The family thinks the FBA hypothesis (attention-maintained) is wrong because at home, the same behavior doesn't get attention but still happens.

Family observations matter. Bring it to the team. School and home behavior can have different functions because the contexts differ — but family disagreement should always be heard and considered. The case manager and BCBA should follow up; you can support by listening to the family and confirming you'll bring the concern to the team.

Closing thought

FBAs are how serious behavior support starts. Done well, they turn behavior from something mysterious or chaotic into something the team can understand and address. Done poorly — rushed, biased, or based on bad data — they produce BIPs that don't work and frustrate everyone.

Paras are usually the biggest determinant of FBA quality, even though they don't write the FBA. The data you bring, the patterns you notice, the honest reporting of what's actually working — that's the raw material from which good FBAs are built. Take the role seriously. Push back when you see flaws. Communicate clearly with the BCBA and team. The student depends on the FBA being right.

| |

| :-: |

| Bottom lineFBAs identify the function of behavior so BIPs can address it. Operational definitions, ABC data, scatter plots, setting events, and honest reporting of adult responses are the para's contribution. Hypotheses are testable, not proven. Multiple functions are common. Flag concerns, support BIP revisions when behavior changes. Maintain confidentiality. |

Related briefs

05.01 Function-Based Thinking — the underlying framework

05.03 Reading and Running a BIP — the document FBAs feed into

05.04 Antecedent Strategies — what good prevention looks like

05.13 When the Plan Isn't Working (planned)

06.01 Data Types Overview

06.04 ABC Narrative Recording

12.06 Working with the BCBA

13.01 FERPA and Confidentiality

16.07 I Was Asked to Do Something That Felt Wrong

Page of