Incident report layout: what goes on it and why each field matters

Last updated 2026-07-10

What is an incident report layout and why does the structure matter?

An incident report layout is the field-by-field skeleton of your form. The order of fields, the labels you use, and the space you give each section all shape the quality of information you get back. A badly arranged form produces vague reports. A well-arranged one produces reports you can act on.

This is more than paperwork. The Bureau of Labor Statistics recorded 2.6 million nonfatal workplace injuries and illnesses in private industry in 2023, and OSHA requires employers to log and analyze that data under 29 CFR 1904 ^[1][2]. Employers with 10 or more employees at establishments in most industries have to keep injury and illness records. If your layout leaves out required fields, your records are deficient. If it buries the useful fields under the bureaucratic ones, your supervisors stop filling it out carefully.

The layout sets the tone. A form that opens with "employee social security number" signals paperwork. A form that opens with "what happened and how do we stop it from happening again" signals a safety culture. Both can be OSHA-compliant. Only one gets you good data.

See the companion article on incident report basics if you need a primer on when to file before you worry about how to design the form.

What are the 12 core sections every incident report layout needs?

Here is the layout sequence that holds up in practice. None of it is arbitrary. Each section exists because someone downstream needs the information for a specific purpose: OSHA recordkeeping, workers' comp, corrective action, or litigation defense.

1. Report header Report number, date of report, and who completed it. This lets you track whether reports get filed promptly. OSHA expects records to be accurate and accessible, and a missing report number makes it hard to cross-reference your OSHA 300 Log ^[2].

2. Incident date, time, and shift The exact date and time the incident happened, separate from the report date. Shift matters because incident rates often cluster by shift, and you cannot see that pattern without the data.

3. Location Building, department, specific workstation or area. "Warehouse" is useless. "Warehouse, receiving dock, forklift staging lane" is not. The more specific the location, the faster you spot a problem area.

4. Injured or ill person Name, job title, department, hire date, and years in the role. Keep the SSN off the main form. OSHA's rules require you to protect employee privacy for certain sensitive cases, and SSNs create exposure you do not need ^[2]. If workers' comp wants it, collect it separately.

5. Description of the incident A free-text narrative of what happened, in the worker's own words if you can get them. Give this field real space, at least six to eight lines. Cramped narrative fields produce cramped narratives.

6. Injury or illness description Body part affected, nature of injury or illness (laceration, strain, chemical exposure, and so on), and which side of the body. The OSHA 301 Incident Report form asks for these specifics because the 300 Log columns are keyed to injury type ^[2].

7. Root cause and contributing factors This is the section most forms skip or botch. Ask three things: what was the direct cause, what was the indirect cause, and what system-level condition made this possible? A simple three-line structure works. Resist the urge to merge it with the incident description.

8. Witnesses Name, contact info, and whether a statement was collected. Witness information is time-sensitive. It belongs on the form, not in someone's email inbox.

9. Medical treatment First aid only, or did the employee get treatment beyond first aid? Referred to a physician? Hospitalized? These answers decide OSHA recordability. Under 29 CFR 1904.7, cases requiring medical treatment beyond first aid are recordable ^[7].

10. Lost time and restrictions Days away from work, days on restricted duty, and return-to-work date. These numbers feed straight into your OSHA 300 Log columns.

11. OSHA recordability determination A yes/no checkbox: is this case recordable on the OSHA 300 Log? Plus who decided and when. This field forces someone to make a conscious call instead of letting cases slip.

12. Corrective actions What specific actions get taken, who owns each one, and by what date. Without this section, an incident report is an autopsy. With it, the form becomes a corrective action tracker.

How does the OSHA 301 Incident Report form compare to a custom layout?

OSHA publishes a free, fillable Form 301 that satisfies the 29 CFR 1904.29 requirement to keep an incident report for each recordable case ^[8]. It is a solid baseline. If you have fewer than 20 employees and you are just getting started, using the OSHA 301 as-is is a perfectly reasonable call.

Here is the catch. The 301 was built as a universal minimum, not a root-cause tool. It asks what happened but does not push you to explain why. It has no corrective action field. It collects data for compliance, and it stops there.

