Skip to main content
From 'He Always Melts Down After Lunch' to Usable ABC Data
FBA & Data Collection

From 'He Always Melts Down After Lunch' to Usable ABC Data

Five real-sounding hallway anecdotes translated step-by-step into ABC log entries, and how a few weeks of honest entries turn instinct into a testable pattern.

TeacherParaSpecialist10 references1 resource
Back to Blog
Bobby Hillman
Bobby Hillman, M.Ed., LBA, BCBA
Founder, Classroom Pulse
August 20, 2026
8 min read

Best For

Teams this article is built to help

TeacherParaSpecialist

Category: FBA & Data Collection

Evidence

What backs this guide

10

Curated references are cited at the end of the article.

Materials

What you can leave with

3
  • Condensed key takeaways
  • 1 bonus download
  • Interactive self-check quiz
Share this article:

"He always melts down after lunch." "She's only like this with the sub." "He's fine until math." If you've said any of these in a hallway, congratulations: you've already done the hardest part of behavior assessment. You noticed a pattern. The anecdote IS the hypothesis. The only thing missing is the format that turns your professional instinct into evidence a team can act on. That format is the ABC log, and the translation is easier than you think.

Your Anecdote Is Already a Hypothesis

Teachers and paraprofessionals spend more hours watching students than any evaluator ever will. When you say "always after lunch," you're reporting a real observed regularity. Your brain has run hundreds of informal observations and found a pattern. Behavior science doesn't dismiss that. It just asks one follow-up question: can we write it down in a way that lets us test it?

That's all an ABC log is. Three columns:

  • A (Antecedent): what happened right before (the specific demand, transition, denial, or situation)
  • B (Behavior): what the student actually did, in observable words
  • C (Consequence): what happened right after (what the behavior got, or got the student out of)

The anecdote supplies the hunch; the log supplies the receipts. There's solid research behind why ABC data beats simple frequency counts, but the short version is this: counting incidents tells you how bad the week was. ABC entries tell you what to change. Let's walk five hallway anecdotes through the translation, one at a time.

Anecdote 1: "He Always Melts Down After Lunch"

The instinct here is about time. But "after lunch" isn't an antecedent; it's a window. Inside that window, something specific is happening: the transition from a loud, unstructured cafeteria to seated quiet work, usually with a demand attached within minutes. The log entry forces you to name the actual trigger.

The Anecdote

"Devon always melts down after lunch. Every single day, it's a disaster."

The ABC Entry

A: 12:42, returned from cafeteria; told to sit and begin silent reading within 2 minutes of entering room

B: Pushed book off desk, put head down, yelled "no" when prompted twice

C: Given 10 minutes at the calm-down corner; reading task not resumed

Notice what the entry captured that the anecdote didn't: the transition, the two-minute demand window, and (crucially) that the task went away afterward. Two weeks of entries like this can distinguish "he needs a buffer after the cafeteria" from "silent reading demands are the problem," which lead to very different supports.

Anecdote 2: "She's Only Like This With the Sub"

This anecdote is about people, but people aren't antecedents either. What a substitute actually changes is the environment: routines run differently, expectations are announced differently, and familiar supports (the visual schedule, the quiet signal, the seating arrangement) often quietly disappear.

The Anecdote

"Maya is an angel for me. The minute there's a sub, she's a different kid."

The ABC Entry

A: Substitute teacher; morning visual schedule not posted; sub announced a page-number change to the usual routine

B: Left seat, walked the perimeter of the room, tore the corner of her worksheet

C: Sent to buddy classroom for the rest of the period

"Sub day" belongs in the entry too, but as a setting event: the background condition that makes the behavior more likely, rather than the trigger itself. Setting events like disrupted routines, poor sleep, or a rough morning at home quietly raise the odds of behavior hours before anything visible happens. Logging them separately from antecedents is what lets the pattern show: maybe Maya handles subs fine when the visual schedule stays up. That's an intervention you can hand a substitute on a sticky note.

Anecdote 3: "He's Fine Until Math"

"Math" is a 55-minute block containing a dozen different situations: warm-ups, direct instruction, cold-calling, independent problem sets, partner work. The anecdote says where to look; the log finds what inside that block actually sets things off.

The Anecdote

"Jaylen is fine all morning. Then math starts and it all falls apart."

The ABC Entry

