ISO 45001: Near Misses Are Warnings. Is Your Business Listening?

A near miss can reveal a risk before someone is hurt. Learn how ISO 45001 helps businesses encourage reporting, understand what went wrong and follow safety improvements through.

ISO 45001: Near Misses Are Warnings. Is Your Business Listening?

A worker steps back just before a reversing vehicle reaches them. A box falls from a shelf and lands beside someone. An employee slips on a wet floor but manages to stay upright.

Nobody is injured. Work carries on.

Later, someone says, “That was close.” But the event never reaches the person who could help prevent it happening again.

The vehicle route stays the same. The shelf is still overloaded. The leaking pipe remains on the maintenance list.

The business has received a warning and lost the chance to learn from it.

Near misses can show where everyday work is putting people at risk. When businesses dismiss them because nobody was hurt, they leave important questions unanswered. What allowed the event to happen? Could someone else face the same danger tomorrow? Are the current safety measures working?

ISO 45001 near miss reporting helps bring those questions into a clear process. This blog explains how to make that process useful, from the first report through to checking that improvements work.

What counts as a near miss

A near miss is an event that causes no injury or ill health but had the potential to do so. HSE uses this distinction in its investigation guidance. www.hse.gov.uk

The key word is “event”. A damaged cable spotted before use is a hazard. Someone almost receiving an electric shock during use is a near miss. Both need attention, even though the reports may be recorded under different headings.

For practical purposes, your people should not have to win an argument about labels before they can raise a concern. Give them a clear route to report what happened or what they noticed. The person reviewing it can help classify it afterwards.

An office example might involve someone catching their foot on a loose cable and recovering their balance. On a construction site, it could be a tool falling close to a worker below. In a warehouse, a pedestrian might narrowly avoid a moving forklift.

Use examples from your own work when explaining near misses. A definition becomes much easier to understand when people can connect it with something they have seen.

Why an uninjured person can still signal a serious problem

The outcome of an event does not tell the whole story.

Imagine a heavy object falling from height. If it lands in an empty space, nobody is hurt. If a person is standing in that space, the consequences could be severe. The storage or lifting problem may be the same in both cases.

That is why the response should consider what could reasonably have happened, as well as what actually happened. A potentially fatal near miss needs urgent attention even when everyone walks away unharmed.

Smaller events also deserve review. Repeated trips in one corridor might point to damaged flooring, poor lighting or a delivery route that leaves boxes in the way. Each report adds detail about how that area is being used.

Avoid turning every report into a prediction that a serious accident is certain. Instead, use it as evidence to assess the risk and decide what action is needed. That makes the response more credible and helps direct resources where they matter most.

How ISO 45001 supports learning from near misses

ISO 45001 provides a framework for managing workplace health and safety. ISO identifies leadership, worker participation, hazard identification, risk assessment, incident investigation and continual improvement among its key elements. www.iso.org

Near miss reporting connects these activities. Workers describe an event. The business considers what it reveals about risk. Managers support the response. The team checks whether changes have improved the way work is done.

A practical system should give people a way to raise concerns, make someone responsible for reviewing them and keep track of agreed actions. It should also allow useful lessons to reach others who face similar risks.

This can be supported by a simple form and action register. A digital system may help a larger business, especially where teams work across several sites. Choose a method your people can use during normal work.

Certification does not replace the need to respond to a warning. A business still needs to show, through its daily decisions, that safety concerns receive attention.

Why people may keep quiet

If workers are not reporting near misses, start by asking what makes reporting difficult.

Some may fear being blamed for the event. Others may think a supervisor will see the report as criticism. A new starter might not want to appear inexperienced. A contractor may worry that raising a concern will affect future work.

Practical barriers matter too. A form kept in a locked office will not help a night shift. A long online questionnaire may be hard to complete on a phone. People may also be unsure whether they should report an event that happened on a customer’s premises.

Then there is the response to previous reports. If someone took the time to raise a concern and never heard anything back, they may reasonably doubt that another report will help.

Ask people about these barriers privately or in small discussions where they can speak freely. Their answers can reveal problems that a written procedure does not show.

Make the first response count

The first reply can shape whether someone reports again.

Thank them for raising the issue. Check whether anyone needs help and whether the danger is still present. Explain who will review the report and what will happen next.