Most employers with 50 or more people, or with incidents that keep repeating, do better with a custom layout that embeds the 301 fields and adds root cause, corrective action, and a recordability decision block. The 301 fields you have to keep if you build your own form: case number, date of injury or illness, employee information, the narrative description, nature and body part of injury, and the medical treatment questions ^[8].

Layout type	OSHA 301 compliant	Root cause section	Corrective action tracking	Best for
OSHA Form 301 (standard)	Yes	No	No	Small employers starting out
Custom form with 301 fields embedded	Yes	Yes (if added)	Yes (if added)	Employers who want prevention data
Workers' comp carrier form only	Sometimes	Rarely	No	NOT recommended as your only form
Electronic recordkeeping system	Yes (if configured correctly)	Often yes	Often yes	Larger employers, multi-site

One trap to watch: your workers' comp carrier's incident form does not automatically satisfy your OSHA recordkeeping obligation. These are separate requirements. Use both, or build one form that covers both.

What order should the fields appear in, and does order actually matter?

Order matters more than most people expect. Form-design research on cognitive load consistently finds that people fill out earlier fields more carefully and later fields fast or not at all. That gets worse under stress, which is exactly the condition incident reports get filled out in.

The sequence that works: start with facts (what, when, where, who), move to description and cause, then to consequence (injury type, medical treatment, lost time), then to decision and action (recordability, corrective actions, sign-offs). It follows the natural arc of a supervisor's investigation.

What fails: opening with administrative fields like report number, department code, and cost center, then stranding the incident description on page two. Nobody fills out page two well.

One rule I would not skip. Put the corrective action section before the signatures, never after. If corrective action is the last thing before "submit," supervisors write something minimal just to close the form. If it comes before sign-off, it reads as part of the investigation.

Give the narrative field space proportional to its weight. A box two inches wide and one inch tall tells people you do not expect detail. Use at least a quarter of the form's real estate for incident description and root cause combined.

What details about the injured employee should an incident report capture?

Capture enough to identify the person, their role, and their experience level. Anything past that is usually unnecessary on the incident report itself, and it creates privacy exposure.

The fields you need: full name, job title, department, date of hire, and length of time in the current job or task. That last one gets overlooked constantly. BLS injury data consistently shows elevated injury rates among workers in their first year in a role, and especially in their first month ^[3]. Skip time-in-role and you cannot see that pattern in your own numbers.

Keep date of birth, home address, and SSN off the main incident report. Date of birth can help with trend analysis but OSHA does not require it, and it creates exposure if the form ever gets seen without authorization. The SSN belongs in your HR system, not on a safety form a forklift operator fills out at the workstation.

For certain injuries, OSHA's recordkeeping standard requires you to withhold the employee's name from the public log. These "privacy concern cases" include sexual assaults, mental illness, HIV/AIDS and other infectious diseases, and injuries to reproductive organs ^[2]. Build in a checkbox: "Privacy concern case? Do not enter name on OSHA 300 Log."

See our guide on forklift certification for an example of how role-specific risk data shapes incident reporting in high-hazard jobs.

How should you document root cause on an incident report?

Root cause is where most incident report layouts fall apart. They offer one blank field labeled "cause of accident" and call it done. You get answers like "employee not paying attention" or "wet floor." Those tell you nothing and fix nothing.

A better layout prompts at three levels:

Immediate cause: The direct physical or behavioral event. The employee slipped. The guard was not in place. The chemical splashed.

Contributing causes: The conditions that made the immediate cause possible. The floor was wet because the drain was clogged. The guard had come off the prior shift and nobody put it back. The employee never got chemical handling training.

System or root cause: The management or program failure underneath it. No inspection schedule for drains. No procedure requiring guards to be reinstalled before shift handoff. No training record or verification system.

This three-level structure lines up with OSHA's accident investigation guidance ^[4]. You do not need to call it "5 Whys" or any named method on the form. Just give people three clearly labeled fields. That alone lifts report quality a lot.

