Everyone home safe, every day. It is one of the most widely used phrases in UK rail. It reflects a real belief that safety is the point, not a constraint on getting the job done.

But a value, however sincerely held, is not the same as a culture. And a culture is not the same as a system. During Rail Safety Week, when the industry comes together to reflect on progress and share learning, it is worth asking what it actually takes to make that commitment real, in practice, across every team, every shift, every site.

The answer involves two things that are more closely connected than they are often treated: the way an organisation thinks about why incidents happen, and the methodology it uses to find out. Get either of those wrong, and even the strongest stated commitment to safety will leave gaps that incidents will eventually find.

The problem with how most organisations think about error

Human and Organisational Performance, or HOP, starts from a simple observation: people are fallible, and even the best people make mistakes. Where there are humans, there is error. That is not a character flaw or a training failure. It is a fundamental feature of how people work, particularly under pressure, in complex environments, with competing demands on their attention.

The implications of that observation are significant. If error is normal and predictable, then the right response to an incident is not to find the person who made the mistake and correct their behaviour. The right response is to ask what conditions made the error possible, and whether those conditions still exist for everyone else doing the same work.

HOP also recognises that individual behaviour is shaped by the organisational environment. How work is designed, how procedures are written, how leaders respond when things go wrong, what is rewarded and what is discouraged: all of these influence what people actually do, often in ways that are invisible to anyone sitting outside the work. Blame does not fix error traps. It just makes people less willing to talk about them.

The gap between work as imagined and work as done

One of the most useful concepts in HOP is organisational drift: the gradual gap that opens up between how work is designed and how it is actually carried out. Every organisation experiences this. Procedures are written with the best intentions, but the reality of work is always more complex, more pressured, and more variable than any document can fully capture.

Over time, teams develop workarounds. Small adaptations accumulate. Things that were once deviations from the plan become the way things are done around here. None of this is malicious. Most of it reflects genuine problem-solving by experienced people trying to get the job done safely and efficiently within the constraints they actually face.

The risk is that latent conditions, the things that are quietly building in the gap between the imagined and the real, go unnoticed until something goes wrong. At that point, they tend to look like individual failures, because they become visible only at the moment of the incident. But they were there long before.

In rail, the conditions that drive this drift are well known to anyone who has worked operationally. Time pressure, shift handovers that lose critical information, a hierarchy that makes it difficult to raise concerns without consequences, or procedures that were written for a version of the work that no longer quite exists. These are not edge cases. They are the normal working environment for a large part of the industry.

Learning from work, not just from failure

Traditional safety programmes focus almost entirely on unwanted events. Incidents, near-misses, injuries generate investigations, actions, and reports. That is necessary, but it offers a limited view of what is actually happening across an organisation. The vast majority of work happens without incident, and there is an enormous amount to learn from understanding why things go right, not just why they occasionally go wrong.

Learning Teams, a practical application of HOP thinking, offer a structured way to do exactly that. Rather than waiting for failure to generate learning, a Learning Team brings together the people who actually do the work to explore how it really gets done: what supports good performance, what creates pressure, where the gap between the procedure and the reality has grown. It is a conversation, not an audit. The goal is understanding, not accountability.

In rail, where operational knowledge is often concentrated in experienced frontline teams and does not always make its way into formal safety processes, this kind of structured conversation can surface things that no investigation ever would, because nothing has gone wrong yet. The latent conditions that HOP talks about become visible before they produce an outcome.

A HOP culture is only as strong as the RCA methodology behind it

HOP is a mindset. It changes the questions you bring to safety work, but it does not replace the need for structured investigation when things do go wrong. In fact, a HOP-informed approach raises the bar on what root cause analysis needs to deliver.

When you approach an investigation through a HOP lens, human error is never the final answer. It is the starting point for a deeper question: what were the conditions that made this error possible? What was the gap between how this work was designed and how it was actually being done? What had been accumulating in the system before this event occurred? Those questions require a methodology that is structured enough to guide investigators toward real answers, and consistent enough to produce data that can be compared across teams, sites, and time.

Without that consistency, the learning stays local. A team identifies a systemic issue and addresses it for their patch. The same issue continues elsewhere because no one has connected the data. The conditions that produce failure remain in place across the organisation, and the next event depends on luck rather than learning.

This is why the commitment to getting everyone home safely every day is only as strong as the investigation methodology behind it. A strong safety culture without robust RCA is a culture that cannot learn fast enough to prevent recurrence. The two are not separate concerns. They belong together.

What this requires across a distributed railway

This challenge exists in any large organisation. In a sector as complex and distributed as UK rail, with maintenance teams spread across regions, major projects running across multiple contractors, and a reform agenda actively reshaping how the industry is structured, the consistency challenge is significantly greater.

When investigation methodology varies across teams, when the gap between work as imagined and work as done is never formally captured, when near-misses are filed rather than analysed for patterns, safety leadership ends up managing incidents rather than understanding risk. Rail Safety Week is built around the idea that sharing learning across the sector makes everyone safer. That is exactly right. But learning can only be shared if it has been captured consistently enough to be legible to others.

How COMET helps the Rail industry

A safety culture that genuinely gets everyone home safe does not happen because an organisation believes in it. It happens because the right questions get asked after every incident, because the gap between how work is imagined and how it is actually done gets surfaced before something goes wrong, and because the learning from both travels further than the team it started with.

Rail Safety Week is a good moment to ask an honest question: does the system behind your safety culture actually match the strength of your commitment to it?

COMET is a dedicated incident investigation and root cause analysis platform, built by career investigators, with a growing track record in rail including work with Network Rail, HS2, and East West Rail. If you would like to find out more about how we are helping rail organisations close the gap between safety commitment and safety practice, we would welcome a conversation.

Find out more about COMET for Rail

Or come and see us at Rail LIVE Stand M106

‍

References

Rail Safety Week - railsafetyweek.org

Network Rail - Everyone home safe: safety vision and lifesaving rules

ORR - Health and safety across the railway sector: annual report 2024-25

‍