Skip to content
English
  • There are no suggestions because the search field is empty.

MOC and RIK

What is MOC/RIK?

MOC (Management of Change) is a formal process for documenting, reviewing, and approving changes to equipment, processes, or procedures before they are implemented. It ensures that changes are properly evaluated, approved by the right people, and confirmed once complete.

RIK (Replacement in Kind) is a simplified process for documenting an equipment replacement with an exact equivalent part — where no true "change" is being made, only a like-for-like replacement that still requires documentation.

Key point: MOC and RIK both require initiating a form and moving it through an approval workflow — MOC involves a full multi-stage review process, while RIK is streamlined and requires only MOC Coordinator sign-off.

Why MOC/RIK Matters

MOC/RIK is essential because:

  • Change control - Ensures that equipment or process changes are evaluated for safety and operational risk before being implemented
  • Accountability - Every stage of a change — from initiation through approval, implementation, and confirmation — is documented with the user who acted and when
  • Visibility - The MOC/RIK Dashboard gives supervisors and coordinators a live view of all active change requests across the organization
  • Compliance - Formal change management documentation supports regulatory and internal audit requirements
  • Risk management - Requiring approvals before changes are made reduces the risk of unplanned or unevaluated changes affecting operations
MOC vs. RIK — When to Use Which
MOC RIK
Use when Making a change to equipment, a process, or a procedure Replacing a piece of equipment with an exact equivalent part
Review process Full multi-stage review (Coordinator → Approvers → Change Approvers → Change Confirmers) Streamlined — MOC Coordinator approval only
Typical examples Changing a chemical treatment program, modifying a process setpoint, replacing equipment with a different model Replacing a failed pump with an identical pump, swapping a like-for-like valve

If you are unsure whether a change qualifies as a RIK or requires a full MOC, consult your MOC Coordinator.

The MOC Workflow

A MOC request moves through the following states:

Draft → Initiated → Pending Approval → Pending Change Approval → Pending Change → Completed
↓ (any stage)
Rejected
↓ (any stage, manually)
Canceled

Stage-by-Stage Breakdown

1. Draft The form has been saved but not yet submitted. Only the initiator can see it. Use Draft to work on the form before it is formally submitted.

2. Initiated The form has been submitted. The assigned MOC Coordinators receive an email notification and must review the request. The coordinator can approve it (moving it forward), reject it, or request a revision.

Email sent to: MOC Coordinators

3. Pending Approval The MOC Coordinator has approved. Notifiers (optional — informed but not required to act) and Approvers (required — must approve before progressing) receive email notifications and are now active. All Approvers must approve before the request moves forward.

Email sent to: Notifiers and Approvers

4. Pending Change Approval All Approvers have approved. The assigned Change Approvers receive an email notification and must review and approve the actual planned change.

Email sent to: Change Approvers

5. Pending Change The Change Approver has approved. The assigned Change Confirmers receive an email notification. The change can now be physically implemented. Once complete, the Change Confirmer confirms that the work was done.

Email sent to: Change Confirmers

6. Completed The Change Confirmer has confirmed the change is complete. The MOC request is closed as a completed record. Note: No email notifications are sent when a MOC is completed — check the MOC/RIK Dashboard to see completed requests.

Email sent to: No one

Rejected Any reviewer at any stage can reject the request. A rejection resets all reviewers for that stage and sends an email notification to the initiator. The initiator may need to revise and resubmit depending on the reason for rejection.

Email sent to: Initiator (the person who submitted the MOC)

Canceled Any active request can be manually canceled at any stage. Canceled requests are moved to closed records.

The RIK Workflow

RIK uses a simplified workflow:

Draft → Initiated → Completed
↓
Rejected / Canceled

Only the MOC Coordinator needs to approve a RIK. There are no Approvers, Change Approvers, or Change Confirmers. Once the Coordinator approves, the request moves directly to Completed.