Want a shortcut? Use a checklist of common contributing factors (training gap, equipment failure, procedure not followed, inadequate supervision, environmental condition) and ask the investigator to check all that apply, then explain. That hybrid captures structured data and narrative context in the same pass.

What information about medical treatment does OSHA require you to record?

This section decides whether a case lands on your OSHA 300 Log. Get it right.

Under 29 CFR 1904.7, a work-related injury or illness is recordable if it results in any of the following: days away from work, restricted work or job transfer, medical treatment beyond first aid, loss of consciousness, diagnosis of a significant injury or illness by a healthcare professional, or death ^[7].

First aid is a closed list in the standard: nonprescription medication at nonprescription strength, tetanus immunizations, cleaning or flushing or soaking wounds, wound closure with bandages or butterfly strips (not sutures), hot or cold therapy, non-rigid support, drilling a fingernail to relieve pressure, eye patches, removing splinters, and similar minor treatments ^[7]. Go past that list and the case is recordable.

Your layout should include:

• Was first aid administered? (Yes/No) By whom?
• Was the employee referred to a physician or other licensed healthcare professional? (Yes/No)
• Did the employee visit a physician or other healthcare professional? (Yes/No)
• Did the employee require prescription medication? (Yes/No)
• Was the employee hospitalized overnight? (Yes/No)
• Was the employee transferred or terminated as a result? (Yes/No)

These yes/no fields feed straight into the recordability call. If even one is "yes" beyond the first-aid tier, you almost certainly have a recordable case. A named person signing off on that determination closes the loop and gives you an audit trail.

How do you connect the incident report to the OSHA 300 Log and 300A Summary?

The OSHA 300 Log, 300A Annual Summary, and 301 Incident Report are a three-document set under 29 CFR 1904 ^[2]. Each incident report feeds one row of the 300 Log. The 300A summarizes a year of 300 Log data, and it has to be posted from February 1 through April 30 each year.

The link runs through a shared case number. Every 301 (or equivalent incident report) gets a case number. That same number goes in the first column of the 300 Log. During an inspection, the compliance officer cross-references these documents. A missing case number, or a case on the 300 Log with no matching 301, is a recordkeeping violation under 29 CFR 1904.29 ^[8].

Your incident report layout should include:

• A case number field that says "Transfer this number to OSHA 300 Log"
• A checkbox: "Added to OSHA 300 Log? Date: ___"
• A field for the 300 Log classification (injury, skin disorder, respiratory condition, poisoning, hearing loss, all other illnesses)

The 300 Log must be kept for five years from the end of the calendar year it covers ^[9]. Keep your incident reports for the same period. Build a retention note into the layout: "Retain this record until [year]." Whoever files the form fills in the retention year at completion, and now records management runs itself.

If your business uses OSHA training to prepare supervisors for these duties, the recordkeeping connection is worth covering head-on in that training.

Should your incident report layout be paper, digital, or both?

Paper still works fine for most small businesses, and OSHA has no rule that says go digital. The rule is that records be accurate, complete, and accessible to authorized employees, former employees, and OSHA ^[2]. A well-organized paper file clears that bar.

Paper has real weaknesses, though. Forms get lost. Handwriting is often illegible. Trend analysis across dozens of paper forms means manual data entry. And a form filed in a cabinet does not alert anyone when a corrective action deadline passes.

Digital forms fix most of that. A fillable PDF is free to build and keeps the structure of a paper form. A spreadsheet-backed form adds trend analysis. Software adds workflow, notifications, and analytics.

My honest take for a business under 50 employees: use a fillable PDF or a simple digital form that maps to the OSHA 301 fields. Back it up. Keep a log. That is enough. You can build a custom safety program that includes this form structure in about 15 minutes using SafetyFolio's program generator, which outputs OSHA-aligned templates you can modify and own.

For a business with multiple sites or departments, software earns its keep. A safety software subscription runs roughly $3 to $10 per employee per month (pricing varies widely), and that is almost always less than the cost of one missed recordable case that triggers a citation. Recordkeeping violations under 29 CFR 1904 carry penalties up to $16,131 per willful or repeated violation as of 2024 ^[5].

