Skip to content
Risk Based Process Safety (RBPS)Manage Risk

Management of Change

Governance of engineering, organisational, and procedural change with PHA, SIL, and FERA triggers

Strategic context

What this element is and why it matters

Management of Change is the gatekeeper that stops uncontrolled modifications from collapsing the risk control framework. The element maps to OSHA PSM 1910.119(l) and covers any change to chemicals, technology, equipment, procedures, organisation, or operating conditions, with the single exception of replacement in kind. Bhopal, Texas City, Flixborough, and BP Macondo can each be traced back to changes that bypassed MOC discipline, and our team builds the gate that keeps your facility from joining that list.

Management of Change

Individual significance for organisations

MOC is where the organisation either keeps control of its risk or quietly loses it. Every site that has suffered a major incident has an MOC failure story behind it. Sites that treat MOC as bureaucratic friction lose the discipline, while sites that treat it as the central risk management discipline keep control through decades of operation. MOC quality is a strong leading indicator of overall PSM maturity.

Contribution to Risk Based Process Safety (RBPS)

MOC is the integration point for nearly every other RBPS element. It triggers PHA revalidation (Element 7), process safety information updates (Element 6), procedure updates (Element 8), training updates (Element 12), and the pre startup safety review (Element 14). Without MOC discipline every other element drifts, and with it the system stays calibrated to current plant reality.

Key requirements

What compliant execution looks like

Change identification across chemical, technology, equipment, procedural, and organisational change
A clear line between replacement in kind and an MOC eligible change
A PHA, SIL, FERA, and hazardous area classification re review trigger per change type
A pre startup safety review gate before commissioning per OSHA PSM (i)
Training and procedure updates completed before operation
MOC backlog management with a full audit trail
Implementation methodology

How we implement this element

A focused six step methodology calibrated to deliver management of change as a working capability rather than a documented compliance artefact.

MOC Scope Definition

We define the boundary between an MOC eligible change and a replacement in kind, cover chemical, technology, equipment, procedural, and organisational change, and align it with CCPS and OSHA guidance.

Review Trigger Matrix

For each change type we specify the mandatory PHA, SIL, FERA, hazardous area classification, and pre startup safety review re review, and integrate it with an electronic MOC system such as SAP, Maximo, or Sphera.

Approval Hierarchy

We define the MOC initiator, technical reviewer, area approver, and area authority signoff, align it with the risk tier, and set the authorisation cycle time.

Pre Startup Safety Review Gate

We run the pre startup safety review per OSHA PSM (i), confirming that design and construction match, training is complete, procedures are updated, and PHA actions are closed.

Backlog and KPI Discipline

We track the MOC backlog and cycle time KPI, send a close out signal to engineering and operations, and integrate it with corporate HSE governance.

Audit and Continuous Improvement

We run a monthly MOC quality audit, a root cause review of MOC failures, and integration with incident lessons learned.

Implementation flow

Element implementation flow chart

A decision gated workflow that shows the actual sequence of activities from initiation through steady state operation, with key decision points highlighted.

Start
A change is requested by operations, engineering, or safety
Decision
Replacement in kind?
Decision gate, where yes means no MOC and no means proceed
Initiator Submits MOC
A form capturing technical basis, scope, safety and health impact, and time period
Review Trigger Determination
PHA, SIL, FERA, hazardous area classification, and pre startup safety review re review per change type
Technical Review
Multi discipline reviewer signoff with open items resolved
Area Authority Approval
Site level signoff before implementation
Implementation
Construction, installation, or procedure change
Decision
Pre startup safety review required?
Decision gate
Pre Startup Safety Review Execution
Per OSHA PSM (i), covering design match, training, procedures, and PHA closure
Information and Procedure Update
Documentation refreshed before live operation
MOC Close Out
All gates satisfied and the audit trail recorded
Monthly Quality Audit
Backlog, cycle time, and failure root cause analysis
Deliverables

What we produce

  • An MOC scope definition and procedure
  • A review trigger matrix per change type
  • An electronic MOC system implementation
  • Pre startup safety review gate criteria per OSHA PSM (i)
  • A backlog tracking dashboard
  • An audit programme with a monthly quality review
Common pitfalls

Where execution fails

  • Misclassifying a real change as replacement in kind so it bypasses MOC
  • Approval reduced to a rubber stamp with no depth in the technical review
  • Information and procedure updates slipping after MOC closure
  • An MOC backlog accumulating beyond a manageable size
Standards & references

Codes this element is built on

OSHA 29 CFR 1910.119(l) (Management of Change, US)OSHA 29 CFR 1910.119(i) (Pre Startup Safety Review)CCPS Guidelines for the Management of Change for Process SafetyISO 45001 2018 Cl.8.1.3 (Management of Change)MSIHC Rules 1989 Rule 4 (India)Factories Act 1948 §41B (India)
Implement this element

Talk to us about implementing Management of Change

We can scope this element implementation against your facility, regulatory context, and existing management system maturity, then integrate it with the other Risk Based Process Safety (RBPS) elements you already operate.