How to Write an Incident Report
A good incident report is short, factual, and written soon after the event. This guide shows the fields to capture and a template you can copy today.
Why Good Reporting Matters
Clear reports help teams spot patterns, act earlier, and help demonstrate due diligence. Missing or vague reports lead to repeated incidents and slower response.
What to Include
Information to Capture
- Summary — one-line description of what happened
- Date and time it occurred
- Location — site, building, area
- People involved or affected, and any injuries
- What happened — factual sequence of events
- Immediate action taken
- Evidence — photos, files, witness names
- Follow-up owner — who closes it out
Tips for clarity
- Stick to facts, not assumptions
- Be specific but brief
- Report as soon as possible
- Use photos when helpful
- Include context others may need
Use a Checklist for Prevention
Pair reporting with routine inspections from our industry checklists:
Make Reporting a Habit
The best incident reports come from teams that report early and see change follow. Start with one real report this week and review it together.