Adelyons / Nello / ABC data for an IEP meeting
How to prepare ABC data for an IEP meeting
ABC data (antecedent, behavior, consequence) is one of the few things a parent can bring to an IEP meeting that the team cannot argue with: it is what happened, when, where and what helped. Prepared well, it turns "the afternoons are hard" into "three times a week, nearly always after an unplanned change, and a quiet corner settles it in ten minutes". This guide covers how much to collect, what to put on the page, and how to use it in the room.
Start two to four weeks before the meeting
A week of entries mostly shows the most memorable days. Two to four weeks of reasonably consistent rows is usually enough for the timing and the common antecedents to show. If the meeting is sooner, bring what you have and say how long it covers; a short, honest record still beats an impression.
Log the calm days too. A record with only hard moments in it has no baseline, and the team will want to know what a good day looks like as much as a hard one. If the school is willing, ask a teacher or aide to log the school hours in the same columns, so home and school can be read side by side (see sharing one behavior log between home and school).
What to record in each entry
| Field | Why the team needs it |
|---|---|
| Date and time | Shows when in the day and week hard moments cluster, which is often the first useful pattern. |
| Setting | Home, classroom, lunchroom, bus: tells the team whether a support is needed in one place or everywhere. |
| Antecedent | What was happening just before: a transition, a request, noise, a wait. This is where accommodations come from. |
| Behavior | What you saw, in plain words a camera would agree with. No labels like "defiant". |
| Consequence | What happened after, and what helped. The "what helped" column is the one teams use most. |
| Intensity and minutes | Lets everyone see whether things are getting easier over time, not only how often. |
The printable ABC data sheet has exactly these columns, and the ABC chart examples show weak rows next to stronger rewrites.
Condense it to one page
Nobody in a 45-minute meeting will read forty raw entries. Bring a one-page summary and keep the full log as backup. The summary needs five things:
- How often: incidents per day or per week, and the window it covers ("14 incidents over 21 days").
- When: the time of day and weekday they cluster in.
- Where: the settings, ranked.
- The common antecedents: the top three, with counts.
- What helps: the consequences that reliably preceded calm, with counts.
The FBA-ready ABC summary page shows this layout with a live sample, and the free online ABC log builds the counts from rows you type in.
Turn the counts into requests
Data is most useful when each pattern is paired with a concrete question for the team. Some examples of how families phrase it:
- "Nine of the fourteen incidents followed a transition with no warning. Can a visual or verbal warning before transitions be written into the plan?"
- "Most school entries are in the lunchroom. Is there a quieter place to eat, or a shorter time there?"
- "Headphones and a quiet corner helped in most entries. Can those be available in class without having to ask each time?"
Keep the language about needs and supports, not blame. The record describes a person communicating under stress; the point of bringing it is to change the environment around them, not to build a case about them. If the team suggests a functional behavior assessment (FBA), your ABC data is a natural starting point for it.
Send it ahead of the meeting
Email the one-page summary to the case manager a few days before, and ask for it to be attached to the meeting notes. A team that has read the numbers beforehand spends the meeting on what to do about them. Bring printed copies for everyone anyway.
Common mistakes worth avoiding
- Bringing only the worst days. It reads as a complaint, not a record. Show the whole window.
- Interpretations in the behavior column. "Was manipulative" invites an argument; "left the room and hid under the table for eight minutes" does not.
- No dates on the summary. Counts without a window cannot be compared at the next review.
- Changing what you record halfway through. Keep the columns the same so this meeting's numbers can be compared with the next one's.
Preparing the IEP data in Nello
Nello logs a hard moment as Antecedent, Behavior and Consequence in under a minute, with the setting, intensity, minutes and when it happened. The free CSV export carries every ABC entry; the ABC data report (Nello+) lays out frequency per day, a time-of-day grid and ranked antecedent, consequence and setting tables as a PDF for the team. A teacher can add the school day from a link, and at a desk you can read the history and print the free ABC data sheet in Nello on the web.
More guides: Health & care · all Adelyons guides