Near Miss Report Template: Capture Potential Harm and Prevent Recurrence

A near miss report template helps people record an event that had the potential to cause injury, ill health, damage, loss or disruption even though the feared outcome did not occur. The purpose is learning and prevention, not proving that nothing was wrong.

Use your organization’s approved definitions, emergency procedures and reporting channels. An initial reporter should describe observations and protect people; trained safety, operational, HR, legal or other responsible reviewers determine classification, investigation depth and required notifications.

Make reporting easy and non-punitive

People report more useful information when the route is visible, quick and psychologically safe. Explain what counts as a near miss under local policy, where to submit it and what happens next. Allow urgent verbal escalation while requiring the key facts to be transferred into the controlled record.

Avoid forms that demand a root cause or corrective solution from the observer. The reporter may know exactly what they saw but not why a system failed. Separate factual reporting from later analysis so uncertainty is not disguised as certainty.

Supervisors should acknowledge the report and address immediate exposure without blaming the reporter. Deliberate misconduct, employment issues or legal questions may need separate authorized processes; the near miss form should not prejudge them.

Copy this near miss report template

NEAR MISS REPORT

Report ID / date submitted:
Reporter contact or approved anonymous route:
Event date and time:
Location / activity / equipment involved:

WHAT WAS OBSERVED
Sequence of events:
Conditions immediately before the event:
What prevented or limited harm:
Actual outcome, if any:
Potential people / assets / operations affected:

IMMEDIATE RESPONSE
Work stopped or area controlled:
People notified:
Temporary controls applied:
Emergency or specialist support requested:

EVIDENCE
Witnesses or information sources:
Photos / records / equipment status:
Privacy or access restrictions:

REVIEW AND ACTION
Initial classification / reviewer:
Investigation required / owner / due date:
Contributing factors confirmed:
Corrective or preventive action / owner / due date:
Authorization required:
Effectiveness check / date / evidence:
Closure decision / authorized reviewer:

Adapt the fields to the operating environment. Do not let a generic template replace mandatory forms, notification routes or emergency action.

Describe the event sequence objectively

Record what happened in chronological order: the activity underway, the trigger, the movement or change observed, and how the event ended. Use concrete details such as position, direction, task stage or equipment state where known. Label estimates and second-hand information.

Avoid conclusions such as “careless operator” or “equipment failure” in the observation field unless evidence has established them. A useful statement distinguishes “the load shifted when lifted” from an unverified explanation of why it shifted.

Include the work state that made the sequence understandable: whether the task was starting, running, changing over or shutting down; whether guards, permits or handoffs were involved; and whether conditions had changed from normal. Record measurements only when they were obtained safely and the method is known. If timing, distance or equipment state is uncertain, preserve the range or uncertainty instead of converting recollection into a precise fact.

Record the actual outcome separately from potential harm. If anyone may have been injured, exposed or medically affected, follow the approved incident and health response immediately; do not use the near miss label to bypass care or reporting.

Assess credible potential harm

Describe who or what could reasonably have been affected and the plausible type of harm. Consider employees, contractors, visitors, the public, property, environment, data and continuity where relevant. Avoid sensational worst cases that are not connected to the observed event.

Use the organization’s risk method to assess consequence and likelihood. The assessment should be performed or reviewed by an authorized, competent person. A risk register template can connect a recurring exposure to broader ownership without replacing the event record.

Escalate events with credible severe potential even when no harm occurred. Frequency and severity are different signals: a rare event with serious potential may require immediate controls, while repeated lower-consequence events may reveal a persistent weakness.

Apply immediate controls without obscuring evidence

Protect people first. Stop work, isolate an area, remove an item from service or call specialist support only within training and authority. Emergency procedures take priority over completing the form.

Record what changed, who authorized it and whether the control is temporary. Preserve relevant evidence without creating additional risk. Do not move, repair, reset or discard equipment merely to restore production if policy requires the condition to be secured for review.

Temporary controls need an expiry or review point. A warning sign or verbal reminder may reduce exposure briefly but should not silently become the permanent response.

Preserve evidence and privacy

Potential evidence may include photographs, equipment logs, work instructions, permits, maintenance records, environmental conditions or witness accounts. Capture only what is safe, authorized and relevant. Record source, time and access restrictions so reviewers can assess reliability.

