ISO 9001:2026 publication starts an edition-controlled transition
ISO now identifies ISO 9001:2026 as the published sixth edition and lists ISO 9001:2015 as withdrawn. Quality teams should replace the old under-publication watch with an edition-controlled transition record while preserving which requirements, procedures, audits, training, contracts, and certificates still belong to the 2015 baseline.
Editorial figure by Quality Systems Index. Source context: ISO 9001:2026 official standard record.
Close the publication watch and open a transition record
The direct answer is that ISO 9001:2026 is no longer a draft or under-publication item. ISO records Edition 6 as published on September 16, 2026 and shows the 2015 edition as withdrawn. Replace the monitoring status with a dated publication event, but do not relabel historical evidence. The transition register should identify the organization and QMS scope, current certificate and certification body, applicable contracts or sector schemes, 2015 baseline, 2026 source copy, comparison method, accountable owner, and the authoritative transition timetable when obtained. [1]
Publication status and implementation status are different fields. One can change on September 16 while procedures, audits, competence records, supplier requirements, product controls, software configurations, and certificates remain tied to the earlier edition until controlled decisions change them. Preserve each record's governing edition and effective period. A dashboard that flips every item to 2026 on publication date would destroy the evidence needed to explain when and why the QMS changed.
Build a requirement-to-operation crosswalk
ISO's public page describes clearer requirements, stronger emphasis on quality culture and leadership, separated treatment of risks and opportunities, and closer alignment with other management-system standards. These are high-level publication descriptions, not a clause-by-clause gap analysis. The organization should work from an authorized copy and create a crosswalk linking every applicable 2026 requirement to current process, procedure, role, evidence, system, metric, audit coverage, and unresolved change. [1]
Classify the result as unchanged, wording or interpretation review, process change, document change, training change, system or configuration change, audit-program change, contract or supplier change, or unresolved. Retain the old mapping and the review evidence. Where one control supports several requirements, show the relationship without using a single compliant status. Where a requirement has no evidence owner, create an exception with due date and acceptance authority.
Get the transition clock from the responsible authority
ISO says certified organizations will transition within the timeframe set by their certification cycle and directs them to their certification body. The ISO product page does not establish one universal deadline for every certified organization, customer contract, accreditation arrangement, or sector scheme. Record the source and date of the timetable that actually governs the organization, including certification-body communication, audit window, certificate expiry, surveillance or recertification events, customer requirements, and accepted exceptions. [1]
Plan backward from those authoritative dates, but keep completion evidence at the work-item level: approved gap assessment, controlled changes, training and competence, implemented configuration, operational records, internal audit, corrective action, management review, readiness decision, certification-body result, and revised certificate where applicable. A project percentage or completed checklist cannot prove that an individual requirement is effective in the QMS.
Preserve the boundary between standard, certification, and software
ISO describes ISO 9001 as a QMS requirements standard that organizations can use with or without certification. Publication does not certify an organization, approve an implementation, or establish that a product template meets the requirements. QMS software may support controlled documents, training, audits, nonconformance, corrective action, risk, change, and management review, but configuration and records must be evaluated against the organization's approved interpretation and scope. [1]
Close the transition only with a dated authority record: the edition adopted, scope, requirement mapping, approved changes, implementation evidence, audit and review results, open exceptions, certification or customer outcome if applicable, and owner who accepted residual risk. This article does not interpret the standard text or set a deadline. It identifies the publication-status correction and the evidence structure needed to keep two editions from being mixed.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Quality Systems Index will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.