Incident report: what it is, what goes in it, and how to write one

Last updated 2026-07-09

What is an incident report and why does every workplace need one?

An incident report is a written record of an unplanned event that caused, or could have caused, injury, illness, property damage, or a near miss. It captures the facts right after the event, before memories fade and before anyone starts quietly rearranging the story.

The case for writing one every single time is practical, not bureaucratic. Incident reports give you a paper trail for workers' compensation claims, evidence of good-faith safety management if OSHA shows up, and a pattern-spotting tool that tells you which machines, tasks, or shifts keep producing problems. A single data point is noise. A year of incident reports is a map of your worst hazards.

OSHA's recordkeeping standard, 29 CFR 1904, requires covered employers to log certain work-related injuries and illnesses on the OSHA 300 Log. But that threshold, roughly injuries requiring more than first aid or resulting in days away from work, is the wrong trigger for writing an internal report. Write the report for everything. The near miss where the forklift almost clipped a pedestrian is worth more than the report you write after someone gets hurt, because you still have a chance to fix it. ^[1]

Businesses with ten or fewer employees are partially exempt from OSHA's routine recordkeeping under 29 CFR 1904.1. That exemption does not mean incidents stop mattering, and it does not save you from the phone reporting rules after a fatality or an inpatient hospitalization. ^[2]

What are the required fields in an incident report?

A good incident report answers six questions: who, what, where, when, how, and why. Strip out anything that doesn't serve those six and you have a clean, legally defensible document.

Here are the fields every incident report template should include:

Basic identification

• Report number and date written
• Name of the person completing the report
• Date and exact time of the incident
• Location (building, floor, specific machine or work area)

People involved

• Injured or affected person's full name, job title, department, and length of employment
• Names and contact information of witnesses

Incident description

• What the person was doing at the moment of the incident
• What happened, in plain factual language (not conclusions)
• Equipment, materials, or substances involved
• Environmental conditions at the time (wet floor, poor lighting, loud area)

Injury or damage

• Nature of injury or illness (laceration, strain, chemical exposure, etc.)
• Body part affected
• Property or equipment damaged
• First aid or medical treatment given on-site
• Whether the person was transported for medical care

Immediate response

• Who was notified (supervisor, safety officer, HR)
• Whether the scene was secured or preserved
• Corrective actions taken immediately

Root cause and follow-up

• Probable cause of the incident
• Contributing factors (missing guard, untrained worker, broken equipment)
• Corrective actions planned with owner and due date
• Signature of supervisor or safety manager

OSHA's Form 301, the Injury and Illness Incident Report, captures most of these fields and is a legally acceptable format for employers required to keep records under 29 CFR 1904. ^[3] Use Form 301 as your incident report, or use it as a checklist to confirm your own form is complete.

What types of incidents need a report?

Most safety programs sort incidents into four buckets, and all four earn a written report.

Injuries and illnesses. Any event that harms a worker: cuts, burns, fractures, sprains, chemical exposure, heat illness. If it crosses OSHA's recordable threshold under 29 CFR 1904.7, it also goes on the OSHA 300 Log. ^[4]

Near misses. An event that could have caused injury or damage but didn't. A scaffold board that shifted but nobody fell. A chemical spill contained before anyone was exposed. Near misses are your best early warning system. The National Safety Council promotes near-miss reporting on the logic that unreported near misses precede serious injuries, and the ratio idea behind it (sometimes called the Heinrich Triangle or Bird Triangle) is well established in the safety literature even though the exact numbers move around by study. ^[5]

Property damage. A forklift backing into a rack, a pipe leak that ruins equipment, a vehicle accident on company property. No injury doesn't mean no report.

Security incidents. Workplace violence, theft, vandalism, or threats. These often land in HR files, but they should also feed your safety incident log.

The practical test is simple. If you'd be uncomfortable explaining to an OSHA inspector why you have no documentation of an event, write a report.

How do you write an incident report correctly?

Speed and accuracy are both required. Complete the report within 24 hours. Memory degrades fast, and witnesses scatter. That 24-hour window is not an OSHA rule for internal reports, but it's the professional standard most risk managers and insurers use.

Use factual language, not conclusions. Write "employee's left hand contacted the blade of the table saw," not "employee was careless with the saw." Conclusions about fault belong in the root cause section. The description should read like a security camera transcript.

