Risk + Safety + AMC

Bow-Tie Analysis and ALARP Demonstration

Threats through the top event to consequences · every barrier named, owned and tested.

A bow-tie puts the whole hazard on one page · what can release control, what happens if it is released, and every barrier on both sides. It is the one risk technique a board, a regulator and a control room operator can all read, which is why it carries the ALARP argument.

25 marquee operators · 21 countries · verified roster
Bayer · Pfizer · TATA · Adani · JSW · ISRO · Siemens · Bosch · DuPont · Mahindra · Hindalco · and others
Bayer
Pfizer
TATA
Adani
JSW
Nestle
ISRO
Mahindra
Siemens
Bosch
DuPont
Aditya Birla
Hindalco
Amazon
Indian Oil
ITC
Asian Paints
Dr. Reddy
Kia
Bureau Veritas
Lloyd
Halliburton
Jindal Steel
AMNS
Rolls Royce
Bayer
Pfizer
TATA
Adani
JSW
Nestle
ISRO
Mahindra
Siemens
Bosch
DuPont
Aditya Birla
Hindalco
Amazon
Indian Oil
ITC
Asian Paints
Dr. Reddy
Kia
Bureau Veritas
Lloyd
Halliburton
Jindal Steel
AMNS
Rolls Royce
Why this matters

What does a bow-tie show that a risk register does not?

Barriers, and whether anyone owns them. A risk register records that a hazard exists and assigns it a rating. A bow-tie draws the pathway · each threat that can release the hazard on the left, the top event in the centre, each consequence on the right, and every prevention barrier and mitigation barrier positioned where it actually sits on that pathway. The moment the diagram is drawn, three things become visible that a register conceals · threats with only one barrier, barriers that are claimed on several different pathways at once, and barriers that nobody in the organisation actually owns or tests.

Escalation factors are the second contribution. A barrier is not a permanent property of the plant; it is defeated by specific conditions · a bypassed interlock, a degraded detector, an untrained crew on nights, a deferred proof test. A bow-tie names those conditions and requires a control against each, which is what converts a diagram into a management system.

ALARP then rests on something defensible. Demonstrating that risk is as low as reasonably practicable requires showing which further measures were considered and why the sacrifice was grossly disproportionate to the reduction. That argument is far stronger when it is made against a named set of barriers than against a risk rating.

Method

How we deliver Bow-Tie Analysis and ALARP Demonstration

Barrier-based analysis with escalation factors and named ownership · ALARP demonstration documented for regulatory and board review. Routes to the Risk + Safety practice lead within 24 hours.

01

Hazard and top event definition

The hazard and the top event stated precisely · the top event is the moment control is lost, not the consequence and not the cause. Getting this wrong is the most common error in bow-tie work, and it produces a diagram in which threats and consequences sit on the wrong sides and no barrier can be placed correctly.

02

Threat and consequence identification

Every credible threat capable of releasing the top event on its own is identified on the left, and every credible consequence flowing from it on the right, drawing on HAZOP findings, incident history and major accident scenarios rather than starting from a blank page.

03

Barrier identification and classification

Prevention barriers placed on each threat line and mitigation barriers on each consequence line, each classified by type · hardware, instrumented, procedural or behavioural · and tested against whether it is genuinely effective, independent and auditable. A barrier that only detects, or only warns, is recorded as such rather than credited as a barrier.

04

Escalation factors and controls

For each barrier, the conditions that would defeat or degrade it are identified · bypass, deferred testing, competence gaps, environmental conditions, common cause between barriers claimed as independent · and a control assigned against each escalation factor.

05

Ownership, assurance and ALARP demonstration

Every barrier assigned a named owner, a performance standard and a verification activity, so the diagram becomes a live assurance framework. The ALARP argument is then documented · the further measures considered, their cost and their risk reduction, and the reasoning where a measure was ruled out as grossly disproportionate.

Standards + compliance

Built to the standards your auditors quote

Barrier analysis and ALARP demonstration follow recognised major accident hazard and risk management practice as applied by regulators and corporate safety functions. Every deliverable independently reviewed and signed by a Chartered Engineer (CEng MIE India).

