AUTHORITATIVE STATUS PAGE 

ISO Standards and Revisions: Current Status

Published Editions, Drafts and Transition Information Kept Distinct

ISO standards and revisions must be reported by exact edition, date and development stage. This page records the current position of major management system standards and explains how organisations can prepare without treating a draft, amendment or expected publication as the current requirements edition. 

Status checked: 28 August 2026 

ISO standards and regulations authority page

THE ESSENTIAL READING RULE 

Publication Status Comes Before Commentary

A revision announcement, committee decision, DIS, FDIS and publication are not the same event. The authoritative position starts with the ISO project page and published edition. Certification-transition details then come from the relevant accreditation and certification system. 

 

Use the full reference

State the complete designation and edition, including ISO/IEC where applicable and any amendment relevant to the published standard. 

 

State the development stage

Describe DIS, FDIS and under-publication projects accurately instead of presenting all future  work as an issued standard.

 

Date the status

A standards authority page becomes misleading when current claims have no clear date against which they were checked. 

 

Link to primary sources

Use ISO, the applicable accreditation body and the organisation’s certification body for authoritative status and transition information. 

CURRENT POSITION 

Major Management System Standards at 28 August 2026

This table distinguishes the current published requirement from projects and certification transitions. It is a monitoring summary, not a substitute for obtaining the relevant standard or professional advice. 

 

Standard Current position on 28 August 2026 Revision or transition position Authoritative source
ISO 9001 ISO 9001:2015 with Amendment 1:2024 remains the published requirements edition. Edition 6 is under publication and expected in September 2026. It has not yet replaced the 2015 edition. ISO 9001 project page
ISO 14001 ISO 14001:2026 is the published fourth edition. ISO 14001:2015 and its 2024 amendment are withdrawn as ISO publications. Certified organisations must follow the transition arrangements applying to their certification. UKAS states a certified-customer transition deadline of 30 April 2029. ISO 14001:2026
UKAS transition bulletin
ISO 45001 ISO 45001:2018 with Amendment 1:2024 remains the published requirements edition. A revised edition is at Draft International Standard stage. A DIS does not replace the current published standard. ISO 45001 lifecycle
ISO/IEC 27001 ISO/IEC 27001:2022 with Amendment 1:2024 is the current published requirements edition. No later requirements edition is shown as published by ISO. Use the full ISO/IEC designation and edition. ISO/IEC 27001:2022
ISO 22301 ISO 22301:2019 with Amendment 1:2024 is the current published requirements edition. ISO records the standard as due to be revised. No replacement requirements edition is yet published. ISO 22301:2019
ISO/IEC 42001 ISO/IEC 42001:2023 is the current published AI management system requirements standard. Supporting standards now include ISO/IEC 42005:2025 for AI impact assessment guidance and ISO/IEC 42006:2025 for certification bodies. ISO/IEC 42001:2023

THE TWO IMMEDIATE REVISION PRIORITIES 

ISO 9001 Is Approaching Publication. ISO 14001 Has Already Changed.

The difference matters operationally. Quality teams can prepare against a nearly published project while retaining ISO 9001:2015 as the current basis. Environmental teams must now work from ISO 14001:2026 and manage the applicable certification transition. 

 

ISO 9001: Edition 6 under publication

ISO shows the sixth edition in final production with a September 2026 date and states that it will replace ISO 9001:2015. Until publication, gap work should remain labelled as preparation against the forthcoming edition—not conformity to a published ISO 9001:2026. 

 

ISO 14001:2026 published

ISO published the fourth edition in April 2026 and lists the 2015 edition as withdrawn. UKAS states that accredited certification bodies have until 30 April 2027 to transition and certified customers until 30 April 2029. Organisations should confirm their audit plan with their certification body. 

ISO standard revision lifecycle placeholder

STANDARD DEVELOPMENT LIFECYCLE 

Understand the Stage Before Taking Action

ISO records project stages so users can distinguish a review, draft, approval and published standard. That status should control the language used in policies, plans, websites and audit preparation. 

  • Review may confirm the existing standard without a new edition
  • Draft content can change before publication
  • DIS and FDIS provide progressively firmer preparation information
  • Under publication means approval is complete but final production remains
  • Only the published edition replaces the earlier ISO publication
  • Certification transition begins under separate accredited arrangements

Preparation can start before publication. Claims of conformity must still identify the actual published standard used. 

