Blog — OQSHA

Security and Safety | Rapid Reporting and Resolution of Incidents

Management of Change Is Not an Approval Form
Management of change safety review by plant, engineering and EHS leaders in an Indian industrial facility

A pump is replaced.

A line is rerouted.

A temporary bypass is added.

An interlock setting changes.

A contractor modifies a work method.

A maintenance turnaround introduces temporary arrangements that will later be reversed.

By the time many organisations start filling out the MoC form, the change has already begun creating risk.

That is the real reason management of change safety matters.

The purpose of MoC is not simply to document that a change happened.

It is to determine what the change affects, what new hazards or conditions it creates, which other controls must change with it, and what must be true before the changed system is used.

When MoC becomes a document-only exercise, the organisation can approve the change on paper while the real operational impacts remain spread across HIRA, PTW, engineering review, training, startup checks and field verification.

That is why management of change safety should be treated as a control process, not an approval form.


Why Change Becomes Risk Before It Becomes Paperwork

Change is usually visible first in the work itself.

A team installs a new component.

A process parameter is altered.

A temporary isolation arrangement is introduced.

A new raw material is trialled.

An operating sequence changes.

Work may begin because the change seems minor, urgent or technically obvious.

But risk can increase immediately if the organisation has not yet asked the right questions.

What else does this change affect?

Does it alter the hazard profile?

Does it affect the operating envelope?

Does it change maintenance, isolation, startup or emergency conditions?

Does it affect contractors or adjacent areas?

HSE’s plant modification guidance makes this point clearly: all modifications involving procedures, plant and equipment, people or substances should be subject to formal management procedures and risk assessment, and changes may affect other parts of the plant that are quite remote from the source of the change.【turn394899view1†L66-L87】

That is why management of change safety starts before the form is complete.

It begins at the moment the change becomes real enough to alter risk.


What Should Trigger MoC?

One of the most common weaknesses is assuming MoC only applies to major engineering modifications.

That is too narrow.

OSHA’s PSM rule requires written procedures to manage changes other than “replacements in kind” to process chemicals, technology, equipment, procedures and facilities affecting a covered process, and defines “replacement in kind” as a replacement that satisfies the design specification.【turn929717view0†L613-L650】【turn929717view2†L113-L117】

Even outside OSHA’s specific scope, that is a useful principle.

A practical MoC trigger review should consider whether the change affects:

  • process conditions;
  • equipment or materials;
  • procedures or methods;
  • control systems or interlocks;
  • layouts or access;
  • operating limits;
  • maintenance requirements;
  • contractor activities;
  • staffing or competency needs;
  • emergency arrangements;
  • environmental conditions;
  • temporary protections or workarounds.

The test should not be:

“Is this a big project?”

It should be:

“Could this change alter how risk is created, controlled or recovered?”

That produces much stronger management of change safety than a dollar-value or project-size filter.


What Good MoC Actually Reviews

A mature MoC process does not stop at the description of the change.

OSHA says a written MoC procedure should address, before the change, the technical basis, the impact on safety and health, modifications to operating procedures, the necessary time period for the change and authorization requirements.【turn929717view0†L620-L639】

That gives a practical review structure:

1. Technical basis

Why is the change being made?

2. Risk impact

What hazards or operating consequences could change?

3. Procedure impact

What instructions, limits or methods must be updated?

4. Time profile

Is the change temporary, permanent or phased?

5. Authorisation

Who reviews, approves and closes it?

For management of change safety, those questions should lead directly into action—not sit inside the form without operational consequences.


Linking MoC to HIRA, PTW and PSSR

MoC is not a substitute for every other control.

It is the process that tells the organisation which other controls now need attention.

HIRA

HIRA or other risk-assessment methods should help the organisation understand what hazards or exposures the change creates, modifies or removes.

The MoC identifies the need to reassess.

HIRA helps evaluate the changed risk.

PTW

