8 Misconceptions About Management of Change — Why MOC Matters for All Businesses

When I discuss Management of Change (MOC) with plant personnel, familiar faces quickly arise: the seasoned professional who cites OSHA 1910.119(a)(2) and sighs that their process is not a “covered process,” and the less experienced who complains that their drawing‑management system is lagging behind and that catching up would consume years of resources.

Other responses are equally common: “We already have a procedure for managers to approve small projects and alterations,” or a tongue‑in‑cheek comment about the “pennies and nickels” filling their car’s ash tray. These reactions reveal a shared uncertainty: what exactly is MOC, and why should it matter to a facility that is not regulated under the OSHA 1910.119 framework?

OSHA 1910.119(l)(1) defines MOC requirements: “The employer shall establish and implement written procedures to manage changes (except for “replacements in kind”) to process chemicals, technology, equipment and procedures; and changes to facilities that affect a covered process.” Although the regulation focuses on process safety, the core principle—controlling change to prevent loss—has relevance far beyond regulated industries.

For facilities that qualify as a “covered process,” the MOC requirements are well understood and essential to continued operation. More alarming, however, is the fact that studies attribute up to 80 % of major industrial accidents to uncontrolled change. In that sense, MOC can be seen as a form of life insurance: the fewer accidents, the higher the return on investment.

Even if your plant is not subject to OSHA’s specific MOC rules, every business that seeks to remain competitive must manage change. MOC is a cost‑effective loss‑prevention tool that complements safety, reliability, and environmental stewardship programs.

It is important to remember that MOC applies only to changes to existing systems; design of new processes or facilities is outside its scope. The MOC process assumes that the current system has known strengths and weaknesses, and seeks to mitigate the risks associated with modifying it.

In simple terms, MOC is a structured approach to preventing or mitigating losses—whether they affect safety, health, the environment, or business performance—resulting from changes to how a facility is built, operated, maintained, or repaired. Every business that wants to protect its assets and reputation will benefit from a robust MOC program.

What constitutes a “change”?
“Recognizing change” is often the most challenging part of MOC. The first step is a clear definition that matches your business objectives and any applicable regulations. A vague definition leads to paralysis and creates loopholes for those who wish to bypass the process.

Leadership should decide what risks the organization wants to control and then identify the changes that would increase those risks. For example, a change could involve hardware, software, procedures, or process parameters. Even non‑hardware modifications—such as a new software patch or a revised operating limit—must be considered.

OSHA’s source document distinguishes a change from a “Replacement in Kind” (RIK), which is a replacement that satisfies the original design specifications. The broader definition in OSHA 3313 clarifies that a change is “an alteration or adjustment to any component, variable or property within an existing system (except those within clearly defined boundaries or responsibilities).” This view acknowledges that technology, chemicals, and procedures are as critical as physical equipment.

Because each organization has a unique risk profile, the definition of a change must reflect its tolerance for uncontrolled modification. Below are common examples that most businesses would consider MOC‑eligible:

• Adding new process equipment or critical business systems, including software
• Replacing equipment or parts that are not “in kind”
• Modifying or adding to process equipment or critical systems
• Adjusting process control or instrumentation, including control strategies
• Changing specifications or sourcing of maintenance, repair, and operations (MRO) parts
• Altering safety systems—interlocks, shutdowns, fire or explosion suppression
• Revising standard operating procedures (SOPs) or emergency procedures
• Modifying site‑level organizational structure or maintenance procedures
• Changing raw material or component specifications or sourcing
• Altering utilities connections—air, electrical, gas, water, steam, etc.
• Adjusting critical data network connections
• Updating quality assurance (QA) procedures or test equipment

A brief, multi‑disciplinary brainstorming session early in the design phase can help ensure that the chosen definitions and examples align with business priorities and risk tolerance.

What about “temporary” changes?
There is no permanent change—only a temporary change that is eventually returned to its original state. Yet temporary changes are the most frequent cause of incidents. Therefore, MOC should treat temporary changes the same as permanent ones, with special attention to the return process. OSHA 3313 clarifies that “MOC procedures should ensure that equipment and procedures are returned to their original conditions at the end of a temporary change.” Treating temporary changes as permanent protects against the highest risk exposure.

Eight Common Misconceptions About MOC

1. “I’m not making a real modification; I’m just improving something.”
   Any change in configuration, form, fit, function, material, or procedure falls under MOC unless explicitly excluded by your criteria. Minor improvements that alter the system’s context can inadvertently increase risk. Empower employees to recognize and report such changes before they become critical.
2. “I’m behind; I can’t start MOC because we have outdated drawings.”
   Document control is a complement, not a replacement, for MOC. Prioritizing corrective actions based on system criticality allows you to move forward without waiting for every document to be perfect. MOC protects the future; it cannot amend past mistakes.
3. “This is an emergency; we don’t have time for MOC.”
   In emergencies, the discipline of a well‑established MOC process is even more essential. A controlled, documented approach to temporary bypasses or substitutions often saves more time and reduces risk than ad‑hoc workarounds. MOC should include a clear emergency procedure that does not bypass the core principles.
4. “Routing this form for approval takes too long.”
   Approval levels must be proportional to the change’s risk. Streamline the process by limiting approvers to those with the right expertise and authority, and by tailoring the workflow to the situation.
5. “The area manager already approves funding; that’s sufficient.”
   Authority to approve funds is not the same as the knowledge needed to evaluate a change’s technical or safety impact. A balanced, multidisciplinary review team delivers more reliable outcomes.
6. “We’re a warehouse or data center; there’s no danger.”
   MOC protects against all forms of loss—product quality, customer trust, equipment downtime, data integrity, and more. Even low‑hazard environments can suffer costly failures if changes are uncontrolled.
7. “MOC won’t catch every problem, so why bother?”
   While no system is perfect, MOC dramatically reduces the likelihood of accidents. It also provides a valuable audit trail that speeds root‑cause analysis when unforeseen issues arise. The cost of missed incidents often far outweighs the expense of MOC.
8. “Software or procedure changes don’t need MOC.”
   Software updates and procedural changes have caused significant incidents in many industries. Treat any alteration that could affect safety or performance the same way you would a physical modification—complete review, documentation, and approval.

Conclusion
A well‑designed MOC program is a vital loss‑prevention tool for every organization, regardless of industry or regulatory status. It does not need to be burdensome; with the right structure, MOC can coexist with continuous improvement and agile change management. The time to implement a robust MOC process is now.

This article first appeared in the July edition of Life Cycle Engineering’s newsletter, RxToday.

About the author

Sam McNair is a senior consultant with Life Cycle Engineering (LCE). A Professional Engineer and Certified Maintenance and Reliability Professional, Sam has more than 32 years of experience in discrete manufacturing, chemical process industries, mining, machine processes, automation, aviation, construction and utilities. He specializes in reliability engineering with a focus on integrating maintenance and manufacturing functions. Contact Sam at smcnair@LCE.com. For more information about Life Cycle Engineering, visit www.LCE.com.