Management of change

The MOC module puts every proposed change through a structured impact review before it's approved. Temporary changes carry an expiry date so they aren't quietly left in place, and each change has a human-readable number like MOC-0001.

Request a change

1. Go to Management of change and use the Request a change form.
2. Choose the site and change type (process, equipment, procedure, personnel, chemical, or organizational), give it a title, and describe the change and its justification.
3. Record who requested it. If it's temporary, tick Temporary change and set the expiry date — a temporary change won't save without one.
4. Click Request change. The system opens a change like MOC-0001.

Review, approve, implement

1. Open the change to work its impact review — tick each area you've assessed (process safety, environmental, equipment integrity, procedures, training, pre-startup review) and add notes. Required areas are marked with an asterisk, and Approve unlocks only once every required area is assessed.
2. Reject is available while the change is under review — the reason you type is recorded on the change.
3. After approval, Mark implemented, then Close when the change is fully in place; your closure notes are recorded too.
4. While a change is open, use Raise CAPA to track any follow-up work it generates — the change then links to that CAPA.

Link a change to a PSM covered process (1910.119(l))

For a facility under Process Safety Management, a change to a covered process should be governed through MOC as element (l). Start these changes from the process's Management of Change row on the PSM page — + New change opens this form already linked to that covered process (a banner confirms it, and you can Unlink). Linked changes show the process in the register and the MOC log CSV, and the process's PSM element then reflects the live change activity. The Process column shows which covered process each change belongs to (or "—" for an unlinked change).

What happens automatically

• The list flags overdue temporary changes in red; filter by status to see just those.
• A temporary change past its expiry that's still in place escalates to the safety team by notification — naming the PSM covered process when the change is linked to one — so restore the original state or extend it through MOC. Set who's emailed for that queue under notification routing.

Tip: keep temporary changes honest — set a realistic expiry so overdue ones surface before they become permanent by accident.

Related

• Process safety (PSM) — Management of change is a core PSM element
• CAPA (corrective & preventive actions) — Change gaps drive CAPA follow-up to closure
• Risk assessments — Rate the change's hazards during impact review
• Controlled documents — Update controlled procedures affected by the change