Management of Change (MOC): Best Practices for Industrial Operations
Management of Change (MOC): Best Practices for Industrial Operations
Author: Fidelis Associates | Published: 2026-03-02 | Last Updated: 2026-03-03
Meta Description: Management of Change (MOC) is a PSM requirement for evaluating proposed changes to process chemicals, technology, equipment, and procedures before implementation. Learn MOC best practices.
Definition
Management of Change (MOC) is a systematic process required by OSHA 29 CFR 1910.119(l) for evaluating and authorizing changes to process chemicals, technology, equipment, and procedures before implementation. MOC ensures that proposed changes are assessed for their impact on process safety, that affected employees are informed and trained, that documentation is updated, and that Pre-Startup Safety Reviews are conducted where required. It is one of the 14 elements of Process Safety Management and a critical control against unintended consequences from operational changes.
What Triggers an MOC
MOC is required whenever a change affects the safety or health aspects of a process covered by PSM — whether at a petroleum refinery, a chemical manufacturing facility, a midstream gas processing plant, or a hydrogen production facility. Common triggers include:
- Process chemistry changes — new feedstocks, catalysts, or reaction conditions
- Technology changes — modified control logic, new instrumentation, or revised operating parameters
- Equipment changes — new equipment, modifications to existing equipment, or changes in materials of construction
- Procedure changes — revised operating procedures, new startup or shutdown sequences, or modified emergency procedures
- Organizational changes — staffing reductions, shift schedule changes, or restructuring of safety-critical roles (often overlooked)
What Does Not Require MOC
Replacement-in-kind — replacing equipment with equipment that meets the original design specifications — generally does not require MOC. However, the determination of replacement-in-kind must be documented, and the definition must be applied carefully. A "like-for-like" replacement that changes materials of construction, design pressure, or control configuration is not replacement-in-kind and does require MOC.
The MOC Process
An effective MOC process follows a structured lifecycle from initiation through close-out.
Step 1: Request and Description
The person proposing the change submits an MOC request describing what is being changed, why, and the expected impact. The description must be specific enough to evaluate the safety implications.
Step 2: Hazard Evaluation
A qualified reviewer (or team) evaluates the proposed change for its impact on:
- Process safety information (P&IDs, operating limits, equipment specifications)
- Process hazard analysis findings and safeguards
- Operating procedures
- Maintenance and inspection programs
- Training requirements
- Emergency plans
For complex or high-risk changes, the evaluation may require a formal PHA review, a What-If analysis, or a LOPA evaluation.
Step 3: Authorization
The change must be authorized by responsible management before implementation begins. Authorization should be based on the hazard evaluation results and confirmation that all required actions (procedure updates, training, PSSR) are planned.
Step 4: Implementation
The change is implemented according to the authorized scope. Implementation controls should ensure the change does not exceed the evaluated scope and that any deviations from the authorized scope trigger a new or revised MOC.
Step 5: Pre-Startup Safety Review
If the change is significant enough to alter process safety information, a Pre-Startup Safety Review (PSSR) must be completed before the changed process is placed in service. PSSR confirms that the change was implemented as designed, safety systems are operational, and affected personnel have been trained.
Step 6: Close-Out
MOC close-out confirms that all required actions are complete:
- Process safety information has been updated (P&IDs, equipment lists, operating procedures)
- Affected employees have been trained on the change
- PHA documentation has been updated to reflect the new process configuration
- PSSR is complete (if required)
- Temporary changes have been either removed or converted through a new permanent MOC
What Is the Difference Between MOC and Replacement-in-Kind?
One of the most common MOC failures is misclassifying a change as replacement-in-kind to avoid the MOC process. The distinction matters because replacement-in-kind does not require the hazard evaluation, authorization, and documentation updates that MOC provides.
| Scenario | Replacement-in-Kind? | | ------------------------------------------------------------------------ | ---------------------------------------- | | Replacing a pump with the same model, materials, and capacity | Yes | | Replacing a pump with a different model that meets original design specs | Possibly — must verify all specs match | | Replacing a carbon steel pipe section with stainless steel | No — material of construction change | | Replacing a relief valve with a higher set pressure | No — design specification change | | Updating control logic for a different operating scenario | No — technology change | | Replacing a gasket with a different material rated for the same service | Requires evaluation — often triggers MOC |
When in doubt, the safer path is to process the change through MOC. An unnecessary MOC is far less costly than an unmanaged change that leads to an incident.
Common MOC Failures
Temporary Changes That Become Permanent
Temporary MOCs are approved with a defined duration, but the change remains in place after the expiration date without review. Without a system for tracking and enforcing temporary change durations, facilities accumulate undocumented modifications.
Incomplete Close-Out
The change is implemented and the process is restarted, but MOC close-out tasks — document updates, training, PHA revisions — are not completed. This creates a gap between the actual process configuration and the documented process safety information.
Scope Creep During Implementation
The original MOC authorizes a specific change, but during implementation, additional modifications are made without returning to the MOC process. Each additional modification should be evaluated for its own safety impact.
Organizational Changes Bypassing MOC
Changes to staffing levels, shift structures, or roles with safety-critical responsibilities are rarely processed through MOC, even though they can significantly affect process safety at petroleum refineries, petrochemical plants, and other energy infrastructure operations. Reducing the number of operators on a shift, eliminating a dedicated safety role, or consolidating maintenance coverage across multiple units are all changes that warrant MOC evaluation.
Inadequate Hazard Evaluation
The MOC request is submitted and approved, but the hazard evaluation is superficial — a checkbox exercise rather than a genuine assessment of the safety implications. This is particularly common for changes that are perceived as minor or routine at established refinery and chemical manufacturing operations.
Integrating MOC with Other PSM Elements
MOC does not operate in isolation. It connects directly to several other PSM elements:
- Process Safety Information — Every MOC that changes the process must result in updated PSI (P&IDs, equipment specs, operating limits).
- PHA — Changes that affect the basis of existing PHA scenarios must trigger a PHA update or, at minimum, a screening review.
- Operating Procedures — Procedure changes must be reflected in the operating procedures and communicated to operators.
- Training — Affected employees must be trained on the change before they are expected to work with the modified process.
- PSSR — Significant changes require a PSSR before restarting the process.
- Incident Investigation — Investigation findings often reveal MOC failures as contributing causes, reinforcing the need for robust MOC discipline.
How Should Emergency Changes Be Handled in the MOC Process?
Emergency situations sometimes require immediate action — a change cannot wait for the full MOC review cycle without risking a worse outcome. A well-designed MOC program accounts for this reality with a defined emergency MOC pathway, not by suspending MOC requirements.
Emergency MOC bypasses are justified when a condition presents an imminent safety hazard, when equipment failure is causing or threatening an environmental release, or when inaction could lead to a catastrophic event. The threshold should be high. Time pressure or operational convenience do not qualify.
Even during an emergency, minimum documentation is required before or immediately after implementation: what was changed, why the emergency designation was applied, who authorized the change, and what temporary controls are in place to manage hazards until normal operating conditions are restored.
After the emergency is stabilized, formal MOC review must follow within a defined time period. Best practice is 72 hours for simple changes and no more than two weeks for complex ones. All normal MOC steps — hazard evaluation, process safety information updates, procedure revisions, training, and PSSR where required — must be completed retroactively. The fact that the change has already been implemented does not eliminate these obligations; it only changes the sequence.
Emergency MOC authority should be limited to a small group of designated individuals — typically senior operations and safety leadership. Each use should trigger a management review to confirm the emergency designation was appropriate.
The most common failure mode in emergency MOC programs is normalization: "emergency" becomes a routine mechanism for bypassing review. Track and trend every emergency MOC. If the rate is climbing, or if the same types of changes appear repeatedly, the underlying causes — inadequate planning, chronic equipment reliability issues, or cultural pressure to skip process — need to be addressed directly.
Key Takeaways
- MOC applies to changes in process chemistry, technology, equipment, procedures, and organizational structure — not just hardware.
- The boundary between MOC and replacement-in-kind must be clearly defined and consistently applied; misclassification is one of the most common MOC failures.
- Every MOC must be closed out completely — document updates, training, PHA revisions, and PSSR are not optional follow-up items.
- Temporary changes require the same rigor as permanent changes and must be tracked to ensure they are removed or formally converted.
- MOC integrates with PSI, PHA, training, PSSR, and incident investigation; treating MOC as a standalone process creates systemic gaps.
Assess Your Program
Is your MOC process catching changes before they are implemented, or are changes routinely bypassing the system? Start with a free assessment.
For an expert evaluation of your MOC program, FidelisGap identifies systemic weaknesses in change management processes and provides actionable corrective actions.
Related Resources
- What is Process Safety Management? A Complete Guide — MOC is one of the 14 PSM elements. Understand the full framework.
- The 14 Elements of PSM: A Practitioner's Breakdown — Practical guide to all 14 PSM elements.
- How to Conduct a Process Hazard Analysis (PHA) — PHA and MOC are tightly linked; changes often require PHA updates.
- What is a Pre-Startup Safety Review (PSSR)? — Significant changes require PSSR before the process is placed in service.
Frequently Asked Questions
What are the most common MOC program failures? The three most common MOC failures are: (1) changes that bypass the MOC process entirely, often because the boundary between MOC and replacement-in-kind is poorly defined or because organizational and procedural changes are not recognized as MOC triggers; (2) temporary changes that become permanent without completing the MOC lifecycle — approved with a defined duration but never formally closed out or converted; and (3) incomplete close-out where the change is implemented and the process restarted, but downstream tasks like procedure updates, training, PSI revisions, and PHA documentation are not completed. Of these, incomplete close-out is the most prevalent because the urgency to implement the change rarely matches the urgency to update the documentation.
How should emergency changes be handled under MOC? Emergency changes — modifications required to address an imminent safety hazard or prevent an immediate shutdown — still require MOC, but the process may be compressed. Best practice is to establish a pre-defined emergency MOC procedure that allows an authorized individual to approve the change with an abbreviated evaluation, with the understanding that the full MOC documentation, hazard evaluation, and close-out tasks will be completed within a defined timeframe after the emergency is resolved (typically 72 hours to two weeks). The emergency MOC must still be documented and tracked through the normal close-out process. An emergency MOC procedure is a best practice; OSHA 1910.119(l) does not provide an explicit emergency exemption.
What is the difference between MOC and replacement-in-kind? Replacement-in-kind means substituting equipment or components with items that meet the original design specifications in every respect — same materials, capacity, design pressure, temperature rating, and control configuration. If any specification differs from the original design, it is not replacement-in-kind and requires full MOC evaluation per 29 CFR 1910.119(l). Common misclassifications include changing materials of construction (e.g., carbon steel to stainless steel), substituting gasket materials, changing relief valve set pressures, or installing a "functionally equivalent" component from a different manufacturer with different specifications. When in doubt, process the change through MOC — an unnecessary MOC is far less costly than an unmanaged change that leads to an incident.
Fidelis Associates provides MOC program development, auditing, and process safety consulting through FidelisCore. Our team helps facilities build MOC systems that integrate with PHA, PSSR, training, and document management for sustainable compliance.
Ready to strengthen your operations?
Talk to a Fidelis specialist about how we can help.