Behavior Log Templates That Teachers Actually Use

A behavior log is any structured record of what a student did, when they did it, and what happened around it. That definition is broad on purpose. The right log depends on the question you are trying to answer, not the template that shows up first on Google.

This is the guide we wish existed when we were building our own: which template to use for which situation, what to include, and, the part everyone skips, when the paper log has to become something else.

Type 1: The frequency log

Use a frequency log when you need to know how often a specific behavior happens. Not how bad it was, not what triggered it, just the count. This is the log to reach for when a parent or SAT team member says 'I feel like it's happening all the time' and you need to know whether that means 3 times a day or 30.

• Student name and date at the top.
• The target behavior defined in one specific, observable sentence (e.g. 'Leaves seat without permission,' not 'Is disruptive').
• A grid of time blocks, usually class periods or 15-minute intervals.
• A tally column and a daily total.

Type 2: The ABC log

ABC stands for Antecedent, Behavior, Consequence. Use it when you need to figure out why a behavior is happening, usually in preparation for a Functional Behavior Assessment or a Tier 3 review. It is the highest-fidelity log you can run and also the most time-intensive, which is why it should be a temporary tool, not a daily habit.

• Antecedent: what happened right before (e.g. 'Given a math worksheet with 20 problems').
• Behavior: what the student did, described in observable terms (e.g. 'Crumpled paper, put head down').
• Consequence: what happened right after (e.g. 'Sent to buddy room for 10 minutes').
• Time, setting, and staff member present.

Run an ABC log for one to two weeks, not one to two months. The point is to spot a pattern quickly, same time of day, same subject, same peer, so you can test a hypothesis. Once you see the pattern, switch to a lighter-weight log to monitor whether your intervention worked.

Type 3: The Daily Behavior Report Card (DBRC)

A DBRC, sometimes called a point sheet, is the workhorse log of Tier 2. Instead of tracking incidents, it tracks positive behaviors across the day, with a rating (typically 0–2 or 0–3) for each period. It is the log to use when a student is on CICO or a similar Tier 2 plan.

• Three or four target behaviors written as positives (e.g. 'Follows directions,' 'Stays on task').
• A row for each class period or subject.
• A simple rating scale, we use 0, 1, 2. Anything more granular gets inconsistent between teachers.
• A daily goal (e.g. 80% of possible points) and a place for the check-in adult to initial.

The DBRC is where most schools get behavior tracking right or very wrong. Right: same card format across the building, defined behaviors, daily goal, adult check-in. Wrong: every teacher designs their own card, behaviors are things like 'Good day,' and the card lives in the student's backpack until it is lost.

Type 4: The incident log

An incident log records the serious stuff, fights, elopement, property damage, restraints, anything that would go on an office referral. It is not a Tier 1 or Tier 2 tool. It is a compliance and safety record.

• Date, time, location, staff involved.
• Description of what happened in observable terms, no interpretation.
• Actions taken (call home, admin notified, referral filed).
• Follow-up plan and who owns it.

When paper stops working

Every behavior log we have described works fine on paper for one student, for a couple of weeks. The wheels come off when you have five students on Tier 2, three teachers filling in the card, and a SAT meeting in nine days where someone has to summarize six weeks of data. That is when paper becomes the intervention getting in the way of the intervention.

You do not need enterprise software to fix this. You need one place where every adult can enter data in under a minute per student, where the trends show up automatically, and where the SAT team can pull a report without asking someone to spend their planning period transcribing. That is exactly what we designed Cub Guide to do.

The short version

Pick the log that matches the question. Define the behavior specifically enough that two adults would tally the same event the same way. Keep the format consistent across the building. And when the paper starts getting lost, in the wash, or transcribed at 9pm on Sunday, that is the log telling you it is time to upgrade the system, not the students.