Incident Report: How to Write One, With a Free Template

What Is an Incident Report?

An incident report is a written record of something unplanned that happened at work, such as an accident, a near miss, a lost laptop or a service failure. It says what happened, when and where, who was involved, and what was done. It sticks to facts and does not assign blame.

When You Need One and Who Reads It

Write one soon after the event, while details are fresh. Your own policy says which events count and by when.

Some work injuries must be reported to a regulator, such as OSHA in the United States, within hours or days, and some data losses carry notice duties. Check your own policy. If an injury, a complaint or a legal claim is possible, ask your safety, HR or legal lead before you file.

The readers are a manager, a safety or compliance lead, sometimes an insurer or a regulator, and later, someone looking for patterns. They were not there. The report must make sense to a stranger a year from now.

What Goes in an Incident Report

1. Basics. Date, time, place and who wrote the report.
2. Summary. Two or three sentences.
3. Timeline. Events in order, each with a time where known.
4. Who Was Involved. Roles, not opinions. Keep personal and health details to the minimum the report needs.
5. Immediate Response. What was done, and by whom.
6. Impact. What was affected: people, equipment, data, service.
7. Likely Cause. Kept apart from the timeline and marked as likely, not proven.
8. Follow-Up. Actions, owners and dates.

How to Write an Incident Report, Step by Step

1. Write Down the Facts Now. Times, places, what you saw and heard.
2. Separate What You Saw from What You Think. A fact can be checked. A guess goes under cause.
3. Put Events in Order. One line each, with a time.
4. Use Roles and Plain Words. Say "the driver," not "the careless driver."
5. Record What Was Done. Calls made, who was told.
6. Name a Likely Cause, and Say How Sure You Are.
7. List Follow-Up Actions with an Owner.
8. Have Someone Who Was There Read It.

A Short Example

This sample is invented.

Date and Place: March 12, warehouse loading bay, about 2:15 p.m. Summary: A pallet of boxes slid off a pallet jack and landed on the floor. No one was hit. Some stock was damaged.

Timeline:

• 2:15 p.m. The pallet tilted on the ramp and slid off.
• 2:16 p.m. The operator stopped work and told the shift lead.
• 2:25 p.m. The area was cordoned off. Eight boxes were set aside as damaged.

Impact: Eight boxes damaged. Bay closed for 40 minutes. Likely Cause (not confirmed): The pallet was not wrapped, and the ramp was wet. Follow-Up: Wrap all pallets before moving (shift lead, by March 19). Dry the ramp each shift (facilities, by March 19).

Common Mistakes

• Mixing Fact and Opinion. "He rushed" is a guess. "The pallet was moved at 2:15 p.m." is a fact.
• Assigning Blame. Describe causes in the process, not in a person.
• Adding Private Detail. Leave out health information unless your policy requires it.
• Skipping Follow-Up. A report with no actions changes nothing.

How to Do It with AI Using the Template

The Logic Lab template, "Write an Incident Report," takes your rough notes and returns a clear report. It builds a timeline, keeps the likely cause apart, and drafts actions.

Checks are built in. Every timeline line is quoted from your notes. Every time and number in the report must appear in your notes. No line may put the fault on a person. Personal and health details are listed so you can remove them. The report ends with a reminder to check it with the people who were there and with your own policy, and that step stays yours.

The template runs in your own AI tool. Logic Lab runs no AI and does not see what you paste. This is a drafting aid, not legal advice, and it cannot tell you what you must report. Follow your organization's rules on what to report.