Guide · Data collection
How to collect ABC data
ABC data — antecedent, behavior, consequence — is the record of what happens around a behavior. Collected consistently, it reveals why a behavior keeps happening. Here's how to capture it so it's actually usable later.
The three parts
- Antecedent — what happened right before (a demand given, a transition, told to wait, attention divided).
- Behavior — what the student did, described observably (what you'd see on video, not a label like "defiant").
- Consequence — what happened right after (redirected, ignored, removed from the activity, given a break).
What makes ABC data usable
- Log it in the moment. Reconstructed-from-memory data at the end of the day loses the antecedent, which is the part that matters most.
- Be consistent. Everyone on the team should use the same categories for antecedents, behaviors, and consequences — otherwise the data can't be counted.
- Capture context — period, setting, and who was present — so patterns by time of day or activity can surface.
- Everyone logs. Paras, aides, and teachers all see the behavior; the data shouldn't live in one person's notebook.
From data to a decision
Collected consistently, ABC data answers the real question: what is this behavior getting or avoiding? Once you can see that most incidents follow the same antecedent, the intervention almost writes itself.
ABC Tracker is built for exactly this.
- One-tap logging of antecedent → behavior → consequence — fast enough to do in the moment.
- Shared categories & shared data so the whole team logs into one consistent picture.
- Charts by behavior over time, by period, and by day of week.
- AI reads the chains, finds the pattern and likely function, and drafts a Behavior Intervention Plan.
Log ABC data in seconds — start a free trial
15-day free trial · built by a special-education teacher.