Learning Hub

ISO 14001:2026 vs 2015: what changed

The 2026 revision sharpens climate, biodiversity, value-chain and data lineage requirements. Here's what existing certified companies need to update.

Dcycle Team Dcycle Team 5 min

ISO 14001:2026, published 15 April 2026, keeps the familiar 10-clause structure but tightens several areas — most importantly climate, value-chain and audit-trail rigour. Existing certified companies have approximately three years to transition (expected deadline 2029).

What changed

Clause 4.1 — Context

Organisations must now explicitly assess climate change, biodiversity and natural capital risks when documenting context. Generic statements about “external issues” no longer pass — auditors expect specific risk identification tied to your sites and value chain.

Clause 4.2 — Interested parties

Stakeholder engagement must now align with disclosure frameworks like CSRD and EU Taxonomy. The expectation: explicit traceability between interested parties’ needs and your sustainability disclosure obligations.

Clause 5.1 — Leadership

Top-management commitment becomes more demanding. Generic policy statements are not enough — auditors expect documented integration into business strategy, capital allocation, and risk management. Board minutes and investment criteria become audit evidence.

This reflects the broader trend: sustainability moves from compliance silo into corporate governance.

Clause 6.1.2 — Environmental aspects

The aspect register shifts from “lifecycle consideration” (2015) to “operational and auditable lifecycle assessment” (2026). You must document upstream and downstream impacts, not just on-site operations. The register also needs to feed into the same data layer used for Scope 3 emissions reporting.

Clause 8.1 — Operational control

Supplier and value-chain engagement becomes mandatory operational control, not an optional consideration. Expect to evidence:

  • Supplier environmental criteria in procurement.
  • Ongoing monitoring of supplier performance.
  • Documented escalation when criteria are not met.

Clause 8.2 — Emergency preparedness

Emergency preparedness now explicitly covers climate-related physical risks — flooding, water stress, extreme heat, wildfire. Previous editions didn’t require this.

What hasn’t changed

  • The 10-clause PDCA structure.
  • The fundamental EMS concept.
  • The certification process (gap → implement → internal audit → external audit → surveillance).
  • The 3-year certification cycle with annual surveillance.

Most existing documentation remains usable — but it needs additions, not replacement.

Transition plan for currently certified companies

Within 90 days

  • Revise the context analysis to address climate and biodiversity risks. Use double-materiality-style thinking (similar to CSRD) to identify what matters and to whom.
  • Map your environmental aspects with full lifecycle scope; tie each to Scope 3 categories where applicable.

Within 6 months

  • Update operational controls to reflect lifecycle aspects and value-chain due diligence.
  • Add climate physical risks to emergency preparedness procedures.
  • Document leadership integration — board minutes, capex policy, risk register entries.

Before recertification (year 3)

  • Audit evidence chains — every external claim must trace back to EMS data with documented provenance. A spreadsheet-based KPI dashboard is unlikely to pass a 2026 audit if it can’t show data lineage from source to report.
  • Refresh internal audit programs to cover the new clause requirements.
  • Run a transition gap analysis at least 6 months before the recertification audit.

How it relates to CSRD and CDP

ISO 14001:2026 is the closest the EMS standard has ever been to disclosure frameworks like CSRD:

  • Double-materiality thinking is now expected in the context analysis.
  • Value-chain and Scope 3 considerations align with ESRS E1.
  • Audit evidence rigour overlaps with assured CSRD reporting.

Companies certified to ISO 14001 are better positioned for CSRD; the work increasingly overlaps. Build the data layer once.


Was this helpful?