How to Write an Incident Report, with Examples

Published on 10/18/2026 • Updated on 10/22/2026

Banner illustration for the article: How to Write an Incident Report, with Examples

A supervisor writes: Worker was careless and hurt his hand. The safety officer reads it and learns nothing. What was the machine? What was the worker doing? Was there a guard? What first aid was given? Without answers, nobody can stop the next injury.

Writing a good incident report is a skill that can be learned in an afternoon. This guide shows how to structure the report, how to choose words, and what weak and strong versions look like, with examples. It also gives a checklist to use before you sign. For a ready layout, see our incident report format guide.

On this page

What a good report does

A good report lets a person who was not there understand exactly what happened, in order, and see what should change. It is accurate, specific, neutral and complete enough to act on.

Key idea: Write for the reader who must prevent the next one, not for the reader who wants someone to blame.

A simple structure

Step 01

Set the scene

Date, time, place, equipment, task being done, conditions.

Step 02

Tell what happened

Events in order, in plain verbs.

Step 03

State the result

Injury or damage, treatment and who was told.

Step 04

Record what was done

Immediate actions at the scene.

Step 05

Add cause and action

Likely causes, root cause and the fixes with owners and dates.

Choosing words

Instead of Write
Worker was careless Worker reached into the feed area while the press was running
Machine was faulty Guard interlock did not stop the press when the gate opened
Floor was dangerous Oil on the floor, about one metre across, near bay 3
He should have known He had not yet completed the machine safety induction
Bad lighting Light in aisle B was out; reading on meter was low

The right-hand versions are things you can check. The left-hand versions are opinions.

A weak example and a strong one

WEAK Worker hurt his hand on the machine. Supervisor told him to be careful. Sent to first aid. STRONG At 14:20 on 12 March, operator R. Shah was clearing a jam at press P-4, bay 3, with the press switched to auto. His right hand was caught between the die and the guard. The press stopped after the second stroke. He has a deep cut to two fingers. The supervisor applied pressure, called first aid at 14:22 and sent him to the hospital at 14:35. The press was locked out.

The example is made up. The strong version names the task, the state of the machine, the injury, the times and the actions. It also points to the cause: the operator cleared a jam with the press in auto.

Finding the cause

Ask why until you reach something you can change. Stopping at the person usually stops the investigation too early.

Why was his hand in the die? He cleared a jam. Why not with the press off? Switch was in auto. Why not switched off? No rule, no lock-out step. Why no rule? Procedure never written. Root cause: no lock-out procedure for jams.

The fix is a written lock-out step, training and a check, not a reprimand.

Report with photographs from the spot

VisitorFlow Incident Management lets supervisors write the report on a phone, attach pictures and track actions.

See Incident Management Software

Taking witness statements

  • Speak to each witness alone and soon after the event.
  • Ask open questions: what did you see, what did you hear.
  • Write their words, not your summary.
  • Ask them to sign and date the note.
  • Do not discuss one witness account with another.

Keep the statements with the report. Differences between accounts are normal. Note them without trying to settle them on paper.

Examples for three common events

A near miss

At 09:15 on 5 March, a pallet of cartons fell from the second rack in aisle C, about two metres from a picker. The pallet had been placed over the beam edge by a forklift at 08:50. No one was hurt. The area was cleared and the rack inspected. Likely cause: pallet placed off the beam. Action: add a placement check to the forklift routine and retrain the operator.

A security event

At 22:40 on 7 March the night guard saw a person climbing the rear wall near gate 3. The guard shouted and called the security head. The person left on foot. The wall section was checked and a gap in the fence light found. Action: replace the light and add a camera check to the round.

Property damage

At 11:05 on 9 March a forklift struck the corner of rack R-12 while reversing. The beam bent about three centimetres. The area was cordoned and stock moved. Likely cause: blind corner and no mirror. Action: install a convex mirror and a floor marking.

All three are made up for the guide. Each states time, place, what happened, the result, immediate action, a likely cause and a fix.

Sensitive details and privacy

Incident reports hold personal data about people: names, injuries, sometimes health details. Share them only with those who need them for the investigation and the fix. Keep paper copies in a locked file and limit digital access. When you share a report in a safety meeting, remove names unless they are needed. If the report involves a visitor or contractor, record their name and company and keep it with the same care.

Following up with the people involved

Speak to the person hurt, or to the person who raised the near miss, once the report is closed and the fix is in place. Tell them what changed. A short word from the supervisor, or a note on the board, shows that the report led to something. It also encourages others to report next time, which is the real aim of the whole system.

A checklist before you sign

  • Date, time and place are exact.
  • Equipment and task are named.
  • Events are in order.
  • Only facts and quotes are included.
  • Injury and treatment are stated.
  • Actions at the scene are listed with times.
  • Cause and corrective actions have owners and dates.
  • Photographs are attached.

A worked example from start to finish

Worked example (assumed) 14:20 Incident. 14:22 First aid called. 15:00 Supervisor writes the first page. 16:00 Safety officer reviews, adds root cause. Next day: lock-out step added to the work instruction. Day 7: all press operators briefed and signed. Day 30: audit finds the step in use. Report closed.

The report did not end when the page was signed. It ended when the fix was checked.

Common mistakes

Opinion words

Careless, lazy, stupid tell nothing.

Missing times

Times let you check the response.

Close the action

Verify the fix, then close the report.

Another mistake is writing the report days later from memory. Facts fade and details change with each retelling.

A third is copying the last report word for word. Each event is different, and a copied cause hides the real one.

A one-week skills drill

Train supervisors to write better.

Step 01

Day 1: share examples

Show the weak and strong examples.

Step 02

Days 2 to 4: practise

Each supervisor rewrites a past report.

Step 03

Day 5: review

Safety officer gives feedback and agrees a standard.

Repeat for new supervisors, and once a year for everyone. Collect a few of the best rewritten reports, with names removed and details changed, and keep them as models for the next group. A real example from your own plant teaches the standard more clearly than any template can.

Five-minute self-check

Check your last report against these points.

Answer yes or no

  • ☐ Does it name the task and equipment?
  • ☐ Are events in order with times?
  • ☐ Is it free of opinion words?
  • ☐ Does it state a root cause?
  • ☐ Do actions have owners and dates?

Two or more no answers mean this is worth fixing before anything else on your list.

Reader Q&A

How do I start an incident report?

Set the scene: date, time, place, equipment, task and conditions. Then describe what happened in order.

What should I avoid writing?

Opinions, blame and guesses. Write what you saw, heard and did.

How long should it be?

Long enough for a stranger to understand. Most reports fit one page with attachments for photographs and witness notes.

Who should read it?

The supervisor, the safety officer and, for serious events, management and any authority the law requires.

How do I find the root cause?

Ask why repeatedly until you reach something that can be changed, such as a missing procedure or a failed guard.

When is a report closed?

When corrective actions are done and checked, not when the form is signed.

Bottom line

A good incident report is specific, ordered and neutral. It names the task and the equipment, states the facts and ends in actions with owners and dates.

Use the structure above and read every report back for opinion words before signing. If a sentence cannot be checked by someone else, rewrite it until it can.

Write reports people act on

VisitorFlow runs visitor, material gate pass, courier, maintenance and incident workflows on one cloud platform.

See Incident Management Software See Material Gate Pass Software Book a Free Demo
Author of the Blog Post
Aadeshwar Modi
Technical Content Writer at VisitorFlow

Aadeshwar Modi is a marketing technical content writer who loves writing on technology and AI topics.

Recent Post