How to write an incident report (with a simple template)

A good incident report is a clear, factual account of an unplanned event, written soon after it happened, that gives anyone reading it later enough detail to understand and act. The goal is not to assign blame or to write beautifully. It is to capture the truth quickly, while it is still fresh, so the organisation can learn from it and fix the cause.

What makes a good incident report?

A good incident report is timely, factual, complete and objective. Timely, because memory fades fast and detail is lost within hours. Factual, because it records what was seen and done, not opinions about who was at fault. Complete, because a half-filled report leaves the next reader guessing. And objective, because the report is a record, not an argument. Stick to what happened and you produce something an investigator, an insurer or an auditor can rely on later.

One field matters more than any other and is the one people most often skip: what could have happened. A trip that grazed a knee and a trip that nearly went down a stairwell can look identical in a basic log. Recording the potential severity is what tells you which one to worry about. For why those close calls matter so much, see what is a near miss.

How to write an incident report, step by step

Follow these steps in order and you will produce a report that holds up.

1. Make sure the scene is safe first. Tend to any injured people and remove ongoing danger before you write anything. The report can wait a few minutes. Safety cannot.
2. Capture it as soon as you can. Write while the detail is fresh, ideally on the spot. The longer you wait, the more accuracy you lose.
3. State the facts in order. Describe what happened as a simple sequence: what came first, what happened next, how it ended. Use plain language and short sentences.
4. Record the essentials. Date, time, exact location, the people involved, witnesses and the reporter.
5. Describe the outcome and immediate action. Note any injury, ill health, damage or loss, and what was done straight away, such as first aid or isolating a machine.
6. Note the potential severity. Ask what could have happened if luck had not intervened, and record it.
7. Classify it. Choose a consistent category and severity so the report can be trended alongside others later. Categories should be configurable to your work, not forced into a fixed list.
8. Attach evidence. Add photos, readings or documents at the point of capture, while they are easy to gather.
9. Stick to objective language. Write “the guard was not in place”, not “Sam forgot the guard again”. Describe conditions, not character.
10. Submit it to the right person. Route the report so it reaches whoever can triage and act, rather than leaving it in a drawer or a personal inbox.

A simple incident report template

Use this structure as a starting point. Keep it short enough that people actually complete it, and adapt the categories to your own work.

A worked example

Here is the same template filled in, to show the level of detail to aim for. Notice that it stays factual throughout.

• Reporter: Warehouse operative, day shift.
• Date and time: 12 May 2026, 14:20.
• Location: Aisle C, racking bay 14.
• Type of event: Near miss, falling object.
• People involved: One operative in the aisle, one witness on the adjacent forklift.
• What happened: A poorly stacked box slid from the third shelf and fell into the aisle. The operative had walked past the spot around five seconds earlier. No one was struck.
• Outcome: No injury, no damage.
• Immediate action taken: Aisle cordoned off, box removed, bay restacked.
• Potential severity: High. A direct hit could have caused a serious head injury.
• Evidence: Photo of the shelf and the fallen box attached.
• Action and owner: Review stacking standard for bay 14; team leader; within one week.

Common mistakes to avoid

A few habits quietly ruin otherwise good reports. Avoid them and your data stays useful.

• Waiting too long. A report written the next day loses the detail that makes it useful.
• Writing opinions as facts. “He was careless” is a judgement. “The walkway was unlit” is a fact you can fix.
• Leaving out the potential severity. Without it, a serious near miss looks as trivial as a minor one.
• Inconsistent categories. If everyone classifies events differently, you cannot trend them. Keep categories consistent and configurable.
• No owner or due date for the action. A finding with no owner is a finding that never gets fixed.

Once a report is written, it should move into investigation and corrective action rather than sitting still. For what comes next, see incident investigation basics, and for the bigger picture see our guide to incident reporting. Capturing all of this on a phone, with photos attached in the moment, is exactly what digital reporting is built for.

Logincident