How to write an incident report that actually holds up

Last updated 2026-07-09

What is an incident report and why does it matter?

An incident report is a written record of any workplace event that caused injury, illness, property damage, or a near miss. It's your account of what happened before memories fade, witnesses scatter, and the details that actually explain the event get lost.

Nobody writes a good incident report for fun. They do it because a clear record protects the business, finds root causes, and satisfies OSHA recordkeeping requirements under 29 CFR 1904 ^[1]. A sloppy report, or worse, no report at all, turns a manageable incident into a citation, a lawsuit, or a repeat injury.

The Bureau of Labor Statistics counted 2.6 million nonfatal workplace injuries and illnesses in private industry in 2023 ^[2]. Most of those generated some kind of internal report. The gap between companies that use those reports to prevent the next injury and companies that file them and forget them is almost entirely about how the report got written.

Say this part plainly. The incident report you write for internal purposes is separate from OSHA's official forms. Your internal report feeds the information you'll use to fill out the OSHA 300 log, the 301 incident form, and any state forms. Get the internal report right and everything downstream gets easier.

What information must be included in an incident report?

Every incident report needs six categories of information, no matter your industry or headcount. Miss one and the report is legally and operationally incomplete.

1. Who was involved Full name, job title, department, length of employment, and shift. If the injured person is a contractor, note the contracting company. Include names and contact information for every witness.

2. What happened A plain-language narrative of the event sequence, written in order. Stick to facts you can verify: what the person was doing, what equipment or materials were involved, what the immediate trigger was. Skip conclusions like "employee was careless." That's an interpretation, not a fact.

3. Where it happened Specific location, more than "the warehouse." Name the exact area, machine, workstation, or address. If location contributed (poor lighting, wet floor, tight clearance), describe those conditions.

4. When it happened Date and exact time of the incident. Also record when it was reported to a supervisor and when the report was completed. Time gaps matter in investigations and workers' comp claims.

5. What injuries or damage resulted Describe injuries in plain, observable terms: lacerations on the left forearm, lower back pain, loss of consciousness. Note whether first aid was given on-site, whether the employee was referred to a physician, and whether they left work early. For property incidents, describe the damage without guessing dollar values yet.

6. Why it happened and what you're doing about it Most reports skip this section or botch it. Separate contributing factors (root causes) from immediate causes. "The forklift struck the shelf" is the immediate cause. "No pedestrian aisle was marked in that section" is a contributing factor ^[3]. Then write specific corrective actions with named owners and deadlines. Not "remind employees to be careful."

A table helps here:

Report Element	What to Include	Common Mistake
Who	Full name, title, tenure, witnesses	Missing contractor info
What	Factual chronological narrative	Opinions mixed with facts
Where	Exact location, conditions	"The warehouse"
When	Incident time + report time	Skipping report timestamp
Injuries/Damage	Observable terms, medical referral	Speculative severity
Root Cause	Contributing factors, more than triggers	Blaming the employee
Corrective Action	Named owner, specific fix, deadline	"Remind employees"

When do you need to file an incident report?

Start your internal incident report within 24 hours of the event, ideally the same shift. The longer you wait, the more details drift. Witnesses start agreeing with each other's versions. The injured worker's memory of the sequence shifts. Physical evidence gets cleaned up or moved.

OSHA's timelines are tighter and legally binding. Under 29 CFR 1904.39, employers must report any work-related fatality to OSHA within 8 hours ^[4]. Any in-patient hospitalization, amputation, or loss of an eye must be reported within 24 hours. You report by calling 1-800-321-OSHA or filing through OSHA's online reporting page.

Separately, injuries and illnesses that meet OSHA's recording criteria get entered in your OSHA 300 log within 7 calendar days of learning about the incident ^[1]. The 300A annual summary must be posted every year from February 1 through April 30.

Near misses deserve reports too, even when nothing OSHA-recordable happened. A near miss today is often an injury next month under slightly different conditions. Companies that document near misses tend to run lower injury rates over time because they fix the condition before someone gets hurt, not after.