Where work presents an immediate danger, make the situation safe through the appropriate site arrangements. That might involve stopping the task, isolating equipment or keeping people away from an area. Recording the event must not delay necessary protection.

Keep the conversation factual. Ask the person to describe what they saw, what they were doing and the conditions at the time. Avoid deciding the cause before you have gathered the evidence.

Encouraging honest reporting does not remove responsibility for unsafe behaviour. It means concerns are heard fairly and decisions are based on evidence. A worker who reports their own mistake can provide valuable information about how to prevent another person making it.

Keep reporting simple enough to use

A useful first report captures the essentials without asking the worker to investigate the whole event.

Record when and where it happened, the task involved, what occurred and what harm was possible. Note anyone who witnessed it and any immediate steps taken. Photographs may help where taking them is safe and appropriate.

Make it clear who receives reports. If people can report verbally, explain who records that conversation so it does not disappear at the end of a shift.

Consider how the process works for people with different language, reading or access needs. A short conversation may be more effective than handing someone a form they cannot easily complete. People away from the main workplace need a route that works for them too.

You can offer more than one reporting method, provided reports reach the same review process. The aim is to capture useful information while it is fresh, then follow it through consistently.

Investigate the conditions behind the event

“They should have been more careful” rarely gives a business enough information to improve.

HSE advises investigators to look beyond human error and consider the factors that influence behaviour. For example, a worker may take a shortcut because the planned route is blocked, the instructions are unclear or the task cannot be completed as described. www.hse.gov.uk

These possibilities need evidence. Speak with the people involved, look at the work area and compare the written method with the way the job was being done. Check relevant maintenance records, training information and previous reports.

Ask open questions. What happened before the event? What made the task difficult? Was the right equipment available? Had anything changed? What prevented injury on this occasion?

An investigation may identify several contributing factors. Do not force everything into one simple cause if the evidence points to a wider problem.

Match the depth of investigation to the potential harm and likelihood of recurrence. A serious warning may need specialist input. A simpler event may be addressed through a shorter review with the workers involved.

A warehouse example of useful learning

Consider this fictional example. A forklift brakes sharply when a pedestrian steps into its route near a loading bay. Nobody is hit.

The first suggestion is to remind everyone to watch where they are going. A closer review shows that stacked pallets hide the crossing point. The pedestrian route is poorly marked and visiting drivers are not clearly told where to wait.

Workers explain that the area becomes especially crowded during morning deliveries. The written traffic plan does not reflect that pattern.

The team clears the obstructed sightline and introduces suitable immediate controls. It then reviews the layout, delivery arrangements and separation of vehicles and pedestrians with competent support. Visiting drivers receive clearer instructions.

After the changes, someone observes the area during the busy period and asks workers whether the route is usable. Further changes are made where needed.

The value comes from understanding the work and following the action through. The report alone would not have changed the risk.

Choose actions that deal with the risk

Training and reminders can be useful, but consider whether the hazard itself can be removed or reduced.

If people keep tripping over a cable, a permanent routing solution may offer better protection than repeated warnings. If a doorway brings vehicles and pedestrians together, review the layout and separation arrangements rather than relying only on people noticing each other.

The right measure depends on the task and the risk. Involve people who understand the work and obtain competent advice where the decision needs specialist knowledge.

Also check whether a proposed change introduces another problem. Moving storage away from a crossing point, for example, should not block an escape route or make manual handling more difficult.

Write actions so that someone can tell when they are complete. “Improve housekeeping” is vague. An action that names the area, the required change, the responsible person and the due date is easier to manage.

Give action owners the authority and resources they need. Responsibility without time or support can leave a serious issue waiting in a spreadsheet.

Check the change before closing the report

Completing a task does not always mean the risk has been dealt with.

A revised procedure may be unclear. New equipment may be unsuitable for the space. A barrier may be moved because it makes the job difficult. These problems can emerge only when people use the change during normal work.

Build a check into the action plan. Decide what evidence will show that the measure works and who will review it. For a changed route, this could include observing traffic during a busy period. For new equipment, it could involve checking its use with the workers who rely on it.

Update the relevant risk assessment, instructions or training where the findings require it. Let the person who reported the event know what changed and why.