Permit to work controls the execution of specific high-risk tasks during implementation, testing, modification, commissioning or reinstatement.

HSE’s permit guidance states that a permit is a formal system for certain work, helps communicate hazards and precautions, and is not a replacement for robust risk assessment.【turn394899view2†L48-L66】

So PTW does not replace MoC.

It operationalises specific work inside the wider change process.

PSSR

Where applicable, PSSR helps confirm whether the modified or new system is ready for startup.

Under OSHA’s PSM rule, the pre-startup safety review for certain new or modified facilities must confirm, among other things, that construction and equipment match design specifications, relevant procedures are in place, modified facilities meet MoC requirements, and operator training is complete.【turn929717view1†L503-L525】

That relationship is critical:

MoC defines and manages the change.
HIRA evaluates the changed risk.
PTW controls specific work.
PSSR verifies readiness before startup.

This is the operating chain behind effective management of change safety.

Management of change safety workflow linking HIRA, permit to work, verification and startup readiness

Temporary and Emergency Changes Need More Discipline, Not Less

Temporary changes are often where control weakens.

A bypass is installed “for a few days.”

A temporary operating method is introduced during maintenance.

A non-standard component is used until the correct one arrives.

An emergency repair is carried out under schedule pressure.

Because the change is not intended to be permanent, teams sometimes lower the quality of review.

That is risky.

Temporary changes still create real operating conditions.

HSE’s guidance highlights the need for accurate recording and monitoring of plant and process changes, while OSHA’s MOC framework specifically requires consideration of the time period for the change.【turn394899view1†L88-L93】【turn929717view0†L633-L639】

For management of change safety, temporary and emergency changes should therefore answer:

  • Why is the temporary condition necessary?
  • What additional risks does it create?
  • What interim controls apply?
  • Who authorised it?
  • What is the expiry or review point?
  • What conditions must be met before restoration?
  • How will the change remain visible to operations, maintenance and supervision?

A temporary workaround should not become a permanent blind spot.


Verification Before Start-Up Matters More Than Signature Count

A change can look complete even when the system is not ready.

The work may be finished.

The permit may be closed.

The equipment may be installed.

The form may be approved.

That still does not automatically mean the process is safe to start.

OSHA’s PSSR requirements for covered facilities emphasise that before introducing hazardous chemicals, the employer should confirm design conformity, adequacy of procedures, MoC compliance for modified facilities and completion of operator training.【turn929717view1†L510-L525】

The broader management lesson applies widely:

Before startup, ask whether the organisation has verified:

  • installation against design;
  • removal or control of temporary arrangements;
  • updated procedures;
  • relevant inspections or tests;
  • operator readiness;
  • outstanding actions;
  • relevant permit status;
  • emergency readiness;
  • approval to operate under the new condition.

In other words, management of change safety should culminate in operational verification—not merely administrative closure.


What Leadership Should Measure About Change Quality

Many organisations measure MoC activity in ways that say very little about safety quality.

For example:

  • number of MoCs raised;
  • number approved;
  • number closed.

Those counts are easy to report.

They do not tell management whether changes were reviewed well.

Better questions include:

  • How many changes were implemented before formal review?
  • How many temporary changes exceeded their review or expiry date?
  • How many MoCs required follow-up because procedures or drawings were not updated?
  • How many changes generated open safety-critical actions at startup?
  • How many changes were linked to incidents, near misses or repeat deviations?
  • How many startups proceeded with unresolved or weakly justified exceptions?
  • How many affected workers were informed or trained before the changed system was used?

Those are much more meaningful indicators of management of change safety than approval volume alone.


Contractors and Maintenance Teams Must Be Inside the Change Trail

Change often happens through projects, shutdowns, contractors and maintenance teams.

That means MoC quality is not only an engineering or EHS issue.

It affects:

  • contractor selection and communication;
  • safe work practices;
  • field supervision;
  • permit control;
  • startup coordination.

