Management of Change

Why This Matters

Most organisations are good at managing steady-state work and surprisingly weak at managing change. A temporary hose, a bypassed interlock, a new chemical, a different contractor, or a “quick” layout tweak can quietly remove controls people still believe are in place.

Management of Change (MOC) is the discipline of recognising change early, assessing consequences, approving with eyes open, implementing with updated documents and briefings, and verifying the result. Without MOC, risk assessments and permits may describe a workplace that no longer exists.

MOC is not bureaucracy for its own sake. It is how you stop yesterday’s assumptions from governing today’s hazards.

Key Ideas

Change includes hardware, procedures, people, and materials — not only capital projects. Temporary workarounds that last beyond a defined short window are still changes.

Like-for-like replacement may follow a lighter path, but “like-for-like” must be defined tightly. A different manufacturer’s seal is not automatically identical in performance.

Emergency changes still need a path: stabilise safely, document what was done, and complete full MOC as soon as conditions allow.

Step-by-Step Process

1. Propose. What is changing, why, when, who is affected, and what success looks like.
2. Screen. Decide routine like-for-like versus full MOC using written criteria.
3. Assess. Hazards, process interactions, emergency impact, environmental effects, training needs, and document updates.
4. Approve. Competent reviewers sign before implementation; higher risk needs higher authority.
5. Implement. Update procedures, labels, drawings, and briefings as required.
6. Verify. Confirm the field matches the approval; watch for unintended effects.
7. Close. Capture lessons; set a post-implementation review date for significant changes.

What to Capture

Worked Scenario: Temporary Bypass

A sensor fails and production wants a temporary bypass “until the part arrives Friday.” Without MOC, the bypass becomes permanent by neglect. With MOC, the proposal states compensatory monitoring, who watches readings, maximum duration, and what happens if the part slips to next week.

Approval requires a named owner, a hard end date, and a daily check. If Friday passes, the bypass is re-approved or the unit stays down. Close-out removes the bypass, restores the sensor, and records why the failure happened so the spare strategy can improve.

The record can stay light; the calendar ownership is the control.

Questions That Expose Weak MOC

Before you treat the process as complete, walk these questions with the people who will live with the result:

• What exactly is different after this change?
• Who can be harmed in a new way?
• Which documents and labels will be wrong if we forget them?
• What is the maximum time a temporary state may last?
• Who has authority to say no under production pressure?
• How will we verify the field matches the approval?

Going Deeper in Practice

Create a visible MOC log for the site: open changes, owners, end dates, and overdue verifications. Review it in the same meeting where you review incidents — change is a leading source of latent hazards.

Connect MOC to contractors: method changes on site are MOC events. Connect to chemical introductions: new products are MOC events. Connect to staffing: loss of a critical competent person can be an organisational MOC.

Teach supervisors the difference between operational flexibility and uncontrolled change. Flexibility without assessment is improvisation in hazardous systems.

Failure Patterns to Watch

• Post-hoc approvals
• Eternal temporary bypasses
• Orphan document versions
• No post-implementation check
• Unclear screening criteria
• Silent contractor method changes

What Good Looks Like After 90 Days

People can explain the process without reading a slogan poster. Records match reality. Actions close on time more often than they slip. Leaders sample quality, not only quantity. Near misses and changes reopen the right documents instead of creating orphan notes.

New supervisors receive a practical walkthrough within their first weeks. Contractors hear the same expectations as employees for the work they share. Stop-work and escalation routes are used without career punishment for good-faith calls.

Cadence and Leadership Sampling

Set a simple review rhythm: weekly sampling of live records, monthly trend review of overdue actions, and quarterly refresh of trigger lists or scope definitions.

Leaders should ask quality questions: Does this match the field? Are owners real? Did we reopen after the last near miss? Quantity metrics without quality sampling will be gamed.

Common Pitfalls

• Calling everything like-for-like to avoid assessment
• Temporary changes with no end date
• Approvals after implementation
• Documents not updated so the next shift works blind
• Training skipped for people affected overnight
• No link between MOC and permit or emergency plan updates
• Contractors changing method on the day without re-screening

Screening Criteria You Can Defend

Write screening criteria in plain language: what counts as like-for-like, what always needs full MOC, and what needs urgent MOC after emergency action. Include examples from your own site history so the criteria feel real.

Ambiguous screening is how risky changes slip through as “minor.” If two competent supervisors would disagree, tighten the wording and add a default: when unsure, use full MOC.

Publish the criteria where supervisors actually plan work — not only in a rarely opened manual.

Documents, Labels, and the Next Shift

The most common MOC injury pathway is simple: the field changed, the procedure did not, and the next shift trusted the old page. Build a mandatory document and label checklist into every MOC with more than trivial risk.

Verification should include a fresh pair of eyes walking the area with the old and new description in hand. If they cannot see the difference, the communication plan is incomplete.

For multi-shift operations, require a handover note on significant MOCs for at least the first two cycles after implementation.

Portfolio View of Open Changes

Individual MOC forms can look tidy while the site carries ten temporary states nobody tracks as a set. Keep a single open-change list with end dates and residual risk flags.

Leadership review should ask which temporary states are about to expire and which have already expired without close-out. Overdue temporary MOCs are latent failures waiting for a busy day.

Connect chronic temporary states to capital or procurement decisions so the organisation either funds the permanent fix or accepts the risk consciously — not by neglect.