Schools make decisions based on what they can document. Your job is to give them clear, count-able facts so they can’t be dismissed as “just parent perception.”
1. Start with an observable definition
Vague labels like “disruptive” or “non-compliant” mean different things to different people. Define the behavior so anyone could count it.
Example of a strong definition
“Leaves assigned seat and moves more than one body length away from the desk without permission during independent work.”
Weak definition
“He’s disruptive during class.”
Why it matters: A clear definition forces the team to agree on what is actually happening before they can argue about what to do about it.
2. ABC data is the backbone
Every incident is a mini experiment. What happened right before, what the behavior looked like, and what happened right after tells the team why the behavior keeps happening.
A — Antecedent
The trigger right before: a demand, transition, peer conflict, denied request, correction, sensory load, or routine change.
B — Behavior
The observable, countable behavior you defined. Log it the same way every time.
C — Consequence
What happened after: task removed, adult attention, item given, peer reaction, removed from area, or the behavior stopped on its own.
Why it matters: When the same antecedent and consequence show up repeatedly, the team can guess the function and design a support that actually addresses it.
3. Capture setting events
Setting events are slow triggers. They don’t cause the behavior on their own, but they make it more likely.
Sleep
hours / quality
Meds
missed, late, or changed
Mood
anxiety, illness, frustration
Hunger
skipped meals
Routine
substitute teacher, schedule change
Sensory
loud spaces, crowded events
Why it matters: A tough morning can explain why a behavior spiked on Tuesday but not Wednesday. That context makes the data credible, not excusable.
4. Use it in the IEP meeting
Bring facts, not feelings. The patterns you collect here are designed to be read aloud in a meeting without editorializing.
- •Open with the definition so everyone is talking about the same behavior.
- •Show frequency and time of day: “This happened 12 times in 3 weeks, mostly during transitions after lunch.”
- •Connect antecedents and consequences: “Every time the task was removed, the behavior stopped within 30 seconds.”
- •Cite setting events: “It happened on 4 of the 5 days he slept less than 7 hours.”
- •Balance the record with strengths: Mention what worked, what helps him recover, and what he does well.
Why it matters: A clear pattern statement turns a debate into a problem-solving conversation.
5. Navigate to the right supports
The goal of the data is not to prove the child is difficult. It is to show the team where to intervene.
Behavior stops when task is removed or reduced
Likely function: Escape from demands
Support direction: Break tasks into smaller chunks, offer choices, pre-correct, teach help-seeking
Behavior gets adult or peer attention every time
Likely function: Access to attention
Support direction: Scheduled attention before the behavior, teach replacement requests, ignore minor attention-seeking safely
Behavior ends with getting the item or activity
Likely function: Access to tangible
Support direction: Visual schedule of access, first-then board, teach waiting and replacement requests
Behavior happens when alone or unstructured, and stops on its own
Likely function: Sensory / automatic
Support direction: Sensory breaks, substitute activity, environmental enrichment, not punishment
Why it matters: The right support depends on the function. A sensory behavior punished by loss of recess will likely get worse, not better.
What this app does and does not do
- •It does organize your observations into a consistent, shareable record.
- •It does not diagnose. Only qualified clinicians diagnose disabilities or conditions.
- •It does not replace your advocacy. It arms it with evidence.
Privacy note
Records like these may be shared with, requested by, or subpoenaed from you in a dispute. Log facts you would be comfortable reading aloud in a meeting. Your records are stored privately in your own account and are never shared unless you export them.