ISO 9001:2015 remains published while its revision advances

The current record separates published and developing work

The direct answer in ISO's standards record is that ISO 9001:2015 remains the published fifth edition while a revision is under development. Those are separate lifecycle states. Work on a revision does not silently change the requirements, edition reference, certification scope, audit criteria, customer obligation, or controlled copy that an organization currently applies.

A quality-system register should preserve issuer, official title, edition, amendment, publication and status dates, source, applicable contractual or certification basis, internal adoption decision, and controlled-document version. A roadmap entry for the revision should remain planning information until ISO publishes a new edition and the relevant organization, customer, scheme, certification body, or other authority establishes how it applies.

The 2024 amendment belongs in the current baseline

The ISO record lists ISO 9001:2015/Amd 1:2024 as a published amendment to the current edition. A system that stores only the base year can miss an amendment that forms part of the maintained standards record. At the same time, an amendment should not be relabeled as a complete new edition or used to imply that every certified organization has already completed a particular implementation step.

The standards object should connect the base publication and amendment while preserving each artifact's identity, date, source, review, interpretation, affected internal documents, actions, approvals, and evidence. Where licensed standards text controls, the platform should reference the authorized copy and avoid reconstructing protected requirements from secondary summaries. Public metadata supports status management; it is not a substitute for lawful access to the applicable text.

Certification status is not the same as edition status

ISO explains that organizations may implement ISO 9001 without seeking certification and that, where certification is stated, the full reference should be used. The standard's publication status, an organization's chosen quality-system baseline, a certification body's audit criteria, a certificate's scope and dates, and a customer's contractual requirement are related but distinct facts.

Quality software should not convert a selected standard into a certification badge. It should preserve the certified legal entity and sites, certificate issuer, accreditation context where established, standard edition, scope, issue and expiry dates, status source, and evidence limit. A certificate also does not establish product conformity, process capability, correct inspection, accepted first article, or effectiveness of every workflow implemented in the system.

Revision planning needs controlled triggers

A useful readiness process can inventory affected procedures, audit materials, supplier requirements, customer clauses, training, integrations, forms, records, and software configurations while the revision develops. Those activities should be clearly labeled as planning and linked to the source version used. Teams should not predict final requirements or replacement timing from drafts, development stages, marketing summaries, or a vendor's roadmap.

Buyers should ask a provider to demonstrate edition and amendment history, current applicability, draft segregation, impact assessment, controlled adoption, migration, and historical audit evidence. This article reports ISO's public status record reviewed on July 29, 2026. It does not predict publication, transition, certification, contractual application, or conformity and does not reproduce the standard's licensed requirements.

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.