What if FBA Findings Differ Across Settings?

Compare FBA findings across settings

Create one comparison row per setting. Use the same target definition where appropriate and record eligible opportunities, observation time, task, partner, antecedent events, client communication, ordinary supports, consequence, latency, health context, and exclusions. Mark every component that differs before comparing rates.

Begin with matched units. If the response can occur only during a transition, divide events by eligible transitions rather than total observation hours. If duration matters, report the total response time and opportunity context. Preserve both event counts and exposure so a busy setting does not appear worse simply because it contains more relevant opportunities.

Comparison fieldExamples of meaningful differencesOpportunityTransition type, task, request, delay, denied item, unstructured timePerson and partnerFamiliarity, language, response timing, training, authorityEnvironmentNoise, crowding, privacy, lighting, schedule predictabilityAccessAAC, visual supports, mobility, sensory and instructional materialsHealthSleep, pain, medication, hunger, illness, fatigueConsequenceHelp, delay, removal, attention, access, no observable changeObservationDate, duration, observer, recording method, missing periods

Do not force one definition across settings if the actual response forms differ materially. The clinician may need related but separate definitions, with a clear explanation of what can and cannot be compared.

Treat differences as assessment leads

A setting contrast can identify protective conditions. Predictable previews, accessible communication, quieter routes, smaller task steps, responsive partners, or meaningful choice may correspond with fewer concerns. Preserve these supports while examining them. Removing a helpful support merely to provoke the response can add risk and erase what the assessment has learned.

Direct client input can explain setting differences that an observer misses. Ask about pain, sensory conditions, privacy, relationships, confusing expectations, and desired outcomes in an accessible manner. Keep the person's report alongside observed counts.

Interpret the evidence cautiously

Unequal exposure can create a misleading contrast. Five events in ten difficult transitions and one event in a single easy transition cannot be compared as simple totals. Missing AAC, different response effort, crowded rooms, or partners who respond differently may explain part of the pattern and suggest more precise supports.

Descriptive co-occurrence does not establish function. If a delay follows four of five events at school, staff may be responding to the event rather than the event being maintained by delay. State whether evidence is interview, record, descriptive observation, experimental comparison, or treatment evaluation.

When settings differ on several features, change one relevant condition at a time when feasible and safe. If multiple access or safety repairs are needed, make them together and describe a bundled change. Do not prioritize causal neatness over the person's health, communication, or comfort.

Privacy and school or workplace rules may limit who can observe or receive identifiable data. Create a role-appropriate family summary without removing the information needed for the clinical decision. Confirm recording, transmission, and retention rules before using video or remote observation.

Use current assessment and ethics sources

Hanley's FBA review distinguishes descriptive observation from proof of a functional relation. The functional-analysis review explains systematic experimental comparisons. Events that often follow behavior in one setting may simply co-occur, so clinicians should state which findings are descriptive and what could test them.

Keep communication available

The ASHA AAC portal supports continuous access to communication tools. Preserve the person's established communication, a usable stop or correction response, ordinary supports, and accessible participation throughout this specific assessment decision.

A practical example

During ten school transitions, Jalen's defined response occurs five times, and a delay follows four. AAC is available in six of ten transitions, and only three receive a visual preview. During six home transitions, the response occurs once; the family previews all six, AAC is available, and the route is quieter.

The team preserves five of ten and one of six rather than averaging six events across sixteen unlike transitions. It notes that delay, AAC, preview, noise, partners, and transition types differ. Jalen reports that unexpected route changes are difficult and asks for a visible plan.

School staff introduce the preview and reliable AAC access during six later ordinary transitions. The response occurs twice. This small sequential change may support the accessibility repair, but it does not isolate preview from AAC, experience, or other conditions. The FBA keeps the setting-specific counts and updates the hypothesis cautiously.

Questions for a cross-setting meeting

Ask each setting to bring the definition, plan version, raw opportunity counts, supports, client communication, and observation coverage. Map what matches and what differs. Avoid asking one partner to defend their report against another.

End with one or two safe, client-informed questions, named owners, and a recheck date. The goal may be to transfer a protective support, improve data comparability, or determine that different local plans are appropriate. A single universal function is not the required outcome.

Write conclusions that preserve context

The report should state each setting's finding before any combined interpretation. A useful format is: “In the observed school transitions, the response occurred in 5 of 10 opportunities and delay followed 4 of those 5. At home, it occurred in 1 of 6 transitions with preview and AAC available. These descriptive samples differ in opportunity type, supports, partners, and noise.”

Then separate supported facts, hypotheses, and next tests. The observed counts are facts under sampled conditions. A possible relation with predictability or access is a hypothesis. A planned preview and AAC integrity review is a next test. Keeping the three layers distinct prevents a descriptive pattern from becoming a universal causal label.

Avoid a single average when conditions are incompatible. If an overall number is required, show its numerator and denominator and explain that it does not replace setting-specific results. Keep pending settings, missed opportunities, and health pauses visible.

When one setting cannot implement a proposed support, document the constraint and identify alternatives rather than judging the person against an unavailable plan. The clinical owner should decide whether different setting-specific arrangements still pursue the client's shared priorities.

Create a follow-up table with one row per agreed repair, the setting owner, implementation measure, client communication, target and replacement outcomes, and review date. Keep an unavailable support visible as an operational limitation. At the next meeting, review whether the repair occurred before interpreting the client's response. This sequence prevents a plan from being labeled ineffective in a setting that never received the planned access or partner behavior.

Questions families can use

Were definitions matched? Were opportunities comparable? Which supports and partners differed? What did the client report? Are observation windows representative? Which change can be tested safely?