Incident Report Format (Free Template)

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

Banner illustration for the article: Incident Report Format (Free Template)

A worker slips on an oily floor near a press. He is fine and goes back to work. Nobody writes it down. A month later another worker slips at the same spot and breaks a wrist. The second report is long and urgent. The first report, if it had been written, would have prevented the second event.

A clear incident report format makes writing the report quick and the content useful. This guide gives the fields every report should have, a layout you can recreate in Word or Excel, a sample entry, rules on who fills it and when, and a way to turn reports into action. The format is given inline and no file download is provided.

On this page

What an incident report is for

An incident report is a short factual record of something that happened: an injury, a near miss, damage, a security event or a safety lapse. It captures the facts while they are fresh, supports investigation and shows patterns over time.

Key idea: A good report states what happened, not who to blame. Facts first, causes second, actions third.

Fields every report should have

Section Fields
Basics Report number, date and time of incident, date and time reported, location
People Persons involved, injured or witnessing, with role and department
What happened Plain description in order of events
Injury or damage Nature of injury, body part, first aid or treatment, property or equipment damaged
Immediate action What was done at the scene, who was told
Cause Immediate cause and likely root cause
Corrective action Action, owner, due date
Sign-off Reporter, supervisor, safety officer, date

A layout to copy

INCIDENT REPORT No: INC-____ Date of incident: ________ Time: ______ Reported on: _____________ Time: ______ Location / area: _____________________ Type: [ ] Injury [ ] Near miss [ ] Damage [ ] Fire [ ] Security [ ] Other People involved (name, role, dept): _____________________________________ Witnesses: __________________________ What happened (in order): _____________________________________ _____________________________________ Injury / damage: ____________________ Treatment given: ____________________ Immediate action: ___________________ Likely cause: _______________________ Root cause (why): ___________________ Corrective action | Owner | Due date _____________________________________ Reported by: ______ Supervisor: ______ Safety officer: ______ Date: _______

The format fits one page. Leave enough space for the description, since people write more when the box looks big enough.

A sample entry

Sample (made up) INC-0207 12 March, 14:20 Press shop, bay 3 Type: Near miss What happened: Operator slipped on oil near press P-4. He caught the rail and did not fall. Immediate action: Floor wiped, area coned. Likely cause: Hydraulic hose weeping oil. Root cause: Hose past its replacement date. Action: Replace hose, add to PM schedule. Owner: Maint. Due: 14 March.

Note that the near miss got a full report. It is cheap to write and prevented the injury the second slip could have caused.

Who fills it and when

Step 01

Report quickly

The person involved or the first witness tells the supervisor at once.

Step 02

Write the facts

The supervisor completes the form the same shift, with the person and witnesses.

Step 03

Review

The safety officer checks it within a day and adds the cause and actions.

Step 04

Close out

Actions are tracked to completion, and the report is closed with a date.

Serious injuries and certain events may have legal reporting duties to authorities. Ask your safety officer or adviser which events in your industry and state must be reported and within what time.

Report from the spot, not the office

VisitorFlow Incident Management lets staff report from a phone with photographs and tracks actions to closure.

See Incident Management Software

Writing a good description

  • Write in the order things happened.
  • Use plain facts: what was seen, heard and done.
  • Name roles and equipment, not opinions.
  • Avoid words like careless or negligent.
  • Include conditions: lighting, floor, noise, time into shift.

Our guide on how to write an incident report goes deeper, with examples of weak and strong descriptions.

Types of event to report

Type Example
Injury Cut, fall, burn, strain
Near miss Object falls and misses a worker
Property damage Forklift hits a rack
Fire or spill Small fire, chemical leak
Security Theft, trespass, threat
Environment Oil leak to drain
Health Fainting, heat illness

Our guide on near miss versus incident versus accident explains the differences in detail. For the form, one layout can cover all, with the type ticked at the top.

Photographs and evidence

A phone photograph of the spot taken before the area is cleaned gives more than a paragraph of text. Take wide and close pictures. Note the time. If equipment was involved, record its tag and the date it was last serviced. Keep a copy of any CCTV clip with the report, following your retention rules for video.

Do not move or repair evidence until it has been photographed, unless it is needed to make the area safe.

What happens after the form

Within a day the safety officer should review each report. For minor events a short note of cause and action is enough. For serious events, form a small team with the supervisor, a technician and an employee representative to investigate. Look for the underlying causes, such as poor lighting, missing guards, long shifts or unclear instructions, and not only the final act.

Tell the person who reported what was done. People report more when they see that reports lead to changes.

Using the reports to prevent repeats

A report only pays when someone reads it and acts. Review all reports in a monthly meeting. Count by area, type and cause. Look at open actions and ask why any are late. When the same cause appears twice, find the fix that lasts, not the quick one.

A worked example of a monthly review

Worked example (assumed) Month: 14 reports. By type: 6 near miss, 5 minor injury, 3 damage. By area: press shop 7, stores 4, dispatch 3. Top cause: slips on oil (4). Action: weekly hose and seal check in press shop, mats at bay entrances. Review next month.

The numbers are invented. The method is count, find the pattern, fix it and check next month.

Common mistakes

Reports only for injuries

Near misses are the cheapest lessons.

Blame language

Describe facts, not faults.

Track actions

A report with no closed action prevents nothing.

Another mistake is leaving the form in the office. Keep copies at each supervisor desk and at the gate.

A third is asking for too much detail on the first page. Keep the first page short and attach extras, such as photographs and witness notes.

A fourth is punishing the reporter. If a person is disciplined for reporting a near miss, the next one will go unreported. Keep discipline for ignoring rules, not for speaking up.

A one-week start

Get the form into use.

Step 01

Day 1: form

Print or build the layout and place copies.

Step 02

Days 2 to 4: brief

Tell supervisors what to report and by when.

Step 03

Day 5: review

Read the first reports and agree actions.

Hold the first monthly review within the month, and invite one supervisor from each area. Ask each to bring one event that nearly went wrong and was never written down. The discussion shows people that small events matter, and it brings out the habit of reporting. Over a quarter the number of near miss reports should rise before it falls, which is a good sign: it means people are speaking up.

Five-minute self-check

Check your reporting against these points.

Answer yes or no

  • ☐ Is there one standard form?
  • ☐ Are near misses reported?
  • ☐ Is the report written the same shift?
  • ☐ Do actions have owners and dates?
  • ☐ Is there a monthly review?

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

Reader Q&A

What is an incident report?

A short factual record of an injury, near miss, damage or safety event, written soon after it happens.

What should an incident report include?

Date, time, place, people, a description in order, injury or damage, immediate action, cause, corrective actions with owners and dates, and sign-offs.

Who should fill it in?

The supervisor, with the person involved and witnesses, in the same shift. The safety officer reviews it.

How soon should I write it?

The same shift, while memories are fresh. Serious events may need to be reported to authorities within set times.

Should near misses be reported?

Yes. They show the hazards that have not yet hurt anyone.

Can I keep the form in Excel?

Yes, for modest volume. A digital system adds photographs, alerts and action tracking.

Bottom line

A good incident report is short, factual and followed by action. Use the format above, report near misses too and review the pattern monthly.

Start with the form and a monthly review meeting. Keep the form to a single page, put copies where supervisors can reach them, and tell every new joiner on the first day that reporting a near miss is welcome and not a mark against anyone.

Make incident reporting easy

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