ISO 9001:2026 Change Planning Record: What to Capture Before You Implement a QMS Change

A quality management system change should be planned before it is put into practice. That sounds obvious, but many organisations record only the decision and the new procedure. A useful change planning record makes the reasoning visible: why the change is needed, what it may affect, who needs to know, how it will be introduced and how the organisation will judge whether it worked.

For the current ISO 9001:2026 operating amendment, the confirmed change-planning area is clause 6.3. The practical emphasis is on planning the information and communications needed for change, monitoring progress and reviewing effectiveness, including the results of the change. This is a focused improvement to the way a QMS change is controlled; it is not a reason to replace every document in an established system. Use the ISO 9001:2026 transition readiness tool to consider the wider confirmed change areas, then keep the change record specific to the change you are actually making.

Begin with the change and its reason

The first section should identify the proposed change in plain language. A short title, request number, date raised and owner make the record traceable. Then describe what is changing and why. The reason might be a customer requirement, an audit finding, a recurring error, a new service, a process improvement or a change in equipment. Avoid vague entries such as “update the system”. Name the process, document, service or activity affected.

The ISO 9001 pack includes a Change Management Procedure and a Change Request Form that can provide a starting structure. For a broader set of practical starting documents, see the free ISO templates. The pack follows ISO 9001:2015 including Amendment 1:2024; it does not claim to follow ISO 9001:2026. Tailor the fields to your real approval routes and operating arrangements rather than treating the blank form as evidence.

A good reason statement allows a later reviewer to answer three questions:

• What problem or opportunity prompted the proposal?
• What outcome is the organisation seeking?
• What would happen if the change were not made?

This gives the change an objective without turning the record into a business case. If the change is connected to a customer, statutory, regulatory or contractual requirement, record that connection and point to the relevant source in the controlled evidence system.

Record the impact before approval

The next part is an impact assessment. List the processes, documents, roles, sites, suppliers, equipment, software and records that could be affected. Consider the effect on quality, delivery, safety where relevant, compliance obligations, resources and training. Do not limit the assessment to the department proposing the change: an alteration to purchasing, for example, may affect incoming checks, production planning, customer commitments and performance measures.

Include the interested parties that may need to be consulted or informed. That may include customers, employees, external providers, regulators or owners, depending on the change. The assessment does not need to predict every possible consequence. It should show that the organisation considered the plausible effects and decided what level of control is proportionate.

Separate the assessment from the approval decision. A manager signing a request does not, by itself, show that the impacts were understood. Record who completed the assessment, when it was reviewed and any assumptions that still need testing. Where the proposal creates a significant uncertainty, make the uncertainty an action rather than hiding it in general wording.

Turn the decision into an implementation plan

Once the change is approved, list the actions needed to introduce it. Each action should have an owner, due date and status. Typical actions include revising a controlled procedure, configuring software, notifying a provider, briefing staff, completing training, testing an output, withdrawing an obsolete version and checking that the new method is available at the point of use.

The plan should also identify dependencies. If a revised inspection method cannot be used until equipment is available, or a new customer communication depends on contract approval, record that relationship. This makes delays visible and gives management a basis for rescheduling or escalating the work.

Use controlled document and record references rather than attaching a collection of uncontrolled copies to the request. The ISO 9001:2026 document control review explains why the status, approval and availability of changed information matter when reviewing a QMS.

Plan communication, not just training

Training is only one possible response. Some changes require a short briefing, an updated work instruction at the workstation, a supplier notification, a customer message or a revised escalation route. Record who needs to receive the information, what they need to understand, when communication will happen and how completion will be evidenced.

Communication should match the risk and the audience. A person who performs a changed activity may need practical instruction and an opportunity to demonstrate competence. A customer may need confirmation of a changed specification or service arrangement. An external provider may need revised information about acceptance, delivery or verification. Do not claim that a message was effective merely because it was sent; record the relevant acknowledgement, briefing attendance, test result or other evidence.

Define how effectiveness will be checked

A change is not complete when the last implementation action is ticked. Define the check that will show whether the intended outcome was achieved. This could be a sample of completed records, a process measure, customer feedback, an internal observation, a first-article review, an audit check or a comparison of results before and after implementation. State who will review the result and when.

The check should also look for unintended effects. A faster process that creates more errors has not delivered the intended improvement. If the result is inconclusive, record the follow-up action, responsible person and new review date. If the change is ineffective, the organisation may need to correct the implementation, revise the plan or withdraw the change under control.

Keep the evidence proportionate. A low-risk wording correction may need approval and a document check. A change affecting a critical service process may need staged testing, wider communication and a period of monitoring. The important point is that the record shows why the chosen check was suitable.

Close the record with a clear trail

At closure, confirm the approved change, implementation status, communication evidence and effectiveness result. Link the final record to the revised controlled documents and any associated training, monitoring, audit or customer records. Note unresolved issues instead of closing them silently. A change owner or quality lead should sign off the conclusion, with the date and any required follow-up.

For a wider baseline check, use the ISO 9001 gap analysis tool to identify evidence that may be missing from the wider QMS. You can also compare the approach with ISO 9001:2026 internal audit objectives and ISO 9001:2026 opportunity register guidance. These are related applications, not substitutes for the change record itself. The ISO 9001:2026 hub brings the confirmed topics together for further reading.

A practical change planning record is therefore more than an approval form. It connects the reason for change to its impacts, actions, communications and evidence of results. That trail helps process owners implement changes consistently and gives internal auditors and management a clear basis for review, while allowing an established QMS to improve without unnecessary rewriting.