Near-Miss Reporting That Actually Produces Actions

Many sites collect near-miss cards and report the number each month. A rising number is celebrated as a good reporting culture. But a count tells nobody what changed on site.

A near miss is a free warning about a control that did not hold. The value is in what happens after the card is written.

Why reports go nowhere

• The form asks what happened but not what control failed.
• Nobody owns the follow-up, so the card is filed.
• The reporter never hears back, and stops reporting.
• Reports sit in a folder separate from the risk register, so the assessment never changes.

A flow that produces actions

1. Capture: location, what nearly happened, and the credible worst outcome.
2. Triage within a target time your site sets: is this a one-off, or does it point at a control that applies elsewhere?
3. Assign: every accepted report gets an owner and a due date, or a written reason why no action is needed.
4. Link: connect the report to the risk register entry it challenges, and review that entry.
5. Close the loop: tell the reporter what was done, in person or at the next briefing.

Rate by potential, not by outcome

Near-miss reporting here is about internal learning. It does not replace any statutory duty to notify the authority of an incident, which depends on the emirate and the authority with jurisdiction over the site.

Nobody was hurt, so the temptation is to rate it low. Rate it by the credible worst outcome. A dropped tool from height that landed in an empty area carries the same potential as one that landed on a person.

Measure what matters

• Share of reports triaged within your target time.
• Share of actions closed by their due date.
• Number of risk register entries reviewed because of a report.
• Repeat reports for the same hazard — a sign the earlier action did not work.

These are leading indicators you can act on. The total number of cards is not.

"General practice guidance, not legal advice and not a statement of any authority's requirements. Permit, reporting, briefing and coordination rules are set by the applicable authority (for example ADOSH-SF in Abu Dhabi, Dubai Municipality, Trakhees, DSOA, JAFZA or the relevant emirate municipality), the client and the main contractor. Where they differ from this article, follow them."

Continue with

• Inspections & Incidents module — https://sitesafetyuae.com/modules/inspections
• Risk Register Best Practice — https://sitesafetyuae.com/resources/site-risk-register-best-practices
• Risk Matrix Scoring Drift — https://sitesafetyuae.com/resources/risk-matrix-scoring-drift-uae-sites

Site Safety UAE builds the HSE Operations Dashboard for UAE and GCC construction projects — permits, inspections, incidents and risk actions in one place. Start free, no card required — https://sitesafetyuae.com/get-started.