ABC Data Examples for Teachers: 8 Filled-In Classroom Samples

It's 2:50 on a Thursday. The school psychologist stops you in the hallway and asks if you have any ABC data on the student who threw his quiz on Tuesday. You have a sticky note that says "Eli, quiz, rough day." That's it.

I've been that teacher. Most of us have. The good news is that ABC data is not complicated once you've seen a few filled-in examples, and that's what most of the resources out there skip. You get a blank PDF, a definition, and a lot of jargon.

I'd tell you a joke about antecedents, but you'd need to know what happened right before it.

This post gives you plain-language definitions, eight completed ABC examples from elementary classrooms, the mistakes that make ABC data hard to use, and a free printable ABC data sheet. I'm a third grade teacher and a former RBT, not a behavior analyst, so this is written from the classroom side of the table: what to write down so the people who analyze it have something useful to work with.

What Is ABC Data?

ABC stands for antecedent, behavior, consequence. It's a simple way to record a behavior along with what happened right before it and right after it.

The IRIS Center at Vanderbilt, a federally funded resource for educators, defines the three parts this way in its ABC model page:

• Antecedent: any situation, action, or event that comes before a behavior
• Behavior: an observable and measurable act
• Consequence: any response, action, or event that follows a behavior

ABC data is one of the tools behavior teams use to look for patterns, and it often feeds into a functional behavior assessment (FBA). If you want the bigger picture of how it fits with frequency counts, tally sheets, and other methods, How to Track Student Behavior in the Classroom walks through each one.

Antecedent vs. Behavior vs. Consequence, in Plain Language

Antecedent: what happened right before

The antecedent is the event right before the behavior. Not the whole morning. Not "it was a Monday." The thing that happened in the seconds or minutes before.

Good antecedents are specific: "I said, 'Clear your desks, it's test time.'" "A classmate took his eraser." "The bell rang to line up from recess."

Behavior: what the student actually did

The behavior is what a video camera would have recorded. Something you could see or hear, and ideally something you could count or time.

"Put his head on the desk for about six minutes" is a behavior. "Shut down" is a description of how it felt to you. "Said 'This is stupid' and slid the paper off his desk" is a behavior. "Was disrespectful" is a judgment.

Consequence: what happened right after

In my experience, this is the part teachers misread most often. A consequence is not a punishment. It's simply whatever happened next: what you did, what other students did, and what changed for the student.

If classmates laughed, that's part of the consequence. If the hard worksheet went away, that's part of the consequence. If you said nothing and kept teaching, write that too. The consequence column can hold some of the most useful information on the sheet, so don't leave it as "redirected."

8 Antecedent, Behavior, Consequence Examples From Elementary Classrooms

These students are made up. The situations are ones most elementary teachers will recognize. Each one includes a quick note on why it's written the way it is.

1. Head down during independent writing (2nd grade)

• Antecedent: Teacher said, "Take out your journals and write three sentences about your weekend," then walked to the small group table.
• Behavior: Marcus put his head down on his folded arms. His pencil stayed in the cup. No writing for about six minutes.
• Consequence: Teacher walked over, said, "Let's get started," and wrote the first word for him. He wrote one sentence.

Why it works: It doesn't say Marcus was lazy or avoiding writing. It records the task, the time, and the fact that adult help came right after. Whether that matters is a question for later, once there are more entries.

2. Not lining up after recess (1st grade)

• Antecedent: Whistle blew to line up at the end of recess. The aide called "Line up" twice.
• Behavior: Ava stayed on the swing, said, "No, five more minutes," and kept swinging for about two minutes.
• Consequence: The aide walked over and stood next to the swing without talking. Ava got off and walked to the back of the line. The class waited for her.

Why it works: It quotes exactly what Ava said instead of summarizing it as "refused." It also notes that the class waited, which is easy to forget and might matter.

3. Calling out during a read-aloud (kindergarten)

• Antecedent: Read-aloud on the carpet. Teacher asked, "What do you think will happen next?"
• Behavior: Leo shouted an answer without raising his hand. This happened four times in about ten minutes.
• Consequence: The first two times, the teacher said, "Hands up, Leo." The third and fourth times, the teacher called on him and repeated his answer to the class.

Why it works: It records a count and a time window. It also honestly records that the teacher's response changed partway through. How you respond is part of the record, so write it down even when it changes.

4. Pushing at math centers (3rd grade)

• Antecedent: Partner dice game at math centers. Jayden took the dice from Sofia's side of the table.
• Behavior: Sofia pushed Jayden's shoulder with an open hand and said, "Give it back." Jayden did not fall.
• Consequence: Jayden gave the dice back. Teacher separated the partners, and Sofia finished center time at her desk with an independent worksheet.

Why it works: The antecedent includes what the peer did. When you're writing about one student, it's tempting to leave the other kid out, but what a peer did right before is often the most important part of the entry.

5. Ripping up a quiz (4th grade)

• Antecedent: Teacher handed out a 20-problem multiplication quiz and said, "You have 25 minutes."
• Behavior: Eli ripped his quiz in half and threw both pieces on the floor.
• Consequence: Teacher said, "Take a break at the calm corner." Eli went. He did not take the quiz that day.

Why it works: It doesn't say "Eli was trying to get out of the quiz," even if that's your hunch. It does record that the quiz went away, which is the fact a behavior team would want to see.

6. Dropping to the floor in the hallway (2nd grade)

