Skip to main content
    QHSEtech
    Updated
    All glossary terms
    Content date: · No individual check logged· AI use

    Management of ChangeMOC

    Definition

    Management of Change — review and control of proposed changes that may affect risks, operating conditions or responsibilities.

    Editorial definition: The QHSE Standard, updated 3 October 2026 · https://qhsetech.com/glossary/moc

    Scope: Apply the triggers and approvals required by the site's management system and relevant rules.

    Example for your evaluation: Trace a temporary change from review and authorisation through expiry or permanent adoption.

    Sources checked: . Examples are editorial illustrations.

    What OSHA process safety management requires for change

    The most specific legal text is OSHA's process safety management standard, 29 CFR 1910.119(l). Employers must establish and implement written procedures to manage changes to process chemicals, technology, equipment and procedures, and changes to facilities that affect a covered process. Replacements in kind are excluded; the standard defines one as a replacement that satisfies the design specification.

    Before any change, the procedure must address the technical basis for the change, its impact on safety and health, modifications to operating procedures, the time period needed, and authorisation requirements. Operating and maintenance employees and contract employees whose tasks will be affected must be informed of the change and trained in it before start-up, and process safety information and operating procedures must be updated where the change affects them.

    Management of change is not only a process safety term. ISO 45001:2018 has clause 8.1.3 management of change, and ISO 9001:2026 has 6.3 planning of changes and 8.5.6 control of changes; its foreword says requirements on changes to the quality management system were strengthened.

    Sources opened :

    What an MOC record holds in software

    • A change request: what changes, the category (chemical, technology, equipment, procedure or facility), and whether it is permanent or temporary with an end date.
    • The technical basis and the safety and health review, including the hazard analysis method used.
    • Affected documents, such as process safety information, drawings and operating procedures, each with an update task and an owner.
    • The people to inform or train, contractors included, with completion recorded before start-up.
    • Authorisations, a link to the pre-startup safety review where one is required, and closure only once documents are updated; for a temporary change, an expiry alert and a recorded decision to remove it or make it permanent.

    MOC or pre-startup safety review?

    They are separate PSM elements. MOC decides whether and how a change is made. The pre-startup safety review in 1910.119(i) applies to new facilities and to modifications significant enough to require a change in process safety information; it confirms, before highly hazardous chemicals are introduced, that construction and equipment match the design, procedures are in place and adequate, and training is complete. A modified facility must also meet the MOC requirements, so the two records should link to each other.

    A hypothetical example: a temporary pipe spool becomes a fixture

    The scenario below is invented to show how a change record behaves over time and does not describe a real facility. A transfer line develops a leak, and the plant fits a temporary spool made from a different grade of pipe so that production can resume that night. The shift supervisor raises a change request marked temporary, with an end date three weeks away, and an engineer reviews it the same day. The review notes the different material, the pressure it will see and who needs to know. Operators are briefed, the drawing is marked up, and a short authorisation is signed.

    Three weeks pass and the replacement part has not arrived. The expiry alert goes to the change owner, who has to choose between removing the spool, extending the change with a fresh review, or converting it to permanent. This time the engineer extends it by two weeks and records why. When the part finally arrives it is fitted as a like-for-like replacement of the original design, and the owner closes the temporary change after confirming that the marked-up drawing was updated and the operators were told. If nobody had acted at the expiry date, the spool would simply have stayed in service with no one deciding that it should, which is how many temporary changes become permanent by default.

    Common misunderstandings about management of change

    • Change management in an IT or project sense is a different thing. In safety and process work the term is about the physical plant, materials, procedures and organisation, and the question is what the change does to risk.
    • Small changes are not exempt by being small. A different gasket material, a relocated sensor or a relaxed staffing level can alter risk, and the screening question should be about effect, not size.
    • A like-for-like swap needs checking too. The point of a replacement-in-kind test is that the replacement meets the original specification; if it is merely similar, the exception probably does not apply.
    • A temporary change is not outside the process. Temporary changes are the ones most likely to be forgotten, so they need a time limit and a recorded decision at the end.
    • Approval is not the end. Documents have to be updated, people informed or trained, and the change confirmed as working as intended before the record is closed.
    • Organisational change counts. Reducing a night shift, merging two roles or changing a contractor can change who is available to respond, even when no equipment is touched.

    How management of change relates to other glossary terms

    Change control touches nearly every other safety process, so the glossary terms below are the ones most often asked about alongside it.

    • PSM: the US standard where management of change is a named element, written for covered chemical processes.
    • Permit to work: once a change is approved, the physical work to implement it is typically controlled by permits.
    • Lockout/tagout: a modification can add or remove energy sources, which means isolation procedures may need revising.
    • ISO 45001: the management system standard that expects planned changes to be assessed for their health and safety effects.
    • ISO 9001: includes planning and control of changes to the quality management system and to products and services.

    Records and evidence that usually exist for a change

    • The change request, with the reason, the description, the category and who proposed it.
    • The screening result: why the change was or was not treated as a controlled change.
    • The hazard or risk review that was carried out, with who took part and what it concluded.
    • A list of the documents, drawings and procedures that were updated, and who updated them.
    • Communication and training records for the people affected, including contractors.
    • Approvals, with names, roles and dates, and any conditions attached.
    • For temporary changes: the expiry date, any extension and the final decision.
    • Post-implementation checks, and a link to any start-up review that followed.

    What a software tool needs to capture for management of change

    • A screening step at the start that asks standard questions and records the answer, including a recorded decision that a change is not covered.
    • Configurable approval routes that depend on the change category and risk, with named approvers and a time stamp on each decision.
    • Task lists that tie each affected document or procedure to an owner and a due date, and block closure until they are done.
    • A distinct temporary type with an end date, automatic alerts before expiry and a mandatory outcome at that date.
    • Links to related records such as risk assessments, permits, training and start-up reviews, rather than free-text references.
    • Version history on the change itself, so an amended scope shows what it replaced.
    • Search and reporting that can list all open and overdue changes by site, unit and age.

    Catalog profiles documenting management of change

    Same rule for every product: tagged “Management of Change”, with a sourced management-of-change capability in its record, or one the vendor stated to us, labelled as vendor-stated. Documented and conditional capabilities qualify; check the linked scope before treating a module as included.

    Ordered by how closely our sources document this process, not by quality. Sponsored placements are labelled. How lists are ordered

    All 10 matching profiles are shown. Documentation review, not hands-on testing or a claim of compliance.

    Related software

    Frequently asked questions

    Are replacement-in-kind changes excluded?

    US OSHA PSM distinguishes replacement in kind from covered changes. Confirm that the proposed replacement meets that definition and the site's procedure.

    What triggers a pre-startup review?

    Under OSHA PSM, the trigger includes new facilities and modifications significant enough to require a change in process-safety information.

    What should a software demo show?

    Follow a temporary change through approvals, affected documents, communication and expiry. Ask what happens if the expiry is missed.

    More safety terms

    Related guides