Change control

Change control covers ISO 9001 Clause 6.3 (planning of changes) and 8.5.6 (control of changes): carrying out changes in a planned way and reviewing them, so nothing changes without review.

Request a change

In Change control, raise a change request with a title and an optional code. Set the type of change (process, product, document, supplier, system, or other), a risk level (low, medium, or high), who requested it, and a target date. Record the reason for the change and what is changing.

Work the lifecycle

Each change request moves through a controlled lifecycle:

Requested → Assessing → Approved / Rejected → Implementing → Verified → Closed

The Assessing stage is your impact assessment; Approved or Rejected is the review decision; and Verified confirms the change did what it was meant to after implementation. You can advance changes one at a time, set status in bulk across several, and save filtered views.

What the dashboard watches

The Quality dashboard surfaces Awaiting approval (requests still in Requested or Assessing) and High-risk open changes, the two the person running change control checks first.

Tip

Set the risk level honestly at request time. High-risk changes are pulled out on the dashboard so they get the review attention Clause 8.5.6 expects, rather than slipping through as routine.

Next steps

• Documented information: pair document changes with your controlled documents.
• Evidence: attach the approval and verification records for each change.