An incident or occurrence report is a tool used to document, analyze, and prevent workplace injuries

Last updated 2026-07-09

What is an incident or occurrence report actually used for?

An incident report does four jobs at once. Confusing them is why most companies do it badly.

Job one is factual documentation. You are creating a timestamped, written account of what happened before memory fades, witnesses quit, or a lawyer coaches everyone. Courts and OSHA inspectors treat your report as a contemporaneous record, which means it carries more weight than somebody's recollection six months later.

Job two is root-cause analysis. A good report does not stop at 'worker tripped on cord.' It traces back to why the cord was there, who owned housekeeping in that zone, whether that person was trained, and whether a hazard walk had covered the area recently. Skip that chain and you fix the symptom while the cause sits there waiting to trip the next person.

Job three is OSHA recordkeeping. Under 29 CFR 1904, employers with more than ten employees in most industries must record work-related injuries and illnesses that cause days away from work, restricted work, job transfer, medical treatment beyond first aid, loss of consciousness, or a significant diagnosis by a healthcare professional ^[1]. The incident report feeds your OSHA 300 Log.

Job four is trend analysis. One incident tells you almost nothing. Twelve incidents in a year, mapped by department, time of day, and task, tell you exactly where your safety program is leaking. That only works if every report is built the same way.

None of that happens with a two-line form that reads 'employee hurt knee, sent to clinic.' The quality of the report decides everything downstream.

What is the difference between an incident report and an OSHA recordable?

They are related but not the same, and mixing them up creates real compliance problems. An incident report is an internal document. An OSHA recordable is a legal classification. You write the first for almost everything. You decide the second against a specific test.

Write an incident report for any event worth investigating: injuries, illnesses, near-misses, property damage, unsafe conditions. You should write one for a near-miss where nobody got hurt at all.

Under 29 CFR 1904.7, an injury or illness is recordable if it is work-related, is a new case, and meets at least one general criterion: days away from work, restricted duty, job transfer, medical treatment beyond first aid, loss of consciousness, or a significant diagnosis ^[1]. Meet that threshold and you must log it on the OSHA 300 Log within seven calendar days of learning the case is recordable ^[2].

The practical rule is simple. Write an internal report for everything. Decide separately whether OSHA's criteria force you to log it. A worker who stumbles but catches themselves generates a report (near-miss, worth investigating) and no 300 Log entry. A worker who needs prescription-strength anti-inflammatory after that stumble generates both.

The Bureau of Labor Statistics counted about 2.6 million nonfatal workplace injuries and illnesses in private industry in 2023, at a rate of 2.4 cases per 100 full-time workers ^[3]. Every recordable case started as some version of an incident report. The ones that never got written up are the invisible risk sitting in your facility right now.

What information does a complete incident report need to include?

OSHA does not mandate a single federal form for your internal report. Form 301, the Injury and Illness Incident Report, satisfies the recordkeeping rule for cases that go on the 300 Log, but most companies use a more detailed internal form and transfer the relevant data over to 301 ^[2].

A complete internal report covers:

Basic facts. Date, time, exact location. Employee name, job title, department, and time in that role. The supervisor on duty.

Narrative of the event. Plain language describing what the employee was doing, what went wrong, and the sequence that led to the outcome. Capture the employee's first-person account if possible, plus the supervisor's independent account.

Injury or illness description. The specific body part, the nature of the injury (laceration, strain, burn), and the object or substance involved.

Witness information. Names and contact details for anyone who saw the event or the conditions behind it.

Medical treatment. Where the employee went, what was done, and whether prescription medication, restricted duty, or days away resulted. This is what determines recordability.

Root cause and contributing factors. The section most forms skip. Equipment failure? Missing training? Missing PPE? A procedural gap? Pressure to work too fast? Bad lighting? You need honest answers.

Corrective actions. Specific steps, a named owner, and a due date to prevent recurrence.

Form 301 covers the factual and medical pieces and barely touches root cause ^[2]. Build your internal form to go further. That is where the prevention value lives.

Report component	Required for OSHA 301	Needed for root-cause prevention
Date, time, location	Yes	Yes
Employee and job info	Yes	Yes
Injury/illness description	Yes	Yes
Medical treatment detail	Yes	Yes
Root cause analysis	No	Yes
Corrective actions with owner + deadline	No	Yes
Near-miss documentation	No	Yes
Witness statements	No	Yes

Does OSHA require you to file an incident report?

