Last updated 2026-07-09

TL;DR
An incident report form documents the who, what, when, where, and how of a workplace injury, illness, or near-miss. OSHA requires most employers to record work-related injuries on Form 300 and Form 301 within 7 days of learning about them. A good form captures enough detail to prevent the next incident, more than satisfy a checkbox.
What is an incident report form?
An incident report form is a written record of the facts about a workplace event: an injury, illness, near-miss, property damage, or any situation that had the potential to hurt someone. It answers the questions a supervisor or safety manager needs to understand what happened and why.
The form is not a disciplinary document. That distinction matters a lot, because employees who fear punishment stop reporting, and unreported near-misses become tomorrow's injuries. The goal is information: where did it happen, who was involved, what were the conditions, and what could be changed to prevent a repeat.
Workplace incidents cost U.S. employers roughly $167 billion per year in direct and indirect costs, according to the National Safety Council's 2023 Injury Facts report [1]. Most of those costs trace back to events that had warning signs. A solid incident report form is how you catch those signs before they compound.
There are two layers here. One is the internal form your organization uses, which can be as detailed as you want. The other is OSHA's mandatory recordkeeping forms, which apply to most employers with more than 10 employees and carry specific legal requirements. You need both, and they do different jobs.
What does OSHA actually require on an incident report?
OSHA's recordkeeping rule lives at 29 CFR 1904 [2]. It requires covered employers to keep three forms: the OSHA 300 Log of Work-Related Injuries and Illnesses, the OSHA 300A Annual Summary, and the OSHA 301 Injury and Illness Incident Report. The 301 is the closest thing OSHA has to a formal incident report form.
OSHA Form 301 asks for the employee's name and job title, date of birth, date hired, gender, date and time of the incident, location where it occurred, whether the employee was treated in an emergency room or hospitalized overnight, a description of what the employee was doing just before the incident, how the injury or illness occurred, the object or substance involved, and the nature of the injury or illness [2]. That is a specific and fairly detailed list.
The regulation at 29 CFR 1904.29 requires employers to record each recordable injury or illness on the OSHA 300 Log within 7 calendar days of receiving information that a recordable injury or illness has occurred [2]. The 301 (or an equivalent form) has to be completed inside that same 7-day window.
A recordable injury, under 29 CFR 1904.7, means any work-related injury or illness that results in days away from work, restricted work or transfer to another job, medical treatment beyond first aid, loss of consciousness, or diagnosis of a significant injury or illness by a healthcare professional [2]. First-aid-only cases do not go on the 300 Log, though many employers still document them internally.
Some industries are partially exempt from routine recordkeeping. Employers with 10 or fewer employees at all times during the prior calendar year are generally exempt, and establishments in certain low-hazard industries listed in Appendix A to Subpart B of 29 CFR 1904 are also exempt, though they must still report fatalities and severe injuries [2]. Check the OSHA recordkeeping page to confirm whether your specific NAICS code is exempt before you assume you are off the hook.
What types of workplace events need an incident report?
Most people think of incident reports as injury paperwork. A good safety program casts a wider net.
Recordable injuries and illnesses go on the OSHA 300 Log as required. But the more useful category for prevention is near-misses: events where no one got hurt but the conditions for harm were present. A pallet that shifted but didn't fall. A chemical container that spilled but got contained fast. A worker who tripped but caught themselves. None of those land on the 300 Log. All of them deserve a report.
Property damage events matter too, especially around forklifts, heavy equipment, or compressed-gas systems. A forklift clipping a rack is a near-miss for the worker who could have been standing there. Documenting it creates a record you can track over time.
Here is a practical breakdown of what typically triggers a report:
| Event Type | OSHA 300 Log Required? | Internal Report Recommended? |
|---|---|---|
| Recordable injury or illness | Yes | Yes |
| First-aid-only injury | No | Yes |
| Near-miss (no injury or damage) | No | Strongly yes |
| Property or equipment damage | No | Yes |
| Environmental release or spill | Depends on other regulations | Yes |
| Workplace violence incident | Yes, if recordable [3] | Yes |
| Vehicle/fleet incident | Depends on work-relatedness | Yes |
The Bureau of Labor Statistics found that private industry employers reported 2.8 million nonfatal workplace injuries and illnesses in 2022 [4]. That number reflects only what got reported and recorded. Near-miss rates are harder to measure, but some safety researchers estimate near-misses outnumber recordable injuries by anywhere from 30 to 300 to one, depending on the industry. Getting near-miss reporting right is where most small employers can move the needle fastest.
What should be on an incident report form template?
A good incident report form template covers six areas. Skip any of them and you will find yourself going back to the employee or supervisor to fill in gaps, which only gets harder as memories fade.
Section 1: Basic identification. Name of the person involved, their job title, department, supervisor's name, date and time of the incident, and the exact location (building, floor, specific area, more than "the warehouse").
Section 2: Incident description. What was the person doing right before the incident? What happened? Use a first-person narrative space here, more than checkboxes. Checkboxes tell you the category. Narrative tells you the story. Both matter.
Section 3: Injury or illness details. Nature of injury (laceration, strain, fracture, rash, etc.), body part affected, whether the person left work, sought medical attention, was hospitalized, or returned to the same job. This is the data that feeds the 300 Log.
Section 4: Witnesses. Name, contact, and a brief statement field for each witness. Witness accounts often surface details the injured person didn't notice or couldn't recall.
Section 5: Root cause and contributing factors. This is the section most forms do badly. A checkbox for "employee error" is nearly useless. You want the conditions: Was the lighting adequate? Was there a written procedure? Was the employee trained? Was the equipment in proper condition? Had this type of incident happened before? A structured why-analysis, even a simple one, belongs here.
Section 6: Corrective actions. What immediate steps were taken? What follow-up actions are planned? Who owns them? What is the due date? Without this section, the report is a historical document instead of a prevention tool.
For IT departments, an incident report template swaps the physical hazard fields for system-related ones: the affected system, the type of incident (data breach, hardware failure, physical injury in a server room, and so on), business impact, and escalation path. The structure holds. The vocabulary shifts.
You can download OSHA's free Form 301 directly from OSHA.gov [2], and plenty of employers use it as their internal report too. It is adequate but not great for root-cause analysis, so most safety-focused organizations pair it with their own template.
How do you fill out an incident report form correctly?
The worst mistakes happen in the first 30 minutes after an incident, when everyone is stressed and the priority feels like getting back to work. Slow down. The quality of the report depends almost entirely on how fast and how carefully it gets done.
Make sure the scene is safe and the injured person has been cared for. Nothing else happens before that. Once immediate needs are handled, the supervisor or safety lead should start the report while the facts are fresh.
Get the exact time, more than the date. Incident patterns often cluster around shift changes, end-of-day fatigue windows, or specific tasks. Time data lets you see those patterns.
Describe what happened in plain, factual language. "Employee slipped on wet floor near receiving dock" beats "accident occurred." Keep blame out of the description section. The narrative describes events, not conclusions.
Do not leave root-cause fields blank. If the answer is "unknown," write that and note what investigation steps are planned. A blank field looks like the question got skipped. "Unknown, pending floor inspection" looks like you are managing it.
Get witness signatures before witnesses go home. Memories drift fast, and a signed statement beats a later recollection every time.
Once the form is complete, route it through whatever review you have, whether that is a supervisor sign-off, a safety committee review, or direct escalation to management. Then actually track the corrective actions to closure. That last step is where most programs fall apart: the form gets filed, the hazard stays put, and the same incident happens again six months later.
What is the deadline for submitting an incident report?
For OSHA recordkeeping, the 7-calendar-day clock starts when the employer receives information that a recordable injury or illness has occurred, not when the incident happened [2]. That matters if, say, a worker reports an injury two days after it occurred.
Fatalities and severe injuries are more demanding. Under 29 CFR 1904.39, employers must report a work-related fatality to OSHA within 8 hours and a work-related in-patient hospitalization, amputation, or loss of an eye within 24 hours [2]. Those reports go straight to OSHA, not into the log.
For internal incident reports, best practice is same day or as soon as possible while facts are still accurate. Many employers set a policy of 24 hours for first-aid-only events and immediate notification for anything involving medical treatment, lost time, or a near-miss with serious potential.
State plan states may have added or different reporting requirements. There are 22 state plans covering private-sector employers and 6 covering only state and local government employees [5]. If you operate in California, Washington, Michigan, or another state-plan state, check with your state agency, because some have shorter reporting windows or broader recordable definitions than federal OSHA.
Where can you get a free incident report form?
Several reliable sources offer free, downloadable forms.
OSHA's website has the official Form 300, Form 300A, and Form 301 as PDFs and as Excel versions that auto-calculate the 300A summary [2]. These are the legally required forms for recordkeeping, and they cost nothing.
For internal-use forms that go further than OSHA's minimum, the National Safety Council [6] and many state workers' compensation boards publish templates with root-cause and corrective-action sections. Check your state's workers' comp agency specifically, because their forms are often built to feed the claims process, which saves you duplicate data entry.
For industries with specific hazards, trade associations sometimes publish sector templates. Construction employers should look at OSHA's construction directorate materials. Healthcare employers have OSHA's healthcare worker templates on the OSHA healthcare industry page.
If you are building or updating a written safety program and want incident investigation baked in (it should be), SafetyFolio's safety program generator walks you through incident reporting procedures as part of the broader written program, so the form does not live in isolation from the rest of your documentation.
One honest caveat on free templates: a template is only as good as the training that comes with it. Hand someone a form without explaining what good answers look like and you get bad reports. Budget 30 to 60 minutes to walk supervisors through a completed example before you deploy any new form.
How long do you have to keep incident report records?
OSHA requires you to keep the OSHA 300 Log, the 300A Annual Summary, and the 301 Incident Report for 5 years following the end of the calendar year the records cover [2]. Records from 2024 must be kept through the end of 2029.
During that retention period, you must give access to current and former employees, their personal representatives, and their authorized employee representatives (unions, for example) on request [2]. Former employees can request their own 301 record. They cannot request records for other workers.
For your internal incident reports, especially near-misses or property damage that never hit the 300 Log, there is no federal mandate on retention length. Most employment attorneys suggest keeping them at least 3 to 5 years, or longer if there is any chance of a workers' compensation dispute or litigation. Some states have longer statutes of limitations for workplace injury claims, so know your state's rules.
Store records somewhere you can actually retrieve them. A filing cabinet that floods or a shared drive that gets wiped during an IT migration has ended more than one OSHA inspection badly.
What is the difference between an incident report and an accident report?
The words get used interchangeably, but there is a real distinction worth keeping.
"Accident" implies randomness, something that just happened with no preventable cause. Safety professionals largely dropped the word decades ago because it discourages looking for root causes. If it was just an accident, why bother investigating?
"Incident" is the preferred term because it is neutral. It says something occurred without implying whether it was preventable. The investigation decides causation.
From a recordkeeping standpoint, OSHA uses the word "incident" in its Form 301 title for exactly this reason. You will still see "accident report" on older insurance forms and some workers' compensation paperwork, but most modern safety management systems and OSHA guidance use "incident."
Here is the practical part. If your organization still calls its form an accident report, renaming it to incident report is a low-cost, high-signal move. It sets a different tone for the investigation before anyone writes a single word.
How do incident reports connect to your broader safety program?
An incident report form is not a standalone document. It is the data-collection piece of a larger incident investigation and prevention process, and that process should be written down somewhere in your safety program.
OSHA does not have a specific standard requiring a written incident investigation procedure for general industry, but OSHA's General Duty Clause (Section 5(a)(1) of the OSH Act) requires employers to provide a workplace free of recognized hazards [7]. An employer who documents incidents but does not investigate or correct them has built a documented record of recognized hazards. That is not a position you want to be in during an inspection.
A few standards do require specific incident investigation steps. 29 CFR 1910.119, the Process Safety Management standard for highly hazardous chemicals, requires incident investigation for near-misses as well as actual incidents, with a written report and a 5-year retention requirement [8]. If PSM applies to you, your incident report form has to clear a higher bar than OSHA 301.
For most small employers, the connection looks like this: the form captures data, the data feeds a monthly or quarterly review, the review spots patterns (same department, same equipment, same time of day), and those patterns drive training, engineering controls, or procedure changes. That loop is how incident reporting actually reduces injuries over time. Skip the review step and you are just filing paperwork.
If you are building or updating your written safety program, you can learn more about incident reports as part of a broader safety structure, and consider connecting your incident data to your OSHA training calendar so you are retraining on the hazards that actually showed up in your facility.
What are the most common mistakes on incident report forms?
These show up over and over in audits and post-incident reviews.
Waiting too long. Reports finished days after an incident are less accurate. Details blur, witnesses remember differently, and the scene may have changed. Set a firm policy: the form starts the same shift.
Vague descriptions. "Employee was hurt" tells you nothing. "Employee strained lower back while lifting a 65-pound box from floor level to a shelf above shoulder height, without using the available lift assist" tells you exactly what to fix.
Blaming the employee and stopping there. Human error is almost never the whole story. The more useful question is what system or condition made the error easy to make. Were the tools adequate? Was the procedure clear? Had the person been trained recently?
Skipping the near-miss category. Many forms have no near-miss checkbox or section. If yours doesn't, add one. Near-miss data is some of the most valuable safety intelligence you can collect.
Leaving corrective actions open forever. Track them. Assign owners. Set deadlines. Review them at your next safety meeting. If corrective actions keep sitting open for months, the reporting process has turned into a paper exercise.
Using the report as a discipline trigger. When employees know a form leads to a write-up, they stop reporting. Keep safety reporting and HR discipline as separate processes.
OSHA's recordkeeping page has a useful FAQ section covering some of these gray-area situations, particularly first aid versus medical treatment determinations [2]. Bookmark it.
How do incident reports affect your OSHA inspection and your workers' comp costs?
Incident reports sit at the center of two separate financial consequences: OSHA enforcement and workers' compensation premiums.
During an OSHA inspection, a compliance officer will usually ask to review your 300 Logs for the past 5 years. Gaps, inconsistencies, or a log that looks suspiciously clean relative to your industry can trigger a deeper look. An employer cited for recordkeeping violations under 29 CFR 1904 faces penalties up to $16,550 per serious violation as of 2024, with willful or repeated violations reaching $165,514 [9]. Those numbers update annually based on inflation adjustments.
For workers' compensation, your experience modification rate (EMR or X-Mod) is calculated partly from your claim history. A well-documented incident report that captures the facts accurately, including the employee's immediate medical care, their return-to-work status, and the corrective actions taken, can help manage claims costs by showing active safety management. Insurers and state rating bureaus look at claims history over a 3-year window. Better documentation of incidents, paired with genuine hazard correction, shows up in lower EMRs over time.
The less obvious connection is litigation. A thorough incident report, completed fast and factually, creates a record that reflects a diligent employer. A sloppy or missing report reads like negligence or concealment to a plaintiff's attorney. Neither federal OSHA standards nor most state workers' comp statutes require you to document in a way that protects you legally, but doing so is in your interest.
For a closer look at how OSHA enforcement works and what inspectors actually check, the OSHA overview is a good starting point.
Frequently asked questions
Is an incident report form the same as the OSHA 301?
Not exactly, but OSHA Form 301 is the official injury and illness incident report required under 29 CFR 1904.29. It is the minimum required format. Many employers use Form 301 as their internal incident report, though larger organizations often supplement it with a longer internal form that adds root-cause analysis and corrective action tracking fields the 301 does not have.
Do I need to report near-misses to OSHA?
No. Near-misses are not reportable to OSHA under 29 CFR 1904 unless they result in a recordable injury or illness. But you absolutely should document near-misses internally. Near-miss data is leading-indicator information: it tells you where your next injury is likely to come from before someone gets hurt. OSHA's Voluntary Protection Programs treat near-miss reporting as a sign of a mature safety culture.
What makes an injury recordable versus first-aid only?
Under 29 CFR 1904.7, a recordable injury results in days away from work, restricted duty, job transfer, medical treatment beyond first aid, loss of consciousness, or a significant diagnosis by a healthcare professional. First aid includes things like bandages, non-prescription medication at non-prescription strength, and hot or cold therapy. The OSHA recordkeeping page has a full list of what counts as first aid versus medical treatment.
Can employees see the incident report forms I file?
Yes, with limits. Under 29 CFR 1904.35, current and former employees and their representatives have the right to access OSHA 300 Log entries. Employees can also request a copy of their own Form 301. But employees can only see the injury and illness entries on the 300 Log for other workers, not the full 301 details for co-workers, which protects individual privacy.
What happens if I don't file an incident report on time?
For OSHA 300 Log entries, the 7-day deadline is a hard rule under 29 CFR 1904.29. Missing it can result in a recordkeeping citation during an inspection. For fatalities and severe injuries under 29 CFR 1904.39, failing to report within 8 or 24 hours respectively can result in significant penalties. Late filing beats no filing, but the citation risk stays until the record is corrected.
Do small businesses with fewer than 10 employees need to fill out incident report forms?
Employers with 10 or fewer employees at all times during the prior calendar year are exempt from routine OSHA 300 Log recordkeeping under 29 CFR 1904.1. They are still required to report fatalities to OSHA within 8 hours and severe injuries within 24 hours. Using an internal incident report form is still good practice regardless of size, because it helps identify and correct hazards.
What is an incident report template for IT departments?
An IT incident report template adapts the standard format to cover both physical safety incidents (ergonomic injuries, electrical hazards in server rooms) and information security incidents (data breaches, system outages). It typically includes fields for the affected system, type of incident, business impact severity, immediate containment steps, and root cause. The structure mirrors a safety incident report, but the vocabulary fits an IT context.
Can I use a digital or electronic incident report form?
Yes. OSHA's recordkeeping rule explicitly allows electronic recordkeeping. Forms 300, 300A, and 301 are available in Excel format from OSHA.gov. Many safety management software platforms offer electronic incident reporting that auto-populates 300 Log entries. If you use software, make sure it can produce the required OSHA format on demand, because that is what an inspector will ask to see.
How detailed does the incident description need to be?
OSHA Form 301 asks for a description of what the employee was doing just before the incident, how the injury or illness occurred, the object or substance that directly harmed the employee, and the nature and body part affected. In practice, more detail is almost always better. Aim for a description specific enough to reconstruct the event without relying on memory. One to three sentences of factual narrative is usually enough.
Do I need to report a workplace vehicle accident on an incident report?
It depends on work-relatedness and outcome. Under 29 CFR 1904.5, injuries are work-related if an event in the work environment caused or contributed to them. A vehicle accident during a work errand is work-related; a commute accident is not. If the accident results in a recordable injury, it goes on the 300 Log. Property-damage-only vehicle incidents are not OSHA recordable but are worth documenting internally.
What is the difference between an incident report and an accident investigation report?
An incident report captures the facts: what happened, who was involved, when, and where. An accident investigation report goes further, analyzing root causes and contributing factors through interviews, scene examination, and document review. The incident report is often the starting document; the investigation report is the analytical follow-up. Larger organizations keep both; small employers often combine them into a single multi-section form.
Does OSHA require a written incident investigation procedure?
Not explicitly for most general industry employers, though OSHA's Process Safety Management standard (29 CFR 1910.119) does require written incident investigation for PSM-covered facilities. OSHA's General Duty Clause requires employers to address recognized hazards. Consistently documenting incidents without investigating or correcting them builds a written record of recognized hazards, which is a liability during inspections.
How do I get a free incident report form?
OSHA provides Forms 300, 300A, and 301 free on OSHA.gov in both PDF and Excel formats. Many state workers' compensation agencies also offer free templates. For internal forms with more detail, the National Safety Council and state safety councils publish templates. Your state's department of labor website is a good first stop if you want a form that feeds your workers' comp claims process.
Sources
- National Safety Council, Injury Facts 2023: Workplace incidents cost U.S. employers roughly $167 billion per year in direct and indirect costs
- OSHA, Recordkeeping Rule 29 CFR 1904 and Forms 300, 300A, 301: Employers must record recordable injuries on the OSHA 300 Log within 7 calendar days; Form 301 fields and employer access obligations under 29 CFR 1904.29 and 1904.35; fatalities within 8 hours and severe injuries within 24 hours under 29 CFR 1904.39
- OSHA, Workplace Violence recordkeeping guidance: Workplace violence incidents are recordable if they meet the standard recordability criteria under 29 CFR 1904
- Bureau of Labor Statistics, Survey of Occupational Injuries and Illnesses 2022: Private industry employers reported 2.8 million nonfatal workplace injuries and illnesses in 2022
- OSHA, State Plans overview: There are 22 state plans covering private-sector employers and 6 covering only state and local government employees
- National Safety Council, safety resources and templates: NSC publishes incident report templates including root-cause and corrective-action sections
- OSHA, OSH Act Section 5(a)(1) General Duty Clause: The General Duty Clause requires employers to provide a workplace free from recognized hazards likely to cause death or serious physical harm
- OSHA, Process Safety Management standard 29 CFR 1910.119: 29 CFR 1910.119 requires written incident investigation for near-misses in PSM-covered facilities with a 5-year record retention requirement
- OSHA, Civil Penalty Adjustments for Inflation 2024: Serious OSHA violations carry penalties up to $16,550 per violation; willful or repeated violations up to $165,514 as of 2024