Anonymous case anchors

What this looks like in production

Three landmark engagements from our verified roster · quantified outcomes, no client names disclosed without written permission.

LNG terminal, GCC · loss of containment bow-ties

Bow-ties built for the principal loss-of-containment top events, which identified several threat lines carrying a single prevention barrier and one barrier being credited independently on multiple pathways where a common cause existed.

Refinery, India · barrier ownership review

Existing bow-ties reviewed for ownership and assurance rather than redrawn. A material proportion of barriers had no named owner and no verification activity, and were being reported as in place on that basis.

Chemical site, South Asia · ALARP case for regulator

ALARP demonstration prepared for a major accident scenario, documenting the additional measures considered, the risk reduction each would deliver and the reasoning for those ruled out as grossly disproportionate.

Frequently asked

Bow-tie and ALARP · the questions safety leads ask

What is a bow-tie diagram?
A bow-tie sets out a single hazard on one page. The top event, the moment control over the hazard is lost, sits in the centre. Threats capable of causing it are on the left, consequences flowing from it on the right, and the knot is formed by the barriers · prevention barriers on the threat side, mitigation barriers on the consequence side. Escalation factors, the conditions that defeat a barrier, hang off each barrier with their own controls. It combines the logic of a fault tree and an event tree in a form that a non-specialist can read, which is why it is used for communication as much as for analysis.
What does ALARP mean in practice?
As low as reasonably practicable. It requires risk to be reduced until the sacrifice of any further measure · in cost, time or trouble · would be grossly disproportionate to the risk reduction it achieves. The important consequence is that the burden of demonstration sits with the duty holder, not the regulator. It is not enough to say a risk is low; you must show which further measures were considered, what each would achieve, and why those not implemented were ruled out. Bow-ties support that because the candidate measures are additional or strengthened barriers, which are concrete things to cost and evaluate.
What makes something a barrier rather than a safeguard?
A barrier must be effective, capable of stopping the pathway on its own; independent of other barriers claimed on the same pathway and of the threat itself; and auditable, so its performance can be verified. Measures that only detect, warn or record are important but are not barriers, and recording them as barriers is the most common way a bow-tie overstates the protection in place. Independence is where most claims break down · two barriers relying on the same power supply, the same operator or the same instrument are one barrier with a common cause.
How does a bow-tie relate to HAZOP and LOPA?
They feed each other. HAZOP identifies hazardous scenarios and existing safeguards, which populate the threat lines and the barriers. LOPA quantifies whether the independent protection layers on a given pathway are sufficient against a tolerable frequency. A bow-tie assembles both into a barrier picture across the whole hazard and adds escalation factors and ownership, which neither of the others carries. It does not replace them · a bow-tie drawn without a preceding hazard identification tends to record the barriers people remember rather than the ones the scenarios require.
Who should own a barrier?
A named individual with the authority and the budget to maintain its performance, not a department. Each barrier needs a performance standard stating what it must do, and a verification activity that confirms it still does. This is where bow-ties earn their keep in operation · the diagram becomes an assurance framework in which every barrier has an owner, a standard and evidence, rather than a picture drawn once for a safety case and filed.
Do bow-ties need to be kept up to date?
Yes, and they are more sensitive to change than most risk documents because barriers degrade operationally rather than conceptually. A bypassed interlock, a deferred proof test, a vacancy in a role that owns a procedural barrier · none of these change the diagram's structure but all change whether the protection is actually present. Bow-ties are most useful when reviewed against real barrier status on a regular cycle and after any incident, management of change, or period of extended bypass.

Scope your Bow-Tie Analysis and ALARP Demonstration engagement.

Tell us your plant, region, and scope · a named Chartered Engineer responds within 24 hours.

  • 4 fields. No phone interview to start.
  • Per-discipline routing to the Risk + Safety + AMC practice lead.
  • Anonymous case anchors sent with first reply.
  • Same-day callback for deadline-driven enquiries.

Risk + Safety + AMC Scoping

HAZOP/LOPA/SIL/QRA · 5-year AMC retainer · Practice Lead Safety responds in 24 hr.