If your state runs its own OSHA-approved plan (there are 22 state-plan states covering private employers), your timelines may differ ^[5]. California's Cal/OSHA, for one, requires reporting a serious injury within 8 hours regardless of hospitalization status.

What is the step-by-step process for writing an incident report?

Here's how to actually do it, in order.

Step 1: Secure the scene and provide care first. Nothing on this list beats getting the injured person medical attention. Once that's handled, preserve the scene if you can. Take photos before anything is moved or cleaned. If a machine was involved, keep it locked out until the investigation is done.

Step 2: Notify the supervisor and HR immediately. The supervisor should be at the scene. HR needs to know because workers' comp starts the clock from the date of injury.

Step 3: Interview the injured worker and witnesses separately. Separate interviews keep witnesses from aligning their stories. Ask open-ended questions: "Walk me through what you were doing before this happened." Document what people say in their own words, in quotation marks when possible. Note the time and date of each interview.

Step 4: Document the physical environment. Photograph the exact location from several angles. Measure anything relevant (aisle width, shelf height, clearance). Note environmental conditions: lighting level, floor surface, temperature if relevant, time of day and shift. Check whether required signage or guarding was in place.

Step 5: Review related records. Pull the maintenance log for any equipment involved. Check training records for the injured employee on the relevant task. Look at prior incident reports from the same area or equipment. This context is what separates a surface-level report from one that actually finds root causes.

Step 6: Write the narrative while facts are fresh. Plain language. Past tense. Separate what you know from what you're inferring. If something is uncertain, say so: "Employee reports she did not hear the warning alarm; it is unclear whether the alarm sounded."

Step 7: Identify root causes with a structured method. The 5 Whys technique handles most simple incidents. Ask why the incident happened, then why that underlying condition existed, and keep going until you reach a systemic cause. For complex events, a fishbone diagram (cause-and-effect diagram) organizes multiple contributing factors ^[6].

Step 8: Write specific corrective actions. Each action gets a named owner and a due date. "Safety manager will install anti-fatigue mats at Station 4 by July 25" is a corrective action. "Management will look into mats" is not.

Step 9: Get signatures. The supervisor who investigated signs. The department manager signs. The injured employee should get to review the report and note any disagreement. Some organizations add a union rep signature where applicable.

Step 10: File and follow up. Enter the information in your OSHA 300 log if it qualifies. File the report somewhere secure but accessible. Set a calendar reminder to verify corrective actions were completed. A corrective action nobody verifies might as well not exist.

What does OSHA actually require you to record and report?

OSHA's recordkeeping rule, 29 CFR Part 1904, applies to employers with 11 or more employees in most industries ^[1]. Employers with 10 or fewer employees, and employers in certain low-hazard industries (a list OSHA keeps by NAICS code), are partially exempt from routine recordkeeping but still must report fatalities, hospitalizations, amputations, and eye losses.

An injury or illness is OSHA-recordable if it's work-related, is a new case, and meets at least one of these: it results in days away from work, restricted work or job transfer, medical treatment beyond first aid, loss of consciousness, a significant injury or illness diagnosed by a healthcare professional, or it's one of several specific conditions (hearing loss, cancer, tuberculosis, needlestick, and others) ^[1].

Three OSHA forms are involved:

• OSHA 300 Log: the running list of recordable injuries and illnesses for the year.
• OSHA 300A Summary: the year-end summary posted for employees each February through April.
• OSHA 301 Incident Report Form (or equivalent): detailed information about each recordable case, completed within 7 days.

OSHA's posting instruction reads: "You must post the 2024 Summary of Work-Related Injuries and Illnesses (OSHA Form 300A) from February 1 through April 30, 2025" ^[11]. The forms must be kept for 5 years following the end of the calendar year they cover.

Electronic submission is required for certain employers. As of 2024, establishments with 100 or more employees in designated high-hazard industries must submit their 300 log data electronically each year through OSHA's Injury Tracking Application (ITA). Establishments with 20 to 99 employees in high-hazard industries must submit their 300A summary data ^[10].