Reviewer Roles
Role Required? Responsibility
MOC Coordinator Required First reviewer — evaluates and approves or rejects the initial request. Required for both MOC and RIK
Notifier Optional Informed of the change — receives notifications but does not need to approve
Approver Required (MOC only) Must formally approve the change before it proceeds to the change stage
Change Approver Required (MOC only) Approves that the planned change is ready to be implemented
Change Confirmer Required (MOC only) Confirms that the change has been physically completed

Reviewer roles are configured by administrators. The specific users assigned to each role for a given MOC request are set when the request is created or by the MOC Coordinator.

Email Notifications

EZ Ops automatically sends email notifications to keep reviewers informed as MOC/RIK requests progress through the workflow. Understanding when notifications are sent helps you know when to check your email versus when to monitor the MOC/RIK Dashboard.

Who Gets Notified and When

When a MOC/RIK is Submitted (Initiated):

  • ✅ MOC Coordinators receive notification
  • ❌ Initiator does NOT receive confirmation

When MOC Coordinator Approves → Pending Approval:

  • ✅ Notifiers receive notification (if configured)
  • ✅ Approvers receive notification
  • ❌ Initiator does NOT receive notification

When All Approvers Approve → Pending Change Approval:

  • ✅ Change Approvers receive notification
  • ❌ Initiator does NOT receive notification

When Change Approver Approves → Pending Change:

  • ✅ Change Confirmers receive notification
  • ❌ Initiator does NOT receive notification

When Change Confirmer Approves → Completed:

  • ❌ NO ONE receives notification (including the initiator and MOC Coordinator)

When Any Reviewer Rejects at Any Stage:

  • ✅ Initiator receives notification
  • All reviewers for that stage are reset to "Not Started"

When Anyone Adds a Comment:

  • ✅ Initiator receives notification
  • ✅ All MOC Coordinators receive notification
  • ✅ All Notifiers receive notification
  • ✅ All Approvers receive notification

What's Included in Notification Emails

Each notification email contains:

  • MOC/RIK title
  • Name of the person who created it
  • Date created
  • Location
  • Current workflow status
  • Link to the MOC/RIK Dashboard
  • Comment details (if the notification is for a new comment)

Important: What Initiators Should Know

As the person who submits a MOC/RIK, you will ONLY receive email notifications if:

  • Someone rejects your request
  • Someone adds a comment

You will NOT receive email notifications when:

  • Your MOC/RIK is approved and moves forward through the workflow
  • Your MOC/RIK reaches "Completed" status

This means: If you want to track the progress of your MOC/RIK as it moves through approvals, you must check the MOC/RIK Dashboard regularly. Silence does not mean your request is stuck — it often means it's being approved and progressing normally.

Dashboard Monitoring Recommendation

Because notifications are only sent to the next reviewer group (not to initiators or previous reviewers), the MOC/RIK Dashboard is the primary tool for monitoring request status:

  • Initiators: Check the dashboard periodically to see if your MOC has progressed or been completed
  • MOC Coordinators: Check the dashboard to see completed MOCs, as you won't receive completion notifications
  • All users: Use the dashboard's filter and search features to track specific requests
How to Create a MOC or RIK Request
  1. Navigate to the MOC/RIK section - Access MOC/RIK from the navigation menu
  2. Select the form type - Choose either MOC (Management of Change) or RIK (Replacement in Kind) based on what you are documenting
  3. Fill out the form - Complete all required fields describing:
    • What is being changed or replaced
    • The reason for the change
    • The location and equipment involved
    • Any relevant supporting details, attachments, or photos
  4. Save as Draft (optional) - Save the form as a Draft if you need to return to it before submitting
  5. Submit (Initiate) - Submit the form to move it to the Initiated state. The assigned MOC Coordinator is notified immediately
How to Review a MOC/RIK Request (Reviewers)

