Skip to main content
  • Solutions
      • Compliance Management
      • Audits and Inspections
      • Compliance Obligations
      • Document Management
      • Incident Management
      • Management of Change
      • Risk Register
      • Pipeline Safety
      • Task Tracking
      • Training
      • Environmental
      • Air Quality
      • ISO 14001
      • EPA RMP
      • LDAR
      • SPCC
      • Stormwater
      • TSCA PCB Management
      • Waste Management
      • Water Quality
      • Health and Safety
      • ISO 45001
      • Asbestos
      • Chemical Management
      • Emergency Planning
      • Industrial Hygiene
      • Hazard Analysis
      • Process Safety Management
      • Other
      • ISO 9001
      • Contractor Management
      • Customer Management
      • Data Management
      • Land Management
      • Oil and Gas
      • Preventive Maintenance
      • EHS Dashboard
      • Mobile EHS App
  • Industries
      • Mining
      • Oil and Gas
      • Manufacturing
      • Food and Beverage
      • Higher Education
      • Healthcare
      • Construction
      • Municipalities
      • Utilities/Power
      • Transportation
      • Petrochemicals
      • Chemicals
  • About
      • Accessibility
      • Security
      • AI Features
      • System Status
      • Release Notes
      • Support
      • Why Ecesis
      • About EDS
      • Frequently Asked Questions
      • Join Our Team
      • Pricing
      • EHS Resources/Tools
      • EHS Compliance Calendars
      • EHS Calculators
      • EHS Inspections
      • EHS Program Audits
      • EHS Blog
Ecesis EHS Software
  • Ecesis EHS Software on LinkedIn
  • Ecesis EHS Software on Facebook

PSM Management
of Change Guide

Management of Change (MOC) is the gatekeeper that prevents uncontrolled modifications from introducing new hazards into your covered processes. Under 29 CFR 1910.119(l), employers must establish written procedures to manage changes to process chemicals, technology, equipment, procedures, and facilities that affect a covered process. MOC is one of the most frequently cited PSM elements because changes happen continuously and each one has the potential to invalidate existing safeguards. Ecesis provides dedicated MOC software with customizable workflows, impact assessments, and complete audit trails.

Every unmanaged change to a covered process is a potential OSHA citation
Distinguishing changes from replacements in kind requires clear definitions
MOC must trigger updates to PSI, procedures, training, and PSSRs simultaneously

What OSHA Requires

Under 29 CFR 1910.119(l), employers must establish and implement written procedures to manage changes (except replacements in kind) to process chemicals, technology, equipment, and procedures, and changes to facilities that affect a covered process. Procedures must address:

  • The technical basis for the proposed change
  • Impact of change on safety and health
  • Modifications to operating procedures
  • Necessary time period for the change
  • Authorization requirements for the proposed change

Employees involved in operating a process and maintenance and contract employees whose job tasks will be affected by a change must be informed of, and trained in, the change prior to startup. If a change results in a change to process safety information, that information must be updated accordingly. If a change results in a change to operating procedures or practices, those must be updated as well.

Step-by-Step Implementation

Define What Constitutes a Change

The most important step in MOC implementation is clearly defining what requires an MOC versus what qualifies as a replacement in kind. Develop written criteria that address:

  • Changes requiring MOC: Different materials of construction, different operating conditions, different process chemicals, different equipment specifications, modified control logic, altered operating procedures, changes to safety systems
  • Replacements in kind (no MOC required): Replacing equipment with identical specifications (same manufacturer, model, materials, rating). Document that the replacement meets all original design specifications
  • Gray areas: Equipment that is functionally equivalent but from a different manufacturer, procedure changes that do not affect safe operating limits, temporary modifications. Define how these will be evaluated

Train operations and maintenance personnel to recognize when an MOC is needed.

Design the MOC Workflow

Build a structured workflow that ensures every change is properly evaluated and authorized before implementation:

  • Initiation: Anyone can submit a change request describing the proposed change and its purpose
  • Technical review: Evaluate the technical basis, impact on safety and health, and modifications needed to PSI, procedures, and training
  • Authorization: Appropriate level of management approval based on the risk and scope of the change
  • Implementation: Execute the change per the approved plan, update documentation, and conduct training
  • PSSR: Perform pre-startup safety review before operating under new conditions
  • Closeout: Verify all action items are complete, documentation is updated, and training is documented

Integrate with Other PSM Elements

