ALARP Explained: When Risk Is Not Yet Acceptable

ALARP means a risk has been reduced as low as reasonably practicable after available controls, further options and the sacrifice required for additional reduction have been tested. It matters when leaders are tempted to treat a remaining risk as acceptable before they have proved that stronger controls would be unreasonable.

ALARP, short for as low as reasonably practicable, is a risk-management judgment in which an organization demonstrates that further risk reduction would require sacrifice that is grossly disproportionate to the additional safety benefit. The term is not a label for comfortable risk. It is evidence that control options were examined seriously.

Definition

ALARP sits between two weak habits. One habit is chasing zero residual risk in a way that ignores technical, operational and economic reality. The other is approving remaining risk because the spreadsheet color changed from red to yellow. A serious ALARP argument rejects both habits because it asks what else could reduce exposure, who would benefit, what sacrifice would be required and whether the organization has authority to make the change.

The term comes from UK-style reasonably practicable reasoning, although US safety teams often borrow it inside process safety, major hazard and enterprise risk conversations. That borrowing needs discipline because OSHA language usually focuses on hazard identification, prevention and control, not on ALARP as a legal formula. For a US operation, ALARP should therefore be treated as a decision test, not as a substitute for regulatory duties, recognized standards or field verification.

Core terms inside an ALARP decision

Most bad ALARP decisions fail because leaders use similar words as if they meant the same thing. The distinctions below keep the conversation grounded.

Inherent risk

The level of exposure before controls are considered, which shows the original seriousness of the hazard.

Existing controls

The barriers already in place, including engineering controls, procedures, competence, supervision, alarms and emergency response.

Residual risk

The remaining exposure after controls are applied and verified against the actual work.

Reasonably practicable reduction

A further control that can reduce risk without sacrifice that is grossly disproportionate to the safety benefit.

Risk acceptance

A leadership decision to tolerate a remaining risk under defined conditions, ownership and review dates.

How to differentiate ALARP in practice

A useful ALARP review starts with the work, not with the matrix. If the field condition has changed, if a temporary waiver is active or if the supervisor cannot show that the control still works, the residual-risk number is premature. This is where dynamic risk assessment becomes a practical companion because it tests whether the job still matches the risk picture assumed by the office review.

When ALARP is different from residual risk

Residual risk is a condition after controls. ALARP is an argument about whether the organization has reduced that condition far enough. A bow-tie, JSA or risk matrix may show residual risk, but those tools do not prove ALARP unless they also show which extra controls were considered and why rejected options were not reasonably practicable.

This distinction is important for serious injury and fatality exposure. A remaining risk may look moderate on a matrix because likelihood is scored low, even though the consequence is fatal. Andreza Araujo's work in Far Beyond Zero challenges safety management that becomes satisfied by the absence of accidents, because silence can hide exposure whose controls have not been tested under pressure.

When not to use ALARP

Do not use ALARP to excuse a missing legal requirement, an expired temporary control, an unverified critical control or a known engineering fix that the site postponed for budget convenience. Those cases are not ALARP decisions. They are control gaps that need ownership.

The same caution applies to temporary risk waivers. A waiver can be legitimate when it has an owner, compensating control and expiration date, although repeated extensions often reveal that the organization has normalized exposure rather than reduced it. ALARP language should make that drift harder to hide, not easier to approve.

What evidence should support the decision

An ALARP file should show the hazard, credible consequence, exposed group, existing controls, rejected options, estimated safety benefit, operational sacrifice, decision owner and next review trigger. It should also include field evidence, because documents cannot prove that a control is alive.

For material risks, connect the ALARP decision with a critical control verification calendar. If the calendar shows repeated control failure, the ALARP claim should be reopened. If a competent person has authority to stop or correct the work, the decision should also connect with the limits described in the competent person role.

Recommendation

Use ALARP as a disciplined question before risk acceptance: what further reduction is possible, what would it change, what sacrifice would it require and who has authority to say no. If the answer depends only on a risk matrix color, the decision is not ready.

For the Headline Podcast audience, the cultural test is direct. A mature organization does not use technical vocabulary to make risk sound respectable. It uses vocabulary to force a better decision while there is still time to change the work.