SHARE Knowledge Hub

Establishing a process safety management system

A process safety management system keeps major-accident hazards, safety-critical barriers and decision rights under control through the whole plant life. Start with credible release, fire, explosion and toxic scenarios; give each barrier a performance standard, owner and test; and make impairments, change, learning and restart decisions visible. COMAH duties depend on site nation, dangerous-substance inventory and tier.

Updated 2026-10-22UK focusProcess safetyCOMAH and major accident hazards

Understanding Establishing a process safety management system

A process safety management system is the organised way an operator prevents, detects, controls and mitigates major accident hazards involving dangerous substances, pressure, fire, explosion, toxic release, loss of containment or escalation. It is not a policy alone, a personal-safety programme or a collection of disconnected procedures. It connects the credible major accident scenarios at a site to the barriers that control them, the people who own those barriers and the evidence that they work today.

Why this matters at work

A process safety system starts with the energy and hazardous inventory that could escape control. Typical initiating events include corrosion, overpressure, loss of cooling, wrong material, pump or seal failure, human error, degraded safety instrumented function, ignition source, utility loss, vehicle impact, external fire, alarm overload, poor isolation, unauthorised change and loss of containment during transfer or maintenance. The top event may be release, loss of control, ignition, runaway reaction or structural failure.

Investigate loss of containment, process excursions, near misses, barrier demands, alarm floods, impairment breaches, unauthorised changes, emergency failures and recurring abnormal conditions at a level proportionate to potential consequence. Preserve evidence, establish a competent team, define the event and intended system state, collect documents and worker accounts, analyse technical, organisational and human factors, identify immediate and underlying causes, then restore safe conditions before returning to normal operation.

How organisations manage this in practice

Investigate significant excursions, loss of containment, barrier demands or failures, unauthorised changes and recurring abnormal conditions in proportion to potential consequence. Preserve evidence, define the intended state and examine technical, organisational and human factors with the relevant competence. Seek worker accounts and disconfirming evidence rather than stopping at operator error. Manage present danger and recovery separately from establishing the complete historical explanation. Translate findings into changes to design, integrity, operating limits, procedures, competence or resourcing, with owners and verification. Apply change control and readiness review where corrective work alters the system. Check similar assets and scenarios and revise barrier and indicator information. Close actions through evidence that the risk control works, not only a new document or training attendance. Management review should expose unresolved critical defects, dependencies and operational restrictions and ensure resources address them. Keep national legal duties and reporting distinct from the organisation's improvement method; a successful audit or lack of incidents does not guarantee that every major-accident barrier is effective.

Digital control systems, alarm management, historians, maintenance systems, electronic permits, remote access and engineering workstations can affect barrier health. Define asset ownership, access control, change authority, backup, recovery, patching, obsolescence, configuration management, cyber incident response and how safe operation is maintained when systems are unavailable. The relevant standard of control depends on the plant and threat, but cyber resilience must not be isolated from process safety management.

Restoration fields identify expiry review, safe rollback or permanent-change decision, removal of temporary equipment and overrides, restored functions, corrected records and affected-worker briefing. Close with verification after operation and investigation of recurrence. An incomplete or failed change stays in the control system with its restrictions; it cannot disappear through administrative closure. Keep actual signatures and operational security information outside the teaching corpus. Sources: Operating procedures; Organisational change; Plant modification; Maintenance procedures; Permit to work systems.

Connect the overfill barrier to today’s operating decision

For the overfill scenario, policy sets responsibility, the operating procedure sets receiving limits, the instrument owner controls proof tests and the shift supervisor checks the live barrier and bypass register before transfer. A failed or unverified critical trip changes today’s transfer decision; it cannot wait for the next audit score.

An authorised bypass decision must address the actual scenario and operating restrictions through the site’s competent process. Shift handover carries the impairment, limits, owner and expiry or review condition. Restart requires verified restoration and the appropriate technical release. A signed policy or strong personal-injury rate cannot establish major-accident readiness; retain nation, inventory and COMAH-tier qualifications.

Content amended 19 October 2026 by the SHARE Knowledge Hub editorial team. This records an editorial content change; the existing technical-review and approval status still applies.

Make the tank barrier standard testable

A loss-of-containment scenario connects causes and consequences to barriers. Each important barrier needs an owner, performance requirement, evidence and an impairment response.

Three colleagues review an inert process drawing and tabular binder beside a glazed chemical-plant view, without operating equipment or demonstrating a test.
Illustrative process-safety scenario review. Papers and the plant view do not prove a valid design basis, available protection, completed test or permission to operate.

Connect the scenario to the barrier and its evidence

