How do you document and track a near-miss incident?

• A. Prompt reporting, investigation to determine root causes, corrective actions, effectiveness monitoring, and sharing lessons.
• B. Wait for multiple incidents before filing a report.
• C. Only inform supervisor; no investigation.
• D. Documentation is optional.

Answer: (A)

Documenting and tracking a near-miss is about quickly capturing what happened, digging into why it happened, putting preventive actions in place, checking that those actions work, and sharing what was learned to prevent recurrence. Prompt reporting preserves accurate details while they’re fresh, and it signals that safety learning starts before an incident occurs. Investigating to uncover root causes goes beyond blaming someone; it seeks underlying factors—conditions, processes, or controls that allowed the near-miss to happen—so you can address the real risks rather than just the symptoms. Implementing corrective actions targets those underlying factors, not just the surface issue, and monitoring their effectiveness ensures they actually reduce risk over time. Sharing lessons learned helps others anticipate similar hazards and prevents the same mistake from occurring elsewhere. This proactive approach turns near-misses into valuable safety intelligence and supports continuous improvement.

Choosing to wait for multiple incidents delays learning and misses the opportunity to prevent a real injury or damage. Limiting reporting to informing a supervisor without any investigation leaves you blind to root causes and missed improvements. Treating documentation as optional erodes safety records and makes it harder to track progress or demonstrate accountability.