Why Reporting Should Be Simple

One of the things we've seen consistently over the years is how easily incident and hazard reporting can become more complicated than it needs to be.

It is not difficult to see why. When something happens at work, there can be a lot of information that eventually needs to be gathered and a number of people who may need to be involved. Managers may need to understand the circumstances and what immediate action has been taken. Safety teams may need to review the event, assess its significance and determine what happens next. Injury management, insurance, regulatory or other organisational requirements may also come into play.

The challenge is that, over time, much of that downstream complexity can find its way into the first reporting step.

That first report has a much simpler purpose. Someone has been injured, a near miss has occurred, a hazard has been identified or something simply does not look right, and the organisation needs to know about it.

Most people making that report are not safety professionals. They may only report something occasionally, they may only know part of what happened, and they may not understand how the organisation classifies different events, applies severity ratings or decides what process should follow.

But the process can sometimes ask them for information and context in areas they might not fully understand.

We've seen forms and processes that are comprehensive from the organisation's point of view but much harder to navigate for the person actually trying to raise the issue. What makes sense to the people receiving the information does not always make sense to the person providing it.

That can create more work for everyone. Information may be incomplete or inconsistent, managers and safety teams may need to go back and clarify what was entered, and in some cases people may decide that reporting something is simply too difficult.

One of the simplest ideas we've heard through our work is also one of the most useful: tell us what happened.

The first step should make it easy for someone to explain what they know. The people with the right experience and responsibility can then work through the detail that follows.

That does not mean removing rigour from safety management. In many ways, it means putting the rigour in the right place.

We've seen safety teams put a great deal of thought into creating a reporting experience that is straightforward for workers while still giving the organisation what it needs further through the process. Technology can play an important part in supporting that, particularly when it helps make reporting accessible, guides people through the right questions and allows more complex triage and workflow to happen behind the scenes.

The reporting process itself still relies heavily on people.

The person making the report provides what they know. A manager can follow up, understand the immediate context and make sure the person involved is supported. The safety team can then bring the experience and judgement needed to review what happened, apply consistency and determine what needs to happen next.

That division of responsibility matters because not everybody should be expected to understand or manage the entire safety process.

The same applies to classification. Whether something is considered an incident, near miss or hazard can matter greatly to the organisation, but that does not necessarily mean the person making the initial report is best placed to decide. The significance of an event may only become clear once more information is gathered, and different people can reasonably interpret the same event in different ways.

In our experience, understanding what happened first is often more useful than trying to classify it too early.

There can also be much more behind a single event than the original reporter could reasonably be expected to untangle. An event might involve an injury, property damage, environmental impact or several people across different parts of the organisation. Different teams may ultimately need different information, but the reporting process should not require the person at the front end to understand how all of those pieces fit together.

That complexity still needs to be managed. It just does not all need to sit with the person making the first report.

Accessibility is another part of the same problem. In large and distributed workforces, people may be working in the field, moving between sites, travelling or away from immediate access to a manager or desktop system when something happens. A reporting process that works well in an office may be far less useful somewhere else in the business.

This matters particularly for hazards and near misses, where the perceived significance of the issue may be relatively low and the effort required to report it can influence whether it is raised at all.

Something else we've seen is that making reporting easier can sometimes lead to more reports. That can initially look like the organisation has more problems, when in reality it may simply have better visibility of what was already happening.

That visibility can be incredibly valuable. A hazard raised before somebody is injured gives the organisation an opportunity to act, while a near miss that is reported and followed up creates an opportunity to learn without first experiencing a more serious consequence.

Behind a good reporting process is a lot of work that most people will never see. It is the manager who follows up properly, the safety professional who asks another question, the person who checks whether an event has been classified appropriately, and the team that looks beyond one report to understand whether the same risk may exist somewhere else.

We've been fortunate to work alongside many people who do that work well. They understand how complex workplace safety can be, but they also spend a lot of time trying to make that complexity easier for the rest of the organisation to navigate.

For us, that is one of the clearest lessons around reporting.

The organisation may need a complex safety process behind the scenes, but reporting something in the first place shouldn't feel complex or overwhelming. People should feel confident that when something happens, raising it is simple and straightforward, and the right people can take it from there.