OSHA does not require a specific internal form for every event. It requires something narrower: recording qualifying injuries and illnesses on the 300 Log, the 300-A Summary, and the 301 Incident Report form, and keeping those records for five years ^[2].

Separately, 29 CFR 1904.39 requires you to report severe incidents directly to OSHA by phone or online inside strict windows. Fatalities go in within 8 hours. Any in-patient hospitalization, amputation, or loss of an eye goes in within 24 hours ^[4]. That is a reporting duty to the agency itself, not internal paperwork.

The practical answer for a small business: yes, you need a written process for documenting incidents, and yes, serious ones trigger federal reporting. OSHA will ask to see your internal reports during an inspection after a serious event. You want them for that, and you want them to run your safety program with your eyes open instead of shut.

If you have ten or fewer employees, you are partially exempt from routine 300 Log maintenance, but you still must report fatalities, hospitalizations, amputations, and eye losses under 1904.39 ^[4]. The exemption changes your paperwork. It does not change the fact that incidents still cost you money and people.

What is a near-miss report and why does it matter more than you think?

A near-miss is an unplanned event that caused no injury and no property damage but easily could have. Safety people call it a free lesson, and that is exactly what it is.

Heinrich's triangle, a model from industrial safety research first published in 1931, proposed that for every serious injury there are many minor injuries and many more near-misses beneath them. The exact ratios Heinrich cited have been picked apart in later research (Fred Manuele's work in Professional Safety has questioned the empirical basis for the specific numbers), but the direction holds: near-misses are far more frequent than injuries, and they expose the same hazards before anyone bleeds.

OSHA pushes near-miss reporting on purpose. Its guidance on incident investigation says near-misses should be investigated with the same rigor as actual injuries because they usually reflect the same system failures ^[5].

The barrier is culture, not process. Workers do not report near-misses when they expect to get punished for it. A 2021 survey by the National Safety Council found 66 percent of workers said they would be less likely to report a near-miss if they thought it would lead to punishment ^[6]. Your reporting system is only as good as the trust behind it. When people believe reporting brings blame, they stop reporting, and your early-warning system goes dark.

Keep the near-miss form short. Five fields, maximum. Print the non-punitive promise right on it. The goal is information, not accountability theater.

Who is responsible for completing an incident report?

It depends on your written safety program, but the process that actually works puts several people on it at different stages. Single-author reports are where small businesses go wrong.

The injured or affected employee should complete their portion as soon as they are medically able. Their first-person account of what they were doing and what they felt is irreplaceable, and delay strips out the detail.

The direct supervisor fills out their section separately, before comparing notes with the employee. You want two independent accounts, not one story that has already been talked over. The supervisor usually owns the initial corrective-action fields too.

A safety officer or operations manager reviews the finished report within 24 to 48 hours, checks that the root cause says more than 'employee error,' and confirms every corrective action has an owner and a due date.

For anything potentially recordable, whoever keeps your OSHA 300 Log needs to know right away. Under 29 CFR 1904.29, you must record the case on the 300 Log within seven calendar days of learning it meets the criteria ^[8].

The classic failure: a supervisor fills out the form alone, drops it in a drawer, and nothing changes until OSHA shows up asking about it. Build a process where at least two people see every report and one named person tracks whether corrective actions actually close. If you want a written safety program that bakes this workflow in from the start, SafetyFolio's program generator writes incident reporting procedures straight into your program document in about 15 minutes.

How do incident reports connect to your overall OSHA written safety program?

An incident report is not a standalone document. It is one output of a larger safety system, and its value multiplies when it feeds back into that system instead of dying in a folder.

Under OSHA's Recommended Practices for Safety and Health Programs, incident investigation is one of the core elements, alongside hazard identification, hazard prevention and control, education and training, program evaluation, worker participation, and management leadership ^[5]. The incident report is the paper trail of the investigation element.

Here is the loop. A hazard-identification program finds risks before they bite. Training cuts human error. When an incident happens anyway, the report captures what hazard-ID missed or what training failed to stop. The corrective actions from that report update your hazard controls and, when it fits, your training. Program evaluation then checks whether the same incident comes back.

Without incident reports, the loop breaks. You cannot judge whether your safety program works if you have no record of when it failed.

That is why your written program needs a section spelling out the incident reporting procedure: who fills out what form, in what timeframe, who reviews it, and how corrective actions get tracked. OSHA does not dictate the format, but inspectors look for evidence of a systematic process. A program that lives only in someone's head is not a program.