Connect the scenario to the barrier and its evidence. Three colleagues review an inert process drawing and tabular binder beside a glazed view of vessels and pipe racks. Markers identify the drawing, binder and plant context. Neither paper nor the external view establishes a credible scenario, independent protection, a passed test, actual bypass status or permission to operate.
Conceptual assurance only. No SIL, test interval, set point, independence rating, bypass instruction or operating limit is assigned.
Full written explanation

Chemical-plant review: a drawing, register and installation need an explicit connection to the actual protective function.

  1. Define the credible scenario. Connect initiating causes, loss of containment and consequences for this installation. A generic hazard label is insufficient.
  2. Make the function testable. State what the barrier must do, who owns it and what evidence covers the required performance and dependencies.
  3. Use today’s actual status. Resolve failed, bypassed or unverified protection through the authorised impairment process. Feed findings back into the system.

Change the pathway

  • The drawing is not the design basis. Use verified site information and competent scenario review.
  • Document volume is not assurance. A binder cannot prove availability or end-to-end function.
  • Personal-injury rates are separate. A favourable injury record cannot establish major-accident protection.

Evidence check: Conceptual assurance only. No SIL, test interval, set point, independence rating, bypass instruction or operating limit is assigned.

The actual overfill barrier and today’s operating decision

Primary references: HSE: process-safety assurance indicators — HSG254 · HSE: instrumented-system elements — verify the current design basis · HSE: managing for health and safety — HSG65

Open the complete HD image (new tab)Download image

The actual overfill barrier and today’s operating decision

Primary references: HSE: process-safety assurance indicators — HSG254 · HSE: instrumented-system elements — verify the current design basis · HSE: managing for health and safety — HSG65

Process operators monitoring equipment from a UK industrial control room. Photorealistic illustration.
Illustrative UK workplace scene. Read the practical checks below for responsibilities, evidence and limits. Download image · Download smaller image
  1. Define the scenario

    Describe the initiating causes, loss-of-containment event and credible consequences for this installation.

  2. Set the barrier standard

    Specify what each barrier must do and how competent evidence demonstrates it. Identify dependencies and accountable owners.

  3. Manage impairment and learning

    Hold or otherwise control the activity through the authorised impairment process, verify restoration and feed lessons back into the system.

A bypassed or unverified trip cannot be counted as available protection. This example assigns no SIL, design rating or operating limit.

What proves a process safety system is working today?

For a credible major-accident scenario, show the current hazard basis, the preventive and mitigative barriers, their owners and performance criteria, and the latest evidence that each works. A policy or incident-free period alone is insufficient.

Barrier evidence model
Barrier area What good looks like Evidence
Cause Identify credible causes rather than vague hazards. Scenario list.
Top event Define the loss of control, release, ignition, explosion or failed decision point. Bow-tie or fault tree.
Consequence Describe escalation, harm, business impact and emergency interface. Consequence analysis.
Prevention barriers Controls that stop the top event occurring. Barrier register and performance standards.
Mitigation barriers Controls that limit consequences after the top event. Proof tests, inspections and drill evidence.
Impairment controls Bypasses, degraded safeguards and overdue tests are authorised and temporary controls set. Impairment log.
ALARP record Risk reduction decisions are documented and periodically reviewed. ALARP decision record.

A tank overfill scenario relies on level control, an independent high-high trip, operator response and bunding. Before transfer, operations checks the trip test and any override, maintenance resolves defects, and the responsible manager decides whether transfer can proceed. A failed or bypassed trip is a hold point, not a late dashboard exception.

SHAREsimulate

How can I practise this topic in 3D?

The dashboard counts injuries but misses failing barriers
3D workplace practiceSHAREsim

The dashboard counts injuries but misses failing barriers

All related inspection points 1 across 1 location
Crown Fuels terminal 1 inspection point

Practice in the SHAREhub environment. Browser practice is separate from workplace competence and formal learning records.

What are the key facts about establishing a process safety management system?

The key facts are that PSM is scenario-led, barrier-led and evidence-led.

Start with major accident scenarios

Define credible loss of containment, fire, explosion, toxic release, overpressure, runaway reaction and escalation events.

Know the hazardous inventory

A PSM system depends on understanding substances, energy, process chemistry, conditions and safe operating limits.

Define barriers clearly

Barriers need owners, performance standards, inspection or test evidence and impairment rules.

Manage the whole lifecycle

Design, commissioning, operation, maintenance, change, emergency response and decommissioning all affect risk.

Use indicators for control, not decoration

Process safety indicators should reveal barrier degradation and prompt leadership action.

Learn from weak signals

Small leaks, nuisance alarms, overrides, overdue actions and workarounds can indicate major accident control drift.

What is a process safety management system?

A process safety management system is the management framework used to control major accident hazards through reliable technical and organisational barriers.

PSM system purpose — part 1 of 2

