Writing School-Friendly FBA Reports: Technical Writing for Educational Teams

A technically impeccable FBA report that no one reads or understands serves no clinical purpose. The goal of documentation is not to demonstrate expertise; it is to guide intervention. This guide addresses the tension between technical rigor and practical utility, providing frameworks for writing reports that educators actually use.

The Readability Problem

Research on educational documents consistently finds that technical reports often exceed the reading level of their intended audience. FBA reports written in dense academic prose may satisfy documentation requirements while failing their primary purpose: guiding intervention.

Common Problems

• Excessive jargon without definitions
• Dense paragraphs without visual breaks
• Recommendations buried in narrative
• No executive summary
• Data presented without interpretation
• Passive voice obscuring responsibility
• Report length exceeding necessity

Effective Characteristics

• Clear executive summary on page 1
• Technical terms defined on first use
• Visual data displays (graphs, tables)
• Numbered, actionable recommendations
• Headers and subheaders for navigation
• Active voice clarifying who does what
• Appropriate length for content

The Audience Test

Before finalizing a report, ask: Could a first-year special education teacher with no ABA training read this and know what to do? If not, revise. The paraprofessional who spends 6 hours daily with the student needs to understand the report as much as the BCBA supervisor.

Report Structure for Maximum Impact

Structure influences whether reports are read and implemented. The following framework prioritizes implementation while maintaining technical completeness.

Page 1

Executive Summary

The entire report in one page. Many readers will read only this.

• Student name, grade, setting
• Referral concern (1-2 sentences)
• Primary function identified
• Top 3-5 recommendations
• Recommended follow-up timeline

Section 1

Background & Referral

• Reason for referral
• Relevant history (brief; not a biography)
• Current placement and services
• Previous interventions and outcomes

Section 2

Behavior Description

• Operational definitions (specific, measurable)
• Topography (what it looks like)
• Current levels (frequency, duration, intensity)
• Examples and non-examples

Section 3

Assessment Methods & Data

• Methods used (interviews, observations, records)
• Observation dates and settings
• Data displays with interpretation
• Pattern analysis

Section 4

Functional Analysis

• Antecedents (triggers, setting events)
• Consequences maintaining behavior
• Hypothesis statement (clear function)
• Summary of evidence supporting hypothesis

Section 5

Recommendations

• Numbered, prioritized recommendations
• Prevention strategies
• Replacement behaviors to teach
• Response strategies
• Data collection plan

Writing Clear Recommendations

Recommendations are where reports succeed or fail. Vague recommendations produce vague implementation. Specific, actionable recommendations increase fidelity.

Ineffective Recommendations

"Provide positive reinforcement."
Too vague. What reinforcement? For what behavior? How often?
"Implement antecedent modifications."
Jargon without specifics. Which modifications?
"Consider a sensory diet."
"Consider" is not actionable. What diet? Who provides it?

Effective Recommendations

"Provide 5-minute computer access immediately after completing math worksheet independently."
Specific reinforcer, timing, and contingency.
"Seat Marcus in the front row, away from window, next to peer model."
Concrete environmental modification.
"Provide 5-minute movement break (walk to office and back) before writing tasks."
Specific activity, duration, timing.

The Effective Recommendation Formula

WHO does WHAT, WHEN, under WHAT CONDITIONS, with WHAT CRITERIA for success.

Example: "The classroom teacher will provide a visual timer showing 10 minutes remaining before transitions. The timer will be placed on Marcus's desk. When the timer reaches zero, Marcus will be prompted to pack up materials. Effective implementation = timer used for 80% of transitions."

Translating Jargon

Technical terminology serves important functions within the profession but can impede communication with educational teams. The solution is not to avoid technical concepts but to explain them clearly.

Jargon Translation Guide

Technical Term	Plain Language
Antecedent	What happens right before the behavior (trigger)
Consequence	What happens right after the behavior
Function	What the student gets or avoids by doing the behavior
Positive reinforcement	Something is added that increases the behavior
Negative reinforcement	Something is removed that increases the behavior
Escape-maintained	The behavior helps the student get away from something
Attention-maintained	The behavior gets the student attention from others
Extinction	No longer providing what the behavior used to get
Differential reinforcement	Reinforcing one behavior while not reinforcing another
Setting event	Background conditions that make behavior more likely

