Special Incident Reports

When incident reports are required, what they must contain, common errors to avoid, and how to complete one accurately under the pressure of a difficult moment.

| | |

| :-: | :-: |

| Audience | Paras who work with students with behavioral or medical needs; supervising teachers who review and sign incident reports. |

| |

| :-: |

| Why This Matters |

| An incident report is a formal written record of an event that was significant enough to require documentation beyond normal session notes. It protects the student by ensuring events are tracked, protects the para by establishing a factual account, and protects the school by demonstrating appropriate response. Done well, it is a straightforward factual account. Done poorly, it creates more problems than it solves. |

When an Incident Report Is Required

Triggering events vary by district, but commonly include:

Physical aggression: student hits, bites, kicks, scratches, or otherwise injures a staff member or peer.

Self-injurious behavior: student engages in head-banging, biting self, scratching, or other self-harm.

Elopement: student leaves the classroom or building without permission.

Restraint or seclusion: any use of physical intervention or removal to a separate space.

Medical events: seizure, allergic reaction, injury requiring first aid or medical attention.

Threat of harm: student makes a credible threat to harm self or others.

Property destruction: significant damage to school property or others' belongings.

When in doubt, file the report. An unnecessary incident report is harmless; a missing incident report for a significant event can create serious problems for the school and the para.

What an Incident Report Must Contain

Most district forms have required fields. Whether the form exists or not, a complete incident report answers:

Who: Student name (or ID if the form uses identifiers), para name, any other staff or students involved.

When: Date, time the incident began, time it ended.

Where: Specific location — not just 'the classroom' but 'the reading corner of Room 14.'

What: A chronological, observable account of what happened. What did the student do? What did staff do? What happened next?

Antecedent: What was happening immediately before the incident? What was the student asked to do? What changed in the environment?

Consequence: How did the situation resolve? What follow-up occurred (nurse called, parent notified, administrator informed)?

Injuries: Any injury to student or staff, even minor, should be noted. 'No injuries observed' is a complete entry when accurate.

Writing the Narrative Section

The narrative is where most incident reports fail. Common problems:

Too vague: 'Student had a behavioral episode.' This tells a reader nothing.

Too interpretive: 'Student intentionally tried to hurt the teacher.' Intent is not observable.

Out of sequence: Events described out of order make it impossible to understand the timeline.

Missing the antecedent: Reports often describe behavior but omit what preceded it, which is often the most important information.

A good narrative is chronological, observable, and specific: 'At 10:15 AM, student was asked to stop playing with the tablet and transition to math. Student said no and remained seated. Para moved closer and repeated the direction. Student stood, grabbed the tablet, and threw it toward the wall. Para moved to a safe distance and calmly said she would wait. After approximately 2 minutes, student sat down. Para offered a choice of math activities. Student selected one and began working at 10:22 AM.'

Completing the Report Under Pressure

Incidents are disruptive. Paras may be shaken, the student may need continuing support, and other students may be present. Some practical strategies:

Make brief notes immediately after the incident, while details are fresh. Even a few keywords written on a sticky note will help when you sit down to write the formal report.

Complete the report before you leave for the day. Memory degrades faster than most people expect, and details that seem obvious now will be uncertain by morning.

Ask a colleague who witnessed the event to confirm your account before submitting, if the form allows.

If you are too distressed to write accurately immediately after an incident, take 20 minutes, then write.

After the Report Is Filed

Filing the report is not the end. Incident reports should be reviewed by a supervisor, who may follow up with questions, request additional information, or trigger a review of the student's behavior plan. The para may be asked to participate in a debrief or functional behavior assessment process.

If incidents are recurring, the pattern in incident reports is often what prompts a team to revisit a student's BIP or support plan. Accurate, consistent incident documentation is how the team knows whether the current plan is working.

| | |

| :-: | :-: |

| ✅ Try this | ⚠️ Watch out for |

| Write the narrative chronologically in observable language. Make brief notes immediately after the incident, and complete the formal report before end of day. When in doubt, file the report. | Wait to file until you can write a perfect report — done and imperfect beats thorough and late. Also avoid omitting incidents because they seem minor or because the para feels responsible for what happened. |

| | |

| :-: | :-: |

| Bottom line | Incident reports exist to protect students, staff, and the school. An accurate, timely, objective account of what happened — including the antecedent, the behavior, the response, and the resolution — is all that is required. Write what you saw, in order, with no editorializing. |

Page of