PSM system purpose — part 1 of 2. Compare the named situations, controls and evidence together. Use the actual task assessment and the linked sources within their jurisdiction.
Learning point: Compare the named situations, controls and evidence together. Use the actual task assessment and the linked sources within their jurisdiction.
Read the complete visual as text
  1. Understand hazards: What it means: Identify hazardous inventory, process conditions and credible scenarios. Evidence: Process safety information and hazard studies.
  2. Control risk: What it means: Select preventive, detection, control, mitigation and emergency barriers. Evidence: Barrier register and performance standards.
  3. Operate safely: What it means: Keep operation within the safe envelope. Evidence: Operating procedures, alarm response and shift logs.

PSM system purpose — part 2 of 2

PSM system purpose — part 2 of 2. Compare the named situations, controls and evidence together. Use the actual task assessment and the linked sources within their jurisdiction.
Learning point: Compare the named situations, controls and evidence together. Use the actual task assessment and the linked sources within their jurisdiction.
Read the complete visual as text
  1. Maintain integrity: What it means: Keep safety critical equipment fit for purpose. Evidence: Inspection, testing and maintenance records.
  2. Control change: What it means: Review technical and organisational change before implementation. Evidence: MOC and pre-start-up review records.
  3. Learn and improve: What it means: Act on incidents, audits, indicators and weak signals. Evidence: Action tracker and management review.

A PSM system is not separate from operations. It should shape how the plant is designed, operated, maintained, modified, inspected, restarted and shut down. If it only appears in a policy, it is not established. See HSE COMAH 2015 overview.

The practical test is simple: can the site explain its major accident hazards, show the barriers relied on, prove those barriers are healthy today and demonstrate that leaders act when the evidence shows degradation?

The strongest systems join technical hazard understanding with management discipline. Hazard studies identify what can go wrong. Procedures, engineering standards, competence, maintenance, permits, MOC, emergency planning, indicators and audit make sure the controls stay real.

PSM system purpose - PSM system purpose
Purpose What it means Evidence
Understand hazards Identify hazardous inventory, process conditions and credible scenarios. Process safety information and hazard studies.
Control risk Select preventive, detection, control, mitigation and emergency barriers. Barrier register and performance standards.
Operate safely Keep operation within the safe envelope. Operating procedures, alarm response and shift logs.
Maintain integrity Keep safety critical equipment fit for purpose. Inspection, testing and maintenance records.
Control change Review technical and organisational change before implementation. MOC and pre-start-up review records.
Learn and improve Act on incidents, audits, indicators and weak signals. Action tracker and management review.

Why should the PSM system start with major accident scenarios?

The PSM system should start with scenarios because paperwork only matters if it controls a real route to a major accident.

Scenario-led PSM questions — part 1 of 2

Scenario-led PSM questions — part 1 of 2. Compare the named situations, controls and evidence together. Use the actual task assessment and the linked sources within their jurisdiction.
Learning point: Compare the named situations, controls and evidence together. Use the actual task assessment and the linked sources within their jurisdiction.
Read the complete visual as text
  1. What can be released or go out of control?: Why it matters: Defines hazardous inventory and initiating events. Example evidence: Inventory register and process description.
  2. What is the top event?: Why it matters: Clarifies the loss of control to prevent. Example evidence: Bowtie or hazard study output.
  3. What prevents it?: Why it matters: Identifies preventive barriers. Example evidence: Design standards, alarms, trips and procedures.

Scenario-led PSM questions — part 2 of 2

Scenario-led PSM questions — part 2 of 2. Compare the named situations, controls and evidence together. Use the actual task assessment and the linked sources within their jurisdiction.
Learning point: Compare the named situations, controls and evidence together. Use the actual task assessment and the linked sources within their jurisdiction.
Read the complete visual as text
  1. What detects it?: Why it matters: Identifies monitoring and response triggers. Example evidence: Gas detection, level alarms and operator rounds.
  2. What mitigates consequences?: Why it matters: Identifies emergency and consequence controls. Example evidence: Isolation, relief, deluge, bunds and emergency plans.
  3. How is barrier health known?: Why it matters: Turns assumptions into assurance. Example evidence: Tests, inspections, indicators and audits.

A generic checklist can miss the danger. A site storing flammable liquid needs to understand overfill, vapour formation, ignition, bund failure, firewater runoff and emergency response. A reactor site needs to understand runaway reaction, pressure relief, incompatible additions, cooling failure and emergency shutdown. A toxic gas system needs to understand detection, isolation, ventilation, shelter, evacuation and responder protection.

Once the scenario is defined, the organisation can ask better questions: what prevents the event, what detects it, what controls it, what limits consequences, what emergency actions are needed and what evidence proves each layer is healthy.

