How to Create an Incident Report: Templates and Examples

Direct answer: Create an incident report by recording what happened, where and when it happened, who was involved, the task and conditions, the harm or potential harm, the response, the evidence reviewed, contributing causes, and corrective actions. Write events in chronological order, separate observations from statements and analysis, and use the official form required by your employer or jurisdiction.

A generic template can help organize facts, but it cannot establish legal compliance everywhere. Requirements differ by country, industry, employer coverage, and incident type. In the United States, OSHA Forms 300, 300A, and 301 apply to covered injury and illness recordkeeping; in the United Kingdom, reportability under RIDDOR uses HSE instructions and forms. Northern Ireland has separate HSENI investigation guidance. Check the current official rules before submitting a regulatory report.

1. Handle immediate safety needs first

Get emergency medical help and control immediate hazards.
Secure the area so people do not face additional danger.
Preserve relevant evidence, including photographs, video, equipment settings, labels, samples, and records.
Notify the supervisor, safety contact, or emergency coordinator required by your process.
Record the time of notifications and any interim controls.

Do not delay urgent care or hazard control while completing paperwork. A report documents the event and supports prevention; it does not replace emergency response.

2. Identify the report’s purpose and audience

Before writing, state whether the document is an initial internal notification, a final investigation, a worker injury or illness record, an insurance document, or a regulator submission. The purpose determines what information is required and who may access it.

Report type	Primary use	Important caution
Initial incident notification	Alert responsible people and begin controls	Mark unknown facts as pending; do not guess.
Internal investigation	Reconstruct events and prevent recurrence	Include evidence, contributing conditions, and actions.
Injury or illness record	Meet an applicable recordkeeping rule	Use the required jurisdictional form and coverage rules.
Regulatory notification	Notify an authority within a specified rule	Confirm reportability, deadline, and submission method.

3. Use this incident report template

Copy the structure below into your organization’s form or document. Adapt fields to the incident and the applicable policy.

INCIDENT REPORT

Report ID:
Status: Initial / Final
Date prepared:
Prepared by (name and role):
Recipients and purpose:

INCIDENT DETAILS
Date and time of incident:
Exact location:
Task or activity:
Work area and environmental conditions:
Equipment, materials, or substances involved:

PEOPLE
Affected person(s) and role(s):
Witnesses (name, role, contact or statement reference):
Supervisor or person in charge:

FACTUAL ACCOUNT
Before the event:
At the event (chronological sequence):
After the event:
Observed harm, injury, illness, damage, or potential harm:
Immediate response and medical treatment, if applicable:

EVIDENCE REVIEWED
Photographs or video:
Equipment or material inspection:
Documents, procedures, permits, or training records:
Witness statements:
Measurements, sketches, or other records:
Evidence limitations or unresolved points:

ANALYSIS
Immediate event:
Contributing conditions:
Underlying or root causes supported by evidence:
Alternative explanations still being assessed:

CORRECTIVE ACTIONS
Action | Owner | Due date | Interim control | Status | Verification

ATTACHMENTS
Attachment ID, description, and reference in the report:

REVIEW
Investigator(s):
Worker or management participants:
Approval or review date:
Follow-up date:

For U.S. covered injury and illness records, OSHA describes collecting information about the affected employee, health professional and treatment when applicable, what the employee was doing, how the event occurred, the injury or illness, and the object or substance involved. See OSHA’s recordkeeping guidance and verify whether your workplace is covered.

4. Write a factual chronological narrative

Build the narrative so another person can reconstruct the event without being present. Use times where known, concrete descriptions, and source labels.

Useful sentence pattern

At approximately [time], [person] was [task] at [location].
The available evidence shows [observable event].
[Witness name or role] stated, “[short attributed statement].”
After the event, [response and condition].
The report confirms [known fact]; [unknown point] remains under review.

Prefer “At about 10:15 a.m., the cart’s front wheel stopped at the raised edge of the floor; the cart tipped and the load fell” over “the employee was careless.” The first sentence records observable events. The second assigns a conclusion without establishing evidence.

Separate three kinds of information:

Observation: what a person saw, measured, or recorded.
Attributed statement: what a witness or participant said, identified by source.
Analysis: an explanation supported by evidence, clearly labeled as such.

Do not turn an assumption into a fact. If camera footage, equipment inspection, or a statement is unavailable, say so and explain how that limitation affects the analysis.

5. Investigate contributing causes instead of assigning blame

