Student Behavior Incident Log

Document what happened — objectively and with care.

A confidential behavior documentation log with an incident table, antecedent tracking, intervention notes, and a pattern analysis section — plus embedded guidance on objective vs. interpretive language and when to escalate as well as a link to an spreadsheet version!

When behavior documentation is done poorly, it becomes a liability — impressionistic, labeling, legally problematic. When it's done well, it becomes the foundation for the intervention that actually helps a student. This log is built around the difference. The incident table prompts teachers to record the antecedent (what happened before), the behavior itself (in objective, observable terms), and the intervention used. A pattern analysis section at the bottom asks teachers to synthesize across incidents before drawing conclusions, reducing the confirmation bias that distorts single-incident reports. Best-practice language guidance ('Student left seat 4 times' versus 'Student was defiant') is embedded throughout.