Be specific about location and time. "Near the loading dock" is useless. "12 feet north of Loading Dock 3, on the painted pedestrian walkway" is useful. Exact times matter for insurance claims and OSHA investigations.

Interview witnesses separately. Group interviews produce one averaged story. Talk to each witness before they compare notes, and record their words with as little editorializing as you can manage.

Find the root cause, more than the immediate cause. The immediate cause of a laceration might be "blade guard removed." The root cause might be "production pressure pushes workers to bypass guards to save time," or "guard replacement parts have been on backorder for three weeks." Fixes aimed only at the immediate cause rarely stop the next one.

Sign and date it. An unsigned incident report is close to worthless in a legal or regulatory setting. The supervisor over the work area should sign. Give the affected employee a copy; they may sign to acknowledge receipt, but that signature should not imply they agree with the facts as written.

If your workplace has a union, read the collective bargaining agreement before you start. Some agreements spell out how investigations run and who takes part.

What does OSHA actually require you to document after an injury?

OSHA's recordkeeping requirements under 29 CFR 1904 apply to most employers with more than ten employees. ^[2] There are three main pieces.

OSHA 300 Log. The injury and illness log where you record each qualifying incident during the calendar year. Retained for five years. ^[4]

OSHA 301 Form. The individual incident report behind each entry on the 300 Log. It must be completed within seven calendar days of receiving information that a recordable injury or illness occurred. ^[3] You can substitute a workers' compensation first report of injury form if it carries the same information.

OSHA 300A Summary. The annual summary of the 300 Log, posted from February 1 through April 30 each year. ^[4]

Severe incidents carry separate reporting duties. You must report any work-related fatality within eight hours, and any work-related inpatient hospitalization, amputation, or loss of an eye within 24 hours, regardless of company size. ^[6] Those are phone reports to OSHA, separate from your internal report. The OSHA hotline is 1-800-321-OSHA.

Some standards add their own documentation duties on top of 1904. The bloodborne pathogens standard at 29 CFR 1910.1030 requires a sharps injury log. The hazard communication standard at 29 CFR 1910.1200 requires records of chemical exposures. Know which standards apply to your industry.

Requirement	Trigger	Deadline	Standard
OSHA 301 Incident Report	Recordable injury or illness	7 calendar days	29 CFR 1904.29
OSHA 300 Log entry	Recordable injury or illness	7 calendar days	29 CFR 1904.29
Fatality report to OSHA	Work-related death	8 hours	29 CFR 1904.39
Hospitalization/amputation/eye loss report	Inpatient or severe injury	24 hours	29 CFR 1904.39
300A Summary posting	Annual	Feb 1 - Apr 30	29 CFR 1904.32

What should a free incident report template include, and where can you get one?

The best free starting point is OSHA's own Form 301, available as a fillable PDF from OSHA.gov. ^[3] It covers every field OSHA needs for recordkeeping. The catch is that it's built for recordable injuries, not near misses or property damage, and it has no fields for root cause analysis or corrective action tracking.

For a real internal template, you want a form that adds three things the 301 leaves out: a root cause section, a corrective action table with owners and due dates, and a near-miss category option.

Microsoft Word format is the most common request because it's easy to edit, needs no software beyond what most businesses already own, and prints clean. A Word incident report template usually runs two to three pages. If you want a free one, your best sources for clean, legally reasonable versions are your state's workers' compensation bureau, OSHA's website, and state OSHA plan offices. ^[7]

Watch out for a few things in templates you find online. Some drop witness contact fields. Many have no root cause section. Some carry signature lines that could read as the employee admitting fault. Read any template closely before you put it into use. A template is a starting point, not a finished safety program.

If you need a full written safety program with incident reporting built in as one piece, SafetyFolio's safety program generator builds OSHA-aligned written programs in about 15 minutes, which is worth knowing if you're starting from scratch.

How is an incident report different from an accident report?

The terms get used interchangeably in most workplaces, and the difference is mostly semantic. Safety professionals have shifted toward "incident" because "accident" implies randomness, as if nothing could have prevented it. "Incident" implies an event you can investigate and prevent. OSHA uses "incident" through most of its guidance.

In practice, the form looks the same either way. What matters more than the title is whether the form captures enough to support root cause analysis and corrective action. A form labeled "Accident Report" with root cause fields and a corrective action table beats an "Incident Report" that only collects basic injury facts.