OSHA’s incident-investigation guidance recommends finding and correcting root causes rather than focusing on fault. Its guidance also supports worker and management participation because each group may know different parts of the work. OSHA states: “Since nearly all worksite fatalities, injuries, and illnesses are preventable, OSHA suggests using the term ‘incident’ investigation.”

Ask questions that move beyond the final action:

What task and plan were in place?
What equipment, guard, control, or procedure was expected to prevent harm?
Was the control available, suitable, maintained, and used?
What environmental or scheduling conditions influenced the work?
Did training, supervision, staffing, communication, or procurement affect the situation?
What made the action likely, and what safeguard failed or was missing?

“Human error” may describe the last action, but it rarely explains why the system allowed the error to produce harm. Record only causes the evidence supports; identify open questions for follow-up.

6. Assign corrective actions that can be verified

Every action should have one owner, a due date, an interim control when risk remains, and a verification method. “Remind staff to be careful” is not a measurable action.

Weak action	Specific action	Verification
Improve housekeeping	Repair the raised floor edge in aisle 3 and inspect adjacent aisles.	Facilities work order and dated inspection photographs.
Retrain employees	Revise the cart route procedure, brief affected workers, and record attendance.	Approved procedure, attendance log, and supervisor observation.
Be more careful	Install a physical wheel stop or barrier before the next shift.	Safety inspection confirms installation and operation.

Track actions after the report is issued. OSHA recommends communicating findings and following corrective actions through completion.

7. Fictional example: completed short report

The following example is fictional and illustrates structure. It is not a real case and is not a legally sufficient form.

Report ID: WH-2026-014
Status: Initial investigation
Incident: 14 May 2026, approximately 10:15 a.m.
Location: Warehouse aisle 3, receiving area
Task: Moving a loaded cart from receiving to storage

Chronology:
At approximately 10:15 a.m., Jordan Lee was moving a loaded cart toward aisle 3.
The front wheel stopped at a raised floor edge, the cart tipped, and two boxes fell.
The camera recording shows the cart approaching the edge; the recording does not show
whether the wheel or load shifted first. Witness Priya Shah stated that the floor edge
was visible from the receiving side. Jordan reported pain in the right wrist.
The supervisor stopped traffic in the aisle, called the first-aid responder, and moved
other carts to a marked route. Jordan was evaluated according to the workplace process.

Evidence:
Camera recording C-014; photographs P-01 through P-04; floor measurement M-02;
witness statement W-01; cart inspection C-I-01.

Analysis:
The immediate event was the cart wheel stopping at the raised edge. Contributing
conditions include the floor defect and the absence of a marked alternate route.
Whether the load height affected stability remains under review.

Actions:
Facilities: repair and measure the floor edge by 16 May; interim barrier installed 14 May.
Warehouse manager: mark an alternate route and brief cart users by 15 May.
Safety lead: review cart-load limits and verify controls on 20 May.

8. Evidence, attachments, and privacy

Label every attachment with an ID and reference it in the narrative. Preserve original files, record who collected them and when, and avoid editing photographs or video in a way that removes relevant context.

Photographs: include location, direction, scale, and date or file metadata where available.
Video: preserve the original export and note camera location and time settings.
Statements: record the speaker, date, interviewer, and whether the words are quoted or summarized.
Measurements: identify the instrument, method, and units.
Records: include the relevant procedure, permit, inspection, maintenance, or training version.

Treat personal and medical information under your organization’s privacy and records rules. Include only what the form and legitimate purpose require. A detailed OSHA Form 301 record does not mean sensitive treatment details belong in a report distributed to everyone.

9. Choosing a template

Compare templates by the questions they help you answer:

Criterion	What to check
Legal and organizational fit	Does it match the applicable employer policy and jurisdiction?
Incident coverage	Can it handle injury, illness, near miss, property damage, and environmental events as needed?
Reconstruction	Does it capture time, place, task, sequence, people, conditions, and equipment?
Evidence	Can you reference photographs, video, measurements, statements, and records?
Analysis	Does it separate immediate events from contributing and underlying causes?
Actions	Are owner, due date, interim control, status, and verification included?
Privacy and access	Can sensitive information be restricted while findings reach the right people?
Scene usability	Can a person complete it safely and quickly on a phone, tablet, or paper?