Scenario-led PSM questions - Scenario-led PSM questions
Scenario question Why it matters Example evidence
What can be released or go out of control? Defines hazardous inventory and initiating events. Inventory register and process description.
What is the top event? Clarifies the loss of control to prevent. Bowtie or hazard study output.
What prevents it? Identifies preventive barriers. Design standards, alarms, trips and procedures.
What detects it? Identifies monitoring and response triggers. Gas detection, level alarms and operator rounds.
What mitigates consequences? Identifies emergency and consequence controls. Isolation, relief, deluge, bunds and emergency plans.
How is barrier health known? Turns assumptions into assurance. Tests, inspections, indicators and audits.

Which core elements make up a process safety management system?

Core PSM elements cover knowledge, hazard analysis, operating control, competence, integrity, change, emergency response, audit and learning.

Different frameworks use different wording, but the substance is consistent. A site needs to know its hazards, control operations, maintain equipment, manage people and contractors, control change, prepare for emergencies and learn from evidence. See HSE COMAH 2015 overview.

The elements should not be isolated departments. A weak MOC can damage asset integrity. Poor competence can defeat procedures. Weak indicators can hide degraded barriers. Poor leadership can normalise overdue safety critical actions.

Core PSM elements - Core PSM elements
Element What it controls Useful evidence
Process safety information Hazardous substances, design basis, operating limits and equipment information. P&IDs, SDS, relief basis, safe limits and drawings.
Hazard identification and risk analysis Credible scenarios and safeguards. HAZOP, LOPA, bowties and action records.
Operating procedures and safe systems Normal, abnormal, start-up, shutdown and emergency operation. Field-verified procedures and shift handover records.
Competence and training People in safety critical roles and tasks. Training matrix, assessments and authorisations.
Asset integrity Safety critical equipment and containment. Inspection, test, maintenance and backlog evidence.
Contractor and permit control High-risk work interfaces. PTW, isolation, induction and supervision records.
Management of change Technical, procedural, organisational and temporary change. MOC screening, risk review and approval.
Emergency planning Response to credible major accident scenarios. Exercises, learning and plan updates.
Audit and review System effectiveness and improvement. Audit reports, indicators and leadership decisions.

How should a site implement a PSM system step by step?

Implementation should build from hazard understanding to barrier ownership, operating control, assurance and management review.

A site should not launch PSM as a branding exercise. Start with the major accident hazard profile and build the system around the controls that actually stop or limit those events.

Implementation needs a realistic plan. The organisation may already have many pieces: HAZOPs, permits, procedures, inspections and emergency plans. The work is to connect them, test them and close the gaps.

PSM implementation steps - PSM implementation steps
Step Action Output
1. Define scope Identify processes, inventories, substances, energy sources and COMAH status. PSM scope and hazard profile.
2. Identify scenarios Define credible major accident scenarios and escalation paths. Major accident scenario register.
3. Map barriers List preventive, detection, control, mitigation and emergency barriers. Barrier register and bowties.
4. Assign ownership Name owners for barriers, elements and risk acceptance decisions. Responsibility matrix and technical authority rules.
5. Set standards Define performance requirements, test frequencies and impairment rules. Barrier performance standards.
6. Gather evidence Connect procedures, tests, inspections, competence and indicators. Assurance plan and dashboards.
7. Audit and review Sample field reality, close actions and review weak signals. Audit programme and leadership review.

How should barriers be defined and assured?

Barriers should be defined by their role in the scenario, their performance requirement and the evidence that proves they work.

A barrier name alone is weak. 'Alarm' is not enough. The system needs to know which alarm, what condition it detects, who responds, how much time is available, whether response is realistic, how the alarm is tested and what happens if it is bypassed or impaired.

The best barrier registers separate prevention, detection, control, mitigation and emergency response. They also distinguish engineered barriers from human or procedural barriers because their reliability and assurance needs differ.

Barrier assurance - Barrier assurance
Barrier type Examples Assurance evidence
Prevention Design, containment, incompatible separation, safe operating limits. Design review, inspection and operating envelope checks.
Detection Level alarms, gas detection, pressure alarms and operator rounds. Functional tests, alarm response records and calibration.
Control Trips, interlocks, emergency shutdown, isolation and relief. Proof tests, bypass controls and impairment review.
Mitigation Bunds, deluge, firewater containment, blast protection and ventilation. Inspection, scenario drills and maintenance.
Emergency response Incident command, evacuation, shelter, firefighting and mutual aid. Exercises, debriefs and plan updates.
Organisational Competence, supervision, permit control and technical authority. Assessments, audits and decision records.

Illustrative seven-step decision route; this is a SHARE teaching example, not a prescribed legal checklist.