What are common mistakes in incident report layouts that undermine your safety program?

The same design mistakes show up on incident report forms across industries. Here are the ones that do the most damage.

Combining incident description and root cause into one field. You get answers that are 80% narrative and 0% analysis. Separate them. Two distinct fields, two distinct labels.

Making corrective action optional. If the form says "corrective action (if applicable)," supervisors read "if applicable" as "rarely." Make it required. If no action is needed, the supervisor checks "no action required" and signs. That forces a conscious decision either way.

No recordability determination section. This is the omission that costs the most. Without a named person deciding whether a case is recordable, cases fall into the gap between your incident report pile and your OSHA 300 Log. The 300 Log discrepancy is a common finding in recordkeeping-focused inspections ^[4].

Too many checkboxes, not enough room for narrative. Checkboxes handle structured data well. They are terrible at capturing sequence of events, environmental conditions, and worker perspective. Balance the two.

Supervisor signs, injured worker does not. Skip the worker's signature and you lose their version of the event. The signature does not mean they agree with the conclusions. It means they reviewed the description of what happened. Add a separate worker signature line.

No version control on the form. Update the form and old copies keep floating around, creating inconsistency. Put a version date in the footer and set a procedure for retiring old versions.

Understanding hazard communication requirements is a good parallel here, because the same principle holds: a form or label that does not communicate clearly protects nobody.

How long do you need to keep incident reports and who gets access?

OSHA's recordkeeping regulation at 29 CFR 1904.33 requires you to keep the OSHA 300 Log, 300A Summary, and 301 Incident Reports for five years following the end of the calendar year the records cover ^[9]. So records from calendar year 2024 have to stay on file through the end of 2029.

During that five-year window, you have to provide copies of the 300 Log to current and former employees, their personal representatives, and their authorized employee representatives within four business hours of a request ^[10]. For 301 Incident Reports, current and former employees can request their own records, and employee representatives can access records in a de-identified format for safety analysis.

OSHA compliance officers can request these records during an inspection. They do not need to give you advance notice once an inspection is underway.

A question that comes up a lot: does the five-year rule also cover near-miss reports that were not recordable? No. OSHA's standard does not require you to keep near-miss reports at all. But keeping them is good practice, and plenty of safety programs do. If you keep them, use the same five-year retention for consistency, and set your filing system up to tell recordable incidents and near-miss reports apart.

Store records somewhere that survives turnover. A filing cabinet only one person knows about is not a records system. A shared drive folder with a clear naming convention is.

Does incident report layout change for near-misses versus recordable incidents?

It should, a bit. Near-miss reports share most of the layout logic of recordable incident reports, but they drop the medical treatment and lost-time sections and lean harder on root cause and preventive action.

The reason to give near-misses their own layout, or at least a clearly marked near-miss section, is simple. You want to capture high-frequency, low-consequence events without making supervisors fill out fields that do not apply. If a near-miss form looks exactly like an injury report, long medical section and all, people stop filing near-miss reports because the form feels wildly out of proportion to the event.

A near-miss layout should include: date and time, location, description of what happened, what hazard was present, what injury could have happened, root cause, and corrective action. Six sections. One page. That covers what you need.

OSHA does not require near-miss reporting, since near-misses do not go on the 300 Log. But OSHA strongly encourages near-miss programs, and its accident investigation guidance treats near-miss tracking as a leading indicator of risk ^[4]. BLS injury data is a lagging indicator. Near-miss data is how you get out ahead.

If you want to see how this fits into broader program design, the OSHA basics overview covers the regulatory framework that makes incident reporting part of a larger compliance picture.

What does a completed incident report layout look like as a field-by-field template?

Here is a stripped-down template you can build from. It is not a fillable form, but it maps every field in order with notes on what each one captures.

--- INCIDENT REPORT FORM | Version: _______ | Report #: _______

SECTION 1: REPORT INFORMATION Date of report: ___ | Completed by: ___ | Title: ___

SECTION 2: INCIDENT DATE AND TIME Date of incident: ___ | Time: ___ | Shift: ___