• Antecedent: Walking in line to the cafeteria. The hallway was loud and two other classes were passing.
• Behavior: Noah covered his ears with both hands and sat down on the floor.
• Consequence: Teacher stayed with him while the aide walked the class ahead. After the hallway cleared, about three minutes later, Noah stood up and walked to lunch with the teacher.

Why it works: It describes the setting (loud, crowded) without diagnosing anything. "Sensory overload" is a conclusion. "Two classes passing, he covered his ears" is an observation.

7. Asking for a break (3rd grade)

• Antecedent: Teacher handed out a reading passage with five comprehension questions.
• Behavior: Maya raised her hand and asked, "Can I have a break card?"
• Consequence: Teacher said, "Thanks for asking," and set a three-minute timer. Maya took her break at the back table, came back on her own when the timer went off, and finished three of the five questions.

Why it works: ABC data isn't only for problem behavior. If a student is learning to ask for a break instead of ripping up the paper, recording the times it works is just as important as recording the times it doesn't.

8. When you didn't see the antecedent (5th grade)

• Antecedent: Not observed. Destiny arrived at 8:40 while the teacher was greeting students at the door.
• Behavior: Destiny walked to her desk and swept her books onto the floor with her forearm.
• Consequence: Teacher said quietly, "I'll check back in a minute." Two classmates turned to look and one laughed. Destiny picked up her books about four minutes later.

Why it works: It says "not observed" instead of guessing. If a sibling later tells you the bus ride was rough, add it as a separate line marked "reported by brother, not observed." Mixing what you saw with what you heard makes the whole entry harder to trust.

Common ABC Recording Mistakes (and How to Fix Them)

In my experience, the trouble with ABC data is rarely the format. It's what ends up in the boxes.

Writing motivation as if it were behavior. "He wanted attention." "She was trying to get out of work." You might be right, but you can't see a motive. Figuring out why a behavior keeps happening is the team's job, and it takes many entries. Your job is to give them clean observations. Write: "Called out four times during the read-aloud. Called on twice."

Using labels instead of actions. "Defiant," "meltdown," "disrespectful," and "aggressive" mean different things to different adults. Swap them for what happened: "Said 'No' and walked to the back of the room." "Cried and kicked the chair leg three times."

Treating the consequence as a punishment column. If you only write "lost recess" or "called home," you miss what happened in the moment: who laughed, what task went away, what attention the student got. Write the first thing that happened right after, then anything else.

Making the antecedent too big. "Rough morning" or "Mondays are hard" can be worth noting somewhere, but they aren't antecedents. The antecedent is the specific event right before.

Writing it at 3:15 from memory. By the end of the day, three incidents blur into one and the times are guesses. A rough note within a few minutes, even three words, beats a polished paragraph written that evening. Always include the time.

Only logging the big ones. If you only record the days a student throws something, the data will make it look like that's all he does. Record smaller incidents too, and note when a usually hard time went fine.

Mixing observed and reported. Anything you didn't see yourself should be labeled with who told you. "Reported by aide" is fine. Writing it as if you saw it is not.

Free Printable ABC Data Sheet

Here's a one-page ABC data sheet you can print and handwrite on. It has columns for date and time, setting, antecedent, behavior, consequence, and whether you observed it or someone reported it to you. One sheet per student keeps it simple.

Columns for date and time, setting, antecedent, behavior, consequence, and observed or reported, with a reminder at the top to write what you saw, not what you assume.

One page, five rows, print and handwrite. No sign-up required.

A few tips that make this sheet easier to fill in:

• Keep it on a clipboard where you actually stand, not in a binder in your desk.
• Short is fine. "Math quiz handed out / ripped quiz, threw on floor / sent to calm corner, no quiz" is a complete entry.
• Ask your team if they already have a preferred ABC form. If they do, use theirs so the data is easy to combine with what other adults are recording.

If you want a general behavior log instead of an ABC-specific one, the free behavior log template has a printable six-column version.

What to Do With ABC Data Once You Have It

You don't need to analyze it yourself. That's important to say out loud, because a lot of teachers feel like they're supposed to figure out the "function" of a behavior on their own. You're not.

What you can do is read across your entries and notice the obvious: does it happen more during writing than during math? Mostly after recess? Is the same consequence showing up again and again? Bring those observations to your school psychologist, behavior specialist, or BCBA as questions, not conclusions. They'll use your data, along with their own observations and interviews, to form a hypothesis. The IRIS Center has a free module on functional behavioral assessment if you want to understand that process better.

If your student has an IEP or is being evaluated for one, How to Document Student Behavior for IEP Meetings covers how your classroom notes fit into that process. And if your team also needs frequency or duration counts, How to Track Student Behavior Data explains those methods.

Where ShortHand Fits (and Where It Doesn't)

To be straight with you: ShortHand doesn't have an ABC data form, doesn't measure frequency or duration, and doesn't analyze ABC data for you. If your team needs formal ABC data collection, use the form they give you or a tool built for structured observation.

What ShortHand does is make the quick note easy. You tap the student, pick a behavior indicator, and type a short note in the optional note field. If you write it as "Before: quiz handed out. Did: ripped quiz. After: calm corner, no quiz," you have the ABC details in a dated note that stays in that student's history. When the team asks what you've seen, the notes are already there instead of on a sticky note in your lanyard. Pro users can also export a student's dated notes as a PDF to bring to a meeting.

If that sounds useful, you can try ShortHand free with sample students, no account needed.

Part of The Teacher's Complete Guide to Documenting Student Behavior.