IMScollect
ISO 9001ISO 14001ISO 27001

Clause 6.3: Planning changes

Title in the standard: “Planning of changes”

New site, new software, new organisation: how do you make sure your management system does not lose its footing along the way? Clause 6.3 in ISO 9001, 14001 and 27001 from the audit’s point of view.

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Updated 15 November 2026

What it is about

No management system stays as it is. A site is added, two departments are merged, a process goes to a service provider, a new ERP system or a cloud service replaces the old tools. Clause 6.3 requires such changes to the management system to happen in a planned way and not in passing.

Planned means that beforehand it has been clarified what the change is for and what it may trigger, whether the system will still work as a whole afterwards, whether the necessary resources are available and who is responsible for what, especially when responsibilities shift. ISO 9001 names these points explicitly, while ISO 27001 requires more briefly that changes are carried out in a planned manner. It has proved worthwhile to check after implementation whether the change works as intended.

Changes to the system need to be distinguished from changes in operations. How a revised drawing, a new formulation or a software update is controlled is covered by the clauses on operation and, in ISO 27001, by a control of its own in Annex A. Clause 6.3 works one level higher: with anything that changes the structure, processes, responsibilities or boundaries of the management system. A new site is the classic example; it almost always affects the scope as well.

What the auditor checks

  • “What has changed in your management system since the last audit?”

    The way in. New sites, a reorganisation, new top management, outsourced processes, new software. The auditor compares the answer with what can be seen in operations and with what is in the documents.

  • “How did you plan the move to the new hall?”

    Whether there was planning before implementation that considered purpose, consequences, resources and responsibilities. Planning that was only written down afterwards can usually be recognised by its date.

  • “Who approved this change?”

    Decision and accountability. For major changes, the auditor expects top management to have been involved and to have released the resources.

  • “Which documents, roles and assessments did you have to adapt afterwards?”

    The integrity of the system: process descriptions, organisation chart, appointed officers, risk assessment, environmental aspects, Statement of Applicability. If the old responsibilities are still in the documents after a reorganisation, planning was missing at exactly this point.

  • “How did you notice that the change is working?”

    Whether anyone looked after implementation: indicators before and after, an internal audit of the new area, feedback from employees.

  • “Does your certification body know about the new site?”

    Significant changes such as a new site or a changed scope usually have to be notified to the certification body; this is governed by the certification contract. The question also shows whether the change was recognised as a change to the system.

Which evidence convinces

  • An overview of planned and implemented changes

    With trigger, date, status and responsible person. It shows that changes are recognised as such and not simply implemented.

  • The planning for each change

    Purpose and possible consequences, effect on the system, resources, responsibilities, actions with deadlines. A short form is enough if it was completed before implementation.

  • The approval

    Who decided and when, before implementation. This shows that the change was released deliberately.

  • Updated documents and assessments

    New versions of processes, roles, risk assessment, environmental aspects or Statement of Applicability, dated after the change. They show that the system has kept pace.

  • A look at the effect

    A note, a comparison of indicators or an audit report after the change. It closes the chain and is the part most often left undone in everyday work.

Typical nonconformities

  1. Change without planning

    The new site has been operating for months, no planning can be seen, processes, roles and risks were not considered. If a significant change was implemented entirely without planning and the system is not working in the new area, that is a major nonconformity. If individual points are missing from an otherwise planned change, it is a minor nonconformity.

  2. Documents lag behind

    The organisation chart and process descriptions show the old structure, appointed officers have left and not been replaced.

  3. Responsibilities unclear

    After two departments were merged, nobody feels responsible any more for calibration, waste disposal or granting access rights.

  4. Planning only after the event

    The planning record is dated after implementation. It then documents what happened, not what was thought through beforehand.

  5. Scope not updated

    A site has been added or a process outsourced, but the scope still describes the old situation.

  6. New software without a look at security

    A cloud service was introduced without a risk assessment, without checking the provider and without updating the Statement of Applicability. Under ISO 27001, this is a common finding on changes.

Differences by standard

ISO 9001ISO 9001

In ISO 9001, clause 6.3 has existed since the 2015 edition and names four points to consider for a change: purpose and possible consequences, the integrity of the system, the available resources and the responsibilities. Changes in operations are covered in several places in clause 8: planned changes in 8.1, changed requirements in 8.2.4, design and development changes in 8.3.6 and changes in production in 8.5.6.

ISO 14001ISO 14001

ISO 14001:2015 has no clause 6.3 of its own. Planned changes are controlled there under operational planning and control (8.1), and planned or new developments have to be taken into account for the environmental aspects (6.1.2). According to ISO and DIN, the 2026 edition gives the planning of changes a clause 6.3 of its own. Anyone making the transition should check whether their route for changes also covers environmental aspects, compliance obligations and emergency preparedness. More on this in the article on the 2026 edition linked below.

ISO 27001ISO/IEC 27001

In ISO/IEC 27001, clause 6.3 was added with the 2022 edition and is brief: changes to the ISMS are carried out in a planned manner. When significant changes occur, the risk assessment also has to be repeated (clause 8.2). Technical changes to systems and applications are covered by a separate change management control in Annex A.

How IMScollect covers it

In IMScollect you keep changes to the management system in a list of their own. Every change needs, when it is created, a title, a reason, a responsible person, a planned date and the standards concerned. In the request you describe the purpose and possible consequences, the effect on the integrity of the management system, the availability of resources and the responsibilities, and you select the companies and departments affected or the whole organisation.

The change passes through three stages: planned, approved, implemented. Whoever approved it stays recorded on the change; a rejection needs a reason and sends the request back for revision. Actions with an owner and a deadline only become tasks after approval, so that nobody works on a change that was never released. Every decision is recorded in the history.

Try it yourself, no call needed.Prefer a walkthrough? Book a guided demo →

Frequently asked questions

What counts as a change to the management system?▾

Anything that changes the structure, processes, responsibilities or boundaries of the system: a new or closed site, a reorganisation, a change in top management or among appointed officers, an outsourced process, new core software, a changed scope.

Does every small change need a request of its own?▾

No. Planning should match the scale of the change. For small changes, a review step in the existing project or approval process is often enough; a request of its own pays off for changes that affect several areas, roles or standards.

Does the certification body have to be informed about changes?▾

About significant changes, usually yes, for example a new site, a changed scope or a fundamentally new organisation. Exactly what has to be notified is set out in the contract with your certification body.

What is the difference between clause 6.3 and change management in Annex A of ISO 27001?▾

Clause 6.3 concerns changes to the management system itself, such as to the organisation, roles and processes. The control in Annex A concerns changes to systems, applications and facilities that process information, that is, the technical change process. The two interlock when a technical change affects the system.

Further reading and viewing

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Philipp builds IMScollect. TÜV-certified auditor with a background in governance, risk and compliance, more than 200 audits conducted and supported.

This page explains in our own words and does not replace the text of the standard. You can obtain the standards from ISO(opens in a new window) or from your national standards body. Clause numbers and titles follow ISO 9001:2026, ISO 14001:2026 and ISO/IEC 27001:2022.