Interview people separately where appropriate and use open questions. Do not coordinate a shared version of events. The research interview notes template offers neutral note-taking patterns, although a safety investigation must follow its own competent process.

Limit personal and medical information to what policy requires. Store sensitive records in approved systems, not an open team channel. If recording a review discussion, obtain authorization and notice and follow retention rules.

Classify and route the report correctly

Terminology differs across organizations. An event described as a near miss in one system may be an incident, dangerous occurrence, quality deviation or environmental event in another. The reviewer should apply the current definitions and document any reclassification.

Define escalation triggers for actual harm, high potential severity, repeated events, regulatory relevance, public impact, suspected tampering or uncertainty about mandatory reporting. Qualified specialists decide legal and external reporting obligations.

Maintain one primary record ID even if the event routes into multiple workflows. Cross-reference related cases rather than copying inconsistent narratives into disconnected systems.

Investigate contributing factors

Choose investigation depth based on credible risk, recurrence and policy. Review the task, environment, equipment, materials, instructions, supervision, workload, change conditions and control design. Human action may be relevant, but stopping at “operator error” rarely explains why the system allowed the event.

Compare the work as planned with the work as actually performed. Check whether the approved procedure was available, usable and consistent with the equipment and workload. Ask what signals people had, what competing goals existed and what recovery opportunities were available. This does not remove individual accountability; it prevents the review from overlooking system conditions that could expose another person to the same event.

Where several contributing factors interact, show the relationship rather than forcing one root cause. An overdue maintenance item, ambiguous instruction and unexpected material condition may each matter. The investigation owner should decide which findings are supported, which remain hypotheses and which require specialist testing.

Distinguish evidence, inference and unknowns. Test possible explanations against records and observations. The audit evidence log template can index supporting material while preserving controlled access.

Use a decision log template when reviewers must choose among control options or formally accept a residual risk. Record who was authorized to decide and what information they relied on.

Assign corrective and preventive actions

Actions should address confirmed contributing factors and follow the applicable hierarchy or control-selection method. A stronger engineered or procedural control should not be replaced by training alone merely because training is faster to schedule.

Write each action as a verifiable change with one owner, due date, required approval and expected evidence. “Be more careful” is not a measurable action. “Install the approved guard and verify clearance before restart” identifies a result, though only qualified personnel may design or approve the actual control.

Use the corrective action report template when the response spans root-cause review, implementation and effectiveness verification.

Verify effectiveness before closure

Completion evidence shows that an action happened; effectiveness evidence shows whether it controls the intended risk. Observe the changed process, review relevant indicators, speak with affected workers and check for unintended consequences at an appropriate interval.

The closure reviewer should be independent enough for meaningful challenge and authorized under the organization’s system. If an action is late, ineffective or creates another hazard, keep the report open or escalate it. Do not close cases merely to improve dashboard performance.

Trend near misses by activity, location, equipment and contributing factor, while protecting identities. A rise in reports can reflect increased trust rather than deteriorating safety, so interpret volume with reporting quality and exposure context.

Use discussion capture responsibly

Near miss reviews may involve personal data, employment concerns and sensitive operational information. Invite only necessary participants, state the learning purpose and separate privileged or confidential processes when instructed by responsible specialists.

For an authorized safety review with clear participant notice, Kuno can help turn discussion into draft notes and actions for human verification. It does not classify events, assess risk or approve controls. Explore Kuno

Review any generated summary against witness statements and controlled evidence. Remove speculative causes and unnecessary personal detail before distribution.

Build a learning loop

Share verified lessons with affected teams in a form they can use. Explain the condition, the control change and who to contact, without naming or shaming individuals. Update procedures, training, maintenance or design records through their authorized owners.

Close the communication loop with the original reporter where policy and confidentiality allow. Explain that the report was reviewed, what changed and why some requested action may not have been selected. Visible follow-through helps staff distinguish meaningful reporting from a form that disappears into a queue, while sensitive employment or personal details remain restricted.

Review whether similar exposure exists elsewhere. A local correction may not address the same equipment, process or supplier condition at another site. Preserve both the original report and the broader action trail.

Make prevention discussions easier to review without outsourcing safety judgment. Kuno supports consented capture and draft follow-ups; responsible people verify facts, controls and closure. See Kuno

FAQ

The FAQ below addresses common questions about reporting, reviewing and closing near misses.