Why near misses deserve real paperwork

The most valuable safety documents on any site are not the reports about injuries. They are the reports about the injuries that almost happened. A dropped tool that landed a meter from someone, a stand of pipe that swung free, a reversing loader that stopped short: each is a full-scale test of your safety systems that cost nothing. The incident pyramid, drawn from decades of industrial data, suggests that for every serious injury there are hundreds of near misses and unsafe conditions underneath it. The generator above turns those events into a clean, consistent, printable report in about two minutes, which matters because reporting friction is the main reason near misses go unrecorded.

Safety incident pyramid diagram showing one serious injury on top of roughly ten recordable injuries, thirty first aid cases, and six hundred near misses and unsafe conditions — The incident pyramid: every serious injury sits on a broad base of near misses. Reporting the base keeps the top empty.

A good incident report does a few specific jobs. It fixes the facts while memories are fresh, separates what happened from why it happened, records what was done immediately, and commits someone to a follow-up action. The form is structured around exactly that sequence, and it deliberately keeps the description field free of leading questions, because the first account should be the reporter telling the story in their own words and their own order.

Writing a description that will still be useful in a year

Stick to observable facts in time order: what was happening, what changed, what resulted. Save opinions about cause for the cause field.
Name equipment and positions precisely: not the pipe fell but a stand of 5 inch drill pipe swung out of the fingerboard at the racking board level.
Record the line of fire explicitly, whether anyone was in it, and by how much they missed being in it. That distance is the difference between a near miss and a fatality report.
Avoid blame language entirely. Reports written to punish get sanitized; reports written to learn get accurate.

The potential severity field is worth a moment of honesty. Classify the event by what could reasonably have happened, not by what did. A dropped hammer that hit nobody is a low actual consequence with a high potential severity, and it is the potential number that should drive how deeply the follow-up digs. Most mature HSE systems trigger a formal investigation above a potential severity threshold regardless of actual outcome.

Where the report goes next

A report that gets filed and forgotten teaches nothing. The follow-up field commits a specific preventive action, and the sign-off block routes the report through the supervisor and HSE reviewer so the action has owners. On a well-run site, near miss reports feed the weekly safety meeting, recurring patterns feed the hazard register, and the count of reports per month is tracked as a leading indicator: a rising report rate with a falling injury rate is the healthiest signature a safety program can show. Print the finished report to PDF, get the signatures, and keep the paper trail alive.

Related Calculators and Reference

Site Inspection Checklist Generator for the proactive side of the same safety system.
Daily Drilling Report Generator where incidents get cross-referenced on the operational record.
Mud Check Report Generator and Cementing Job Report Generator for the other daily paperwork.
External reference: OSHA recordkeeping requirements for which incidents are recordable and how long records must be kept.