OSHA’s contractor provisions in PSM require the host employer to inform contract employers of known hazards and applicable emergency-action provisions, and require the contract employer to ensure training, documentation and compliance with facility safety rules for affected work.【turn929717view1†L460-L499】

That is especially relevant when modifications are executed by contractors but handed over to operations.

The organisation should be able to show not only that the technical work was completed, but that the changed condition was understood by the people who would operate, maintain or supervise it afterwards.


A Practical Management of Change Safety Review

If you want to test whether MoC is functioning as a safety control rather than a document workflow, choose one recent change and trace it end to end.

Ask:

Change trigger

Why did the change arise and what made it an MoC candidate?

Scope

What exactly changed—equipment, process, method, people, conditions or temporary state?

Risk review

What hazards were reassessed and what changed because of that review?

Linked controls

Did HIRA, PTW, training, procedures, inspections or PSSR also change where relevant?

Temporary conditions

Were any temporary protections, deviations or workarounds introduced?

Verification

What was checked before startup or return to service?

Evidence

Can the organisation reconstruct the complete trail?

That is a much better test of management of change safety than asking whether the form exists in the folder.


How Digital Workflows Help Without Replacing Judgement

Software should not make the safety decision on its own.

But it can reduce the fragmentation that often weakens change control.

A connected workflow can help link:

MoC → HIRA → PTW → actions → verification → PSSR → operating handover

That matters because the risk in many organisations is not the absence of forms.

It is the disconnect between related controls.

OQSHA’s relevant workflows can help teams manage linked evidence and actions across MoC, risk assessment, PTW, inspections, CAPA, training and startup-readiness reviews.

The goal is not automation for its own sake.

It is stronger management of change safety through better traceability, ownership and verification.


The Management Question

When a change occurs, do not end the conversation with:

“Was the MoC approved?”

Ask:

“Can we prove that the changed condition was understood, controlled and verified before use?”

That question forces the organisation to think beyond the form.

And that is where management of change becomes a real safety control.


CTA

Test One Change From Trigger to Start-Up

Use the Management of Change Safety Checklist to review one recent or upcoming change across:

Trigger → Risk Review → Work Control → Verification → Start-Up Readiness

Management of change safety checklist reviewed before equipment startup in an industrial plant

FAQ

What is management of change in safety?

Management of change is a structured process for reviewing and controlling changes that could affect risk, operations, equipment, procedures or people. Under OSHA’s PSM rule, written procedures are required for managing certain changes other than replacements in kind, and those procedures must address technical basis, safety impact, procedure changes, time period and authorisation requirements.

What should trigger an MoC?

There is no universal single trigger outside a company’s own process, but a good rule is to trigger MoC when a change could alter hazards, controls, operating conditions, procedures, equipment, temporary arrangements or start-up conditions. HSE’s plant modification guidance states that modifications involving procedures, plant/equipment, people or substances should be subject to formal management procedures and risk assessment.

Is PTW the same as MoC?

No. PTW controls specific high-risk work activities. HSE states that a permit is a formal system for defined work and explicitly says it is not a replacement for robust risk assessment. MoC is broader: it determines whether the change itself needs review, what else it affects and what must change around it.

How does PSSR relate to MoC?

PSSR helps confirm readiness before startup for certain new or modified facilities. OSHA’s PSM standard says the PSSR must confirm, among other things, that construction/equipment conform to design, procedures are in place, modified facilities meet MoC requirements, and training is completed.

What is a replacement in kind?

In OSHA’s PSM definitions, a replacement in kind is a replacement that satisfies the design specification.Organisations should still apply their own procedures and engineering judgement when deciding whether something is truly like-for-like.

Can software ensure change safety by itself?

No. Software can support workflow control, ownership, traceability and evidence, but competent review, operational judgement and authorised decision-making still remain essential.

External Authority Links

0 Comments

Submit a Comment

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