DEVELOPMENT STAGES IN PLAIN LANGUAGE 

From Review to Published International Standard

 

Stage What it means How organisations should treat it
Systematic review ISO members review whether an existing standard should be confirmed, revised or withdrawn. Monitor the outcome. Do not assume a new edition will follow until a revision project is approved.
Working or committee draft Technical content is being developed and debated within the responsible committee. Use for awareness only. Content may change and is not the published conformity basis.
DIS A Draft International Standard is circulated for member enquiry and voting. Begin structured impact analysis, but keep decisions traceable to draft status.
FDIS A Final Draft International Standard is submitted for final approval. Prepare more detailed plans, while recognising that the published edition remains authoritative.
Under publication Approval is complete and ISO is carrying out final production steps. Prepare for release; do not describe it as published until ISO changes the status.
Published The dated edition is issued as an International Standard. Use the published text. Certified organisations must then follow formal transition information from relevant accreditation and certification bodies.

WHY STANDARDS CHANGE 

Revision Maintains Relevance—it Does Not Automatically Rewrite Everything

ISO standards are reviewed to determine whether they remain suitable. A revision may clarify language, align the harmonised structure, address emerging issues or change discipline-specific requirements. 

 

Changed context

Technology, supply chains, environmental conditions, workforce expectations and organisational risk can alter what users need from a standard. 

 

User experience

Ambiguous wording, inconsistent interpretation or difficult integration can justify clarification and structural improvement. 

 

Harmonised structure

Management system standards are aligned where appropriate to improve compatibility and integrated use. 

 

Discipline-specific change

Each committee may strengthen or refine the requirements and guidance particular to quality, environment, safety or another subject. 

HARMONISED STRUCTURE 

Common Architecture Supports Integration—It Does Not Merge the Standards

ISO’s Annex SL harmonised approach gives management system standards a common structure and shared core terms where appropriate. This makes integrated management systems easier to design and use. 

 

Shared structure

Users can recognise common subjects such as context, leadership, planning, support, operation, evaluation and improvement. 

  

Shared organisational controls

One process or control may genuinely support several management-system requirements and evidence needs. 

 

Separate specialist scope

Quality, environment, safety and information security retain different purpose, technical content and competent judgement. 

 

Separate assurance conclusions

An integrated workflow does not mean that success in one standard proves conformity or effectiveness in another. 

THE 2024 CLIMATE-ACTION AMENDMENTS 

An Amendment Is Part of the Current Published Position

In February 2024, ISO published climate-action amendments across many management system standards. They require organisations to consider whether climate change is relevant to their context and recognise that interested parties may have climate-related requirements. 

 

Do not ignore the amendment

Where the underlying edition remains current, the applicable amendment forms part of the published standards position used for implementation and audit. 

 

Do not manufacture relevance

The organisation must determine relevance within its own purpose, context, risks and interested-party requirements rather than add generic climate wording. 

 

Do not confuse amendment and revision

A later full edition may incorporate or develop the topic further. Until then, the amendment applies to the identified published edition. 

OTHER STANDARDS TO MONITOR 

Current Editions and Projects Must Be Tracked Separately

The revision activity around ISO 9001 and ISO 14001 should not obscure the position of other management systems used by the organisation. 

 

ISO 45001

The 2018 requirements edition and Amendment 1:2024 remain current. ISO has published a DIS for the next edition, so organisations can monitor emerging content without changing their certification reference prematurely. 

 

ISO/IEC 27001

The 2022 requirements edition and Amendment 1:2024 remain current. Information-security teams should use the full ISO/IEC designation and distinguish requirements from supporting 27000-series guidance. 

 

ISO 22301

The 2019 requirements edition and Amendment 1:2024 remain current. ISO records the standard as due for revision, but no replacement requirements edition is published. 

 

ISO/IEC 42001

The 2023 AI management system requirements edition remains current. ISO/IEC 42005 and ISO/IEC 42006 add separate impact-assessment and certification-body material; they do not replace ISO/IEC 42001. 

WHO HAS AUTHORITY FOR WHAT? 

Standard Publication and Certification Transition Are Different Responsibilities

Authority is distributed. Confusion arises when a consultant’s forecast, certification-body plan or accreditation deadline is described as though ISO itself published it. 

 

ISO

Develops and publishes the International Standard, its amendments and official project lifecycle status. 

 