For a picture of what a full written safety program should contain, OSHA's injury and illness prevention guidance is a solid starting point ^[5]. And if you want the wider osha compliance context, the agency's structure and enforcement priorities are worth knowing.

What are the most common mistakes in incident reports?

Look at what OSHA cites during inspections and what safety pros flag over and over, and the mistakes fall into a few tight patterns.

Vague language. 'Employee was injured' is not a report. You need the body part, the mechanism (how it happened), and the exact task in progress. Vague wording makes the report legally weak and kills any chance at useful root-cause work.

Premature blame. 'Employee was not paying attention' is a conclusion dressed up as analysis. It shuts down inquiry and guarantees recurrence, because it never asks why the worker's attention slipped or why the task demanded nonstop vigilance in the first place.

No corrective action, or one with no owner. 'Remind employees to be careful' is not a corrective action. Real ones name a specific change (new guard installed, procedure revised, area re-lit), a person responsible, and a deadline.

Late completion. Every hour after an incident, memory fades and the scene changes. OSHA guidance says to start investigations immediately ^[5]. In practice that means hours for serious events and within a day for minor ones.

Missing near-misses. If your data shows only injuries and zero near-misses, your reporting culture is broken, not perfect. In a healthy environment near-misses outnumber injuries by a wide margin.

Never closing the loop. The corrective-action column gets filled in and nobody checks that the work actually got done. Track corrective actions in a simple spreadsheet with a target date and a completed date, and review the open list at every safety meeting.

How long do you have to complete and keep an incident report?

Once you have the information to call a case recordable, you have seven calendar days to record it on the 300 Log ^[2]. There is no separate OSHA deadline for your internal report, but speed matters for accuracy, not compliance. Write it while the facts are still warm.

OSHA requires you to keep the 300 Log, 300-A Summary, and 301 Incident Reports for five years after the end of the calendar year they cover ^[10]. A 2025 injury's records must be retained through December 31, 2030.

For fatalities and severe injuries under 29 CFR 1904.39, the clock is much shorter: 8 hours for a work-related fatality, 24 hours for an in-patient hospitalization, amputation, or eye loss ^[4]. Those are phone reports to OSHA's line (1-800-321-OSHA) or through OSHA's online portal, not written forms, though you will still build supporting documentation around them.

For litigation, employment attorneys generally suggest keeping incident reports well past OSHA's five-year floor, often out to the personal-injury statute of limitations in your state, which usually runs two to six years from the date of injury. Ask your workers' compensation carrier too. They have their own documentation rules, and they do not match OSHA's.

Can an incident report be used against you in a lawsuit?

Yes. Incident reports are discoverable in litigation and workers' compensation proceedings. That is a real concern, but it is not a reason to write weak reports. It is a reason to write accurate ones.

A well-written report that honestly names a hazard and documents the fix actually helps you. It shows good faith and proves you acted on the finding. A vague or falsified report that surfaces in discovery does the reverse. It suggests you knew about a hazard and did nothing, which is the exact factual foundation for negligence.

Some states protect certain safety-related communications. A handful of jurisdictions limit discovery of documents prepared specifically in anticipation of litigation, but a routine incident report written in the normal course of business usually does not qualify. Ask your employment attorney about your state.

The stance that holds up: write reports that are honest, specific, and centered on facts and system failures. Document the corrective actions, then actually complete them. That paper trail is your defense, not your exposure.

How do you use incident report data to prevent future injuries?

One incident report is a case file. A year of them is a dataset. The prevention value lives in the dataset, not the single form.

Start with frequency by category. Group incidents by body part, department, task, time of day, and day of week. Patterns invisible at the case level jump out in aggregate: warehouse slips happen almost entirely in the first hour of the Monday shift, or hand lacerations cluster on one machine run by newer employees.

Then check corrective-action closure rates. What percentage of your actions actually finish on time? If it is under 80 percent, you have an execution problem, not an analysis problem, and no amount of better forms will fix it.

OSHA's 300 Log and the BLS Survey of Occupational Injuries and Illnesses both give you industry benchmarks to measure against ^[3]. If your total recordable incident rate (TRIR) sits above the industry average, you have hard evidence your current approach is underperforming. Below average, and you have evidence your safety spend is paying off.

