Management of Change (MOC) Procedure Template: A Complete Guide

Change is part of every business. Teams replace equipment, update work methods, introduce new materials, and change staff roles. However, even a small change can create new risks if no one checks its impact first. A Management of Change (MOC) Procedure Template helps organizations plan, assess, approve, and track changes before they take effect. It gives teams a clear process to follow. As a result, they can reduce risks, avoid confusion, and keep work under control.

An effective MOC process covers more than approval. It also checks hazards, affected workers, training needs, documents, and follow-up actions. Therefore, every change has a clear owner and a defined path from request to closure.

With eAuditor Audits & Inspections, teams can digitize MOC checklists, record risk assessments, document reviews, and track corrective actions. In turn, managers can keep change records organized and see which tasks still need attention.

What Is a Management of Change (MOC) Procedure?

A Management of Change procedure is a formal process for reviewing and controlling changes that may affect safety, quality, the environment, compliance, or operations.

It helps an organization answer five key questions:

• What is changing?
• Why is the change needed?
• What could go wrong?
• Who must review and approve it?
• How will the team confirm that the change works?

For example, a factory may plan to replace a machine with a newer model. Before installation, the team should check equipment compatibility, guarding, electrical risks, operating instructions, maintenance needs, and staff training.

Similarly, a construction company may change a work method. The team should review the risk assessment, required permits, equipment, and worker instructions before starting the revised task.

The MOC procedure creates a clear record of these decisions. However, it does not replace technical reviews, legal approvals, permit-to-work systems, or other controls that the change may require.

Why Is an MOC Procedure Important?

A planned change can improve performance. An uncontrolled change, however, can introduce risks that the team did not expect.

1. Improve workplace safety

A change may introduce new hazards or weaken an existing control. Therefore, teams should assess risks before they make the change.

2. Protect quality

Changes to materials, equipment, or processes can affect product and service quality. An MOC review helps teams check specifications, testing needs, and quality controls before implementation.

3. Reduce operational disruption

A poorly planned change can cause delays, equipment failures, or confusion. By defining responsibilities and timing, the team can prepare for these issues.

4. Support compliance

Some changes require updated permits, procedures, risk assessments, or regulatory reviews. An MOC process helps teams identify these needs early.

5. Improve communication

People need to know what is changing and how it affects their work. The MOC process helps managers identify affected teams and share the right information.

6. Keep clear records

A documented process shows who requested the change, who reviewed it, what risks were found, and who approved it. These records can support audits and future reviews.

Types of Changes That May Need MOC

The organization should define which changes require formal MOC review. The exact scope depends on its activities, risks, and applicable requirements.

Common examples include:

• Equipment changes: Installing, replacing, or modifying machines, tools, or safety devices.
• Process changes: Altering production steps, operating conditions, or service methods.
• Material changes: Introducing a new chemical, raw material, or product.
• Procedure changes: Revising work instructions, maintenance steps, or operating methods.
• Facility changes: Modifying buildings, storage areas, utilities, or work layouts.
• Personnel changes: Changing key responsibilities or staffing arrangements where these affect risk controls or operational safety.
• Technology changes: Updating software, control systems, or equipment interfaces.
• Supplier or contractor changes: Changing a service provider or work arrangement in a way that affects risk or quality.
• Environmental changes: Modifying waste handling, emissions controls, or pollution prevention measures.
• Temporary changes: Introducing a short-term workaround, bypass, or temporary operating arrangement.

Not every routine adjustment needs the same level of review. However, the organization should define clear criteria so staff know when to raise an MOC request.

What Should a Management of Change Procedure Template Include?

A practical MOC template should guide the team through each stage of the change. The following sections provide a useful starting point.

1. Change Request Details

First, record the basic information about the proposed change.

Include:

• MOC reference number.
• Change title.
• Requestor’s name and department.
• Date of request.
• Site, facility, or work area.
• Equipment, process, or system affected.
• Reason for the change.
• Expected benefits.
• Proposed implementation date.
• Change coordinator or owner.

The description should explain the current situation and the proposed new state. This gives reviewers enough context to assess the request.

