ISO 14001:2026 Clause 6.3 Planning of Changes: A Working Procedure
Clause 6.3 of ISO 14001:2026 is one of only two genuinely new requirements in the 4th edition, and it has no equivalent in ISO 14001:2015. The requirement itself is short: when you determine the need for a change that affects, or can affect, your environmental management system (EMS), that change must be carried out in a planned manner and managed so the organization still achieves the intended outcomes of its EMS. In plain terms, ISO has written a management-of-change requirement into the standard. You can no longer let a new line, a new supplier, or a reorganization quietly reshape your EMS and discover the environmental consequences after the fact.
In my consulting work, this is the clause most teams underestimate, because it reads like a single sentence. The certification body will not treat it as one. They will look for a process: a way to recognize that a change is coming, a way to evaluate it before it lands, and records that show you did. This article turns 6.3 into a working procedure. I cover the verbatim requirement broken down, the triggers that should set the process off, a change-evaluation form you can lift straight into your system, the four clauses 6.3 connects to, and the distinction between a planned change (6.3), an emergency (8.2), and an unforeseen change (handled under 8.1). If you already run ISO 9001, you can extend your existing change clause rather than build from zero. For the full picture of the 2026 edition, see our ISO 14001:2026 requirements explained guide.
What Clause 6.3 actually requires
The clause text is two sentences. The organization determines the need for changes that affect, or can affect, the EMS; those changes shall be carried out in a planned manner; and the changes shall be managed so the organization can still achieve the intended outcomes of its EMS. Two notes follow. The first says the need for a change can arise from internal or external sources. The second reminds you that managing change already appears in several other clauses, so 6.3 is not an island. That is the whole requirement. Everything else is how you operationalize it.
Three words carry the weight. “Determines” means you need a way to notice that a change is happening, ideally before it is live. “Planned manner” means an ad-hoc decision in a corridor does not satisfy the clause; there has to be a deliberate, repeatable way of handling it. “Intended outcomes” ties the change back to the purpose of the EMS, which the standard defines as enhancing environmental performance, meeting compliance obligations, and achieving environmental objectives. So the test for any change is simple to state and harder to pass: after this change, can we still hit those three outcomes, and have we managed the change so we do?
Annex A of the 2026 edition is explicit that the point of planning changes is to make sure intended beneficial effects are achieved and that changes with unintended consequences are mitigated or minimized. The annex is informative, not auditable in itself, but it tells you exactly how the committee expects the clause to be read. Where most articles get this wrong, they treat 6.3 as a documentation exercise. It is a control: evaluate before, manage during, verify after.
What triggers a planned change
The most common failure I see is not a bad form, it is the change that never reached the form. So the first design question is: what events should fire your management-of-change process? The 2026 annex gives a usable list of circumstances that can impact environmental performance, covering both temporary and permanent changes. The table below restates that list as practical triggers, with an environmental example for each so the people raising changes can recognize them.
| Trigger | Typical environmental example |
|---|---|
| New or changed products, services, processes, operations, equipment or facilities | A new production line, a plant expansion, a switch to a different solvent, a new coating booth |
| Changes to compliance obligations | A revised air permit limit, a new state reporting rule, a customer environmental clause added to a contract |
| New knowledge or information about aspects, impacts or risks and opportunities | Monitoring reveals a discharge is higher than assumed, or a material is reclassified as hazardous |
| Developments in knowledge and technology | A cleaner abatement technology becomes available, or a process can be electrified |
| Changes to technical specifications of materials or process inputs | A reformulated raw material, a substituted chemical, a different fuel or feedstock |
| Changes in business assets due to mergers, acquisitions, joint ventures or divestitures | Acquiring a site with its own aspects and permits, or divesting a regulated operation |
| Changes in staff or external providers, including contractors | A reorganization that moves EMS responsibilities, or a switch to a new waste hauler or supplier |
| Business disruption | Supply chain issues, labour disputes, natural disasters, regime change, political unrest or war |
Two practical points. First, the list mixes changes you initiate with changes that happen to you. A merger and a new permit limit both belong in the process even though one is a strategic decision and the other is imposed. Second, the cleanest way to make 6.3 work is to hook it onto decisions that already happen, capital approval, supplier onboarding, engineering change requests, so the environmental evaluation rides along instead of becoming a separate bureaucracy nobody remembers to start.
A change-evaluation form you can lift
Clause 6.3 does not prescribe a form. It does require that changes be carried out in a planned manner and managed, and the practical way to evidence that is a short evaluation record completed before the change goes live and reviewed after. The 2026 edition does not dictate fields, so the template below is a generic structure, not a fixed requirement. It pulls together the questions an auditor will expect you to have answered: why the change, what it could do to the environment and to your EMS, what it needs, who owns it, and what you will keep as proof. Adapt the depth to the size of the change. A like-for-like pump swap needs three lines; a new plant needs all of it.
| Field | What to capture |
|---|---|
| Change reference and date | A unique ID, the date raised, and whether the change is temporary or permanent |
| Purpose of the change | What is changing and why; the intended benefit and the trigger it came from |
| Effect on aspects and impacts | New or changed environmental aspects and impacts the change introduces, assessed against your significance criteria (6.1.2) |
| Potential consequences | Intended beneficial effects, plus any unintended consequences with adverse effects, and how they will be mitigated or minimized |
| Compliance and other obligations | New permits, reporting duties or customer requirements the change creates or alters (6.1.3) |
| Effect on intended outcomes | Whether the change still lets you enhance performance, meet obligations and achieve objectives, with controls if it threatens any |
| Resources required | Budget, equipment, competence and training needed to implement and control the change safely |
| Responsibilities and authority | Who owns the change, who must be consulted or informed, and who has authority to approve it before it proceeds |
| Documents and communication to update | Aspects register, procedures, operating criteria, emergency plans, and who needs to be told internally (7.4.2) |
| Approval and post-implementation review | Approver sign-off and date, then a check after go-live that the change worked as planned and the outcomes held |
The form is your evidence. Keep the completed records as documented information, because at the certification audit “we plan our changes” is a claim, and a folder of dated, signed evaluations is the proof. The post-implementation review line matters more than people expect. It is where you close the loop and catch the change that looked clean on paper but shifted an impact once it was running. To see where this form sits in a full rollout, our ISO 14001:2026 implementation guide sets out the wider project plan.
Where 6.3 connects to the rest of your EMS
The second note under 6.3 says managing change is addressed in various requirements across the standard, and the annex lists them. That is the committee telling you not to build 6.3 as a standalone silo. It is the spine that runs through four clauses you already operate. If your change process does not reach into these, it is not really controlling the change.
| Clause | How 6.3 connects to it |
|---|---|
| 6.1.2 Environmental aspects | 6.1.2 itself says that when determining aspects you take into account change, including planned or new developments and new or modified activities, products and services, with an explicit cross-reference to 6.3. So every planned change should re-run the aspects and significance assessment, and update the register. |
| 8.1 Operational planning and control | 8.1 requires you to control planned changes and to review the consequences of unintended changes, taking action to mitigate adverse effects. This is where the change is actually built into operating criteria and controls once 6.3 has evaluated it. |
| 9.2.2 Internal audit programme | The audit programme must take into account changes affecting the organization, so significant changes should pull forward or shape your internal audit. Audit the change process and audit the areas the change touched. |
| 10.2 Nonconformity and corrective action | When a change goes wrong and produces a nonconformity, 10.2 is the route: react and correct, evaluate the cause, act, review effectiveness, and make changes to the EMS if necessary. A pattern of changes that misfire is itself a signal that your 6.3 process needs work. |
Read together, the flow is clean: 6.3 plans and evaluates the change, 6.1.2 re-checks the aspects, 8.1 controls it in operation, 9.2.2 audits it, and 10.2 catches it if it fails. The standard also threads change through internal communication (7.4.2), control of documented information (7.5.3), and the management review, which considers any need for changes to the EMS. You do not need a new clause for each of these. You need one change process that touches them all.
Planned change, emergency, and unforeseen change
Let me be direct about a distinction teams blur. Clause 6.3 is about changes you choose to make and can plan for. It is not your emergency clause, and it is not the same as something going wrong unexpectedly in operation. Mixing these up leads to either an overloaded change form or a gap an auditor will find. Here is how the three sit apart in the 2026 standard.
Planned change (6.3)
A change you have determined the need for and can carry out deliberately: a new line, a new supplier, a restructure, a revised permit you must adapt to. You evaluate it before it happens and manage it so the intended outcomes hold. This is the change-evaluation form above.
Emergency (8.2)
A potential emergency situation, a spill, a fire, an uncontrolled release, is not a planned change. It is handled under 8.2 emergency preparedness and response, which builds on the potential emergency situations you determine in 6.1.2. Emergencies have their own response planning, testing and post-incident review. Do not route a spill through your change form.
Unforeseen change (8.1)
Then there is the change that was not planned but is not an emergency either: a process drifts, an input quietly changes, a supplier alters something without telling you. The standard handles this inside 8.1, which requires you to review the consequences of unintended changes and take action to mitigate adverse effects. So 6.3 plans the changes you see coming, and 8.1 catches the ones you did not. Together they close the loop.
If you already hold ISO 9001, you have a head start. ISO 9001 has carried a planning-of-changes requirement for years, and the harmonized structure means the wording will feel familiar. You can extend that existing change process to cover environmental aspects, impacts and compliance obligations rather than stand up a separate one. One management-of-change procedure serving both systems is usually cleaner than two.
Frequently asked questions
Making 6.3 work in practice
Of all the changes in the 2026 edition, 6.3 is the one I would not leave until the transition deadline. ISO 14001:2026 was published on 15 April 2026, certification bodies stop issuing new 2015 certificates on 31 October 2027, and all 2015 certificates lapse by 30 April 2029. A management-of-change process is not something you can retrofit the week before your transition audit, because the evidence is the trail of change records you accumulate over months. Start it now, even a simple version, and let it fill up.
If I had to reduce 6.3 to one habit, it would be this: before any change reshapes how you operate, ask what it does to your aspects, your obligations and your intended outcomes, write the answer down, and check it again after the change is live. That is the whole clause, working. You can read the official requirement on the ISO 14001 page at iso.org, and if you want the procedure and change-evaluation form already built and ready to adapt, our ISO 14001:2026 Documentation Kit includes them alongside the rest of the EMS document set.