If the action is delayed, explain the reason and review whether temporary controls remain suitable. An overdue action should stay visible to the people who can resolve it.

Look for patterns across teams and sites

Individual reports can seem unrelated until someone looks at them together.

One team reports a loose floor covering. Another reports poor lighting nearby. A third reports boxes left in the same corridor. Reviewing them together may show why people keep losing their footing in that area.

Look for repeated tasks, locations, equipment and working conditions. Consider whether events cluster during shift changes, busy periods or unusual jobs. Include contractors and temporary workers where their work affects the picture.

Share relevant lessons across the business. If a storage problem is found at one site, check whether the same arrangement exists elsewhere. Do not assume another team will learn about it by chance.

Use plain summaries when sharing findings. Explain what happened, what allowed it to happen and what others should check. Avoid naming individuals unnecessarily or circulating personal details to people who do not need them.

The purpose is to improve work, so keep the message useful to the people receiving it.

Measure the response as well as the reports

A low number of near miss reports can be hard to interpret. It might reflect fewer events, but it could also reflect weak reporting or limited opportunities to speak up.

Likewise, an increase after introducing an easier process may mean people are becoming more willing to report. Review the circumstances before treating the change as good or bad news.

Alongside report numbers, look at the quality of the response. How quickly are serious concerns reviewed? Which actions are overdue? Have similar events happened again? Do workers hear what changed after their reports?

Avoid targets that make people feel they should keep the reported total low. They can work against the information you need. A target focused on reviewing and resolving concerns is more closely connected with the purpose of the process.

Managers should discuss what the information means for their operations. A chart helps only when it leads to a decision, such as funding a layout change or addressing a maintenance backlog.

Understand the difference between internal reporting and RIDDOR

Internal near miss reporting and statutory reporting serve different purposes.

Your internal process helps you recognise risk and improve the way work is managed. RIDDOR requires specified work-related events to be reported to the relevant enforcing authority.

In Great Britain, some defined dangerous occurrences are reportable even when nobody is injured. Not every event described internally as a near miss meets those criteria. www.hse.gov.uk

Do not assume that “no injury” means “no reporting duty”. Equally, do not assume every near miss must be sent to HSE. The responsible person should check the current rules for the event and sector, including the applicable reporting timescale. Northern Ireland has separate reporting arrangements.

Keep this responsibility clear within your process so that a potential statutory report is reviewed promptly. Internal investigation must not delay a required notification.

Whatever the reporting decision, the business still needs to consider the risk and appropriate action. An event can provide an important warning without meeting a RIDDOR reporting threshold.

Benefits of a consultant’s support

When reviewing ISO 45001 near miss reporting, the benefits of a consultant’s support can include an independent view of how the process works in practice.

A consultant can help compare the written arrangements with daily work. They may ask workers how they report concerns, review a sample of investigations and check whether completed actions include evidence of effectiveness.

Support can also help managers make reporting forms clearer, define responsibilities and connect findings with risk assessments, internal audits and management review. Where records are inconsistent, a structured review can reveal where information is being lost.

Choose support that suits the work and the risks. A management system review does not replace specialist advice on matters such as machinery safety or occupational exposure.

The business retains responsibility for its decisions and safety arrangements. Useful support leaves managers and workers better able to recognise warnings, ask good questions and follow improvements through themselves.

Listen to the next warning

You do not need to wait for the next audit to review whether your process is helping.

Choose a recent near miss and trace it from the first report to the latest action. Check what was recorded, who reviewed it, how workers contributed and whether the change was tested. If the report is still open, find out what is holding it up.

Then ask a few people how they would report a similar event today. Include someone on a different shift or away from the main site. Their answers will tell you whether the process is easy to find and use.

Where no reports exist, start a conversation about close calls people have seen and the barriers to raising them. Do not treat an empty register as proof that the workplace is safe.

A near miss gives your business information while there is still a chance to act before someone is harmed. Make that information easy to share, give it a fair review and check that the response changes the work.

The next time someone says, “That was close,” what will your business do with the warning?

Get Started

There has never been a better time to invest in ISO certification. Show your commitment to quality management, the environment or occupational health & safety performance with a UKAS certified ISO certification from Compliant.
Get in Touch

Free Download

Download our free “The ISO process and ongoing Support pdf”