ALARP: Friend or Foe? Navigating the Grey Areas of Risk Reduction

In safety-critical industries, ALARP - As Low As Reasonably Practicable - is a principle everyone recognises. But despite decades of use, it's still one of the most inconsistently applied concepts of risk management today.

Ask five organisations what ALARP means in practice, and you’ll get five different answers.

Some treat it as a genuine decision-making framework, balancing risk, cost, and effort properly. Others reduce it to a box-ticking exercise, or worse, a justification tool wheeled out to defend decisions already made rather than guide them. That's the real problem: if ALARP means something different depending on who you ask, it can't reliably deliver safe, compliant, or efficient outcomes.

The problem: interpretation over intention  

At its core, ALARP means reducing risk until further reduction would be disproportionate to the benefit gained. Simple in theory, but messier in practice.

• What defines “reasonable” is often subjective and not governed
• The main deliverables are different for companies and regulators
• Cost-benefit arguments are inconsistently applied
• Documentation varies widely between organisations
• Decisions may be influenced by commercial or operational pressures
• Over/under-engineering (driving unnecessary cost and delay)
• Inconsistency of the justified decision making (increasing regulatory and safety risk)
• Lack of consistency and auditability

The result? A patchwork of interpretations that can lead to:

• Over/under-engineering (driving unnecessary cost and delay)
• Inconsistency of the justified decision making (increasing regulatory and safety risk)
• Lack of consistency and auditability

In decommissioning especially, where uncertainty, legacy infrastructure, and rapid changes are the norm, this lack of consistency becomes even more pronounced.

Friend or foe? 

ALARP should be an enabler to demonstrate justification. When executed properly:

• Supports defensible, transparent decisions that are auditable
• Aligns stakeholders around risk tolerance
• Balances safety, cost, and practicality
• Builds confidence with regulators and partners

But when applied inconsistently, it risks becoming a barrier; slowing projects, creating ambiguity, and undermining trust.

How DecomX is leading the change in mindset 

The challenge isn’t ALARP itself; it’s how it’s interpreted and operationalised.

Through this “ALARP: Friend or Foe?” series, we’ll explore the real challenges organisations face when applying ALARP and, more importantly, how to address them going forward.

Our goal is to bring clarity, consistency, and confidence to ALARP decision-making by:

• Standardising approaches to evaluating what is “reasonably practicable”
• Embedding structured, auditable workflows into the decision process
• Providing data-driven justification frameworks rather than subjective judgement
• Enabling transparency across teams, contractors, compliance and regulators
• Reducing variability in how ALARP is interpreted across projects and organisations

DecomX is designed to move ALARP from a conceptual principle to a practical, repeatable process, supporting better outcomes for safety, compliance, and cost. The system does the legwork, putting ALARP back in the engineer's hands as a working tool rather than a compliance exercise.

A shared understanding 

 Ultimately, ALARP shouldn't be open to interpretation every time it's applied. It should be applied consistently, transparently, and with confidence because when everyone shares the same understanding, ALARP becomes what it was always meant to be: a tool for better decisions, not a source of uncertainty.