For a broader look at what OSHA is and how the pieces fit, see our overview of osha.

How do you write the narrative section without making legal mistakes?

The narrative is where most incident reports go wrong, usually one of three ways: too vague to be useful, assigns blame in a way that creates liability, or presents speculation as fact.

Write in plain past tense. "At 10:14 a.m., James Rivera was operating forklift #3 in aisle 7 when the left tine struck a pallet rack support column. The impact threw Rivera forward against the steering column." That's factual. "Rivera failed to pay attention and hit the rack" is an interpretation and a legal problem.

Keep conclusions about fault or negligence out of the narrative. Those determinations, if they matter at all, belong in a separate section or a separate HR document. Your incident report is a factual reconstruction, not a disciplinary record.

Do include measurements and observable conditions. "The aisle measured approximately 8 feet wide at the point of impact; the forklift manufacturer specifies a minimum 9-foot aisle for that model" is the kind of specific statement that makes a report useful for both prevention and any later legal review.

If you don't know something, say so out loud. "It is unknown whether the pedestrian warning light at the aisle entrance was illuminated at the time of the incident." That's honest. Leaving it out is worse, because it creates an apparent gap someone will notice later.

One habit that works: read the narrative back to yourself and ask whether a person who wasn't there would understand exactly what happened. If the answer is no, add specifics until it's yes.

What is root cause analysis and how do you do it in an incident report?

Root cause analysis (RCA) means going past the surface event to find the systemic conditions that made the incident possible. It's what separates a useful report from a form that documents the injury and files it away.

The 5 Whys is the most common tool for small businesses, and it started at Toyota ^[6]. Take the immediate event and ask why it happened. Take that answer and ask why again. Repeat until you reach a cause that, if fixed, would actually stop it from happening again. Five rounds is a rough guide. Some incidents resolve in three; complex ones take more.

Here's how it looks:

• Incident: Employee slipped and fell on the warehouse floor.
• Why 1: The floor was wet.
• Why 2: A forklift battery was leaking acid and water from that morning's charging cycle.
• Why 3: The battery had a visible crack noted in last week's inspection but was never removed from service.
• Why 4: No written policy requires cracked batteries to be tagged out and inspected before further use.
• Why 5: Battery inspection criteria were never defined in the maintenance program.

The root cause is the missing policy, not the wet floor. The corrective action is drafting and enforcing a battery inspection standard, more than mopping more often.

For complex incidents with equipment or multiple contributing factors, a fishbone diagram (also called an Ishikawa diagram) helps. It sorts causes into categories: equipment, environment, methods, materials, people, and management. It's handy when you need to present findings to a safety committee or senior management.

Document the RCA process in the report, more than the conclusion. Show your work. An investigator or attorney reviewing the report later needs to see how you got to your root causes, not only what you decided.

What are the most common incident report mistakes and how do you avoid them?

These are the mistakes OSHA citations and workers' comp disputes surface most often.

Waiting too long to write it. Reports written days after an incident lean on reconstructed memory, which is unreliable. Write within 24 hours. For serious incidents, start within the hour.

Writing "employee was careless" or similar blame statements. This creates liability and adds nothing useful. Stick to observable facts.

Vague corrective actions. "Retrain employees" with no owner, no content, and no date is close to meaningless. If a corrective action isn't specific enough to verify, rewrite it.

Skipping near misses. OSHA doesn't require you to record near misses since no injury occurred, but companies that ignore them miss the clearest warning signs they have ^[3].

Not reviewing prior reports for patterns. If this is the third slip-and-fall in the same spot in two years, that's a pattern. The report for incident three should reference incidents one and two by name.

Using the wrong form or skipping OSHA forms entirely. Your internal report doesn't replace the OSHA 301. They do different jobs.

Incomplete witness information. Witnesses sometimes leave the company. Get full contact details at the time of the incident, not weeks later.

Forgetting to verify corrective actions. The follow-up step is the one people skip most. Assign someone to confirm completion and document it.