For U.S. requirements, start with OSHA’s recordkeeping resources. For the UK, use HSE’s RIDDOR reporting instructions. For Northern Ireland, review the HSENI workplace accident/incident investigation template. These resources serve different purposes; do not call a generic template compliant without checking coverage and current rules.

10. Deadlines and jurisdiction checks

Deadlines depend on the jurisdiction and event category. OSHA’s cited U.S. examples require notification within 8 hours of a work-related fatality and within 24 hours of an amputation, loss of an eye, or inpatient hospitalization. These are not universal deadlines. Confirm whether the event qualifies, whether your employer is covered, and which current submission channel applies.

11. Or skip the browser setup

If your report needs a clean record of a public incident page, policy page, status page, or other web evidence, ScreenshotNeo can capture it with one request. It accepts consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers. It also provides an MCP server for Claude, Cursor, and other MCP clients.

See the ScreenshotNeo documentation for all options.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://example.com/status \
  -o incident-evidence.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com/status"},
    timeout=90,
)
r.raise_for_status()
open("incident-evidence.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://example.com/status'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const data = Buffer.from(await res.arrayBuffer());
await Bun.write('incident-evidence.webp', data);

Use a stable, permitted URL and retain the capture timestamp and URL with your evidence log. ScreenshotNeo also supports full-page capture, element selectors, custom headers and cookies, waiting for a selector or network idle, blocking resource types, PDF output, caching with a chosen TTL, signed links, asynchronous jobs, bulk capture, and usage reporting. Choose settings that preserve the evidence needed for your investigation.

Pricing: the Free plan includes 1,000 shots per month with no card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Create a free ScreenshotNeo account.

12. Troubleshooting checklist

Problem	Likely cause	Fix
The report reads like an opinion	Facts, statements, and analysis are mixed.	Label the source of each claim and move conclusions to the analysis section.
The timeline has gaps	Times were estimated or records were not checked.	Use timestamps from logs, cameras, access records, and statements; mark unknowns.
The report blames a worker	It stops at the final action.	Examine equipment, procedures, planning, training, supervision, and conditions.
Actions are never completed	No owner, date, or verification exists.	Assign one owner, a due date, an interim control, and a follow-up review.
Sensitive details spread too widely	The same document is sent to every audience.	Limit medical and personal details and use access controls or separate records.
Screenshot is blank or blocked	The page timed out, required a bot check, or failed to load.	Inspect `X-Page-Verdict`; adjust wait conditions or capture settings and preserve the verdict.
Screenshot contains a popup	A consent, newsletter, or chat element was not removed.	Enable the relevant cleanup step or hide the selector before capture.

13. Performance, reliability, and cost notes

Capture evidence as soon as practical, then store the original response with URL, timestamp, and report ID.
Use a selector or a focused viewport when a full page is unnecessary; use full-page mode when context matters.
Wait for a selector, delay, or network idle when content loads asynchronously.
Use caching with a deliberate TTL for repeated reference captures, but avoid caching when the page changes frequently.
For large investigations, asynchronous jobs and bulk capture can reduce manual repetition; verify each result before attaching it.
Only clean shots are billed by ScreenshotNeo. Failed loads, bot checks, blank pages, timeouts, and cache hits are not billed.

FAQ

Can I use a generic incident report template?

Yes, as an internal starting point, but compare it with your employer’s form and current official requirements. A generic document cannot establish compliance for every jurisdiction or incident.

Should I include the injured person’s diagnosis?

Include only the medical information required by the applicable form and legitimate purpose. Restrict access to sensitive details.

What if nobody saw the incident?

State that there were no direct witnesses, then use physical evidence, recordings, logs, measurements, and participant accounts. Mark conclusions as provisional when evidence is limited.

Is a near miss worth reporting?

Follow your organization’s process. Near misses can reveal failed controls before someone is injured, so record the potential harm and the corrective actions even when no injury occurred.

When is an incident report final?

When the required evidence has been reviewed, unresolved questions are documented, responsible reviewers have approved the findings, and corrective actions have owners and follow-up dates.

Final review checklist

Immediate hazards and medical needs were addressed.
Purpose, audience, status, author, and report ID are clear.
Date, time, exact location, task, people, equipment, and conditions are recorded.
The narrative is chronological and distinguishes observations from statements.
Evidence and limitations are listed and attached references are labeled.
Contributing causes are examined without unsupported blame.
Actions have owners, due dates, interim controls, and verification.
Privacy, retention, and access rules were applied.
Jurisdiction-specific forms and deadlines were checked before submission.