Improving your reporting culture: how to get more near-miss reports

Why do employees not report?

It is rarely unwillingness. Usually an employee weighs costs against benefits, consciously or not. A report takes time, may lead to an unpleasant conversation and visibly leads nowhere. Then not reporting is the easy option. These are the reasons you hear most often:

• Fear of being called to account, embarrassment or a poor appraisal
• The feeling that reporting changes nothing anyway
• It ended well, so it is not a big deal
• Reporting is cumbersome: a form, logging in, time that is not in the schedule
• Uncertainty about what is worth reporting
• A team target such as days without an accident, which makes a report feel like spoiling the result

Diagnose before you choose measures

Simply ask, preferably anonymously: when did you last report something, what held you back and what happened afterwards? Three questions in a toolbox or a short survey already point the way. Which of the reasons above applies to you determines what you tackle first.

Also compare sources. If inspections regularly find unsafe situations while there are hardly any reports, the gap is not in the workplace but in the reporting. Look per department too: a department without reports rarely has no risks.

Make reporting low-threshold

The less effort a report takes, the more often it comes. Let employees report from their phone, with a photo or a short voice recording, and ask in the first report only what happened, where and when. A QR code on the shop floor or in the van lowers the threshold even further.

Also make clear what is worth reporting, with recognizable examples: a missing guard, a leak, a vehicle that nearly reversed over someone. If in doubt, report. An unnecessary report costs less than a missed one.

Feedback is the engine of the reporting culture

Nothing undermines reporting as quickly as a report that disappears in silence. So build feedback from three layers, and make the third a standing item in your team meeting or toolbox:

• Acknowledgement: the report has been received and someone has looked at it, preferably the same day
• Interim update: what are we going to do about it, who will do it and when
• Outcome: what has changed, made visible to the whole group with the message that it came from a report

What it looks like in practice

A technician reports from his phone that the guard of a saw is missing after the workshop moved. The same day he receives an acknowledgement. Within a week the supervisor says that a new guard has been ordered and who will fit it. Two weeks later the workshop manager discusses the result in the team meeting.

Those three touchpoints together cost little time, and they show the whole team that a report achieves something. Best of all, the report is a reason to check all the other machines. That way one reporter solves the problem for everyone.

No blame culture: what supervisors do and avoid

The supervisor's first reaction decides everything. Start with thank you and with the question of what happened, not who did it. Never use reports in an appraisal and do not set targets such as zero reports. Reward reporting, not silence.

Supervisors who report themselves show that it is normal. Where possible, offer the option to report anonymously, and be honest about what you do with the data. A report used against the reporter costs you every report that would have followed.

Making it measurable: is the reporting culture really improving?

More reports is actually a good sign at first. It usually means people dare to report more, not that it has become less safe. So look at the composition and quality of reports too, not just the total. Useful indicators:

• Number of reports per 100 employees per quarter, especially near misses and unsafe situations
• Ratio of near misses to accidents with injury: a growing share of near misses is usually a good sign
• Share of reports answered within the agreed time
• Lead time from report to completed measure
• Spread: do reports come from all departments and shifts, or from one group
• The score on a statement such as I dare to report a near miss in an employee survey

An approach for the first ninety days

Start with a baseline: count the current reports per department and ask the three diagnostic questions. Then make reporting easier, agree with supervisors how they respond and announce that reports are welcome. Say what you will do with them.

Then discuss reports and outcomes on a regular schedule, for example weekly in the team meeting and monthly in a toolbox. Measure again after three months and share the result with everyone, even if it disappoints. That makes the reporting culture a shared project, not a control tool.

How BrydgeOne supports this

In Incidents & reports, reports come in via the platform, the employee app or a public reporting point with a link or QR code, anonymously if desired, and the reporter automatically receives status updates. You follow up measures in Actions, with an owner and deadline.

With Toolbox talks you share outcomes with the team and record attendance. With Satisfaction, employees take part in an anonymous survey, for example about their willingness to report, and you follow up low scores in a structured way.