TRIR is (number of recordable incidents x 200,000) divided by total employee hours worked. Log 50,000 hours with 3 recordable cases and your TRIR is (3 x 200,000) / 50,000 = 12.0, which is brutally high for almost any industry. For reference, BLS put the overall private industry rate at 2.4 in 2023 ^[3].

Review this data quarterly at minimum. Put it in front of supervisors. Treat incident data the way a good factory treats quality defect data: a signal about where the process is failing, not a scoreboard for blaming people.

If your reporting process is solid and you want it wired into a written safety program that tracks corrective actions, SafetyFolio's program generator builds that structure in a format your team will actually use.

What training do supervisors need to write good incident reports?

Supervisors are usually first on scene and the primary author of the report. Their skill sets the ceiling on report quality, so train them like it matters.

At a minimum, supervisor investigation training should cover how to secure and document the scene before anything moves, how to interview witnesses (separate them before they compare stories, ask open-ended questions, write down exact words), how to push past immediate causes to root causes, and how to write corrective actions that are specific and verifiable.

OSHA's 30-hour construction and general industry courses include incident investigation modules, and that training is genuinely useful for supervisors who oversee physical work ^[7]. The osha 30 course is a reasonable baseline for any supervisor in a higher-hazard setting. If your supervisors have not been through osha training that explicitly teaches investigation technique, close that gap.

Formal courses only go so far. The single most useful thing you can do is sit down and review completed reports with supervisors, then give specific feedback. 'This root cause says employee error. Tell me why the system let the error happen' is the kind of coaching that lifts every future report. Generic training with no applied review just produces generic forms.

Frequently asked questions

An incident or occurrence report is a tool used to do what, exactly?

It documents the facts of a workplace injury, illness, near-miss, or unsafe event; finds root causes; satisfies OSHA's 29 CFR 1904 recordkeeping for qualifying cases; and produces the data you need to prevent a repeat. Treat it as both a legal record and a diagnostic instrument, not a form you file and forget after something goes wrong.

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

No. The OSHA 300 Log is a running annual record of qualifying work-related injuries and illnesses. The incident report (OSHA Form 301 or an equivalent) is the case-level document for each recordable event. One feeds the other. You write a 301-equivalent per recordable case and summarize all cases on the 300 Log. Not every incident report becomes a 300 Log entry, but every 300 Log entry should have a supporting report.

Does OSHA require you to complete an incident report for near-misses?

OSHA does not legally require internal near-miss reports, but it strongly encourages them in its Recommended Practices for Safety and Health Programs. Near-misses do not trigger 300 Log entries because no injury occurred. Still, investigating near-misses with the same rigor as injuries is one of the most cost-effective moves a small employer can make to prevent future recordable events.

How long do I have to file an incident report after a workplace injury?

For recordable injuries, OSHA gives you seven calendar days after learning the case is recordable to enter it on the 300 Log. For fatalities, you notify OSHA within 8 hours; for in-patient hospitalizations, amputations, or eye losses, the window is 24 hours under 29 CFR 1904.39. Start your internal report immediately, ideally within hours, while facts and scenes are fresh.

How long do I have to keep workplace incident report records?

OSHA requires you to keep the 300 Log, 300-A Summary, and 301 Incident Reports for five years after the end of the calendar year they cover, under 29 CFR 1904.33. Many employers keep incident reports longer for workers' compensation and litigation reasons, since personal-injury statutes of limitations vary by state and often run past five years.

Who should fill out a workplace incident report?

Best practice is a two-track process. The injured or affected employee provides their account independently, and the direct supervisor completes their section separately before comparing notes. A safety officer or manager then reviews both accounts, verifies the root-cause analysis, and confirms corrective actions have a named owner and a deadline. Single-person reports are a common small-business failure pattern.

What is the difference between a first report of injury and an incident report?

A first report of injury is usually a workers' compensation form sent to your state WC board or insurer to open a claim. An incident report is your internal safety document. They overlap in content but serve different purposes and audiences. You often complete both after a recordable injury. The internal report should go deeper, especially on root cause and corrective actions.

Can incident reports be subpoenaed in a personal injury lawsuit?

Yes. Incident reports are business records and are generally discoverable in litigation. That is not a reason to write vague reports. A thorough report that documents a hazard and shows corrective action was taken demonstrates good faith and is a stronger legal position than a thin or falsified one. Ask your employment attorney about document retention and any state-specific protections.

What is a total recordable incident rate (TRIR) and how does my incident data feed it?

