A student falls in the playground and breaks an arm. Two students fight in a corridor. A parent alleges a teacher spoke harshly to their child. A stranger is seen near the school gate. In each case, the school will be asked the same questions later — by parents, by the principal, sometimes by authorities: What happened? When? Who was there? What did the school do? A student incident report format exists so the school can answer those questions with a written, dated, factual record instead of with memory and argument.
This guide gives Pakistani schools a complete incident report format: what to record, how to write neutrally, how to collect witness statements, and how to file and follow up so that reports lead to action rather than gathering dust. The format is deliberately simple — a report that takes an hour to write will not be written — and it is designed to protect everyone involved: the student, the staff member, and the school.
Why Incident Reports Protect Students and Schools
Incident reports serve four purposes, and all four matter. First, they protect the student. A written record makes sure a child's experience is taken seriously and followed up — not lost because the day got busy. Second, they protect staff. A teacher accused of something that did not happen is defended by a contemporaneous written record far better than by their own word months later. Third, they protect the school. If a parent complains or an authority asks questions, the school can show it knew, it acted, and it followed a process. Fourth, they reveal patterns. One playground injury is an accident; five injuries in the same corner of the playground in a month is a supervision or design problem that only the records reveal.
The cost of not reporting is easy to see in hindsight: a minor incident unrecorded becomes a major dispute, because each side remembers it differently and nobody can prove what happened. The rule should be simple and known to all staff: if it was serious enough to act on, it is serious enough to write down. That includes injuries, fights, bullying reports, safeguarding concerns, property damage, security incidents, and any complaint from a parent that involves a student's safety or welfare. Minor everyday matters can be logged briefly in a daily log, but anything beyond the trivial deserves the full format below.
What to Record: The Essential Fields
Every incident report should answer the same set of questions, in the same order, so that reports are easy to write and easy to find later. The essential fields are: 1. Incident details — date, time, and exact location (for example, "Tuesday, 14 October, approximately 10:40 am, ground-floor corridor outside Class 6-B"). 2. People involved — full names and classes of students, staff present, and any other people involved, with their roles. 3. What happened — a factual, chronological account of the incident itself. 4. Immediate action taken — first aid given, students separated, parents contacted, medical help called, with the time of each step. 5. Injuries or damage — what harm or damage resulted, if any, described plainly. 6. Notifications — who was informed, when, and how (parent called at 11:05, principal informed in person at 11:15).
7. Witnesses — names of anyone who saw the incident, with their statements attached where taken. 8. Reporter details — the name, role, and signature of the person writing the report, and the date and time it was written. Write the report as soon as possible after the incident, ideally the same day. If the school uses a digital system, build the same fields into the form — see our guide on student record keeping.
Report Template at a Glance
Writing Neutrally: Facts, Not Judgements
The single most important writing skill in incident reporting is neutrality: describe what could be seen and heard, not what you concluded about it. "Ali pushed Hamza in the corridor, and Hamza fell and grazed his knee" is a fact. "Ali, who is always aggressive, attacked Hamza unprovoked" is a judgement — and a judgement that Ali's parents will rightly dispute. Labels such as "bully" or "troublemaker" should never appear in an incident report.
Practical habits that keep reports neutral: write in sequence — what happened first, then next, then next — so the reader can follow the incident like a timeline. Quote direct speech where it matters, in quotation marks, and attribute it ("Hamza said, 'He pushed me first'") rather than paraphrasing it into a conclusion. Separate observation from interpretation — if you believe a student was frightened, write what you saw ("Ayesha was crying and holding her arm") and keep the interpretation out, or label it clearly as your impression. Record what you do not know: "It is not known who started the argument" is honest and useful; guessing is neither.
Witness Statements: How to Collect Them
Witness statements corroborate the report — or, just as usefully, correct it. Collect them promptly, while memories are fresh, and keep them separate from the main report so each account stands on its own. Ask each witness to describe what they saw and heard, in their own words. Each statement should end with the witness's name, role, signature, and the date it was given.
With student witnesses, take extra care. Speak to the child privately, in a calm and reassuring way, with another staff member present where the school's policy requires it. Ask open questions — "What did you see happen?" — not leading ones — "Did Ali push him, didn't he?" Never coach a child toward an answer, and never interview children in front of each other, where accounts quickly converge into a single group story. If a child is distressed, stop, offer support, and return to the statement later or accept a shorter account — a distressed child's forced statement helps nobody. See our guide on complaint management. For staff witnesses, the same principles apply: their own words, their own signature, and no pressure to agree with an existing version.
Filing, Follow-Up, and Tracking
A report that is filed and forgotten is a ritual, not a system. Every incident report needs three things after it is written: a home, an owner, and a deadline. The home is where reports live: a central incident register — a numbered logbook or a digital register — with a copy in the relevant student's file, so reports can be found by date, student, or type of incident. The owner is the person responsible for the follow-up: the section head, the pastoral lead, or the principal, depending on severity. See our guide on parent-teacher meetings.
Follow-up actions should be recorded on the report itself: what was decided, who will do it, and by when — and then checked off when done. A short weekly review by the principal or a designated senior — ten minutes, scanning the week's reports — catches the two failures that matter most: follow-ups that never happened, and patterns nobody noticed. That review is also where the school spots systemic issues: repeated injuries in one location, repeated conflicts between the same students, repeated complaints about one routine. Where an incident involves a disciplinary consequence, the report becomes the evidence base for the next step.
Privacy and Access: Who Sees the Report
Incident reports contain sensitive information about children, and the school has a duty to protect it. Access should be limited to staff who need the report for their role — the principal, the section head, the class teacher, and any staff member directly involved in the follow-up. Reports should be stored securely — a locked cabinet for paper, password-protected access for digital records — and never left on desks, in staff rooms, or on shared screens where other students or parents can see them. See our guide on student data privacy.
Three privacy rules deserve emphasis. First, never share incident reports — or their contents — in staff WhatsApp groups, parent groups, or social media, even in anonymised form; screenshots travel, and "anonymised" details usually identify the child to anyone who knows the class. Second, when parents ask about an incident involving their own child, share what concerns their child, and do not disclose other children's personal details or statements — summarise the school's findings rather than handing over another family's information. Third, keep reports for as long as the school's retention policy requires, and dispose of them securely when it ends.
AI Help: Muse AI
Muse AI is Meta's personal AI assistant, and it can help with everyday school planning work like this. For incident reports, one concrete use is turning rough handwritten notes about an incident into a clear, neutral draft summary — organised in time order and stripped of judgement words — which the reporting teacher then checks and corrects before signing.
Join Muse with invite code LTGSWD — in the Muse app, go to Settings > Redeem token and enter the code.
Disclosure: LTGSWD is the author's Muse invite code.