What are common mistakes that make incident reports useless?

After you read enough incident reports, the failure modes get predictable.

Too late. Reports written days after the event contain reconstructed memory, not facts. The scene has changed, witnesses have talked to each other, and the supervisor has already built a theory. Write it the same day.

Too vague. "Employee slipped and fell" tells you almost nothing. "Employee slipped on water pooled near Floor Drain 4 in the main production aisle at 7:15 a.m., landing on his right knee, about two hours after the floor was last inspected" tells you where to look and what to fix.

Blame in the description. The description is for facts. The second a report says "employee was not paying attention" in the description field, it turns into a liability document pointing at the worker instead of a safety tool pointing at the hazard. Save causal conclusions for the root cause section.

No corrective action with an owner. A report that says "need to fix this" without a name and a date produces nothing. Every corrective action needs a person and a deadline.

Missing witnesses. If three people saw it and the report names one, you've lost evidence. Collect names and contact information for every witness before anyone leaves the scene.

Filed and forgotten. The report goes in a drawer and nobody reviews trends. At minimum, a designated safety person should review all reports monthly and look for repeat locations, equipment, tasks, or times of day. Bureau of Labor Statistics data shows repeat exposures and same-type events drive a large share of total recordable cases. ^[8]

How long do you need to keep incident reports?

OSHA's 1904 standard requires you to keep the OSHA 300 Log, 300A Summary, and 301 Incident Report forms for five years after the end of the calendar year the records cover. ^[4] A report from 2023 has to be kept through at least December 31, 2028.

Keep your internal reports at least that long, and many employment attorneys say longer. Workers' compensation statutes of limitations vary by state, and some occupational illness claims (like long-latency diseases from chemical exposure) surface years after the incident. Check your state's statute of limitations for workers' compensation claims. It's usually one to three years from injury or from discovery of illness, though some states allow longer. ^[9]

Store records so they protect employee privacy. The OSHA 300 Log should leave off the employee's name for certain sensitive conditions (privacy cases under 29 CFR 1904.29(b)(7)), including sexual assaults, mental illness, and HIV infection, among others. Internal reports with medical information should live separately from general personnel files.

What should a sample incident report look like for a real workplace situation?

Here's what a completed report looks like for a common scenario, without inventing a specific company or person.

Scenario: A warehouse worker twists his ankle stepping off the loading dock.

Report Number: WH-2024-047 Date of Report: 2024-03-15 Completed by: Shift Supervisor

Incident Date/Time: 2024-03-15 at 6:42 a.m. Location: Loading Dock 2, north building, step between dock platform and concrete floor Person Involved: Receiving associate, 14 months with company Witnesses: Two coworkers present; names and contact info recorded

Description: At about 6:42 a.m., the employee stepped from the loading dock platform to the concrete floor while carrying a handheld scan device in his right hand. His left foot landed on the edge of the painted step rather than the center, rolling his left ankle outward. He fell to his right side on the concrete floor. The step edge was painted yellow with anti-slip tape applied about 18 months ago. The tape showed wear, and roughly 40% had peeled away from the step edge.

Injury: Left ankle pain, visible swelling. First aid applied on-site (ice pack). Employee transported to urgent care by a coworker at 7:10 a.m.

Immediate Actions: Scene secured. Dock 2 closed pending inspection.

Root Cause: Anti-slip tape on the dock step was worn past serviceable condition. No documented inspection process existed for step surface condition.

Corrective Actions: 1. Replace anti-slip tape on all dock steps (Maintenance Supervisor, due 2024-03-17) 2. Add dock step condition to the monthly safety inspection checklist (Safety Coordinator, due 2024-03-22) 3. Brief all dock workers on the step hazard and proper step technique (Shift Supervisor, due 2024-03-16)

This incident meets the OSHA recordable threshold if the urgent care visit results in restricted work or days away from work beyond the day of injury. The OSHA 301 form gets completed in that case.

Notice what this report does. It gives enough detail to find the exact hazard, it names a systemic failure (no inspection process) instead of just individual error, and each corrective action has a specific owner and deadline.

Do incident reports apply to near misses too, and how should those be handled?

Yes, and near-miss reporting might be the more important habit. A near-miss report filed today can head off the injury report that would otherwise arrive next month.