SECTION 3: LOCATION Facility: ___ | Department: ___ | Specific location: ___

SECTION 4: INJURED/ILL PERSON Name: ___ | Job title: ___ | Department: ___ | Hire date: ___ | Time in current role: ___ Privacy concern case? Yes / No (if yes, do not enter name on OSHA 300 Log)

SECTION 5: INCIDENT DESCRIPTION (attach additional pages if needed) Describe in the injured person's own words what happened, including sequence of events: [8-line field]

SECTION 6: INJURY OR ILLNESS Body part: ___ | Side: Left / Right / N/A | Nature: ___

SECTION 7: ROOT CAUSE Immediate cause: ___ Contributing causes: ___ System or root cause: ___

SECTION 8: WITNESSES Name: ___ | Contact: ___ | Statement collected? Yes / No

SECTION 9: MEDICAL TREATMENT First aid only? Yes / No Referred to physician? Yes / No Employee visited physician? Yes / No Prescription medication required? Yes / No Hospitalized overnight? Yes / No

SECTION 10: LOST TIME AND RESTRICTIONS Days away from work: ___ | Days restricted: ___ | Return-to-work date: ___

SECTION 11: OSHA RECORDABILITY Is this case recordable? Yes / No | Determined by: ___ | Date: ___ OSHA 300 Log updated? Yes / No | Date: ___ | Classification: ___

SECTION 12: CORRECTIVE ACTIONS

SIGNATURES Injured employee: ___ | Date: ___ Supervisor: ___ | Date: ___ Safety officer (if applicable): ___ | Date: ___

RETENTION NOTE: Retain this record until ___ (five years from end of calendar year).

---

That is a complete layout you can adapt. Print it at full 8.5 x 11, give narrative sections real space, and you have a functional incident report that satisfies 29 CFR 1904 and gives you data worth acting on. If you want a version pre-populated for your industry and already mapped to OSHA 300/301 requirements, SafetyFolio generates these as part of a complete written safety program.

Frequently asked questions

Is there a specific OSHA-required format for incident reports?

OSHA does not mandate a specific layout. Under 29 CFR 1904.29, you can use OSHA Form 301 or an equivalent form that captures the same information. The fields required by the 301 include incident date, employee information, incident description, nature and body part of injury, and medical treatment details. Any format that covers those fields is compliant.

How quickly does an incident report need to be completed after an incident?

OSHA's rules require entries to the 300 Log within seven calendar days of receiving information that a recordable case occurred, under 29 CFR 1904.29. Most safety programs require the initial incident report within 24 hours. For fatalities, OSHA requires you to report by phone or online within eight hours of learning about the death.

Can one incident report cover multiple injured employees from the same event?

No. OSHA's 300 Log and 301 requirements are per-person. Each injured or ill employee needs their own case number, their own 301 (or equivalent incident report), and their own 300 Log entry. If three workers are hurt in a single event, you file three incident reports and three log entries.

What is a privacy concern case and how does it affect the incident report layout?

Under 29 CFR 1904.29, certain cases must have the employee's name kept off the OSHA 300 Log to protect privacy. These include sexual assaults, mental illness, HIV/AIDS, and injuries to reproductive organs. Your incident report still captures the full name, but a checkbox flags it as a privacy case so whoever enters it to the 300 Log writes 'privacy case' in the name column instead.

Do near-miss incidents need to follow the same layout as injury reports?

Not exactly. Near-miss reports do not need the medical treatment or lost-time sections because no injury occurred. A near-miss layout should focus on incident description, the hazard that was present, what injury could have resulted, root cause, and corrective action. Keeping the form shorter encourages workers and supervisors to actually file near-miss reports.

Should the injured employee fill out the incident report or the supervisor?

Both should contribute. The best practice is to have the injured employee give their account of what happened, then have the supervisor complete the investigation fields including root cause and corrective action. Both sign. This two-input approach captures worker perspective, which is often more accurate about the sequence of events, plus management analysis, which drives corrective action.

What happens if an incident report is incomplete or missing when OSHA inspects?