Global ACI

From 1 January 2026, provides the international cooperation framework succeeding IAF and ILAC. Some legacy documents remain temporarily applicable under its resolutions. 

 

Accreditation body

Bodies such as UKAS accredit certification bodies and publish applicable technical or transition requirements within their system. 

 

Certification body

Plans and performs the organisation’s transition audit, updates certification and explains the timetable applying to that client. 

Consultants, software providers and training organisations may support preparation. They do not publish ISO standards, accredit certification bodies or issue an accredited management-system certificate unless separately authorised to perform that role. 

PREPARING THROUGH OPERATION 

Define, Communicate, Operate and Assure the Revision

A revision should not become a document-editing exercise. The organisation must understand changed expectations, alter the controls and workflows affected, prepare people and verify that the revised system works. 

01 

Define

Obtain the official text, establish scope, interpret changes, map affected requirements and approve the necessary control response. 

02 

Communicate

Explain what has changed, why it matters, which roles are affected and what preparation or competence is required. 

03 

Operate

Implement revised processes, responsibilities, documents, training, risk treatment, monitoring and retained evidence. 

04 

Assure

Audit the revised operation, test evidence, review exceptions and confirm readiness through accountable management decisions. 

Published change → competent interpretation → mapped impact → owned actions → controlled implementation → evidence → internal audit and management review → certification transition 

Connected management system revision assurance

CONNECTED CHANGE WITHOUT DUPLICATION 

Map Revised Requirements to the Controls That Actually Operate

A requirement should connect to the process, control, owner, workflow and evidence through which the organisation meets it. When an edition changes, this relationship reveals what needs review. 

  • Record the exact requirement source and edition
  • Compare changed intent rather than wording alone
  • Identify shared controls supporting several standards
  • Retain separate scope and assurance conclusions
  • Assign actions to the people who own the affected operation
  • Link changed documents, training, risk and monitoring
  • Verify implementation before marking the gap resolved

One control can support several requirements. One update should not automatically close every framework gap. 

A CONTROLLED MONITORING WORKFLOW 

Turn Standards Intelligence Into Managed Change

Organisations need a repeatable route for detecting, assessing and responding to published changes. The monitoring record should distinguish verified fact from commentary and retain the source used. 

  • Monitor ISO project and publication pages
  • Record the checked date, edition and status
  • Capture accreditation and certification-body transition notices
  • Assign competent impact assessment
  • Map affected risks, controls, processes and documents
  • Create owned implementation and competence actions
  • Plan internal audit and management review
  • Track certification-body milestones and retained evidence

The frequency should increase when a project reaches DIS, FDIS or under-publication status. The organisation should still avoid making unapproved operational changes merely because commentary predicts a future requirement. 

ISO revision monitoring and operational action

HOW ZEBSOFT SUPPORTS THE PROCESS 

Operate the Transition Without Claiming to Interpret the Standard

Zebsoft can connect approved requirements and revision decisions to operational change. The organisation’s competent people remain responsible for obtaining and interpreting the standards. 

 

Controlled source record

Retain the edition, status, source, review date, responsible person and applicable organisational scope. 

 

Requirement and control mapping

Connect approved interpretations to organisational controls, risks, owners and existing evidence. 

 

Transition workflows

Coordinate gap assessment, documents, training, actions, approvals, evidence, audit and management review. 

 

Visible readiness

Show unresolved gaps, overdue activity, evidence awaiting verification and the decisions supporting readiness status. 

PRACTICAL TRANSITION CONTROLS 

What a Complete Revision Plan Should Contain

The plan should be proportionate to the changes and the management system’s existing maturity. It must cover operation and evidence, not only rewritten documentation. 

 

Source and scope

Official edition, amendments, certification position, organisational boundaries and affected entities or sites. 

 

Gap and impact

Requirement-level analysis connected to real processes, risks, controls, systems, suppliers and interested parties. 

 

Owned implementation

Approved actions, resources, dependencies, documents, communication, training and evidence expectations. 

 

Assurance and decision

Internal audit, effectiveness checks, management review, certification-body plan and closure authority. 

A document marked “updated” is not evidence that a changed requirement is operating. Closure should depend on suitable implementation evidence and review by the person authorised to accept the result. 

RESPONSIBLE AI. AUTHORITATIVE SOURCES. 

AI Can Assist Interrogation—it Cannot Publish or Interpret the Standard

