Incident & Near‑Miss Reporting Form + Investigation Steps

A frontline-friendly interactive incident and near‑miss report that captures required fields, preserves investigation evidence, and guides corrective actions and verification. Submissions are saved so teams can triage, assign owners, and close the learning loop.

Interactive Tool

Incident & Near‑Miss Report

Why report? Reporting incidents and near-misses helps prevent harm, preserve evidence, and turn learning into action. This form is designed to be quick for frontline use while capturing the information investigators need to act. If you prefer confidential reporting, enter 'Confidential' in the name field and notify your safety lead separately.

How to use: Complete the required fields immediately after the event. If you don’t know exact details, estimate (e.g., approximate time). Attach photos or reference IDs where available. After submission, investigators can update the record with findings, corrective actions, verification, and communications.

Use YYYY-MM-DD HH:MM if possible (local time). Approximate is acceptable.
Be specific (building, line, cell, machine).
If you prefer confidential reporting, enter 'Confidential' and contact the safety lead separately.
Optional for follow-up if you want one. Leave blank for anonymous reports.
Helps with context
One or two sentences explaining the event or near‑miss (what, who, outcome).
Select current condition after any immediate actions.
Paste URLs or system reference numbers. For file attachments use your usual upload process or attach to the incident record after submission.
List anyone who observed the event or was nearby.
Describe immediate steps to make the area safe or preserve evidence.
Were photos, equipment, logs, or other evidence preserved?
Who was interviewed, when, and key notes (useful for investigators).
Capture initial hypotheses to guide the investigation (example chain of why→why→why).
Mark yes if investigation has identified a likely root cause.
Describe actions planned to prevent recurrence, including interim measures.
Who is responsible for completing the action?
YYYY-MM-DD (approximate is acceptable).
How will the team confirm the action worked? (who, method, timing)
Select yes once verification confirms effective closure.
Date verification was completed.
Record who was informed and how (emails, toolbox talks, signage).
Select yes to request a follow-up contact.
Phone, email, or shift/location.
Helps triage response, investigators may adjust.
Indicate known impact to help escalation.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.

Discussion

Comments and conversation will live here.