The barrier to near-miss reporting is almost entirely cultural. Workers don't report near misses because they fear blame, because they figure nothing will happen with the report, or because reporting feels like extra work with no payoff. If your near-miss reports vanish into a folder and nobody visibly acts on them, reporting will stop.

What actually builds a healthy near-miss culture: management responds to every report in view of the crew (even if that's just acknowledging it and laying out the corrective plan), no blame lands on the worker who reports, and there's a fast, simple way to submit. A paper form in the break room works. A QR code on the wall that opens a Google Form works. A shared email inbox works. Pick one and make it obvious.

Near-miss reports should run through the same root cause and corrective action process as injury reports. The form can be shorter, but the analysis should be the same depth. ^[5]

For work involving lockout tagout or other high-hazard tasks, near-miss reports around energy control failures deserve especially fast turnaround on corrective actions.

How do incident reports connect to the rest of your safety program?

An incident report in isolation is just paperwork. Inside a working safety program, it's a feedback loop.

The report feeds your OSHA 300 Log, which feeds your 300A annual summary, which gives you your total recordable incident rate (TRIR). TRIR is calculated as (number of recordables x 200,000) / total hours worked, and it's the number OSHA, insurers, and large clients use to judge your safety performance. ^[8] A TRIR below the industry average is often a condition for bidding certain government or general contractor work.

Incident data should drive your hazard assessments, training decisions, and equipment buys. If three of your last twelve reports involve the same piece of equipment, that's not bad luck. That's a process problem.

A written safety program should spell out your incident reporting procedure in plain language: who completes the report, by when, who it goes to, how it gets reviewed, and how corrective actions are tracked. If you have no written program at all, or yours says nothing about incident reporting, OSHA training resources and OSHA's small business resources are a reasonable place to start. ^[7]

SafetyFolio's safety program generator is one tool that builds these written procedures as part of a complete program, which helps if you want an OSHA-aligned format without writing from scratch.

Frequently asked questions

Is an incident report the same as an OSHA 300 Log entry?

No. The OSHA 300 Log is a running list of all recordable injuries and illnesses for the year. An incident report (OSHA Form 301 or equivalent) is the detailed document for each individual event. Every recordable incident needs both a log entry and a completed incident report. You should also write internal reports for non-recordable events and near misses, which don't go on the 300 Log.

What is the deadline for completing an incident report after an injury?

OSHA requires the 301 Incident Report form within seven calendar days of learning about a recordable injury or illness (29 CFR 1904.29). For your internal report, the professional standard is 24 hours, because reports written days later lose accuracy fast. For fatalities, you must phone OSHA within eight hours; for hospitalizations, amputations, or eye loss, within 24 hours.

Do I need to give the injured employee a copy of the incident report?

Under 29 CFR 1904.35, employees and their representatives can access the OSHA 300 Log and receive a copy of the OSHA 301 form for any incident involving that specific employee, generally within four business hours of the request. For your internal report, most employment attorneys recommend giving the affected employee a copy but having them sign an acknowledgment of receipt rather than an agreement with the facts.

Can a small business with ten or fewer employees skip incident reports?

Employers with ten or fewer employees are partially exempt from OSHA's routine 300 Log and 301 form requirements under 29 CFR 1904.1. But the exemption doesn't cover fatality and severe-injury phone reporting to OSHA, doesn't protect you in a workers' compensation claim, and doesn't remove OSHA's authority to investigate. Writing internal incident reports is still strongly recommended at any size.

What is the best free incident report template in Word format?

OSHA's Form 301 is the most defensible starting point and downloads free from OSHA.gov. For near misses and property damage, you'll need to add fields. State workers' compensation bureaus and state OSHA plan offices often offer free Word-format templates. Look for ones with a root cause section and a corrective action table with due dates; most generic templates online skip both.

Who is responsible for completing an incident report?

The immediate supervisor of the affected work area should complete or directly oversee the report, because they know the task, the equipment, and the conditions. The affected employee should be interviewed as the primary source of what happened. A safety officer or HR manager may review and retain the final report. Don't let completion fall entirely to someone who wasn't there.

What is a near-miss incident report and does it need to be filed with OSHA?

A near-miss incident report documents an event that could have caused injury but didn't. You are not required to file near-miss reports with OSHA; they're an internal safety tool. The value is fixing hazards before someone gets hurt. Organizations with active near-miss reporting programs generally see lower overall injury rates, though the exact size of that effect varies by industry and program design.

Can incident reports be used against employees in disciplinary actions?

Legally, they can be. In practice, using reports mainly as discipline tools kills the reporting culture you need. OSHA's guidance on safety and health program management supports non-punitive reporting systems. If workers believe reporting leads to discipline, they stop reporting. Keep the report focused on hazard identification and correction, and handle genuine policy violations through a separate disciplinary process.

How do you write an incident report for a verbal altercation or workplace violence event?

Use the same framework: who, what, when, where, how. Document the words or actions with direct quotes where possible, and note witnesses. Don't characterize the event as a personality conflict; describe behavior. Workplace violence incidents may trigger OSHA reporting if they cause a recordable injury. They should also be evaluated under any workplace violence prevention program you maintain under OSHA's General Duty Clause.

What happens if an incident report is incomplete or inaccurate?

An incomplete or inaccurate OSHA 301 form can draw a citation under 29 CFR 1904, and OSHA can assess penalties for recordkeeping violations. Beyond regulatory risk, inaccurate reports can expose you in workers' compensation disputes or third-party litigation if the documented facts contradict other evidence. Accuracy matters more than speed, though ideally you hit both inside the 24-hour window.

How is an incident report different from a first report of injury for workers' compensation?

A first report of injury is a form filed with your state's workers' compensation system to open a claim. It's built for the insurance process. An incident report is an internal safety document built for understanding and preventing recurrence. OSHA lets employers substitute a workers' compensation first report of injury for the 301 form if it carries equivalent information. Many employers keep both, because they serve different audiences.

Should incident reports be kept confidential?

Incident reports carry medical information and witness statements that warrant careful handling. The OSHA 300 Log must be available to employees, former employees, and their representatives on request. The 301 form must be available to the affected employee on request. Neither should be casually shared with coworkers or posted publicly. Medical details should be stored separately from general personnel records, in line with ADA and state privacy rules.

What industries have the highest rates of incidents that require reports?

According to Bureau of Labor Statistics data, industries with consistently high total recordable case rates include logging, roofing, animal production (farming), and nursing and residential care facilities. Construction overall runs about two to three times the private-industry average. Industry-specific OSHA standards for high-hazard sectors often add documentation requirements on top of the baseline 1904 recordkeeping rules.

Sources

1. OSHA, Injury and Illness Recordkeeping and Reporting Requirements: OSHA requires covered employers to log work-related injuries and illnesses under 29 CFR 1904
2. OSHA, Partial Exemption for Small Employers (29 CFR 1904.1): Employers with ten or fewer employees are partially exempt from routine recordkeeping under 29 CFR 1904.1 but not from severe-injury reporting
3. OSHA, Form 301 Injury and Illness Incident Report: OSHA Form 301 must be completed within seven calendar days of a recordable injury or illness under 29 CFR 1904.29
4. OSHA, 29 CFR 1904 Recordkeeping Rule Overview: OSHA 300 Log and 301 forms must be retained for five years; 300A Summary must be posted February 1 through April 30
5. National Safety Council, Near-Miss Reporting: Organizations with active near-miss reporting programs see lower overall injury rates; the ratio idea behind it underlies the Heinrich and Bird Triangle safety models
6. OSHA, Reporting Fatalities and Severe Injuries (29 CFR 1904.39): Fatalities must be reported within 8 hours; inpatient hospitalizations, amputations, and eye losses within 24 hours, regardless of company size
7. OSHA, Small Business Resources: OSHA provides free safety and health program resources and template guidance for small employers
8. Bureau of Labor Statistics, Survey of Occupational Injuries and Illnesses (SOII): BLS publishes annual data on total recordable case rates by industry; TRIR is calculated as recordables x 200,000 divided by total hours worked
9. U.S. Department of Labor, Office of Workers' Compensation Programs: Workers' compensation statutes of limitations and claim windows vary by jurisdiction; some occupational illness claims surface years after exposure
10. OSHA, Safety and Health Program Management Guidelines: OSHA guidance supports non-punitive incident reporting systems as part of effective safety and health program management
11. OSHA, 29 CFR 1910.1030 Bloodborne Pathogens Standard: The bloodborne pathogens standard requires a separate sharps injury log in addition to 1904 recordkeeping
12. Bureau of Labor Statistics, Industry Injury and Illness Data: Logging, roofing, animal production, and nursing and residential care facilities consistently show above-average total recordable case rates in BLS data