2. Change Scope and Classification

Next, define the boundaries of the change.

Check whether it affects:

• Equipment or machinery.
• Production or service processes.
• Work instructions.
• Staff roles and responsibilities.
• Materials or chemicals.
• Software or control systems.
• Buildings or infrastructure.
• Environmental controls.
• Quality requirements.
• Emergency arrangements.
• Contractors or suppliers.

Then, classify the change according to the organization’s procedure. For example, it may be permanent, temporary, or urgent.

A temporary change should have a clear expiry date and a plan to restore the original state or approve a permanent solution. Urgent changes should still receive the level of risk review and authorization required by the organization’s emergency process.

3. Reason for the Change

Explain why the organization needs the change.

Possible reasons include:

• Improving safety.
• Resolving an equipment problem.
• Increasing efficiency.
• Improving product quality.
• Meeting a new requirement.
• Replacing obsolete technology.
• Reducing environmental impact.
• Correcting an audit finding.
• Improving reliability.
• Supporting a new business need.

Also, define the intended result. This gives the team a clear goal against which to measure the change later.

4. Impact Assessment

A change can affect several parts of a business at once. Therefore, reviewers should consider all relevant impacts.

Assess whether the change affects:

• Worker health and safety.
• Environmental performance.
• Product or service quality.
• Equipment reliability.
• Production capacity.
• Maintenance needs.
• Operating costs.
• Customer requirements.
• Legal and regulatory obligations.
• Information security.
• Emergency response.
• Training and staffing.

Record the likely impact, the people responsible for reviewing it, and any additional assessment needed.

5. Risk Assessment and Hazard Identification

Risk assessment is a key part of MOC. Before approval, the team should identify new hazards and consider whether the change could weaken existing controls.

Review relevant risks, including:

• Mechanical and electrical hazards.
• Chemical exposure.
• Fire and explosion.
• Stored energy.
• Environmental spills or releases.
• Human error.
• Ergonomic issues.
• Equipment failure.
• Access and evacuation.
• Changes to emergency response.
• Cybersecurity or control system risks, where relevant.
• Risks during installation, testing, and startup.

Then, assess the risks using the organization’s approved method. Record the controls needed to reduce risk to an acceptable level.

Do not approve a change merely because the team has completed a risk form. Reviewers must confirm that the controls are suitable, practical, and ready before the change goes live.

6. Legal, Regulatory, and Internal Requirements

Some changes may trigger specific legal duties or technical requirements. Therefore, check which rules apply before implementation.

Confirm whether the change requires:

• A permit or regulatory approval.
• Engineering review.
• Updated risk assessments.
• Revised operating procedures.
• Equipment certification or testing.
• Environmental approval.
• Customer approval.
• Updated emergency plans.
• Consultation with workers or their representatives.
• Additional inspections.

Assign each requirement to a responsible person. Also, keep evidence of the review and any required approvals.

7. Reviewers and Approval Responsibilities

An MOC process should make it clear who reviews and approves the change.

Depending on the change, reviewers may include:

• The change requestor.
• The department manager.
• Engineering or maintenance staff.
• Health and safety personnel.
• Environmental specialists.
• Quality assurance staff.
• IT or cybersecurity teams.
• Operations managers.
• HR or training staff.
• Senior management.
• External technical experts, where required.

Each reviewer should assess the part of the change that falls within their expertise.

The procedure should also define approval limits. For instance, a minor process update may need a department manager’s approval, while a high-risk engineering change may require several technical and management approvals.

8. Implementation Plan

After the required reviews and approvals, prepare a plan for putting the change into practice.

Include:

• Tasks and milestones.
• Responsible persons.
• Planned dates.
• Required tools and materials.
• Labour and resource needs.
• Work permits.
• Equipment isolation requirements.
• Temporary safety controls.
• Communication arrangements.
• Testing and inspection steps.
• Contingency plans.
• Conditions that would stop the work.

Where possible, plan the change to limit disruption. However, safety and compliance should take priority over speed.

9. Document and Procedure Updates

