Question 4 of 7: The Risk Management Framework, Contents of a Risk Management Policy, and Risk Assessment Techniques

Question 4: The Risk Management Framework, Contents of a Risk Management Policy, and Risk Assessment Techniques (20 marks: 7/7/6)

Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.

(i) The Three Central Tasks of a Risk Management Framework

• A) Risk estimation — the analytical step that quantifies (or, where data is sparse, qualitatively ranks) each identified hazard's risk as a function of the likelihood of an event occurring and the severity of its consequence if it does (risk ≈ likelihood × consequence). This is where techniques such as fault tree analysis, historical incident-rate data, or a qualitative risk matrix are applied to turn a hazard list into ranked risk levels.
• B) Risk evaluation — comparing the estimated risk levels from (A) against a defined tolerability criterion (a risk-acceptance matrix, a regulatory limit, or an ALARP — as low as reasonably practicable — test) to decide which risks are acceptable as-is, which require further reduction, and which are intolerable regardless of cost. This step converts a technical estimate into a management decision about what needs to be acted on and in what priority order.
• C) Risk control — selecting, implementing, and verifying the measures (drawn from the hierarchy of controls) that bring each unacceptable risk down to a tolerable level, and then monitoring that the control remains effective over time — closing the loop back into the hazard control program described in Question 2(i).

Together these three tasks form the standard risk-management cycle (closely paralleling the international ISO 31000 framework's risk assessment → risk treatment structure): estimation quantifies the problem, evaluation decides whether and how urgently it must be addressed, and control acts on that decision.

(ii) Sections a Risk Management Policy Should Include

• Purpose and scope — the objective of the policy and which operations, sites, and hazard types it applies to.
• Management commitment and accountability — a statement of senior management's commitment (paralleling the policy statement of Question 1) and the specific roles/authorities responsible for each stage of the risk-management cycle.
• Risk assessment methodology — the defined process and techniques (from part iii) the organization will use for risk estimation and evaluation, so assessments are consistent and comparable across the organization rather than ad hoc.
• Risk acceptance/tolerability criteria — the risk matrix or ALARP-style criterion against which estimated risks are evaluated, defined in advance so the evaluation step (part i-B) is objective rather than case-by-case.
• Risk treatment/control requirements — the requirement to apply the hierarchy of controls, document the chosen control, and assign an owner and implementation timeline for every unacceptable risk.
• Monitoring, review, and audit — the frequency and method of re-assessing risks and verifying controls remain effective, and the trigger conditions (a process change, a new incident, a new regulation) that force an off-cycle review.
• Reporting and communication — how risk-assessment results, control decisions, and residual risk are communicated to affected workers, management, and (where required) the regulator.
• Records and documentation requirements — what must be retained (assessments, control decisions, monitoring results) and for how long, supporting both due-diligence defence and the trend analysis of Question 1(iii).

(iii) Four Risk Assessment Techniques: Importance and Use

• Preliminary Hazard Analysis (PHA) — a qualitative, early-design-stage technique that identifies hazardous elements/energy sources, the events they could produce, and their potential effects, at a conceptual level of detail. Its importance is that it is used before detailed design is committed, so major hazards can be designed out while a change is still cheap; it is utilized as the first-pass screening tool that scopes which hazards warrant the more detailed techniques below.
• Failure Modes and Effects Analysis (FMEA) — a bottom-up, inductive technique that works component-by-component, identifying every credible failure mode, its local/system-level effect, and a severity/occurrence ranking. Its importance is that it is exhaustive at the individual-component level, so it will not miss a failure mode of any component actually included; it is utilized during detailed design and reliability engineering to prioritize which components need redundancy, derating, or tighter maintenance intervals.
• Fault Tree Analysis (FTA) — a top-down, deductive technique that starts from a defined undesired top event (e.g., "explosion in the reactor") and works backward through Boolean logic gates (AND/OR) to identify the combinations of component failures and human errors that could cause it. Its importance is that, unlike FMEA, it captures multi-component interaction/combination failures, not just single-component ones; it is utilized to quantify the probability of a specific catastrophic event and to identify which combination of failures is the dominant contributor, guiding where redundancy or interlocks are most valuable.
• Job Safety Analysis (JSA) — a task-level technique that breaks a specific job into its sequential steps and identifies the hazard(s) present at each step along with the corresponding safe procedure/control. Its importance is that it operates at the level workers actually experience risk — the individual task — making it directly actionable as a training and procedure document; it is utilized both proactively (before a new or changed task begins) and as a periodic review tool for existing high-risk tasks (developed further in Question 5).

These four techniques are complementary rather than substitutes: PHA screens broadly and early, FMEA and FTA analyze single-component and multi-component failure mechanisms respectively at the design stage, and JSA translates the resulting understanding into a task-level procedure workers use every shift.