Form & Learning Loop

Near-Miss Investigation Form & Learning Loop

A short, non‑punitive interactive near‑miss report plus a repeatable learning loop: capture who/what/when, containment, causes, corrective and preventive actions, owner, verification, and communication steps. Designed to be quick to complete and to store structured reports for follow-up and analytics.

Interactive Tool

Near‑Miss Report & Learning Loop

Purpose: Capture near misses quickly in a non‑punitive way so hazards are analyzed and addressed before they cause injury, downtime, or quality loss. This form is for learning — not punishment. If the situation is an emergency, stop and follow your workplace emergency procedures first.

How to use: Fill the minimum fields needed to explain the event. If you prefer not to be contacted, you may submit anonymously. High‑severity reports will trigger faster review and follow‑up.

Check to omit your name from the stored report. Note: anonymous reports may limit our ability to follow up with questions.
Optional unless you want to be contacted about follow up.
Use format YYYY-MM-DD HH:MM (local time). If unsure, enter approximate time.
Be specific so reviewers can investigate quickly.
Describe the sequence of events in plain language. Include conditions, actions, and any equipment involved.
What was done right away to stop harm or limit risk (e.g., stopped machine, isolated area, provided first aid, removed material)?
1 = Minor (first aid), 3 = Lost time/recordable, 5 = Major/severe
1.0 10.0
Choose all that seem relevant; you can add detail below.
Use this space to describe why the event happened (not just what). Consider how systems, tools, training, or environment contributed.
Any immediate fixes to make the situation safe until a permanent solution is implemented.
Suggest one or more actions that would prevent recurrence (training, engineering change, SOP update, maintenance, signage, etc.). Be specific where possible.
If you don't know, suggest a role (e.g., Maintenance Lead, Shift Supervisor).
Optional. Use YYYY-MM-DD or a relative target (e.g., end of month).
One or two sentences that can be shared at huddles or posted on the safety board.
Checking confirms you understand the non‑punitive intent. If you have concerns, contact your safety representative.
If you have photos or document IDs stored elsewhere, list the file name or reference so reviewers can find them.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
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.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.