Keep the questions to what matters
A near miss report doesn't need the depth of a full incident investigation. What actually happened, where on the site, what type of hazard was involved, what could have happened if circumstances had been slightly different, and what corrective action was taken or is needed — that's enough to act on. Anything beyond that starts adding friction that discourages the next report.
Make it available where the moment happens
A worker is most likely to report a near miss immediately after it happens — not at the end of a shift, not after finding a supervisor, not after locating a form. The same QR code already posted for other inspections, or on a hard hat sticker, works here too: scan, report, done, while it's still fresh and while the motivation to report it is still present.
Close the loop
A report that disappears into a system with no visible outcome teaches workers that reporting doesn't accomplish anything. A supervisor dashboard where near miss reports are reviewed, confirmed, and — critically — where the resulting corrective action is visible back to the crew closes that loop. It doesn't need to be complicated: confirming a report was seen and acted on is often enough to keep the next one coming.
A pattern across multiple near miss reports — the same hazard type showing up repeatedly across a site — is more actionable than any single report. Categorizing reports by hazard type (falling objects, defective equipment, slips and trips, PPE gaps) makes those patterns visible instead of buried in a pile of individual incidents.
What this looks like in practice
A worker sees a near miss, scans the same QR code they use every morning for their FLHA, selects Near Miss Report, answers a handful of questions about what happened and what hazard type it involved, signs, and submits — GPS-stamped, timestamped, on the supervisor's dashboard immediately. No separate app, no separate process to remember, no reason to skip it because it felt like too much effort.