If you are assigned as a reviewer (Coordinator, Approver, Change Approver, Change Confirmer, or Notifier):

  1. Check the MOC/RIK Dashboard - Open the dashboard online to see all active requests that require your attention
  2. Open the request - Click on the MOC/RIK request assigned to you for review
  3. Review the details - Read the change description, supporting information, and any previous reviewer comments
  4. Take action - Depending on your role, you can:
    • Approve - Move the request to the next stage
    • Reject - Return the request; all reviewers for that stage are reset and the initiator is notified
    • Request Revision - Flag that changes are needed before you can approve
  5. Add comments - Record your reasoning, especially for rejections or revision requests
The MOC/RIK Dashboard

The MOC/RIK Dashboard is an online tool for supervisors, coordinators, and administrators to manage all active change requests:

  • View all active requests (Initiated, Pending Approval, Pending Change Approval, Pending Change, Rejected) and closed requests (Completed, Canceled)
  • Filter and search by status, location, initiator, and date
  • Review and approve pending items assigned to you
  • Track where each request is in the workflow and who needs to take action next
Common Issues

"My MOC request is stuck — I don't know who needs to approve it"

  • Check the MOC/RIK Dashboard — the current stage and assigned reviewers are visible
  • Contact your MOC Coordinator, who has visibility into all active requests

"I submitted a MOC/RIK but haven't heard back — how do I know if it's approved?"

  • Initiators do NOT receive email notifications when their MOC is approved and moves forward
  • Check the MOC/RIK Dashboard to see the current status
  • If you see your MOC has moved to "Pending Approval" or beyond, it means the MOC Coordinator approved it
  • Silence is often good news — rejections trigger immediate email notifications

"How do I know when my MOC is completed?"

  • No email notification is sent when MOCs reach "Completed" status
  • Check the MOC/RIK Dashboard and filter by "Completed" to see finished requests
  • The dashboard shows the completion date and who completed the final step

"Why didn't I get notified that my MOC was approved?"

  • This is the current system behavior — email notifications are sent to the next group of reviewers, not to the initiator
  • You will only receive notifications if your MOC is rejected or if someone adds a comment
  • Use the MOC/RIK Dashboard to track progress through approvals

"I submitted a RIK but it isn't moving forward"

  • The MOC Coordinator needs to approve RIK requests — check with your coordinator to confirm they have received the notification
  • Check the MOC/RIK Dashboard to see if it's still in "Initiated" status or has been rejected

"I need to cancel a request that is no longer needed"

  • Any active request can be canceled manually — open the request and select the Cancel option
  • Canceled requests move to closed records and remain visible in history

"I'm not sure if my change needs an MOC or qualifies as a RIK"

  • When in doubt, create an MOC — a RIK is only appropriate for exact like-for-like replacements with no operational difference
  • Consult your MOC Coordinator if you are uncertain
Tips & Recommendations
  • Initiate before you make the change, not after - The workflow exists to evaluate a change in advance. A retrospective MOC records the work but skips the point of it.
  • Be specific in the description - Name the equipment, the location, the nature of the change and the reason. Vague submissions are the main cause of delay in review.
  • Use RIK for like-for-like replacements - It is the faster path, and it keeps a straightforward swap out of full-MOC overhead.
  • Use a comment rather than waiting - A comment notifies every active reviewer and coordinator, so it is the way to ask a question or chase a stalled request without stepping outside the record.
  • Watch the dashboard, because success is silent - No notification is sent when a request is approved or completed. Initiators should track progress on the MOC/RIK Dashboard, and coordinators should consider telling initiators directly when a request closes.

If you review or coordinate

  • Coordinators are the first gate - Everything behind an unreviewed request waits, so a delay at this stage holds up the whole workflow.
  • Act on email notifications quickly - Reviewers do get notified, and the request sits untouched until someone responds.
  • Confirm as soon as the work is physically done - The record stays open until Change Confirmers complete their step.

Remember: Nothing is deleted and nothing is anonymous. Every stage is logged with the user and a timestamp, and a rejected request stays in history to be revised and resubmitted rather than disappearing.