A: Independent practice began; worksheet with 12 two-step word problems, no worked example on the page

B: Crumpled worksheet, said "this is stupid," walked to the pencil sharpener three times in 5 minutes

C: Teacher sat with him and completed the first three problems together

A week of entries might show the behavior never occurs during warm-ups or instruction, only when independent work starts. That shifts the conversation from "he hates math" to "two-step problems without a model are too big a first step," which is a fixable instructional problem, not a character flaw.

Anecdote 4: "She Just Blows Up Out of Nowhere"

This is the honest anecdote: you genuinely haven't spotted the trigger. "Out of nowhere" almost always means the antecedent is either subtle (a peer's whispered comment, a denied request from earlier), delayed (a setting event from the morning), or internal. This is exactly the situation ABC logging was built for: you log especially when you can't see the pattern, because the columns catch what memory can't hold.

The Anecdote

"There's no pattern with Amara. She just explodes randomly. Nothing sets her off."

The ABC Entry

A: Unclear at the moment. Noted: partner activity had just been announced; Amara had not been chosen by the peer she sits next to

B: Swept materials off desk, screamed, kicked chair

C: Class attention turned to her; counselor called; left room with counselor

It's Okay to Write "Unclear"

An honest "antecedent unclear, here's what was happening in the room" entry is far more useful than a guessed one. Ten honest entries let a pattern surface on its own. Ten guessed entries just launder the original assumption into fake data.

Three weeks of "unclear" entries for Amara might reveal that every incident followed a peer-selection moment: partner picking, team choosing, seat selection. Nobody could see that in the moment. The columns could.

Anecdote 5: "He Only Does It for Attention"

Unlike the others, this anecdote skips straight to a conclusion about why. It's a function claim wearing an observation's clothes. Sometimes it's right! Attention is one of the four common functions of behavior, alongside escape, access to tangibles, and sensory/automatic reinforcement. But "for attention" is exactly the kind of claim the consequence column exists to test.

The Anecdote

"Marcus makes those noises purely for attention. He looks right at me while he does it."

The ABC Entry

A: Silent independent writing; teacher conferencing with another student across the room

B: Loud repeated vocal noises, looking toward teacher

C: Teacher crossed the room, gave verbal redirection at his desk; noises stopped for ~10 minutes

If two weeks of entries consistently show low-attention antecedents and attention-delivering consequences, the anecdote is confirmed, and now it's evidence that supports a plan (scheduled check-ins, attention for on-task behavior) instead of an opinion in a meeting. But if half the entries show the noises also happen when the teacher is standing right there, or that they reliably end the writing task, the log just saved the team from building an intervention on the wrong function.

What a Few Weeks of Entries Reveal

One entry proves nothing, and that's fine. The power is cumulative. Somewhere between 15 and 20 entries, patterns stop being arguable:

From Entries to Testable Pattern

Antecedents cluster

14 of Devon's 16 incidents follow the cafeteria-to-desk transition with a demand inside two minutes. The "after lunch" hunch is now a specific, changeable trigger.

Consequences repeat

In 12 of those incidents, the demand was removed or delayed. Now you have a testable escape hypothesis, and a reason the behavior keeps working.

Exceptions teach

The two days with zero incidents both had recess before seatwork. The exception isn't noise. It's a preview of the intervention.

That's the full journey: hallway instinct, honest columns, visible pattern, testable hypothesis. When the behavior team or evaluator eventually asks "what do we know about this behavior?", you're not offering a vibe. You're handing over dated, specific, analyzable evidence they can build a plan on.

And practically speaking, the logging has to be fast or it won't happen during a real school day. A printed form by the desk works; a structured digital tool like Classroom Pulse with pre-loaded antecedent and consequence options gets an entry down to under 30 seconds and graphs the patterns for you. But the format matters less than the honesty and the consistency.

Trust the Instinct. Then Log It.

You were never wrong to notice. "Always after lunch" and "only with the sub" are real signal detected by a trained adult who knows the student. ABC logging doesn't replace that instinct. It promotes it, from something you say in a hallway to something a team can test, graph, and act on.

Start with one student and one anecdote this week. Grab the free ABC Documentation Template, write your first honest entry, and let the columns do what memory can't.

Start Logging ABC Data

References

Hanley, G. P., Iwata, B. A., & McCord, B. E. (2003). Functional analysis of problem behavior: A review. Journal of Applied Behavior Analysis, 36(2), 147–185. https://doi.org/10.1901/jaba.2003.36-147

