MOC CONTROL WORKBOOK Workflow help

How the six-gate MOC workflow works

Progress is controlled by evidence and sign-off. If a gate is not passed, the change stops and returns for clarification, further assessment or completion of actions.

Workflow and sign-off gates

GATE 1INITIATE / RAISE

Define the change

  • Record the present position, proposed change and reason.
  • Identify scope, boundaries, constraints and affected systems.
  • List the people to consult and information to gather.

Evidence: clear proposal, owner, MOC reference and supporting information.

GATE CHECK Is the proposal complete enough to screen?

Change owner or sponsor confirms the record is clear and owned.

GATE 2SCREEN / CLASSIFY

Choose the correct MOC route

  • Confirm the change is not routine replacement or normal maintenance.
  • Identify temporary or permanent status and relevant change categories.
  • Set the assessment level, competent reviewers and required disciplines.

Evidence: documented classification, assessment level and review plan.

GATE CHECK Is the route and assessment level correct?

MOC coordinator or screening reviewer confirms the classification.

GATE 3REVIEW / ASSESS

Understand and control the risk

  • Use a multidisciplinary team with relevant operating and technical experience.
  • Record change effects, existing safeguards and initial risk rating.
  • Define additional safeguards, owners, residual risk and ALARP justification.

Evidence: completed risk worksheet, attendees, actions and residual-risk decision.

GATE CHECK Are risks understood and reduced so far as reasonably practicable?

Assessment leader and review team confirm the assessment and actions.

GATE 4APPROVE / AUTHORISE

Authorise the planned change

  • Review the proposal, assessment, residual risks and dependencies.
  • Confirm conditions, hold points, resources and implementation window.
  • Reject, return for rework or approve within delegated authority.

Evidence: named approver, decision, date and recorded approval conditions.

FORMAL SIGN-OFF Approved to proceed to implementation?

Designated approver accepts the plan and residual risk. Approval is not permission to bypass Gate 5 readiness checks.

GATE 5IMPLEMENT / VERIFY

Complete actions and verify readiness

  • Complete engineering, procedure, training, communication and document actions.
  • Verify safeguards, inspections, testing, permits and pre-start requirements.
  • Release the change in a controlled manner and monitor initial operation.

Evidence: action evidence, readiness review, test results, briefings and release record.

RELEASE SIGN-OFF Are all pre-start conditions complete and evidenced?

Implementation owner and readiness reviewer authorise release into use.

GATE 6CAPTURE + CLOSE

Embed the change and close the record

  • Update controlled drawings, procedures, registers and asset information.
  • Complete or formally transfer remaining actions with owners and dates.
  • Review performance, capture learning and confirm temporary-change reversion where applicable.

Evidence: updated records, post-implementation review, closed actions and lessons learned.

CLOSURE SIGN-OFF Is the change embedded, effective and ready to close?

Closure approver accepts the evidence and closes the MOC record.

MOC CLOSED

Operational documents and responsibilities now reflect the approved change.

Gate not passed — stop and rework

Record the reason and actions. Return to the relevant earlier gate, update the proposal or assessment, then obtain the required sign-off again before progressing.

Key controls throughout the workflow

Control scope changes

If the design, material, operating envelope or implementation method changes, return to screening and risk review.

Keep evidence with the record

Approvals should point to completed assessments, calculations, drawings, certificates, training and test results.

Track approval conditions

A conditional approval is an action, not a waiver. Close or verify each condition before the relevant release point.

Manage temporary changes

Record expiry, monitoring and reversion arrangements. Extension requires review and renewed authorisation.

Sign-off guide

GateDecisionTypical accountable roleMinimum evidence
1 — InitiateReady to screenChange owner / sponsorClear scope, reason, owner and supporting information
2 — ScreenRoute and assessment level confirmedMOC coordinator / screening reviewerClassification, disciplines and assessment plan
3 — ReviewRisk assessment acceptedAssessment leader and review teamHazards, safeguards, risk ratings, actions and ALARP basis
4 — ApproveAuthorised to implementDesignated approverSigned decision, conditions, resources and timing
5 — ImplementReady for release into useImplementation owner / readiness reviewerCompleted actions, tests, training and pre-start checks
6 — CloseChange embedded and record closedClosure approverUpdated documents, review results, closed/transferred actions and learning

Local authority applies: map these generic role descriptions to the named roles and delegated authorities in your site MOC procedure.