Study guide
8.1 Bow-Tie Analysis: Cause and Consequence Diagramming
PECB Certified ISO 31000 Risk Manager Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Principles and Core Concepts of ISO 31000
1.1 ISO 31000 Overview, Purpose, and Scope 1.2 Core Risk Terminology and Definitions 1.3 The 8 ISO 31000:2018 Risk Management Principles 1.4 The Risk Management Standards Landscape and PECB Exam Structure 1.5 Comparing ISO 31000 with COSO ERM, NIST RMF, and Sector Frameworks 1.6 Risk Categories and Risk Management vs. Risk Assessment
2 Chapter 2: Enterprise Risk Governance and Leadership
2.1 Leadership and Top Management Commitment 2.2 Integrating Risk Management into Organizational Governance 2.3 Building a Risk-Aware Culture and the Three Lines Model
3 Chapter 3: Designing and Implementing the Risk Framework
3.1 Framework Design and Context Analysis 3.2 Framework Implementation and Resource Allocation 3.3 Framework Evaluation and Continual Improvement 3.4 The Risk Management Plan and Framework Documentation Architecture
4 Chapter 4: Establishing Context and Risk Identification
4.1 Communication and Stakeholder Consultation 4.2 Defining Scope, Context, and Risk Criteria 4.3 Risk Identification Methods and Risk Register Construction 4.4 The Consultation Process, Communication Principles, and Risk Escalation 4.5 Asset Identification and Evaluation of Existing Controls
5 Chapter 5: Risk Analysis, Evaluation, and Decision Making
5.1 Risk Analysis: Assessing Likelihood, Consequence, and Controls 5.2 Risk Evaluation and Prioritization 5.3 Inherent Risk vs. Residual Risk and Risk Aggregation
6 Chapter 6: Risk Treatment, Monitoring, and Reporting
6.1 The Seven ISO 31000 Risk Treatment Options 6.2 Designing and Implementing Risk Treatment Plans 6.3 Monitoring, Review, Recording, and Reporting Systems
7 Chapter 7: Qualitative and Scenario Risk Assessment Techniques (IEC 31010)
7.1 IEC 31010 Framework and Selection Criteria 7.2 Qualitative Techniques: Delphi, SWIFT, HAZOP, and Brainstorming 7.3 Root Cause Analysis (RCA), Fishbone, and 5 Whys
8 Chapter 8: Quantitative and Predictive Risk Assessment Techniques (IEC 31010)
8.1 Bow-Tie Analysis: Cause and Consequence Diagramming 8.2 Failure Mode and Effects Analysis (FMEA/FMECA) 8.3 Fault Tree Analysis (FTA) vs. Event Tree Analysis (ETA) 8.4 Advanced Quantitative Methods: Monte Carlo, Decision Trees, and LOPA
8.1 Bow-Tie Analysis: Cause and Consequence Diagramming
Key Takeaways Explain This Topic AI
Bow-Tie Analysis is an IEC 31010 standardized qualitative and semi-quantitative risk assessment method that visually links risk causes, central top events, and downstream consequences.
The Top Event represents the critical transition point where control over a hazard is lost, separating preventive barriers on the left from mitigation barriers on the right.
Escalation factors identify conditions or operational states that defeat primary barriers, requiring dedicated escalation factor controls to preserve barrier integrity.
Barrier management integrates quantitative Probability of Failure on Demand (PFD) metrics into As Low As Reasonably Practicable (ALARP) safety frameworks.
Last updated: July 2026
8.1 Bow-Tie Analysis: Cause and Consequence Diagramming
In modern risk management frameworks governed by ISO 31000 and IEC 31010:2019 , Bow-Tie Analysis serves as a premier visual and analytical technique for evaluating complex risk scenarios. It bridges qualitative hazard identification and rigorous quantitative risk assessment by providing a structured, schematic representation of how a central risk event originates, escalates, and impacts an organization. The power of Bow-Tie Analysis lies in its ability to map the complete line-of-sight from initiating root causes through preventative controls, to the central loss event, and subsequently through reactive controls to final consequences.
1. Conceptual Foundation and Architecture
The fundamental structure of a Bow-Tie diagram takes its name from its graphical shape: a central focal point flanked by a left-hand side focused on cause analysis and a right-hand side focused on consequence analysis. At the precise geometric center of the diagram lies the Top Event .
The Top Event and Hazard Definition
Hazard : A source of potential harm, energy, or adverse condition (e.g., pressurized hydrocarbon storage, sensitive customer data, liquid capital reserves).
Top Event : The specific moment in time when control over the hazard is lost, but before major negative consequences have actually occurred. It represents the "loss of containment" or "loss of control."
It is vital for ISO 31000 Risk Managers to distinguish the Top Event from its ultimate consequences. For instance, in industrial safety, an uncontained release of toxic gas is the Top Event; environmental damage or personnel fatalities are consequences. In financial and IT risk management, a breach of administrative access controls is the Top Event; financial theft or regulatory fines are the consequences. [Threat Lines] --> [Preventive Barriers] --> ( TOP EVENT ) --> [Mitigation Barriers] --> [Consequence Lines]
- |
- [Escalation Factors]
- |
- [Escalation Controls]
- 2. Left-Hand Side Architecture: Threat Lines and Preventive Barriers
The left-hand side of the Bow-Tie diagram models all plausible mechanisms that could independently or interactively trigger the Top Event.
Threat Lines (Initiating Causes)
Threats are the initiating causes or failure modes that lead directly to the Top Event if no controls are present. Common threat categories include:
Technical/Equipment Failures : Corrosion of vessel walls, software logic bugs, mechanical fatigue.
Human Error / Procedural Drift : Omission of inspection protocols, incorrect parameter entry, unauthorized override.
External / Environmental Events : Seismic activity, lightning strike, severe market volatility, third-party cyber intrusion.
Preventive Barriers (Control Barriers)
Positioned directly on the threat lines between the threat and the Top Event, Preventive Barriers (also called proactive controls) are designed to interrupt the sequence of events and prevent the Top Event from occurring. Under IEC 31010 standards, barriers are classified by their operational mechanism:
Barrier Type Description Representative Example
Passive Hardware Structural safeguards requiring no automated action or human intervention Blast walls, secondary containment bunds, fixed insulation
Active Hardware / Instrumented Sensor-driven automated systems that detect parameter deviations and initiate protective action High-pressure trip systems, automated fire dampers, automated IP blocking
Administrative / Procedural Formal operational guidelines and mandatory procedural checks Dual-signoff authorization rules, pre-startup safety reviews (PSSR)
Human Intervention Manual actions performed by trained operators in response to alarms Operator manual shutdown upon hearing an acoustic alarm
3. Escalation Factors and Escalation Factor Controls
A critical innovation of the Bow-Tie methodology is the explicit identification of barrier vulnerabilities through Escalation Factors .
Defining Escalation Factors
An Escalation Factor (or defeating factor) is a condition, operational state, or secondary event that reduces the effectiveness of a primary barrier or causes it to fail entirely. Escalation factors do not directly cause the Top Event; instead, they degrade the protective capability of a barrier.
Example : A high-pressure trip valve (Primary Preventive Barrier) may fail to close due to scale buildup or internal corrosion (Escalation Factor).
Example : An automated web application firewall (Primary Barrier) may fail due to outdated rule signatures during a zero-day exploit (Escalation Factor).
Escalation Factor Controls
To restore barrier integrity, risk analysts design Escalation Factor Controls (secondary barriers). These are controls specifically implemented to prevent the escalation factor from undermining the primary barrier.
Escalation Control Example : Implementing a mandatory partial-stroke testing schedule every 30 days prevents valve scale buildup, ensuring the primary trip valve functions on demand.
4. Right-Hand Side Architecture: Consequence Lines and Mitigation Barriers
Once the Top Event occurs, control has been lost. The right-hand side of the Bow-Tie diagram models the potential loss pathways flowing from the Top Event toward final impact scenarios.
Consequence Lines
Consequences are the specific, unwanted end outcomes resulting from the Top Event. A single Top Event typically branches into multiple consequence lines depending on environmental conditions, operational context, and the performance of reactive controls.
Categories of consequences include human injury/fatality, environmental destruction, asset destruction, business disruption, legal liability, and brand degradation.
Mitigation Barriers (Recovery Barriers)
Positioned along the consequence lines between the Top Event and the final consequence, Mitigation Barriers (also called recovery controls) are designed to limit the severity, spread, or duration of the impact after the Top Event has transpired.
Examples of Mitigation Barriers : Emergency deluge fire suppression systems, emergency response protocols, crisis communication plans, disaster recovery data restoration, and financial business interruption insurance.
5. Quantitative Barrier Management and ALARP Integration
While Bow-Tie diagrams are visually intuitive qualitative tools, IEC 31010 emphasizes their semi-quantitative and quantitative utility through Barrier Management .
Probability of Failure on Demand (PFD)
Each barrier is assigned a quantitative reliability metric, typically expressed as its Probability of Failure on Demand ( P F D PFD PF D ) . The P F D PFD PF D represents the likelihood that a barrier will fail to perform its intended safety function when invoked.
To calculate the overall frequency of a specific consequence ( f c o n s f_{cons} f co n s ), analysts multiply the initiating threat frequency ( f t h r e a t f_{threat} f t h re a t ) by the P F D PFD PF D values of all intervening preventive barriers ( P F D p r e v , i PFD_{prev,i} PF D p re v , i ) and mitigation barriers ( P F D m i t , j PFD_{mit,j} PF D mi t , j ): f c o n s = f t h r e a t × ( ∏ i = 1 m P F D p r e v , i ) × ( ∏ j = 1 n P F D m i t , j ) f_{cons} = f_{threat} \times \left( \prod_{i=1}^{m} PFD_{prev,i} \right) \times \left( \prod_{j=1}^{n} PFD_{mit,j} \right) f co n s = f t h re a t × ( i = 1 ∏ m PF D p re v , i ) × ( j = 1 ∏ n PF D mi t , j )
Worked Calculation Example
Consider an industrial processing plant analyzing a catastrophic vapor cloud explosion consequence ( C 1 C_1 C 1 ) resulting from a vessel overpressure Top Event ( T E TE TE ):
Initiating Threat Frequency ( f t h r e a t f_{threat} f t h re a t ) : Overpressurization occurs at 0.10 events/year 0.10 \text{ events/year} 0.10 events/year .
Preventive Barrier 1 (Operator Alarm Response) : P F D p r e v , 1 = 0.15 PFD_{prev,1} = 0.15 PF D p re v , 1 = 0.15 .
Preventive Barrier 2 (High-Pressure Trip System) : P F D p r e v , 2 = 0.02 PFD_{prev,2} = 0.02 PF D p re v , 2 = 0.02 .
Mitigation Barrier 1 (Fixed Water Deluge System) : P F D m i t , 1 = 0.10 PFD_{mit,1} = 0.10 PF D mi t , 1 = 0.10 .
Mitigation Barrier 2 (Emergency Evacuation Protocol) : P F D m i t , 2 = 0.05 PFD_{mit,2} = 0.05 PF D mi t , 2 = 0.05 .
Calculating the mitigated consequence frequency: f c o n s = 0.10 × ( 0.15 × 0.02 ) × ( 0.10 × 0.05 ) f_{cons} = 0.10 \times (0.15 \times 0.02) \times (0.10 \times 0.05) f co n s = 0.10 × ( 0.15 × 0.02 ) × ( 0.10 × 0.05 ) f c o n s = 0.10 × 0.003 × 0.005 = 1.5 × 10 − 6 events/year f_{cons} = 0.10 \times 0.003 \times 0.005 = 1.5 \times 10^{-6} \text{ events/year} f co n s = 0.10 × 0.003 × 0.005 = 1.5 × 1 0 − 6 events/year
If the organization's ALARP (As Low As Reasonably Practicable) threshold for catastrophic events is 1.0 × 10 − 5 events/year 1.0 \times 10^{-5} \text{ events/year} 1.0 × 1 0 − 5 events/year , the demonstrated frequency of 1.5 × 10 − 6 events/year 1.5 \times 10^{-6} \text{ events/year} 1.5 × 1 0 − 6 events/year satisfies safety criteria, confirming that current barrier health is acceptable.
Loading diagram... Comprehensive Bow-Tie Risk Model Architecture
Barrier Classification and Verification Matrix
Maintaining barrier health requires ongoing verification and auditing. The matrix below contrasts barrier types across operational domains and establishes compliance verification standards:
Barrier Architecture Target Risk Dimension Primary Failure Mode Verification & Audit Method
Preventive / Active Tech Threat Interruption Electronic sensor drift, logic fault Functional proof-testing every 90 days
Preventive / Procedural Human Error Control Training decay, procedural bypass Random operational audits & log reviews
Mitigation / Active Tech Damage Containment Mechanical jam, power failure Simulated load testing & emergency power check
Mitigation / Human Response Exposure Reduction Panic, communication blackout Unannounced emergency evacuation drills