A change may make existing documents inaccurate. Therefore, identify which records and instructions need revision.

Check whether the team must update:

• Standard operating procedures.
• Work instructions.
• Risk assessments.
• Maintenance plans.
• Equipment manuals.
• Drawings and diagrams.
• Training materials.
• Inspection checklists.
• Emergency plans.
• Environmental records.
• Quality documents.
• Asset registers.
• Relevant software or system records.

Assign document owners and make sure the approved versions are available before affected staff use the new process.

10. Training and Communication

People need to understand how the change affects their work. Therefore, plan communication and training before implementation.

Check whether:

• All affected employees have been identified.
• Contractors and other relevant parties have been informed.
• New training is required.
• Competence must be reassessed.
• Supervisors understand the new process.
• Emergency responsibilities have changed.
• Training records need updating.
• Employees know where to find the revised documents.

A message or email may inform staff about a change, but it may not be enough for a high-risk task. In those cases, provide suitable training and confirm competence before work begins.

11. Pre-Startup Safety Review

For changes involving equipment, facilities, or higher-risk processes, a pre-startup review may be necessary.

Before the new or modified system starts, verify that:

• Installation matches the approved design.
• Required safety controls are in place.
• Equipment inspections and tests are complete.
• Risk controls have been implemented.
• Operating procedures are approved.
• Maintenance requirements are clear.
• Staff have completed required training.
• Emergency arrangements are ready.
• Outstanding issues have been resolved or formally managed.
• Authorized personnel have approved startup.

The organization should define when this review is mandatory. Do not start affected operations if critical safety or compliance conditions remain unmet.

12. Change Implementation and Monitoring

Once approval and readiness checks are complete, implement the change according to the plan.

During implementation, record:

• Actual start date.
• Tasks completed.
• Deviations from the plan.
• Unexpected hazards or problems.
• Tests and inspections performed.
• Any temporary controls used.
• Relevant approvals and sign-offs.

If the team finds an unexpected risk or the work changes beyond the approved scope, pause as needed and reassess the change before proceeding.

13. Post-Implementation Review

After the change goes live, check whether it achieves the intended result without creating unacceptable new risks.

Review:

• Safety performance.
• Equipment reliability.
• Product or service quality.
• Environmental impact.
• Process performance.
• Staff feedback.
• Unplanned downtime.
• New incidents or near misses.
• Outstanding actions.
• Effectiveness of risk controls.

Compare the actual results with the original goals. If the change does not work as intended, decide whether to adjust it, add controls, or reverse it.

14. MOC Closure and Recordkeeping

Close the MOC only when the organization has completed the required steps.

Confirm that:

• The approved change has been implemented.
• Required documents have been updated.
• Training has been completed.
• Required inspections and tests have passed.
• Open actions have been resolved or formally transferred under an approved process.
• Post-implementation checks are complete.
• Temporary changes have been restored or formally reapproved.
• Final approval has been recorded.
• Supporting records are stored correctly.

Keep the records for the period required by company policy and applicable rules.

Sample Management of Change Checklist

Use these questions as a starting point. Adapt them to the type of change and the organization’s approved MOC process.

Change Request

• Has the change request been recorded?
• Is the reason for the change clear?
• Is the scope defined?
• Have affected systems, equipment, and work areas been identified?
• Has the change been classified as temporary, permanent, or urgent?
• Is a change owner assigned?

Risk and Impact Review

• Have relevant hazards been identified?
• Has a suitable risk assessment been completed?
• Have quality and environmental impacts been reviewed?
• Have legal and regulatory needs been checked?
• Have emergency arrangements been considered?
• Are the required controls defined?

Review and Approval

• Have the right technical and operational reviewers been consulted?
• Have reviewer concerns been addressed?
• Have required approvals been recorded?
• Is the change approved before implementation?
• Are any conditions attached to the approval?

Implementation Readiness

• Is there a clear implementation plan?
• Are resources and responsibilities assigned?
• Have affected workers been informed?
• Has required training been completed?
• Have procedures and records been updated?
• Have required inspections and tests been planned?

