ISO/IEC 17020:2026 Transition: What Changed and Your Deadline

If you are an already-accredited inspection body, you need two things from this page and you need them fast: what changed in the 2026 edition, and the date by which you have to act. Here is the short version before the detail. ISO/IEC 17020:2026 was published on 27 March 2026 and replaces the 2012 edition. Under the ILAC resolution there is a three-year transition window, and accreditations held against the 2012 edition stop being recognised after 27 March 2029. Miss that date without transitioning and your accreditation is no longer recognised.

The trap in those numbers is reading 2029 as “plenty of time.” Your accreditation body does not run its transition assessments on the final day; it runs them across the window, with its own earlier milestones, and assessment slots fill up. The body that books a transition assessment in 2028 is competing for the same assessor diary as everyone else who waited. So the real planning question is not the 2029 deadline, it is your own accreditor’s mandatory date, which comes well before it. This guide gives you the dated roadmap, what actually changed clause by clause, your deadline by accreditor, and a role-based plan to close it out.

The transition timeline at a glance

Four dates frame the whole transition. Two are global and fixed by the ILAC resolution; two are UKAS transition mechanics shown here as a worked example, because UKAS has published the clearest dated schedule. Your own accreditor sets its assessment scheduling inside the same global window.

What actually changed in 2026

The foreword to the 2026 edition lists the headline changes, and they fall into three groups. There are structural changes to how the standard is built, a set of genuinely new requirements, and a loosening of prescription in exchange for more flexibility. As an already-accredited body, your transition work is mostly closing the gaps in the first two groups.

The structural changes

The biggest is independence. The foreword states the categorization of the inspection body’s independence type has been changed to Type A and Type non-A, so the old Type A, B and C model is gone and former Type B and Type C bodies fall under Type non-A. The edition also adds definitions of “item” and “client” that are now used throughout, and it incorporates the common elements shared across CASCO conformity-assessment standards, which is why Clause 8 reads more like the other ISO/IEC 170xx standards than the 2012 version did.

The new requirements

A new subclause on the control of data and information (7.5) and on actions to address risks and opportunities (8.4) was added, and the foreword names both. Alongside them, impartiality became an ongoing monitoring discipline rather than a periodic review (4.1.3), liability provisions now require a documented risk analysis behind your insurance or reserves (5.2.4), and Clause 6.2.9 writes technology into the requirements for the first time, naming computers, automated equipment, data processing, artificial intelligence, augmented reality and remote inspection techniques, all of which must be validated and kept secure. Appeals and complaints, handled together before, are now two separate clauses (7.7 and 7.8), each with a publicly available process.

Where it got more flexible

The foreword is explicit that risk-based thinking allowed some reduction in prescriptive requirements and their replacement by performance-based ones, with greater flexibility in processes, procedures, documented information and organizational responsibilities. For a transitioning body this is the one piece of good news: where the 2012 edition forced a specific document, the 2026 edition often lets you show the outcome your own way. Let me be direct about the limit of that, though. What does not change is that the new clauses above are firm requirements, and flexible never means optional.

For the full clause-by-clause detail of each requirement, the requirements guide walks Clauses 4 to 8 and Annex A in order. The independence reclassification in particular has its own decision tool, covered below.

Your deadline, by accreditor

Every accreditation body works inside the same global window: the 27 March 2029 ILAC deadline applies to all of them. What differs is the schedule each one runs inside that window, and here honesty matters more than a tidy table. At the time of writing, UKAS has published the clearest dated mechanics. The US, Australian and Canadian accreditors operate within the ILAC window but had not all published equivalent dated milestones, so the right move is to take the global deadline as fixed and confirm your own accreditor’s interim dates directly.

The practical reading of this table is simple. Treat 27 March 2029 as the wall, then work to whichever interim date your accreditor sets, because that is the real one. If you are under UKAS, your planning date is 1 January 2028, not 2029. If you are under ANAB, IAS, A2LA, NATA or SCC, ask your accreditor for its transition schedule now and plan to the earliest date it gives you, because waiting for the deadline means competing for assessment slots when everyone else moves at once.

A role-based action plan

A transition stalls when everyone assumes someone else owns it. Split the work by role so each part has a name against it.

Top management

Own the independence decision and the timeline. Confirm the body’s Type A or Type non-A classification under Annex A for each inspection activity, because that decision sets the scope of the re-documentation. Re-affirm the top management commitment to impartiality that clause 4.1.5 requires, and make sure the transition is a standing item in your management review (8.7). Book, or instruct someone to book, the transition assessment with your accreditor early in its window rather than near the deadline.

Technical management

Own the technical clauses. Identify every place you use technology in connection with inspections and build the validation and data-security evidence 6.2.9 now requires, including any AI, remote or augmented-reality method. Stand up the control-of-data controls under 7.5 for the systems that collect, process and store inspection data. Review your inspection methods against the expanded 7.2.5, and make sure method validation records exist where technology is used (7.2.6).

Quality manager and the management-system owner

Own the system changes and the evidence trail. Turn the impartiality review into the ongoing monitoring 4.1.3 expects. Add the documented liability risk analysis behind your provisions (5.2.4). Make sure actions to address risks and opportunities (8.4) are a live part of the management system, and split your appeals and complaints handling into the two separate, publicly available processes of 7.7 and 7.8. Then run an internal audit against the full 2026 edition (8.6) and a management review (8.7) so the transitioned system has evidence of operating before the assessor arrives.

Check your transition readiness

Before you book the assessment, it helps to know where you actually stand against the 2026 changes. Work through the short readiness check below. It walks the changes covered in this guide and gives you a sense of which gaps are still open, so you can aim your effort at the clauses that are not yet closed.

Frequently asked questions

Where to take this next

The fastest way to turn this roadmap into a worked plan is to score yourself against every changed clause and act on the gaps. The ISO/IEC 17020:2026 Transition Checklists Bundle is built for exactly this: a clause-by-clause readiness check you score, with the evidence each requirement expects, so your transition becomes a list of closed items rather than a vague deadline. For the authoritative dates, UKAS publishes its transition mechanics in its ISO/IEC 17020:2026 transition technical bulletin, and ANAB summarises the change list on the ANSI National Accreditation Board blog.