Where enabled, AI can help authorised users interrogate approved internal information, summarise recorded actions and surface possible gaps for review. It must not invent a revision status, reproduce unlicensed standards content, determine conformity or replace competent interpretation. 

 

AI may assist

Search approved records, summarise transition activity and expose connected risks, controls, actions or evidence. 

 

Workflow may automate

Schedule reviews, route approved actions, request evidence, remind owners and expose overdue or rejected work. 

 

People remain responsible

Verify the publication, obtain the standard, interpret requirements, approve changes and reach assurance conclusions. 

MAINTAINING THE AUTHORITY RECORD 

Accuracy Requires a Controlled Review Process

A standards-status page is itself controlled information. Every current statement should be capable of being traced to the source, reviewer and date used, and revised promptly when a project or transition position changes. 

 

Exact reference

Record the full standard designation, edition, amendment and development stage. Avoid shortened language where it could conceal which publication or project is being discussed. 

 

Source hierarchy

Prefer ISO for publication status, the current international accreditation cooperation and relevant accreditation body for transition requirements, and the certification body for the client audit plan. 

 

Review trigger

Recheck the page when ISO changes a project stage, publishes an edition or amendment, or an accreditation body issues transition instructions. Scheduled review remains useful between events. 

 

Superseded history

Update the current position without erasing the earlier record. Retained history explains why earlier plans, audits or communications used a different edition or transition assumption. 

The visible status date tells the reader when the position was verified. Internally, the review should also retain who checked it, which source was opened, what changed and whether related standards pages, workflows or customer communications require action. 

PRACTICAL QUESTIONS 

ISO Standards and Revisions FAQs

Every answer below is tied to the status date shown above. Always recheck the linked primary source before relying on a transition or publication position. 

What is the current edition of ISO 9001?

On 28 August 2026, ISO 9001:2015 with Amendment 1:2024 remains the published requirements edition. ISO shows Edition 6 as under publication for September 2026. Until ISO publishes it, organisations should not describe the new edition as the current standard. 

Is ISO 14001:2026 now published?

Yes. ISO 14001:2026 was published in April 2026 as the fourth edition. ISO lists the 2015 edition and its 2024 amendment as withdrawn. Organisations with accredited certification should follow their certification body’s transition arrangements. 

Has ISO 45001:2018 been replaced?

No. ISO 45001:2018 with Amendment 1:2024 remains the published requirements edition. A revised document is at DIS stage, which provides useful preparation information but is not a replacement standard. 

What did the 2024 climate amendments change?

ISO published climate-action amendments across many management system standards. Organisations must consider whether climate change is a relevant issue in their context, and interested parties may have climate-related requirements. The effect must be evaluated within the organisation’s real scope and management system. 

Does a new ISO edition immediately invalidate every certificate?

Not normally. Publication of a replacement standard and transition of accredited certification are related but distinct events. Transition arrangements set how certification bodies and certified clients move to the new edition. Confirm the applicable timetable directly with your certification body. 

What happened to the International Accreditation Forum?

IAF ceased operating on 1 January 2026 when the new Global Accreditation Cooperation Incorporated began operating. Legacy IAF documents may remain temporarily applicable under Global ACI arrangements, but current international references should use Global ACI and the relevant accreditation body. 

Can Zebsoft interpret a revised standard for us?

No. Zebsoft can structure approved requirements, map them to controls, coordinate change and retain evidence. Competent people remain responsible for obtaining the standard, interpreting requirements, assessing gaps and approving the revised management system. 

How often should this page be checked?

The dated status should be reviewed whenever ISO changes a project stage, publishes an edition or amendment, or a relevant accreditation body publishes transition arrangements. The source link and date should remain visible so users can distinguish current fact from earlier reporting. 

PRIMARY SOURCES AND NEXT ROUTES 

Verify the Status—Then Prepare Operationally

Use ISO for editions and project stages, Global ACI and the relevant accreditation body for current cooperation or transition requirements, and the organisation’s certification body for its audit and certificate plan. 

 

Standards pages

Use Zebsoft’s individual standards pages for requirement-led operational explanations and the relevant management-system workflow. 

 

Standards and frameworks

Use the index to identify the standards, regulations and frameworks supported across the platform. 

 

Platform structure

Use the platform information pages to understand how domains, capabilities, workflows and evidence connect.