Startup and Follow-Up

• Have pre-startup checks been completed where required?
• Are critical controls in place?
• Has authorized personnel approved startup?
• Have unexpected issues been recorded?
• Has a post-implementation review been completed?
• Have temporary changes been closed or extended through formal approval?
• Has the MOC record been finalized?

How to Implement an MOC Procedure Step by Step

A consistent process helps staff understand what to do whenever a change is proposed.

Step 1: Raise the Request

The requestor describes the change, explains why it is needed, and identifies the affected areas.

Step 2: Screen the Change

The coordinator checks whether the request falls within the MOC procedure and identifies the level of review required.

Step 3: Assess Risks and Impacts

Relevant experts review safety, quality, environmental, operational, and compliance impacts. They also define the controls needed before implementation.

Step 4: Obtain Approval

The change goes to the people with the right authority. The team records decisions and resolves concerns before proceeding.

Step 5: Prepare for Implementation

The owner confirms resources, work plans, training, communication, and document updates. The team also prepares any required testing and startup checks.

Step 6: Implement the Approved Change

Staff follow the approved plan. If the scope changes or a new hazard appears, they reassess the situation and obtain further approval where required.

Step 7: Verify the Result

The team checks whether the change works as intended and whether the controls remain effective.

Step 8: Close the MOC

The owner confirms that required tasks and records are complete. The organization then closes the change or continues to manage any formally approved outstanding work.

How eAuditor Audits & Inspections Handles Management of Change

eAuditor Audits & Inspections can help organizations digitize MOC checklists and organize the records linked to each change. A digital process can make it easier to capture information, review risks, and track follow-up work.

1. Create a Custom MOC Checklist

Teams can use a relevant template as a starting point and adapt it to their own process. The checklist can cover the change description, affected areas, risk assessment, reviewer input, approvals, training, and final review.

For example, a manufacturing business may add questions about machine guarding and maintenance. Meanwhile, a warehouse may focus on traffic routes, racking changes, and safe access.

2. Record Change Details and Risks

A digital form can help the requestor record the purpose, scope, and expected outcome of the change. Auditors and reviewers can then document identified risks, required controls, and supporting information.

This gives the team a structured record to review before it approves the work.

3. Support Review and Approval Tracking

MOC workflows often involve several departments. eAuditor can support the organization of review records and approval-related steps, depending on the configuration and features available to the organization.

The team should define who has authority to approve each change. A submitted form alone should never be treated as approval.

4. Document Evidence

Teams can record comments and attach relevant supporting information where the configured form supports those fields. This may include risk assessments, inspection records, updated procedures, or test results.

As a result, reviewers have a clearer record of the information used to make decisions.

5. Track Corrective Actions

If the review identifies a gap, the team can record an action, assign responsibility, and set a target date. For example, an owner may need to update a procedure or arrange additional training before startup.

Follow-up tracking helps prevent important tasks from being overlooked.

6. Keep Records Organized

Digital records help teams retain change requests, assessment findings, and follow-up details in a structured format. This can make it easier to find information during internal audits or future reviews.

The organization should still apply its own access, retention, and record-control rules.

7. Review Change Performance

After implementation, teams can record the results of inspections and post-change reviews. They can then use those findings to identify recurring issues and improve the MOC process.

However, digital tools do not replace competent technical review, required approvals, or safe implementation. Organizations must still follow their own procedures and applicable legal requirements.

Benefits of Using a Digital MOC Procedure

A well-designed digital MOC process can help an organization:

• Standardize how staff raise change requests.
• Identify risks before implementation.
• Clarify review and approval responsibilities.
• Keep change records in one organized process.
• Track training and document updates.
• Monitor outstanding actions.
• Support pre-startup checks.
• Review whether changes meet their goals.
• Identify repeated problems.
• Improve accountability across departments.

The results depend on the quality of the procedure and how consistently teams follow it. Therefore, review the process regularly and update it when the organization’s needs change.

Common MOC Mistakes to Avoid

Making changes before approval

Starting work before the required review can expose people and operations to uncontrolled risks. Define clear approval points and communicate them to all affected teams.

