Management of Change (MOC): Why It Fails and How to Build a Process That Works

Management of Change — MOC — is one of those safety concepts that most organisations agree with in principle and fail to implement in practice. The idea is simple: before you change anything that affects how work is done, you formally assess what that change means for safety. You identify the new hazards it introduces. You implement the necessary controls. You train the people affected. You document what was decided and why.

In the real world, MOC programmes are routinely bypassed, diluted, or applied inconsistently. And when incident investigations dig into the root causes of major accidents, a failed or absent MOC process appears with remarkable frequency.

What Is Management of Change?

Management of Change is a formal safety process that ensures any modification to a facility, process, procedure, equipment, material, or organisational structure is reviewed for its safety implications before the change is implemented. Your existing safety controls were designed for a specific set of conditions. When those conditions change, the controls that were appropriate before may no longer be adequate. MOC is the mechanism that identifies the gap and closes it.

What Requires a MOC Review?

  • Process changes: modifications to operating parameters, introduction of new chemicals, changes to process sequence
  • Equipment changes: installation of new equipment, replacement with non-identical items, modifications to existing plant
  • Procedural changes: revisions to SOPs, new work methods, changes to emergency procedures
  • Organisational changes: restructuring, contractor arrangements, new responsibilities
  • Temporary changes: bypasses of safety systems, temporary use of non-standard materials — these deserve the most scrutiny

“Temporary changes that become permanent are one of the most consistent findings in major accident investigations. If it is still in place six months later, it was never really temporary.”

The Five Steps of an Effective MOC Process

Step 1 — Initiation: The person proposing the change formally documents what is changing, why, and what the new condition will look like.

Step 2 — Hazard Review: A structured assessment of the change’s safety implications — new hazards introduced, controls no longer adequate, additional controls required.

Step 3 — Approval: Review and sign-off at the appropriate authority level, commensurate with the risk level of the change.

Step 4 — Implementation: The change is made with all controls in place — procedures updated, workers trained, HIRARC revised, conditions verified before go-live.

Step 5 — Closure: The MOC record is formally closed confirming all actions are complete. Temporary changes must have a set review date.

Why MOC Programmes Fail

  • Like-for-like exceptions that swallow the rule — applied to changes that are not truly identical
  • Production pressure overrides process — the change goes live, the paperwork follows later
  • No ownership at the right level — MOC lives in the safety department instead of operations and engineering
  • Temporary changes never get closed — no tracking system, no expiry enforcement

Cikgu Barrier’s Take

In my incident investigation work, MOC failures appear in two forms: the absent MOC where no one recognised a change as requiring review, and the inadequate MOC where a review was conducted superficially. Both lead to the same outcome — predictable, preventable hazards that were not predicted, not prevented, and not controlled.

Visit cikgubarrier.com or explore our safety management training programs to build MOC capability in your organisation.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top