When to Use Technical Terms

Technical terminology is appropriate when:

• The audience includes BCBAs or other ABA professionals
• The term has been defined earlier in the document
• No plain-language equivalent exists without losing meaning
• The report will be used for professional documentation or insurance

Even then, consider adding a glossary or parenthetical definitions.

Visual Supports in Reports

Visual displays of data are processed faster than text and are more memorable. Every FBA report should include at least one visual data display.

Effective Visual Elements

• Line graphs: Frequency/duration over time
• Bar graphs: Behavior by setting/activity/time
• Scatter plots: When behavior occurs (time/day)
• Pie charts: Proportion of functions (use sparingly)
• Tables: ABC patterns, antecedent summaries
• Flowcharts: Decision trees for response

Visual Design Principles

• Title every graph clearly
• Label axes with units
• Use high-contrast colors
• Include a legend if multiple data series
• Add brief interpretation below graph
• Print-friendly (avoid color-only distinctions)

Graph Interpretation

Never include a graph without interpretation. After each visual, write 1-2 sentences: "This graph shows that Marcus's off-task behavior is highest during independent writing (average 8 incidents) and lowest during hands-on science activities (average 1 incident). This pattern supports an escape hypothesis."

Hypothesis Statements That Guide Intervention

The hypothesis statement is the bridge between assessment and intervention. A well-written hypothesis directly implies intervention components.

Hypothesis Statement Template

When [ANTECEDENT/SETTING EVENT], [STUDENT] engages in [BEHAVIOR] in order to [FUNCTION: get/avoid WHAT].

Strong example: "When presented with multi-step math problems without visual supports, Marcus engages in task refusal (putting head down, saying 'I can't do this') in order to escape the aversive task demands."

Weak example: "Marcus is frustrated and acts out." (No antecedent, vague behavior, no function)

From Hypothesis to Intervention

A strong hypothesis implies intervention:

• Antecedent: Add visual supports for multi-step problems
• Replacement behavior: Teach Marcus to request help or a break
• Consequence: Honor appropriate escape requests; don't allow task escape via refusal

Common Pitfalls to Avoid

The Biography Problem

FBA reports are not student biographies. Include relevant history only. The reader does not need to know birth weight, developmental milestones from infancy, or family structure unless directly relevant to the current behavior.

Keep background to one page maximum.

The Data Dump

Raw data without interpretation is not useful. Don't include pages of ABC charts without synthesis. Present data summaries with clear patterns identified.

If you include raw data, put it in an appendix—not the main report.

The Hedge

Excessive hedging undermines confidence and implementation: "It appears that the function may possibly be related to attention-seeking behaviors in some contexts."

Be clear: "The primary function is attention from adults. Evidence includes..."

The Diagnosis Hunt

FBAs assess function, not diagnose conditions. Avoid: "This behavior is consistent with ODD" or "Possible ADHD contributing factor."

Stay in your lane: Report what you observed and what maintains the behavior.

The Blame Game

Avoid language that blames staff, parents, or the student. Instead of "The teacher fails to provide reinforcement consistently," write "Consistent reinforcement delivery is recommended."

Focus on what should happen, not who did something wrong.

Quality Control Checklist

Before Submitting Your Report

☐ Executive summary present and complete on page 1 ☐ All technical terms defined on first use ☐ At least one visual data display included ☐ Hypothesis statement is specific and testable ☐ Recommendations numbered and prioritized ☐ Each recommendation specifies WHO, WHAT, WHEN ☐ Readability appropriate for audience (no unnecessary jargon) ☐ Background section is concise (not biographical) ☐ Proofread for errors and clarity ☐ Asked: "Could a first-year teacher implement this?"

Reports That Drive Change

The purpose of an FBA report is not documentation for its own sake—it is to guide effective intervention. Technical accuracy matters, but so does accessibility. The most rigorous analysis is worthless if implementers cannot understand it.

Write for the teacher who will read your report during a 15-minute planning period. Write for the paraprofessional who needs clear guidance. Write for the parent who wants to understand their child. When your reports are read, understood, and implemented, you have succeeded.