StepActionCheckFailure modeHold point
Define hazardIdentify inventory, initiating event, release and affected people/environment.Process-safety lead validates the scenario basis.A generic risk register omits credible escalation.Hold design or operation until major scenarios are stated.
PreventPrefer inventory reduction and independent overfill prevention.Engineering verifies design basis and proof test.A shared instrument can defeat both control layers.Do not operate with an unassessed preventive barrier loss.
DetectSet alarms and independent trips with known response time.Operations checks test and bypass status before transfer.Alarm overload or bypass removes warning.Stop transfer when the critical trip is unavailable.
MitigateProvide suitable containment and emergency isolation.Emergency and engineering teams test reachable actions.Bund or isolation may be impaired by maintenance.Hold operation when the mitigation basis is false.
OperateUse limits, competence, permits and shift handover.Supervisor samples actual records and field practice.Production pressure normalises deviation.Escalate limit excursion and pause unsafe work.
ChangeApply MOC to plant, software, staffing and temporary changes.Technical authority approves revised risk and hand-back.A temporary bypass can become permanent.No restart before changed barriers are verified.
AssureReview leading indicators, tests, actions and near misses.Leader traces one scenario to current barrier evidence.A green dashboard can conceal overdue safety-critical tests.Reopen risk when tests or actions are overdue.

Why is process safety information essential?

Process safety information is essential because people cannot operate, maintain or modify a hazardous process safely if the basis of safety is missing, wrong or not understood.

Process safety information includes chemical hazards, reaction hazards, inventories, design codes, equipment data, P&IDs, relief basis, safe operating limits, cause and effect logic, hazardous area information and emergency assumptions.

Poor information creates hidden risk. If drawings are out of date, operating limits are unclear, relief assumptions are unknown or plant modifications are not reflected in procedures, people may unknowingly defeat the basis of safety.

Process safety information - Process safety information
Information type Why it matters Control check
Hazardous properties Defines fire, explosion, toxic, reactive and environmental hazards. SDS and chemical hazard review.
Design basis Explains why equipment and safeguards are suitable. Controlled design file and calculations.
P&IDs and drawings Support operation, isolation, maintenance and emergency response. Drawing control and field verification.
Safe operating limits Define the envelope that should not be exceeded. Operating procedures and alarm settings.
Safety critical equipment data Supports inspection, testing and maintenance. Equipment register and performance standards.
Emergency assumptions Define response time, isolation and mitigation expectations. Emergency plan and exercise evidence.

How should operating discipline be managed?

Operating discipline should keep the process within the safe envelope during normal, abnormal, start-up, shutdown and emergency conditions.

Operating procedures should be usable. If they are too long, out of date, unclear or not matched to field conditions, people will create informal workarounds. A good PSM system field-verifies procedures with operators and includes what to do when conditions are abnormal.

Shift handover, alarm management, permit interfaces and start-up control deserve special attention because major accidents often occur when the plant is not in steady state.

Operating discipline controls - Operating discipline controls
Control What good looks like Evidence
Operating procedures Clear normal, abnormal, start-up and shutdown instructions. Field-verified procedures and revision history.
Safe operating envelope Defined limits and required response to exceedance. Operating limits and excursion records.
Shift handover Hazards, impairments, permits, alarms and abnormal conditions communicated. Handover logs and supervisor checks.
Alarm response Alarms are meaningful, prioritised and understood. Alarm rationalisation and response training.
Permit interfaces Maintenance and operations share isolation and hazard information. PTW, isolation and handback records.
Stop-work authority Workers can pause work when barrier status is uncertain. Stop-work examples and leadership response.

How does asset integrity fit into the PSM system?

Asset integrity keeps containment, safety critical equipment and protective systems reliable throughout the asset lifecycle.

Asset integrity is where process safety often becomes visible: corrosion, inspection deferrals, overdue relief valve tests, temporary repairs, leaking seals, impaired firewater systems and maintenance backlog all tell leaders whether the plant is drifting.

The PSM system should classify safety critical equipment, define inspection and test requirements, manage impairments, review backlog as major accident risk and prevent production pressure from normalising degraded safeguards.

Asset integrity assurance - Asset integrity assurance
Area PSM expectation Evidence
Safety critical equipment Identify equipment that prevents or mitigates major accidents. SCE register and performance standards.
Inspection and testing Complete tests at required frequency and quality. Inspection reports and proof test results.
Maintenance backlog Review overdue work for major accident risk. Backlog risk review and escalation.
Temporary repairs Risk assess, approve, time-limit and monitor. Temporary repair register.
Impairments and bypasses Control and communicate unavailable safeguards. Bypass log and compensating measures.
Ageing plant Identify degradation mechanisms and long-term replacement needs. Integrity review and lifecycle plan.

How should competence, contractors and human factors be built into PSM?

PSM depends on people who are competent, authorised, supported and given systems that are usable under real operating conditions.

Training attendance is not competence. Competence needs practical assessment, refreshers, supervision and clear authorisation for safety critical roles and tasks.

