MOC (Management of Change)

MOC is the formal gate that ensures operational changes are assessed, approved, and implemented without introducing hidden risk.

How MOC works in practice

A governance sequence that keeps changes controlled from proposal to closure.

1

Initiate change request

Capture the proposed change, rationale, scope, and expected operational impact.

2

Classify risk level

Screen the change and decide whether fast-track or full cross-functional review is required.

3

Run impact assessment

Assess process safety, engineering, maintenance, operations, quality, and compliance impacts.

4

Approve with conditions

Authorize only with clear controls, owners, and acceptance criteria.

5

Implement and train

Execute the change under controlled conditions and brief affected personnel.

6

Verify and close

Confirm outcomes, update documentation, and close with lessons learned.

Where MOC has the most impact

These are the areas where mature teams typically see measurable gains.

01

For HSSE Teams

MOC reduces incident risk from unmanaged modifications by forcing structured hazard review before implementation.

02

For IT & CIOs

Digital MOC workflows improve traceability, approval discipline, and cross-team accountability.

Deep Dive

MOC explained for operations, HSSE, and leadership teams

A practical guide to change governance, control ownership, and closure quality.

Why MOC matters

Most major operational failures are linked to change that was incompletely assessed, poorly communicated, or implemented without control verification.

MOC creates a formal decision trail so risk owners can evaluate consequences before the change goes live.

What strong MOC includes

  • Clear scope and boundaries for the proposed change.
  • Cross-functional impact assessment and explicit risk acceptance.
  • Implementation plan with owners, contingency, and training requirements.
  • Post-change verification and documentation updates before closure.

Typical failure points

  • Implementing before approvals are complete.
  • Treating high-impact changes as routine replacements.
  • Closing changes without verifying field performance and updated drawings/procedures.

Operating principle

No change is complete until controls are verified in operation and the organization is updated to run the new state safely.

Template

Example MOC lifecycle record

This table converts the markdown phase matrix into a structured, auditable format.

Pump replacement MOC example

MOC phaseDescriptionTimeline
InitiationOperations submits change request to replace a cavitating pump with a compatible upgraded model.Week 0
ScreeningCoordinator classifies change as moderate risk and routes to full MOC review.Week 1
Risk assessmentEngineering, maintenance, operations, quality, and safety review technical and operational impacts.Weeks 1-2
ApprovalRelevant authorities sign with conditions and required controls.Week 2
Implementation planDefine isolation, removal, installation, commissioning, and fallback steps.Week 2
TrainingBrief operators and maintainers on startup, shutdown, and new performance baseline.Week 3
ImplementationExecute replacement and commissioning under approved control plan.Week 3
ClosureVerify performance, update documents, and record lessons learned.Week 4

Frequently asked questions

All changes affecting safety, operations, or quality require MOC. This includes "small" changes if they affect a safety control or critical procedure. When in doubt, initiate a MOC. It is better to over-assess than to under-assess and miss a hazard.

Operationalize MOC at workforce scale

Dockt helps teams move from manual credential tracking to proactive, audit-ready competence management.