ISO 9001 clause 6.3: plan QMS changes without losing control

What clause 6.3 requires in practice

Clause 6.3 applies when the organisation decides that the QMS itself needs to change, for example a new process, a restructured function or a different way of controlling work. Such changes must be carried out in a planned manner, not improvised.

The clause lists what to think about before and during the change. The first is the purpose of the change and its possible consequences. The second is the potential effect on the integrity of the QMS. Others are the availability of resources and information, how responsibilities and authorities are assigned or reassigned, and communication of the change. The last two are how the effectiveness of the change will be monitored and evaluated, and how its results will be reviewed.

Not every adjustment needs a project: the clause concerns changes to the QMS that the organisation has decided to make. The outputs are a considered change plan, a handover of responsibilities, clear communication and a follow-up judgement on whether the change achieved its purpose without damaging the system.

Define what is changing and why

Start with the intended result and the boundaries of the change. A restructure, new business system, service transfer or revised management process may affect several parts of the QMS. Explain which processes, responsibilities and information are involved, and consider potential consequences beyond the immediate project.

Maintaining QMS integrity means preserving a coherent system that continues to meet its requirements. A change to one function should not leave essential handovers, evidence or authority arrangements disconnected. The appropriate review depends on the significance and complexity of the proposed change.

Check readiness at the interfaces

Consider the availability of resources and information before implementation. People may need competence, access to current instructions or time to operate the revised arrangement. Responsibilities and authorities may need to be reassigned, especially when work moves between teams or locations.

Communication should reach the people whose decisions or work are affected. Announcing that a project has finished is different from explaining a changed approval route or a new responsibility. Consider relevant external communication as well, where the change affects customers or providers and their requirements.

Why planned change matters to the business

Unplanned change is a common root of quality failures. A reorganisation moves an approval duty and nobody notices; a new system replaces a manual check that was quietly preventing errors; staff learn of a new method after customers have already felt it. Planned change protects service levels during transition, keeps accountability intact, and helps people accept new ways of working because they understand why. It also protects the value of past investment in the system, since each uncontrolled change slowly erodes it. For auditors, a sound approach to change shows that management keeps the system coherent as the business moves.

How to implement clause 6.3

Use a proportionate route: a small change deserves a short conversation, a large one a documented plan. One way Sterling's teams do this is a brief change note, shared with the people affected, answering the clause's considerations in a few lines, with more detail only for larger changes. The clause requires planned change; it does not require a particular form or software, and a proportionate record that the people involved actually read is better than a heavy template.

1. Define what triggers the arrangement, for example a new process, a structural change or a new tool for controlling work.
2. State the purpose of the change and think through its likely consequences.
3. Check what the change could do to the integrity of the QMS, such as lost controls or broken interfaces.
4. Confirm the resources and information needed, and decide who takes over or gives up responsibilities and authorities.
5. Plan communication to everyone affected before the change takes effect.
6. Decide how effectiveness will be monitored and evaluated, and who reviews the final result.
7. Close the change with a review and feed lessons into later planning.

Evidence an auditor expects for clause 6.3

The auditor will follow a recent change from idea to review. Typical evidence includes: The auditor commonly picks a recent change, such as a revised process or a reassigned responsibility, and traces whether it was planned before it happened. Staff interviews help to confirm that communication reached the people who needed it, and that the review took place after the change settled.

• records showing the purpose, consequences and system impact were considered
• evidence that resources and responsibilities were confirmed before implementation
• communications received by the affected staff
• observations of how the changed process operates in practice
• records of the follow-up review and its conclusions

Common nonconformities with clause 6.3

Findings usually arise where change happens informally. Auditors tend to raise these findings by comparing records of change with what the process owners say really happened, and gaps show quickly where a change was made informally. Repeated findings often come from organisations that treat the clause as relevant only to major projects.

• A process or structure was changed and no one considered the effect on the QMS.
• Responsibilities moved but the new owners were never told.
• Staff learned of a change after it started affecting their work.
• The change had no way of being evaluated, so success was assumed.
• Resources the change needed were not available, leaving controls half-implemented.

Illustrative BPO example: transferring a service

Illustrative manufacturing example: a new planning system

A hypothetical manufacturer replaces a production-planning application. The new system improves scheduling visibility, but a review finds that customer-specific inspection conditions are not included in the planned data transfer. If overlooked, production could receive a feasible schedule without the full acceptance requirements.

The team clarifies how those conditions will be transferred, checked and made available to relevant staff. It assigns authority for resolving migration exceptions and communicates temporary arrangements. Evaluation after implementation considers whether actual orders carry the required information and whether scheduling decisions preserve the necessary checks. This is an illustration of QMS change planning, not a technical data-migration specification.

Decide how effectiveness will be assessed

Choose monitoring and evaluation that relate to the purpose and possible consequences of the change. If the purpose is clearer responsibility, examine whether decisions reach the appropriate role. If the purpose is more dependable information, check whether users obtain the right information when needed.

Review the results, including adverse effects and unresolved assumptions. A change can deliver one benefit while creating another weakness. The organisation should be prepared to adjust its approach where evidence shows the intended result has not been achieved. ISO 9001 does not prescribe one universal review period or a formal change-board structure.

Distinguish QMS changes from related operational changes

Clause 6.3 concerns changes to the quality management system. Other clauses address specific changes, including customer requirements, design and production or service provision. The same project may involve several of those provisions. Use the relevant requirements together without assuming one general change form automatically covers every decision.

Useful evidence can include the rationale, affected processes, resource and authority decisions, communications and evaluation results. A dedicated change register is optional. Common failures include unclear ownership, training delivered too late, information left in obsolete systems and review focused only on budget or launch date rather than quality outcomes.