Contractors can affect major accident risk through maintenance, isolation, hot work, excavation, lifting, cleaning, inspection, testing and shutdown work. The host site must set rules, communicate hazards, verify competence and supervise interfaces.

Human factors should be designed into the system. Procedures, alarms, control rooms, staffing, fatigue, workload, communication and handover all shape whether people can respond reliably when barriers are challenged.

RoleLearningDemonstrationAssessorRecordReassess when
OperatorKnow process limits and stop pointsRespond to overfill scenarioShift leadDrill and logChange or alarm
SupervisorManage bypass and safe restartReview test and permitPSM leadDecision logImpairment
EngineerOwn barrier performance basisTrace one safeguardTechnical authorityDesign/test fileMOC
MaintenanceRestore safety-critical assetsDemonstrate test and hand-backEngineering leadWork orderDefect
Emergency leadExercise credible escalationRun scenario drillSite managerExercise recordPlan change
DirectorChallenge high-consequence barrier healthTrace scenario to evidenceIndependent assuranceBoard actionBacklog

Why is management of change central to PSM?

Management of change is central because apparently small technical, procedural or organisational changes can weaken major accident barriers.

Change includes plant modifications, temporary repairs, control logic changes, chemicals, operating limits, procedures, staffing, contractors, suppliers, software, alarm settings, inspection intervals and organisational structure.

A strong MOC process screens for process safety impact before implementation, uses competent review, updates documents, trains affected people, completes pre-start-up safety review where needed and verifies that actions are closed.

MOC controls - MOC controls
Change type Possible PSM impact Control
Equipment change Design basis, relief, materials or isolation may change. Technical review and drawing update.
Operating limit change Safe envelope may be altered. Hazard review and procedure update.
Control system change Trips, alarms or interlocks may be affected. Cause and effect review and testing.
Organisational change Competence, supervision or technical authority may weaken. Organisation risk assessment.
Temporary change Short-term workaround may become normal. Expiry date, review and compensating measures.
Restart after change Hazards may not be ready for operation. Pre-start-up safety review.

How should process safety indicators be used?

Process safety indicators should show whether major accident controls are healthy, degrading or failing.

HSG254 is useful because it encourages organisations to measure the health of controls over major hazard risks. Indicators should be tied to specific barriers and scenarios, not selected because data is easy to count. See HSE developing process safety indicators.

Leading indicators might track overdue safety critical maintenance, proof test completion, MOC action closure, alarm floods, impaired safeguards or emergency drill actions. Lagging indicators might track leaks, releases, fires, trips, demands on safeguards or process safety events.

Process safety indicator examples - Process safety indicator examples
Indicator type Example Leadership question
Leading Percentage of safety critical inspections completed on time. Are we maintaining barriers before demand?
Leading Overdue MOC safety actions. Are changes being closed safely?
Leading Number of impaired safeguards with expired review dates. Are temporary risk acceptances drifting?
Lagging Loss of containment events by severity. Which barriers failed and why?
Lagging Demands on relief, trips or emergency shutdown. Are initiating events increasing?
Weak signal Alarm floods, nuisance trips or repeated permit findings. What common degradation pattern is emerging?

How should PSM audit and management review work?

PSM audit and review should test field reality, barrier health, action effectiveness and leadership decisions.

A process safety audit should not only ask whether procedures exist. It should sample real jobs, maintenance history, barrier tests, MOC records, alarm response, emergency drills, action closure evidence and whether workers understand critical controls. See HSE managing for health and safety.

Management review should focus on major accident risk. Injury rates alone do not prove process safety. Leaders need to see barrier health, high-risk actions, risk acceptances, overdue safety critical work, weak signals and learning from incidents.

PSM assurance levels - PSM assurance levels
Assurance level Typical activity Output
First line Supervisors and operators check permits, isolations, rounds, handover and barrier status. Field checks and immediate corrections.
Second line HSSE, engineering and technical authorities audit PSM elements and barrier evidence. Findings, ranked actions and trend review.
Third line Independent internal or external specialist reviews test system effectiveness. Formal audit report and leadership action plan.
Management review Senior leaders review indicators, impairments, actions and risk acceptance. Decisions, resources and escalation.
Regulator engagement COMAH inspections, safety report review or regulatory findings. Regulator correspondence and verified response.

How should emergency planning connect to the PSM system?

Emergency planning should be based on credible major accident scenarios, not generic evacuation arrangements alone.

Emergency plans should reflect the hazardous inventory and possible escalation. For a fuel terminal, this may include tank fire, bund fire, vapour cloud explosion, firewater runoff and neighbouring impacts. For a toxic process, it may include release detection, isolation, shelter, evacuation, public communication and responder protection.

Exercises should test incident command, communication, isolation, mutual aid, responder access, environmental protection and recovery. Learning should feed back into the PSM system.