Does an incident report format differ by industry?

The core elements stay the same across industries. The specific questions and emphasis shift with the hazards involved.

In construction, reports usually need to note contract structure (who's the general contractor, which sub was involved), fall heights and fall protection status, permit requirements for the work, and whether any excavation or confined space entry happened. OSHA's construction standards under 29 CFR 1926 flag specific incident types that need particular documentation ^[7].

In healthcare, needlestick and sharps injuries trigger a separate log (the Sharps Injury Log) and generally require post-exposure protocols. The report should capture the type and brand of device if known, the procedure being performed, and how the exposure happened ^[8].

In manufacturing, machine-guarding failures, lockout/tagout gaps, and chemical exposures each carry specific regulatory weight. A lockout tagout incident, for example, should document whether an authorized lockout procedure existed, whether it was followed, and whether the equipment was serviced under that procedure.

In retail and food service, the common incidents are slips, falls, and repetitive-motion injuries. Reports here often underplay environmental factors like floor maintenance schedules and footwear requirements, which is usually exactly where the fixable problems live.

The principle holds regardless of industry: match the format to your hazard profile. A generic form beats no form, but a form built around your actual hazards gets you better data.

How do you handle confidentiality when sharing incident reports?

Incident reports hold sensitive personal information about the injured worker. They also expose operational problems you'd rather not circulate freely. Handle them carelessly and you create both privacy and legal exposure.

Baseline rule: limit access to the full report to people with a direct need to know. That usually means the investigating supervisor, HR, the safety manager, senior management, and any outside party with a legal right (workers' comp carrier, OSHA inspector).

OSHA's recordkeeping rule gives employees and their representatives access to injury and illness records. The 300 log must be available to current and former employees, their representatives, and their physicians within 7 business hours of a request ^[1]. That access rule covers the 300 log specifically, not necessarily your detailed internal investigation report.

When you share findings with a broader group (a safety meeting, a department email), summarize the lessons without naming the injured employee. "A hand laceration occurred at Station 7 due to inadequate guarding on the band saw" works for a general safety communication. Using the employee's name does not.

For workers' comp, the report goes to your insurer. Be factual and complete. Insurers use it to decide coverage and investigate the claim, and errors or omissions here complicate the process.

If litigation looks possible, bring your attorney in before the report is finalized. Attorney-client privilege may cover parts of the investigation, depending on how it's structured and your jurisdiction.

How do safety programs and incident reports connect?

An incident report earns its keep when it feeds back into a living safety program. Without that connection, you're just stacking up documentation instead of reducing risk.

Every report should trigger a review of whatever written procedure or program element applies to the incident. If someone gets hurt because a hazard communication training gap left them unaware of a chemical hazard, the report should flag that gap and the program should get updated to close it.

This is where a well-built safety program pays off. When you have written programs for each hazard area, a report can point straight at the gap: "Procedure 4.3 requires weekly inspection of the battery charging area, but records show no inspection was completed in the prior three weeks." That's an actionable finding.

If your business doesn't yet have a formal written safety program for each relevant OSHA standard, incident reports get harder to write well, because you have no baseline to measure against. SafetyFolio's safety program generator produces those written programs in about 15 minutes, which gives you the documented baseline that makes incident investigation useful.

Review your reports in aggregate at least quarterly. Look for patterns by location, shift, task, equipment, or tenure. New employees (those with less than a year on the job) show up disproportionately in workplace injury data, a pattern BLS documents consistently ^[2]. If your reports show that pattern, your osha training program needs to address it head-on.

What's the difference between an incident report and an OSHA 301 form?

People mix these two up, and the confusion has real consequences.

Your internal incident report is a document you create in your own format, at whatever level of detail the investigation needs. There's no single federally mandated format for it. It's your primary investigation document and can run as long and detailed as the incident warrants.

The OSHA 301 (or your state's equivalent) is a specific federal form required for each recordable injury or illness. OSHA calls it the "Injury and Illness Incident Report" and specifies the exact fields it must contain ^[11]. You must complete it within 7 calendar days of learning about a recordable case, and keep it for 5 years.

The 301 is shorter and more standardized than a good internal report. It captures the basics: who, what injury, what body part, what treatment. Your internal report captures root causes, witness statements, photos, corrective actions, and follow-up timelines, none of which appear on the 301.

You can use a substitute form for the 301 if it contains all the required information. Many workers' comp first report of injury (FROI) forms qualify. Check your state plan or workers' comp carrier to confirm.

The practical workflow: write your detailed internal report first, then use it to populate the OSHA 301 and your 300 log. The internal report is the source document. The OSHA forms are the regulatory output.

For a closer look at form types and recordkeeping, our dedicated incident report resource covers it in more detail.

Frequently asked questions

How soon after an incident do you need to write an incident report?

Write your internal incident report within 24 hours of the event. For OSHA reporting, work-related fatalities must be reported within 8 hours under 29 CFR 1904.39. Hospitalizations, amputations, and loss of an eye must be reported within 24 hours. The OSHA 301 form for any recordable injury must be completed within 7 calendar days of learning about the case.

Who is responsible for writing an incident report at a small business?

The injured employee's direct supervisor usually leads the investigation and writes the report, with input from HR and the safety manager where those roles exist. In small businesses without dedicated safety staff, the owner or ops manager handles it. What matters more than who writes it is that the person can document conditions honestly and assign corrective actions to people who will follow through.

Does OSHA require a specific incident report format?

OSHA does not require a specific internal incident report format. It does require specific forms for recordable cases: the OSHA 300 log, the 300A annual summary, and the OSHA 301 incident report (or an acceptable equivalent). Your internal investigation document can use any format, but it should cover who, what, where, when, injury or damage details, root causes, and corrective actions.

What is the difference between a recordable and a reportable incident under OSHA?

Recordable incidents meet OSHA's criteria under 29 CFR 1904 and must be entered in the 300 log within 7 days. Reportable incidents are a narrower set requiring immediate notification to OSHA: fatalities within 8 hours, and in-patient hospitalizations, amputations, or eye losses within 24 hours. All reportable incidents are recordable, but not all recordable incidents are reportable.

Can an employee refuse to give a statement for an incident report?

An employee can decline to provide a written statement, though most company safety policies require cooperation with investigations. OSHA's anti-retaliation provisions under Section 11(c) of the OSH Act protect employees who report injuries; they do not protect refusal to participate in an investigation. Practically, document your attempt to interview the employee and proceed using other available information.

Should you include near misses in incident reports?

Yes. Near miss reporting is one of the highest-value safety practices available to small businesses. OSHA does not require you to record near misses on the 300 log since no injury occurred, but documenting them internally lets you fix hazardous conditions before someone gets hurt. Organizations with active near miss reporting consistently show lower injury rates over time.

How long do you need to keep incident reports?

OSHA requires you to keep the 300 log, 300A summary, and 301 forms for 5 years following the end of the calendar year they cover. Keep internal investigation reports at least as long. Many employment attorneys recommend longer (7 to 10 years) given statute of limitations issues in workers' comp and civil litigation. Confirm retention requirements with your state workers' comp carrier.

What should you never write in an incident report?

Avoid blame statements like "employee was careless" or "worker failed to follow instructions." These are interpretations, not facts, and they create liability without adding useful information. Don't speculate about medical diagnoses. Don't include information you got from rumor rather than direct observation. Avoid vague corrective actions like "retrain workers." Never falsify or alter a report; that creates federal criminal exposure under OSHA's recordkeeping rules.

Do contractors and temporary workers need to be included in your incident reports?

It depends on who controls their day-to-day work. Under 29 CFR 1904.31, you must record injuries to employees on your payroll and to other workers you supervise day-to-day, including temporary workers placed by a staffing agency if you direct their work. Truly independent contractors (managing their own methods) are typically recorded by their own employer. When in doubt, coordinate with the staffing agency in writing.

What's the best way to identify root causes in a workplace incident?

The 5 Whys method works for most small-business incidents: start with the immediate event and ask why five times, digging deeper with each answer until you reach a systemic cause. For complex events with equipment or multiple factors, a fishbone (Ishikawa) diagram organizes causes by category. The goal is finding the condition or policy gap that, if corrected, actually prevents recurrence rather than just describing the accident.

How do you write an incident report for a near miss with no injury?

Use the same structure as an injury report: who was involved, what happened, where and when, what conditions existed, and what corrective action you're taking. The injury section simply notes that no injury resulted. Log the near miss in your internal tracking system and review it in safety meetings. Near miss reports often surface the most fixable problems, because the pressure to move on quickly is lower than after a real injury.

Can an incident report be used against you in court?

Yes, potentially. Internal incident reports are generally discoverable in civil litigation and workers' comp disputes. That's a reason to write them carefully and factually, not a reason to write less. A factual, thorough report showing you investigated and took corrective action is usually better protection than a vague or absent one. Consult your attorney before finalizing a report for a serious incident if you anticipate litigation.

What industries have the highest rates of workplace injuries requiring incident reports?

According to the Bureau of Labor Statistics, construction, manufacturing, transportation, and healthcare consistently show the highest injury and illness rates among private industries. In 2023, BLS data showed total recordable case rates above 3.0 per 100 full-time workers in several goods-producing and service sectors. These industries carry the most active reporting obligations and gain the most from strong investigation programs.

Do you need special software to write an incident report?

No. A well-designed paper or PDF form works fine for most small businesses. The value is in the quality of the investigation and writing, not the platform. Purpose-built safety management software (tools like Intelex, Origami, or SafetyCulture) helps businesses with high incident volume or multiple sites by streamlining 300 log management and corrective action tracking. For a small business with occasional incidents, a consistent template and a shared folder are enough.

Sources

1. OSHA, Recordkeeping Rule 29 CFR Part 1904: OSHA requires employers to record qualifying injuries on the 300 log within 7 calendar days, retain records for 5 years, and make the 300 log available to employees within 7 business hours of a request
2. Bureau of Labor Statistics, Employer-Reported Workplace Injuries and Illnesses 2023: BLS reported 2.6 million nonfatal workplace injuries and illnesses in private industry in 2023; new employees are disproportionately represented in injury data
3. OSHA, Recommended Practices for Safety and Health Programs: OSHA distinguishes immediate causes from contributing factors (root causes) in incident investigation guidance; near miss reporting is recommended even though not required by recordkeeping rules
4. OSHA, Reporting Fatalities and Severe Injuries, 29 CFR 1904.39: Employers must report work-related fatalities to OSHA within 8 hours and in-patient hospitalizations, amputations, or eye losses within 24 hours
5. OSHA, State Plans: 22 state-plan states administer their own OSHA-approved programs for private employers; some states (including California) have stricter reporting timelines than federal OSHA
6. National Safety Council, Incident Investigation: NSC recommends the 5 Whys and fishbone diagram as standard root cause analysis tools for workplace incident investigation
7. OSHA, Construction Standards 29 CFR 1926: Construction-specific OSHA standards under 29 CFR 1926 include incident documentation requirements related to fall protection, excavation, and permit-required confined spaces
8. OSHA, Bloodborne Pathogens Standard 29 CFR 1910.1030 and Sharps Injury Log: Healthcare employers must maintain a separate Sharps Injury Log under 29 CFR 1910.1030 for needlestick and sharps injuries, capturing device type, procedure, and how exposure occurred
9. OSHA, Injury Tracking Application (ITA) Electronic Submission: Establishments with 100 or more employees in high-hazard industries must submit 300 log data electronically via ITA; establishments with 20-99 employees in high-hazard industries must submit 300A summary data
10. OSHA, Recordkeeping Forms and Instructions (300, 300A, 301): OSHA specifies the 300 log, 300A summary, and 301 incident report as the three required recordkeeping forms; the 300A must be posted February 1 through April 30; workers' comp first report of injury forms may substitute for the 301 if they contain all required information