Global ACI gives certified organizations until 30 September 2029, so the decision worth making early is which audit carries the change and when your certification body can certify to the new edition.
Global ACI's [transition document for ISO 9001:2026](https://sys.global-aci.org/uploads/documents/TECH-3-TR_2029-09-30_(M)_ISO_9001_2026_Transition_v1_03.pdf) asks the same question in two of its tables: "Is extra time likely to be needed for the transition?" For accreditation bodies, section 5.1 answers "No". For the audit of certified clients, section 5.2 answers "Possibly". Section 3.2 of the same document calls the overall changes "minimal".
That "Possibly" is the part that lands on your audit calendar. The harder question is which audit carries the transition, and from what date your certification body can do it.
Two kinds of body do the work in this document:
Section 1.2 makes the document "mandatory for all Global ACI MRA AB signatories and accredited CABs." Certified organizations aren't named as bound; they feel it through their certification body.
Section 3.2 reads:
"The overall changes to the document are minimal; therefore, it is expected that organisations will find changes to requirements of the standard to be largely intuitive, practicable, and depending on the organisation’s context and objectives, attainable with reasonable effort. The impact and risk may differ by organisation; it is the certified organisation’s responsibility to determine the changes to its context and management system."
So "minimal" is a characterization with its limit attached, and working out that limit is your job. The same section says certification bodies "will need to invest considerable effort—including audit time and administrative resources—to transition their certified clients," because there are more than one million accredited certificates. Reasonable effort describes the organization; considerable effort describes the certifier.
ISO 9001:2026 itself is paywalled and wasn't read for this post, so the clause changes below are Global ACI's own summary from section 3.1. This is a selection from a list Global ACI heads "Key Changes Include but Are Not Limited To," so it can start a gap check but can't replace reading the standard:
The public summaries differ on that last line. Global ACI's news item and the ISO/TC 176 committee site both say the edition "introduces a new Annex A". Only the standard can settle that, and it's paywalled, so I'm using the transition document's wording.
The earlier dates decide when a 2026 certificate becomes possible. Accredited certification to the 2026 edition is permitted only following "Transition of the CAB’s accreditation by their AB," and the transition document's own Annex A, separate from the standard's, has certification bodies "issuing accredited certificates only after the AB transition decision."
| Date | What the document sets | What it means for a certified organization |
|---|---|---|
| 31 March 2027 | Latest date for ABs to be ready and to announce their transition process | Your certification body's accreditor is due to have a process in place |
| 30 June 2027 | Latest date for a CAB's declaration and supporting documents | A CAB that won't transition is required to tell you in writing by this date (6.2.1) |
| 30 September 2027 | AB transition decisions completed | The latest scheduled point from which your CAB can issue accredited 2026 certificates |
| 31 March 2028 | "New / Initial certifications" only to the 2026 edition | First-time certification to the 2015 edition is closed |
| 30 September 2029 | Client transitions, "including certificate issuance, prior to this date" | Accredited 2015 certifications "are no longer valid" |
Global ACI's news item dates the standard's publication to 16 September 2026, and each period runs from the last day of that month. The arithmetic from here is mine: if your certification body's decision lands on the latest date, 12 of the 36 months are gone, and the certificate has to fit in the remaining 24, along with the audit unless it can run before the decision, an open question below. The decision can come earlier. Section 3.2 says the three-year period "will provide sufficient time to manage the transition effectively."
The AB's decision rests on the certification body's declaration and supporting documents. Document review, head office assessment, and witnessed assessment are all marked "No" ahead of it, though an AB may require more based on risk; the head office check and at least one witnessed audit to the new edition come afterward.
A certification body that misses a transition requirement, timelines included, has to notify affected clients in writing of the delay and its "potential impact/s on their certification" (6.3.1), with no date stated for that notice.
Section 5.2 names three vehicles: the transition audit "may be conducted in conjunction with the certified organisation’s surveillance audit, recertification audit or through a separate special audit." The required content doesn't vary with the vehicle. Each "shall include a review of, but not be limited to" the changed requirements, changes to the organization's context, and the need for any other changes to the management system. Remote delivery is available too, "if they ensure and can demonstrate the transition audit objectives are met," and that burden sits with the certification body.
With the content fixed, the difference comes down to scheduling and time:
"In determining if additional audit time is needed, the certification body shall consider, at a minimum, the degree of change to the client’s management system and whether the transition audit is conducted in conjunction with an annual audit or through a special audit." >"Note: Additional time may not be needed for a full system audit."
The document gives criteria and no figure in days or percent. It points to ISO/IEC 17021-1 and IAF MD 5 for the calculation, which weren't read for this post. The audit row says surveillance, recertification, or special, while the time row says annual or special, and neither "annual audit" nor "full system audit" is defined.
One criterion starts with you. The certification body weighs the degree of change, and section 3.2 has already made determining those changes your responsibility, so you can bring your own gap check to that conversation.
The ranking that follows is my judgment and appears nowhere in the text. Section 5.2 addresses the options to the certification body, so it's a position to bring to yours.
I'd look at the next recertification first. If it falls after your certification body has transitioned and leaves room before the end date, I think it's the natural carrier, because of that note on full system audits. Reading "full system audit" as a recertification is my inference, so test it with your certification body. A special audit is my fallback, since it adds an audit that wasn't already on the calendar.
| Where your next recertification falls | Where I'd look first | What the document offers |
|---|---|---|
| After the transition decision, with room before 30 September 2029 | Recertification | Additional time "may not be needed" if it counts as a full system audit |
| Before the transition decision | A later surveillance audit | I read "annual audit" as covering it, and the time test applies |
| Close against 30 September 2029 | An earlier surveillance audit, if one falls after the decision | Section 4 counts certificate issuance inside the period, so the audit can't be the last step |
| No scheduled audit fits | Special audit | Named in the time test; the text doesn't say which way it moves the time |
The degree of change can reverse this order. If your gap check turns up little, a surveillance audit soon after the decision may serve you better than waiting for a recertification. If it turns up a lot, I'd rather give the change a special audit of its own than load it onto a surveillance audit.
I couldn't resolve these from the text, so they're questions for your certification body:
An organization may choose not to transition, and the certification body "may conduct their audit/s against the previous version," but section 6.4.1 says the certification "will expire at the end of the transition period." A note in 5.2 also says "It is not necessary to modify current / existing ISO 9001:2015 certificates," so a 2015 certificate can show a printed expiry later than the date on which it stops being valid, though the note adds that the certification body may change the expiry date "to reduce marketplace confusion."
The document doesn't mention ISO 27001, or combined or integrated audits. So my ISMS advice is a judgment about the calendar: lay your ISMS audit dates next to the options above before picking a vehicle, because two audits landing together is a staffing question if the same people prepare for both. Whether one audit can serve both standards is a question for your certification body; the documents cited here don't support an answer either way.
Section 5.2 of the [Global ACI document](https://sys.global-aci.org/uploads/documents/TECH-3-TR_2029-09-30_(M)_ISO_9001_2026_Transition_v1_03.pdf) is the part to read next, before you take these questions to your certification body and fix the audit plan.
Quoted passages come from Global ACI-TECH-3-TR 2029-09-30 (M), Version 1.0 (issued 4 September 2026, implementation date 16 September 2026), with acknowledgment of Global ACI's contribution.
devguard's ISO 9001:2026 edition has a roadmap that spreads the open tasks into weekly batches up to a target date you pick, and controls new in 2026 start uncovered, with no credit from coverage you already have elsewhere (Framework 1.6.0 in the changelog).
Angelo runs strategy and the relationships behind devguard. He spends his time with the teams who live with compliance day to day, and keeps what we build tied to what they actually need.
Start free, bring your frameworks, and keep the evidence attached as the work ships. No setup friction, no audit-week fire drill.
Start free, bring your frameworks, and keep the evidence attached as the work ships. No setup friction, no audit-week fire drill.