Which major accident shows why PSM systems matter?

Buncefield shows why a PSM system must control routine operations through reliable barriers, leadership and learning.

At Buncefield in December 2005, a fuel storage depot suffered massive explosions and a large fire after a tank overfilled during a transfer operation. More than 40 people were injured, a large area was evacuated, the fire burned for several days and there was extensive damage to the site and surrounding property.

The process safety lesson is not only 'avoid overfill'. The wider lesson is that routine operations can become major accident scenarios when hazardous inventory, level control, independent overfill protection, alarm response, supervision, leadership attention and learning are weak. A PSM system should have made tank overfill a clearly owned major accident scenario with defined barriers, testing, indicators, escalation and management review.

For a modern site, Buncefield should trigger direct questions: which tanks or vessels could overfill, which independent layers prevent it, how are alarms tested, what happens if instrumentation is impaired, how do operators know the safe limit, what indicators would show drift and how do leaders respond to overdue actions?

Buncefield learning applied to PSM - Buncefield learning applied to PSM
PSM area What failed as a learning theme Modern assurance question
Hazard recognition A routine transfer had major accident potential. Is each credible overfill or loss-of-containment scenario registered?
Independent protection Reliance on level control and overfill protection proved weak. Are independent safeguards tested and impairment-controlled?
Operating discipline Operators needed clear limits, alarms and response expectations. Can operators explain what to do before the safe limit is exceeded?
Indicators Weak signals and degraded control should have been visible. Which indicators reveal barrier degradation before an event?
Leadership Major hazard risk needed stronger senior attention. Do leaders review barrier health, not only personal injury data?
Learning Industry learning needed translating into local action. Can the site prove lessons have changed standards and field practice?

What should be in a major accident hazard and barrier register?

A major accident hazard register should connect scenarios, initiating events, barriers, owners, assurance evidence and escalation rules.

A normal risk register often hides process safety because it collapses complex scenarios into broad words such as 'fire' or 'chemical release'. A PSM register should describe the scenario clearly enough for operators, engineers and leaders to understand what prevents it.

The register should be live. If a barrier is impaired, a test is overdue, a temporary repair is accepted or a change is proposed, the risk status should update.

Major accident hazard register fields - Major accident hazard register fields
Field What to record Example
Scenario Credible major accident event. Tank overfill leading to vapour cloud and ignition.
Initiating events What could start loss of control. Transfer continues after high level.
Preventive barriers Controls that prevent the top event. Independent high-high level trip and operator response.
Mitigative barriers Controls that limit consequences. Bund, firewater, emergency isolation and incident command.
Owner Person or function accountable for barrier health. Operations manager, asset integrity lead or technical authority.
Performance standard What the barrier must do and how often it is tested. Trip proof test interval and response time.
Assurance Evidence that the barrier is healthy. Test records, inspections, audit and indicators.
Escalation What happens when the barrier is degraded. Impairment approval, compensating measure and risk review.

How does establishing a PSM system support NEBOSH PSM study?

This topic supports NEBOSH PSM by showing how major accident prevention is organised, assured and improved.

A strong answer should not describe a generic health and safety policy. It should identify major accident hazards, hazardous inventory, credible scenarios, safety critical barriers, competence, asset integrity, MOC, emergency planning, indicators and leadership review.

Scenario questions often ask what a site should do after weak indicators, repeated leaks, permit failures, maintenance deferrals, alarm problems or organisational change. The answer should connect those weak signals to barrier health and management review.

PSM study prompts - PSM study prompts
Study area What to explain Scenario application
PSM purpose Prevent and mitigate major accidents through a structured system. Explain why injury rates do not prove process safety.
Hazard understanding Inventory, process conditions and credible scenarios. Identify top events and escalation routes.
Barrier assurance Owners, standards, testing and impairment control. Request evidence of barrier health.
MOC Change can degrade safeguards. Screen organisational or technical change.
Indicators Leading and lagging indicators reveal control health. Create indicators linked to barriers.
Accident learning Buncefield and similar events show interacting failures. Translate lessons into local audit questions.

How do management frameworks support this topic?

HSE’s Plan–Do–Check–Act guidance helps assign ownership, deliver controls, check evidence and improve weak arrangements. Apply the relevant legal duties and task-specific technical evidence separately.

Official management guidance: HSE Managing for health and safety (HSG65)

FrameworkStatus and scopeContributionLimit
HSE HSG65GB regulator management guidancePlan, do, check and act with evidence of current controlApply to the actual high-consequence scenario.

What are the warning signs that a PSM system is failing?

Warning signs include degraded barriers, weak signals, poor ownership, overdue safety critical actions and leadership focus on the wrong data.

