Management of Change

Management of Change (MoC) is a register of planned changes: process changes, document changes, new equipment, reorganizations, system changes. Every change gets a number (MOC-0001, MOC-0002, and so on) and must be risk-assessed before anyone can approve it. The page lives at /changes and is called Management of Change. It supports ISO 9001 clause 6.3 and ISO 45001 clause 8.1.3.

The lifecycle is:

Proposed -> Impact assessment -> Approved -> Implementing -> Implemented -> Verified
                              -> Rejected
Cancelled is possible at any point before implementation starts

Before you start

• Module is off by default. An org admin must turn on Change (MoC) under Settings > Modules (in the Quality management group). Until then the /changes route is blocked.
• Any signed-in member of the organization can raise, assess, and approve changes.
• If you want to record which processes and documents a change touches, create them first in Processes and Documents. The assessment dialog only shows pickers for processes and documents that exist.

Raise a change request

1. Open Management of Change and click New Change Request.
2. Fill the dialog:
   • Title (required): what is changing, in one line.
   • Description: scope of the change and what it touches.
   • Reason for change: why the change is needed.
   • Type: Process, Document, Equipment, Organizational, System, or Other.
   • Priority: Low, Medium (default), High, or Urgent.
   • Owner: the person driving the change, or Unassigned.
   • Target date: when the change should be done.
3. Click Create request.

The change is created in status Proposed with the next MOC number for your organization. Use the pencil icon on any row to edit these fields later.

Assess the change

Approval is locked until an assessment exists. This is the core MoC rule.

1. On a Proposed change, click Start assessment. Status moves to Impact assessment.
2. Click Record assessment.
3. In the Impact assessment dialog:
   • Pick Likelihood: Rare, Unlikely, Possible, Likely, or Almost certain (scored 1 to 5).
   • Pick Impact: Insignificant, Minor, Moderate, Major, or Catastrophic (scored 1 to 5).
   • The dialog shows the Risk score as likelihood times impact, out of 25. A score of 15 or more is flagged high risk, 8 or more medium risk. This is the same 1 to 5 scale the risk register uses.
   • Write the Impact summary: what the change affects and how the risk is controlled.
   • Tick the Affected processes and Affected documents checklists.
4. Click Save assessment. The button stays disabled until both Likelihood and Impact are set.

You can reopen the dialog later with Update assessment.

Approve or reject

1. While the change is in Impact assessment, the Approve / Reject button is disabled and shows a lock icon until the assessment is recorded. The row also carries a gray tag reading "Assess risk to unlock approval".
2. Once assessed, click Approve / Reject.
3. The decision dialog shows the assessed risk (for example "Likely x Major = 20 / 25"). Add Decision notes (conditions, rationale, or constraints).
4. Click Approve or Reject.

The decision stamps who decided and when. Rejected is a final state. If someone tries to force an approval without an assessment, the app refuses with a message asking for the impact assessment first.

Implement and verify

1. On an Approved change, click Start implementation. Status moves to Implementing.
2. When the work is done, click Mark implemented. Status moves to Implemented and the date is stamped.
3. Have someone confirm the change worked as intended, then click Verify. Status moves to Verified, the final state, with its own date stamp.

Cancel a change

Before implementation starts (statuses Proposed, Impact assessment, or Approved), each row has a Cancel button. Clicking it opens a confirmation dialog warning that the change will be closed without being implemented and cannot be undone. Choose Cancel change to confirm or Keep change to back out. Once implementation has started, cancellation is no longer offered.

Track the register

• The stats bar counts Open (proposed, in assessment, approved, or implementing), Awaiting approval (in impact assessment), Implementing, and Overdue.
• A change is overdue when its target date is in the past and it is not yet implemented, verified, cancelled, or rejected. Overdue rows show a red target-date tag.
• Filter the list by Status and Type using the dropdowns above the list. The stats always cover the whole register, not the filtered view.

Try it

• Enable Change (MoC) in Settings > Modules. Expected: Management of Change appears in the side nav and /changes loads.
• Create a change "Replace label printer on Line 2" with type Equipment and priority High. Expected: the row appears as MOC-0001 (or the next number) with a Proposed tag.
• Click Start assessment. Expected: status tag becomes Impact assessment; the row shows Record assessment and a locked Approve / Reject button plus the tag "Assess risk to unlock approval".
• Click Approve / Reject before assessing. Expected: the button is disabled and nothing happens.
• Record an assessment with Likelihood Likely and Impact Major. Expected: the dialog shows "Risk score: 20 / 25" flagged as high risk; after saving, the row shows a red Risk 20 tag.
• Click Approve / Reject, add a note, click Approve. Expected: status becomes Approved and a "Decision:" tag names you.
• Walk the rest: Start implementation, Mark implemented, Verify. Expected: status ends at Verified with Implemented and Verified date tags.
• Create a second change with a target date in the past. Expected: the Overdue stat increases and the target tag is red.
• Click Cancel on that second change and confirm. Expected: status becomes Cancelled and it drops out of the Open and Overdue counts.

If something goes wrong

• The page is missing or blocked. The Change (MoC) module is off by default. Ask an org admin to enable it in Settings > Modules.
• Approve / Reject stays locked. The change has no recorded assessment. Both Likelihood and Impact must be saved. The gray tag on the row reminds you.
• Save assessment is disabled. You picked only one of the two scales. Set both Likelihood and Impact.
• Create request does nothing. Title is required.
• No Cancel button on a row. The change is already implementing or later. Cancellation is only allowed before implementation starts.
• An error says the transition is not allowed. The lifecycle is strict. For example, you cannot verify a change that was never marked implemented. Use the buttons offered on the row; they only show valid moves.
• Affected processes or documents lists are missing from the assessment dialog. They only render when the org has processes or documents. Create them in Processes and Documents.