Iwata, B. A., Dorsey, M. F., Slifer, K. J., Bauman, K. E., & Richman, G. S. (1994). Toward a functional analysis of self-injury. Journal of Applied Behavior Analysis, 27(2), 197–209. https://doi.org/10.1901/jaba.1994.27-197

Newcomer, L. L., & Lewis, T. J. (2004). Functional behavioral assessment: An investigation of assessment reliability and effectiveness of function-based interventions. Journal of Emotional and Behavioral Disorders, 12(3), 168–181. https://doi.org/10.1177/10634266040120030401

Ingram, K., Lewis-Palmer, T., & Sugai, G. (2005). Function-based intervention planning: Comparing the effectiveness of FBA function-based and non-function-based intervention plans. Journal of Positive Behavior Interventions, 7(4), 224–236. https://doi.org/10.1177/10983007050070040401

Scott, T. M., Alter, P. J., & McQuillan, K. (2010). Functional behavior assessment in classroom settings: Scaling down to scale up. Intervention in School and Clinic, 46(2), 87–94. https://doi.org/10.1177/1053451210374986

Briesch, A. M., Chafouleas, S. M., & Riley-Tillman, T. C. (2016). Direct behavior rating: Linking assessment, communication, and intervention. Guilford Press.

Chafouleas, S. M., Kilgus, S. P., Riley-Tillman, T. C., Jaffery, R., Christ, T. J., Briesch, A. M., Chanese, J. A. M., & Kalymon, K. M. (2013). An evaluation of the generalizability of direct behavior rating single-item scales to measure academic engagement across raters and observations. School Psychology Review, 42(4), 407–421.

Volpe, R. J., & Briesch, A. M. (2012). Generalizability and dependability of single-item and multiple-item direct behavior rating scales for engagement and disruptive behavior. School Psychology Review, 41(3), 246–261.

Smith, T. E., Thompson, A. M., & Maynard, B. R. (2022). Self-management interventions for reducing challenging behaviors among school-age students: A systematic review. Campbell Systematic Reviews, 18(1), e1223. https://doi.org/10.1002/cl2.1223

Ruble, L. A., McGrew, J. H., Wong, W. H., & Missall, K. N. (2018). Special education teachers' perceptions and intentions toward data collection. Journal of Early Intervention, 40(2), 177–191. https://doi.org/10.1177/1053815118771391

Put This Into Practice

Turn the article into action with ready-to-use materials. Downloads stay open; emailed resources and quiz results are opt-in.

Key Takeaways

  • A hallway anecdote like 'always after lunch' is already a hypothesis; the ABC log is just the format that makes it testable
  • Times, places, and people aren't antecedents; the log forces you to name the specific demand, transition, or situation inside them
  • Conditions like sub days or rough mornings belong in the entry as setting events, separate from the immediate trigger
  • Writing 'antecedent unclear' honestly beats guessing; patterns surface from honest entries, not laundered assumptions
  • Around 15-20 entries, antecedents cluster, consequences repeat, and exceptions preview the intervention

Bonus Materials

Clean downloads to pair with this article

Download resources directly or send a copy to your inbox. Marketing updates are optional.

1 ready-to-use download
PDF download

ABC Documentation Template

Ready-to-use antecedent-behavior-consequence recording form

Download now

Can You Translate the Anecdote?

Test whether you can turn classroom hunches into usable ABC entries.

3 questions~2 min

For classroom teams

Put this into practice with your own data

Log behaviors as they happen, see the pattern on a graph, and bring a clear summary to your next team meeting.

Start Logging ABC Data

Free for up to 3 students. No credit card required.

About the Author

Bobby Hillman
Bobby Hillman, M.Ed., LBA, BCBA
Founder, Classroom Pulse

Bobby Hillman is a Board Certified Behavior Analyst and Licensed Behavior Analyst with an M.Ed. in Special Education and more than 25 years in public special education and autism services. He works as a Behavior Instructional Specialist and founded Classroom Pulse to reduce the documentation load on classroom teams while keeping the detail FBA and BIP work requires.

About Classroom Pulse

Get More Insights Like This

One email on Fridays with the week's new articles. Unsubscribe anytime.

Stay updated with behavior tracking tips. Unsubscribe anytime. Privacy Policy.