Skip to main content

Health and Safety Society August 2026: Industry Insights

· 07 Aug 2026 · 623 words
5 min read

1. Vehicle interaction risk: critical controls need to be genuinely critical

The committee discussion returned several times to a simple but uncomfortable question: are the controls we call critical actually capable of preventing or mitigating a fatal event? In vehicle interaction risk, many controls still depend heavily on people parking in the right location, making the right radio call, recognising a congested situation, interpreting a procedure correctly, or remembering a rule at the end of a long shift.

That does not mean procedures, training, traffic rules and communication protocols are unimportant. It means we should not confuse them with hard barriers. Where heavy vehicles, light vehicles and people must interact, the industry needs a higher and more consistent expectation around engineered separation, protected waiting locations, stopping rules, monitored interaction zones, and fail-safe controls that do not rely solely on human attention.

Possible member takeaway
  •  Review current vehicle interaction controls against credible failure modes, not against the existence of a procedure.
  •  Ask which controls would still work if a person was tired, distracted, inexperienced, under production pressure, or working at 3 am.
  • Treat congestion, equipment saturation and changing work fronts as design problems, not simply behavioural problems.
2. Technology can help, but only when the basics are strong

The committee discussed the opportunity to use practical technology - including location awareness, geofencing, collision awareness systems, cameras, communications networks and automation - to strengthen control performance. The message was not to wait for perfect enterprise technology, nor to assume that technology alone will solve the problem.

Technology must be selected, implemented, maintained and monitored as part of a functioning control system. A sensor that is not cleaned, a warning system that generates nuisance alarms, a network-dependent system with unclear fail-safe behaviour, or an automation layer that introduces new interaction risks can create a false sense of control. Good technology reduces pressure on people; poor implementation simply moves the failure point.

Possible member takeaway
  •  Be brilliant at the basics before adding complex technology.
  •  Design technology controls with clear ownership for inspection, maintenance, monitoring and response.
  •  Use functional safety thinking to ask what the system does when communications, sensors, power, positioning or human response fail.
3. Stronger learning requires better flow of information

A further theme was the difficulty of moving information from the point of work to the level where design, resourcing and capital decisions are made. Many weak signals are visible locally before they become a major event: workarounds, repeated near misses, nuisance alarms, congested work fronts, rule breaches that have become normalised, or controls that are known to be impractical.

The challenge is to aggregate those weak signals without overwhelming senior leaders with raw operational noise. The industry needs better ways to convert repeated local observations into actionable organisational learning, investment decisions and changes to standards.

Possible member takeaway
  • Look for repeated weak signals across sites, contractors, shifts and work groups.
  • Ask whether executive decisions are creating untenable choices for people at the point of work.
  •  Use investigations to trace contributing decisions and system conditions, not just the last decision made before the event.

 

Opportunities for Members

Members can help turn discussion into practical industry learning by contributing examples, questions and lessons from their own operations. Useful contributions might include:

  • Examples of vehicle interaction controls that have materially improved risk reduction.
  • Lessons from technology deployments that worked well - or failed for practical reasons such as maintenance, alarm quality, connectivity or unclear ownership.
  • Examples of investigation methods that identified deeper organisational decisions, rather than stopping at front-line behaviour.
  • Topics, speakers or case studies that should be developed into future HSS webinars or conference discussion sessions.

The committee is particularly interested in practical examples that can help members lift consistency and standards across the industry.  

 

Our site uses cookies

We use these to improve your browser experience. By continuing to use the website you agree to the use of cookies.