What ABC data is
An ABC log records three things about a behavior, in the order they happen:
- Antecedent: any situation, action, or event that immediately precedes the behavior.
- Behavior: an observable or measurable act.
- Consequence: a response, action, or event that immediately follows the behavior.
Those are the definitions the IRIS Center at Vanderbilt uses, where ABC data collection is described as the most common descriptive assessment behind a functional behavioral assessment.[1] Recorded consistently, it shows a clinician what tends to set a behavior off and what keeps it going.
Most of the published guidance on ABC logs is written for teachers. In a group home or a residential program the people collecting the data are direct care staff, the settings change hour to hour, and the log has to work at 7 pm on a Saturday as well as during school.
When to fill one in
- Every time a target behavior named in the resident's behavior plan or treatment plan happens.
- When a clinician asks for ABC data on a new or changing behavior, usually for a set period.
- Alongside an incident report when a behavior also meets your program's definition of an incident. The ABC log captures the pattern; the incident report captures the event and the notifications.
Fill it in as soon as the situation is safe, while the details are fresh. A log completed at the end of the shift from memory loses the antecedent first.
How to fill in each column
Setting
Date, time, where it happened, who was there, and what was going on. IRIS recommends noting the setting, the time of day, and the people involved, because those are often where the pattern turns out to be.[1]
Antecedent
What happened right before: a request, a transition, a “no”, a peer's comment, a phone call ending. Write the event, not the resident's state of mind. “Staff said screen time was over” is an antecedent. “He was in a bad mood” is not.
Behavior
What you saw and heard, described so that someone who was not there could picture it. Add how long it lasted and how severe it was on your program's scale. “Threw a shoe at the wall and shouted for about 2 minutes” beats “escalated”.
Consequence
What happened immediately after, from the resident's point of view: what staff did, how peers reacted, what the resident got, and what they got out of. A consequence is not a punishment; it is simply what followed. “Staff removed the worksheet” is a consequence, and an important one.
Notifications and injuries
Who was told and when (a supervisor, the nurse, a guardian), and whether anyone was hurt. These usually belong on the incident report too.
Worked examples
All three examples are invented.
| Setting | Antecedent | Behavior | Consequence |
|---|---|---|---|
| Tue 7:05 pm, living room, 4 peers and 2 staff, end of phone time | Staff said phone time was over and asked for the phone back. | Held the phone to his chest, said "five more minutes" three times, then threw a couch cushion toward staff (missed). About 2 minutes. Severity: moderate. | Staff restated the expectation once and stepped back. Peers watched. He handed the phone over at 7:08 and went to his room. |
| Wed 3:40 pm, kitchen, 1 staff, homework hour starting | Staff put the math worksheet in front of her and said homework starts now. | Put her head down and said "I'm not doing this" twice; pushed the worksheet off the table. About 6 minutes. Severity: mild. | Staff removed the worksheet and offered a 5-minute break. She returned at 3:52 and finished the first five problems with help. |
| Sat 10:15 am, van, 3 peers and 2 staff, outing to the park | A peer took the front seat she had asked for. | Yelled at the peer and kicked the back of the seat four times. About 1 minute. Severity: moderate. No injury. | Staff pulled over and moved the peer to the back. She stopped kicking. Incident report completed; program manager notified at 10:30. |
Look at the second example. The behavior got the worksheet removed. Logged once, that is a detail. Logged every afternoon for two weeks, it is a pattern the clinician will want to see.
Common mistakes
- Feelings instead of events. “Frustrated” in the antecedent column tells the clinician nothing about what to change.
- Labels instead of behavior. “Defiant” or “meltdown” instead of what the resident actually did.
- Skipping the consequence. It is the column most often left blank, and the one that most often explains why the behavior keeps happening.
- Logging only the big events. The smaller, frequent behaviors are often where the pattern is clearest.
- Writing it hours later. Details blur, and the antecedent goes first.
Reading the log for patterns
One entry rarely means much. IRIS advises collecting ABC data across different days and contexts until one or more patterns emerge.[1] When a clinician reviews the log, they are usually asking:
- Does it happen at a particular time of day, or in a particular place?
- Does it follow a particular kind of request, transition, or person?
- What does the behavior tend to get the resident, or help them avoid?
Those answers shape the behavior plan. The IRIS Center's practice activity walks through a full A-B-C analysis if you want to go further.[2]
Free ABC behavior log template
Print it landscape, one sheet per resident. Keep it where staff can reach it during the shift, not in the office.
ABC behavior log
Resident: ____________________
Target behavior(s): ____________________
| Date and time | Setting and who was there | Antecedent | Behavior, duration, severity | Consequence | Notified | Staff |
|---|---|---|---|---|---|---|
Template from dacnushealth.com/resources/abc-behavior-log. Adapt it to each resident's behavior plan and your program's policies.
ABC logs in software
A paper log in a binder is hard to review across weeks. In Dacnus Clinical Records, behavior logs record the antecedent, behavior, and consequence, with severity, duration, witnesses, and who was notified, on the resident's chart next to the shift notes and the treatment plan.