Ignoring temporary changes

Temporary workarounds can remain in place longer than planned. Set expiry dates, define monitoring requirements, and require formal review before extending or making a change permanent.

Overlooking people and training

A technical change may also affect roles, skills, and daily tasks. Identify affected staff and complete the required training before they use the new process.

Failing to update documents

Old instructions can cause mistakes after a change. Assign document owners and verify that current versions are available before startup.

Using vague risk assessments

A statement such as “risks checked” does not show what the team reviewed. Record the hazards, controls, responsible persons, and remaining risks clearly.

Skipping the post-change review

A change may pass installation checks but still perform poorly in daily use. Set a review date and check whether the change achieved its intended result.

Closing the MOC too early

Do not close a change just because the equipment is running or the new process has started. Confirm that required training, records, testing, and follow-up checks are complete.

Best Practices for an Effective MOC Procedure

Follow these practices to make change management more reliable:

• Define which changes require MOC.
• Keep the request process clear and easy to use.
• Assign one accountable change owner.
• Match the level of review to the risk.
• Involve qualified people from relevant departments.
• Assess safety, quality, environmental, and operational impacts.
• Record decisions and approval conditions.
• Communicate changes to affected workers and contractors.
• Update procedures and training before implementation.
• Use pre-startup checks when required.
• Set clear expiry dates for temporary changes.
• Verify effectiveness after implementation.
• Review overdue actions and recurring issues.
• Keep records according to company and legal requirements.

Most importantly, make sure the MOC procedure supports safe decisions rather than becoming a paperwork exercise. Every review should help the organization understand the change and control its risks.

Frequently Asked Questions

1. What is a Management of Change (MOC) Procedure Template?

It is a structured document that guides a team through change requests, impact reviews, risk assessments, approvals, implementation, and follow-up. It helps ensure that changes receive the right review before they take effect.

2. Which changes require an MOC review?

Changes to equipment, processes, materials, facilities, procedures, or responsibilities may require MOC when they affect safety, quality, environmental performance, compliance, or operations. The organization should define clear screening criteria.

3. Who should approve a management of change request?

Approval should come from people with the authority and expertise required for the change. Depending on its impact, reviewers may include operations, engineering, safety, environmental, quality, IT, or senior management personnel.

4. What is the difference between MOC and risk assessment?

Risk assessment identifies hazards, evaluates risks, and defines controls. MOC is the wider process that manages the proposed change, including the risk assessment, review, approval, implementation, communication, and follow-up.

5. How should a temporary change be managed?

Document the reason, scope, risks, controls, owner, and expiry date. Monitor the change while it remains in place, then restore the original condition or obtain formal approval for a permanent solution.

6. Is MOC required for every small change?

Not necessarily. Organizations should define which changes fall within their MOC process. However, they should not exclude a change simply because it appears small if it could affect safety, quality, compliance, or critical controls.

7. What is a pre-startup safety review?

It is a check performed before certain new or modified equipment, facilities, or processes begin operation. It confirms that required installation checks, safety controls, procedures, and training are in place.

8. How does eAuditor Audits & Inspections help with MOC?

eAuditor can support digital MOC checklists, structured risk and review records, evidence capture, and corrective action tracking. Teams can configure the process to suit their requirements and approval rules.

9. What records should an MOC process keep?

Records may include the request, reason, scope, risk assessment, reviewer comments, approvals, implementation plan, training evidence, updated documents, test results, and post-implementation review.

10. When can an MOC request be closed?

Close it when the required work, approvals, training, documentation, inspections, and follow-up checks are complete. The team should also confirm that the change meets its intended purpose and that any temporary change has been resolved or formally extended.

Final Thoughts

A Management of Change Procedure Template helps an organization control change from the first request to final review. It gives teams a clear way to assess risks, involve the right people, approve work, and check the result.

With eAuditor Audits & Inspections, organizations can organize digital MOC checklists, record supporting evidence, and track actions. By combining a clear procedure with competent reviews and effective follow-up, teams can make changes with greater control and confidence.