MOC does not exist in isolation. Each change can trigger requirements across multiple PSM elements:

  • Process safety information: Update P&IDs, equipment specifications, and chemical data as needed
  • Operating procedures: Revise procedures affected by the change
  • Training: Train affected employees before startup
  • PHA: Consider whether the change warrants a PHA update or a focused hazard review
  • Mechanical integrity: Add new equipment to the inspection schedule
  • PSSR: Conduct review before operating under modified conditions

Build these integration points into your MOC form and workflow so they cannot be overlooked.

Manage Temporary Changes

Temporary changes present unique risks because they are often treated with less rigor than permanent changes but can exist for extended periods. Establish clear procedures for temporary changes that include:

  • Maximum duration allowed before the change must be made permanent or reversed
  • The same review and authorization process as permanent changes
  • A tracking mechanism that ensures temporary changes are reversed at the end of the authorized period
  • Evaluation of whether the temporary change needs its own PHA review

Common Pitfalls to Avoid

Not having clear written criteria for distinguishing changes from replacements in kind
Implementing changes before the MOC is fully approved and closed out
Failing to update process safety information, procedures, and training after the change is implemented
Allowing temporary changes to remain in place indefinitely without follow-up

How Software Supports This Element

Ecesis provides purpose-built management of change software designed for PSM compliance:

  • Customizable workflows: Define your review, approval, and closeout stages with automatic routing to the right reviewers
  • Impact assessment forms: Built-in checklists ensure every MOC evaluates impacts on PSI, procedures, training, PHAs, and mechanical integrity
  • PSSR integration: PSSR checklists are automatically triggered within the MOC workflow
  • Temporary change tracking: Automated expiration tracking and notifications prevent temporary changes from becoming permanent by default
  • Complete audit trail: Every action, approval, and modification is logged with timestamps for audit readiness
Need help implementing Management of Change? Ecesis process safety management software provides the tools to build and maintain a compliant program for this and all other 14 PSM elements. Learn more about Ecesis PSM software or contact us to schedule a free 30-minute demo.

Frequently Asked Questions

What is a replacement in kind?

A replacement in kind is a replacement that satisfies the original design specification. For example, replacing a valve with an identical valve from the same manufacturer with the same pressure rating, materials of construction, and size. If any specification changes, it is not a replacement in kind and requires MOC review.

Do procedure changes require MOC?

Changes to operating procedures that affect how a covered process is operated should go through MOC. Minor editorial corrections or formatting changes that do not alter the substantive content or safe operating parameters typically do not. Your MOC procedure should define the threshold.

How do we handle emergency changes?

Establish an emergency change procedure that allows immediate action to address imminent hazards while still capturing the change in the MOC system as soon as practical. The emergency MOC should be reviewed and formally processed within a defined timeframe (typically 24 to 72 hours).

Who should approve MOCs?

OSHA does not specify approval authority, but the approver should have the technical knowledge and organizational authority appropriate to the scope and risk of the change. Many facilities define tiered approval levels based on the risk assessment of the change.

How long should MOC records be retained?

OSHA does not specify retention periods for MOC records. Best practice is to retain MOCs for the life of the process or equipment involved, as they become important references during PHA revalidations, incident investigations, and compliance audits.

Ecesis PSM Compliance Software

PSM Software

Centralized platform to manage all 14 PSM compliance elements

Management of Change

Submit, route, and approve change requests through defined workflows

Incident Investigation

Report, investigate, and track corrective actions to completion

Training Management

Deliver and track PSM training with comprehension verification

Mechanical Integrity

Schedule inspections, track deficiencies, and manage maintenance

PSM Compliance Calendar

Track deadlines across all 14 elements automatically

Related PSM Resources

PSM Software Implementation Guide 14 PSM Elements PSM Requirements PSM Compliance Calendar Hazard Analysis

What Is Ecesis?

Ecesis is a leading EHS Software Solution that has been helping companies around the world reach their EHS goals since 1993.

About Us

Why Ecesis Join Our Team Pricing Resources EHS Blog

Get in Touch

1499 West 120th Avenue
Suite 110
Westminster, CO 80234
(720) 547-5102 (866) 733-6912 Click To Email Us

Connect With Us

EHS Software on LinkedIn EHS Software on Facebook EHS Blog

Copyright © 2026 EnviroData Solutions, Inc.

Terms of Use    Privacy Statement    Cookies

×

Please complete the form below or call us at (720) 547-5102 to learn more about Ecesis.

Enter Your Name


Enter Your Phone Number


Let Us Know How We Can Help You


Enter Your E-mail


Please check the reCAPTCHA box.