A missing or incomplete 301 Incident Report for a recordable case is a recordkeeping violation under 29 CFR 1904.29. OSHA can cite it as other-than-serious or serious. As of 2024, penalty amounts run up to $16,131 per willful or repeated violation. Incomplete records also make it harder to defend against workers' comp claims or litigation.

How should a small business with no safety officer manage the OSHA recordability decision on their incident report?

Name one person, usually the owner or operations manager, to make the recordability call for every incident. Build a decision checklist into the layout itself: medical treatment beyond first aid, days away, restricted work, loss of consciousness, and significant diagnosis each trigger a recordable case under 29 CFR 1904.7. The checklist removes ambiguity and documents the decision.

Does a workers' comp first report of injury replace the OSHA 301 Incident Report?

Sometimes, not always. If your workers' comp form covers all the fields OSHA Form 301 requires, you can use it as your equivalent form. But many workers' comp forms do not ask about root cause, corrective action, or recordability classification. Check field by field. If there are gaps, supplement the workers' comp form or keep a separate OSHA 301 for each recordable case.

How do you track corrective actions that come out of incident reports?

The corrective action section should assign each action an owner and a due date. Then someone, a safety officer or the operations manager, checks those actions off as completed. A simple tracker works: a shared spreadsheet with columns for report number, action, owner, due date, and completion date. Review it weekly. Unresolved actions older than 30 days need escalation.

Can you use a mobile app for incident reporting and still satisfy OSHA requirements?

Yes. OSHA does not require paper for the 301 or an equivalent form. Electronic records are fine as long as they stay accessible to employees and OSHA within the required timeframes under 29 CFR 1904. You do need to be able to produce printed copies if OSHA asks during an inspection, so make sure your system can export records in a readable format.

What is the difference between an incident report and an accident report?

In most safety programs they are the same document with different names. 'Incident' is the preferred term in modern safety practice because it covers a broader range of events, including near-misses, illnesses, and property damage. OSHA's own forms use the language 'injury and illness' rather than 'accident,' reflecting a shift away from the implication that events are random or unpreventable.

Should a property damage event get an incident report even if no one was injured?

OSHA's 300 Log only covers work-related injuries and illnesses to employees. It does not require logging property-only damage. But many safety programs document significant property damage on a separate incident or near-miss report, because property damage events often share root causes with injury events. Tracking them builds a fuller picture of where your hazards actually are.

How often should you review your incident report layout to make sure it still works?

Review it at least once a year, and whenever OSHA updates its recordkeeping forms or standards. Also review it any time completed reports keep missing information in the same field, which usually means the label is unclear or the field is too small. A layout that made sense at 10 employees may not work at 50.

Sources

1. Bureau of Labor Statistics, Employer-Reported Workplace Injuries and Illnesses (2023): 2.6 million nonfatal workplace injuries and illnesses recorded in private industry in 2023
2. OSHA, Recordkeeping Rule 29 CFR Part 1904: Requirements for OSHA 300 Log, 300A Summary, and 301 Incident Report including fields, retention periods, access rights, and privacy concern cases
3. Bureau of Labor Statistics, Injuries, Illnesses, and Fatalities program: Elevated injury rates among workers in their first year in a role, especially early months
4. OSHA, Incident Investigation guidance: Three-level cause analysis and near-miss tracking as part of OSHA's accident investigation approach
5. OSHA, Civil Penalty Adjustments for Inflation (2024): OSHA maximum penalty of $16,131 per willful or repeated violation as of 2024
6. OSHA, 29 CFR 1904.7 General Recording Criteria: Definition of recordable cases including medical treatment beyond first aid, days away from work, restricted work, and the closed list of first aid treatments
7. OSHA, 29 CFR 1904.29 Forms: Employers may use OSHA Form 301 or an equivalent form that captures the required information for each recordable injury or illness
8. OSHA, 29 CFR 1904.33 Retention and Updating: OSHA 300 Log, 300A, and 301 records must be retained for five years following the end of the calendar year they cover
9. OSHA, 29 CFR 1904.35 Employee Involvement: Employees and their representatives have the right to access injury and illness records; current and former employees may request copies of their own 301 records