PSM failure rarely appears as one dramatic warning. It usually appears as normalised drift: repeated small leaks, nuisance alarms, overdue inspections, bypassed safeguards, incomplete MOC, temporary repairs, vague risk acceptances and poor action closure.

The danger is that each issue is closed locally without asking whether the major accident barrier system is degrading.

PSM warning signs - PSM warning signs
Warning sign How it can lead to harm Response
Overdue safety critical maintenance A barrier may fail on demand. Escalate backlog as major accident risk.
Repeated small leaks Containment degradation becomes normal. Trend, investigate and fix root causes.
Alarm floods or nuisance alarms Operators may miss critical warnings. Review alarm performance and response.
Temporary repairs without expiry Temporary risk becomes permanent. Apply MOC and impairment control.
MOC actions closed on paper only Change may proceed with unresolved risk. Verify physical and procedural completion.
Leadership reviews injury rates only Major accident risk may be invisible. Add barrier health and PSM indicators.
Contractors unclear on hazards High-risk work can defeat site controls. Strengthen induction, PTW and supervision.

What do the acronyms and key terms mean?

Acronyms should be explained because process safety pages use specialist legal, engineering and management language.

Acronyms and terms - Acronyms and terms
Term Meaning
COMAH Control of Major Accident Hazards.
DSEAR Dangerous Substances and Explosive Atmospheres Regulations.
ESD Emergency Shutdown.
HAZOP Hazard and Operability study.
HSG Health and Safety Guidance publication.
LOPA Layers of Protection Analysis.
MAPP Major Accident Prevention Policy.
MOC Management of Change.
P&ID Piping and Instrumentation Diagram.
PSM Process Safety Management.
PSSR Pre-start-up Safety Review.
SCE Safety Critical Equipment.
SMS Safety Management System.

Explore the Crownway Fuels hierarchy

Start at the company policy and follow a branch from duties and responsibilities to procedures and evidence.

Choose a document to see why it is used, who owns it, which duties it supports and what evidence it should produce. Switch to Text hierarchy for a list of expandable branches.

Fictional Crownway Fuels examples for English forecourts, with a separate illustrative bulk terminal. Check site applicability, permissions and actual controls before adapting any document for use.

Loading the Crownway register…

Open the company overview · Go to the documents

Which Crownway Fuels documents support this topic?

Open an editable document, read the preview, or find its place in the Crownway hierarchy. 10 resources relate to this page.

Fictional Crownway Fuels examples for English forecourts, with a separate illustrative bulk terminal. Check site applicability, permissions and actual controls before adapting any document for use.

Major accident prevention policy (9)
  • Major accident prevention policy (CWF-POL-COMAH · Completed fictional example)

    Document the lower-tier MAPP, approved commitments and organisational arrangements implemented through a proportionate SMS.
    Read preview · Download DOCX · Show in hierarchy

  • Major accident prevention and proportionate safety management procedure (CWF-PRO-COMAH · Completed fictional example)

    Explain who does what, in what sequence, the control rationale, evidence, escalation and safe restart conditions.
    Read preview · Download DOCX · Show in hierarchy

  • Lower tier COMAH MAPP and SMS implementation plan (CWF-PLN-COMAH-01 · Completed fictional example)

    Provide the site/task-specific lower tier comah mapp and sms implementation plan and retain its controlled output.
    Read preview · Download DOCX · Show in hierarchy

  • Major accident hazard and scenario register (CWF-REG-COMAH-01 · Blank register with separate fictional worked entries)

    Provide the site/task-specific major accident hazard and scenario register and retain its controlled output.
    Read preview · Download XLSX · Show in hierarchy

  • Major accident risk and barrier evaluation (CWF-RA-COMAH-01 · Blank editable master)

    Provide the site/task-specific major accident risk and barrier evaluation and retain its controlled output.
    Read preview · Download DOCX · Show in hierarchy

  • Safety critical elements and performance standards register (CWF-REG-COMAH-02 · Blank register with separate fictional worked entries)

    Provide the site/task-specific safety critical elements and performance standards register and retain its controlled output.
    Read preview · Download XLSX · Show in hierarchy

  • COMAH notification and public information review record (CWF-FRM-COMAH-01 · Blank editable master)

    Provide the site/task-specific comah notification and public information review record and retain its controlled output.
    Read preview · Download DOCX · Show in hierarchy

  • MAPP and SMS effectiveness audit (CWF-AUD-COMAH-01 · Blank editable master)

    Provide the site/task-specific mapp and sms effectiveness audit and retain its controlled output.
    Read preview · Download DOCX · Show in hierarchy

  • MAPP five yearly and material change review (CWF-FRM-COMAH-02 · Blank editable master)

    Provide the site/task-specific mapp five yearly and material change review and retain its controlled output.
    Read preview · Download DOCX · Show in hierarchy

Worked example for the illustrative bulk terminal (1)

Open the full Crownway library