TRIR is (number of OSHA recordable incidents x 200,000) divided by total hours worked in the year. It normalizes your injury rate to a per-100-full-time-workers basis so you can compare against BLS industry averages. Every case on your OSHA 300 Log feeds the numerator. BLS reported an overall private industry rate of 2.4 recordable cases per 100 workers in 2023.

Are small businesses with fewer than 10 employees exempt from incident reporting requirements?

Partially. Employers with ten or fewer employees are generally exempt from maintaining the OSHA 300 Log under 29 CFR 1904.1. But all employers, regardless of size, must report work-related fatalities within 8 hours and in-patient hospitalizations, amputations, or eye losses within 24 hours under 29 CFR 1904.39. The exemption does not remove the need for internal incident documentation.

What industries are exempt from OSHA recordkeeping requirements?

Employers in certain low-hazard industries (classified by NAICS code) with 10 or fewer employees are partially exempt under 29 CFR 1904.2. A full list of partially exempt industries appears in Appendix A to Subpart B of 29 CFR 1904. Even exempt employers must report severe incidents directly to OSHA and must record cases if OSHA or BLS notifies them they are in the annual survey.

What should a corrective action section in an incident report include?

Each corrective action should name the specific change (not 'remind employees to be careful' but 'install guarding on conveyor belt at station 3'), the person responsible, and a due date. Track completion separately. Open corrective actions are a major finding during OSHA inspections and in post-incident litigation, because they show a known hazard that was not fixed.

How do incident reports relate to OSHA's hazard communication standard?

When an incident involves a chemical exposure, the report should reference the specific chemical, its SDS, and whether the worker had access to that SDS under the hazard communication standard at 29 CFR 1910.1200. Recurring chemical-exposure incidents often point to gaps in labeling, training, or SDS availability. The incident report is the mechanism that surfaces those gaps. See also our article on hazard communication.

Sources

1. OSHA, 29 CFR 1904.7 General recording criteria: An injury or illness is OSHA recordable if work-related, a new case, and meets at least one general recording criterion: days away from work, restricted duty, job transfer, medical treatment beyond first aid, loss of consciousness, or a significant diagnosis.
2. OSHA, Injury and Illness Recordkeeping and Reporting Requirements (Forms 300, 300-A, 301): Employers must record qualifying cases on the 300 Log within seven calendar days and retain 300, 300-A, and 301 forms for five years.
3. U.S. Bureau of Labor Statistics, Survey of Occupational Injuries and Illnesses 2023: Private industry recorded approximately 2.6 million nonfatal workplace injuries and illnesses in 2023 at an incidence rate of 2.4 per 100 full-time workers.
4. OSHA, 29 CFR 1904.39 Reporting fatalities, hospitalizations, amputations, and losses of an eye: Employers must report work-related fatalities to OSHA within 8 hours and in-patient hospitalizations, amputations, or eye losses within 24 hours.
5. OSHA, Recommended Practices for Safety and Health Programs: Incident investigation is one of the core elements in OSHA's recommended safety and health program framework; near-misses should be investigated with the same rigor as actual injuries.
6. National Safety Council, Workplace safety resources and worker perception surveys: 66 percent of workers surveyed indicated they would be less likely to report a near-miss if they believed it would result in punishment.
7. OSHA, Outreach Training Program (10-hour and 30-hour courses): OSHA 30-hour construction and general industry courses include incident investigation as a covered topic for supervisors and workers.
8. OSHA, 29 CFR 1904.29 Forms: Employers must use OSHA Form 300 Log, 300-A Annual Summary, and 301 Incident Report or equivalent forms; the 301 must be completed within seven calendar days of learning a case is recordable.
9. OSHA, 29 CFR 1904.1 Partial exemption for employers with 10 or fewer employees: Employers with ten or fewer employees are generally exempt from maintaining the OSHA 300 Log, though severe incident reporting requirements still apply.
10. OSHA, 29 CFR 1904.33 Retention and updating of old forms: OSHA requires retention of 300, 300-A, and 301 forms for five years following the end of the calendar year they cover.
11. OSHA, 29 CFR 1910.1200 Hazard Communication Standard: Workers must have access to safety data sheets for chemicals they work with; chemical-exposure incidents should reference SDS availability in the incident report.
12. OSHA, 29 CFR 1904.2 Partial exemption for establishments in certain industries: Certain low-hazard industries classified by NAICS code with ten or fewer employees are partially exempt from routine 300 Log maintenance.