# ISO 17020 2026 Changes: Every New and Major Clause on NATA's Checklist, in Plain English

> NATA's Implementation Checklist for ISO/IEC 17020:2026 lists 52 clauses with new or major changes, and you answer every one before your conversion visit. Here is each group in plain English, taken from NATA's own gap analysis, checked on 13 November 2026.

By Dom O'Carroll. Published 2026-11-16; facts last checked 2026-11-13. Canonical: https://subfractal.com.au/thinking/iso-17020-2026-changes

## The short version

- NATA's ISO/IEC 17020:2026 Implementation Checklist lists 52 clauses with new or major changes, and an accredited inspection body answers each one, with evidence, before its scope is moved to the new edition.
- From 1 October 2026 NATA assesses every inspection body against the 2026 edition; conversion happens at your next scheduled assessment, or earlier on request as a chargeable variation, and accreditation of bodies not converted by 31 March 2029 will be suspended.
- The biggest new areas, by NATA's gap analysis, are risk and liability (5.2.4, 8.4), contract review (7.1), equipment and technology (6.2.4 to 6.2.9), data control and records (7.4.3, 7.4.4, 7.5) and a restructured management system (section 8).
- Clause 7.5.1 is new: the system used to collect, process, record, report, store or retrieve inspection data must be validated, and software or configuration changes authorised, documented and validated before they are used.
- Independence is now Type A or Type non-A, with the Type confirmed during NATA's assessment.

NATA has published everything an inspection body needs to prepare for ISO/IEC 17020:2026, but it is all in PDFs: a transition policy, a 46-page gap analysis, an application document and a four-page checklist. This page restates them in one place, with clause numbers, so you can see the whole job before you start.

We have not read the standard itself. Everything below is taken from NATA's documents about it, and where we quote, we quote NATA. Buy the standard, read NATA's current criteria, and ask your NATA client coordinator where anything is unclear.

## What are the dates?

The dates come from NATA's transition policy, SAC 10.02.

| Date | What happens |
|---|---|
| March 2026 | ISO/IEC 17020:2026 published, replacing the 2012 edition |
| 1 October 2026 | All NATA assessments of inspection bodies are conducted against the 2026 edition |
| Your next scheduled assessment after 1 October 2026 | Your accreditation is assessed for conversion. Earlier is possible on request, as a chargeable variation |
| Before that visit | You complete the Implementation Checklist and supply evidence, as part of the usual pre-visit arrangements |
| 31 March 2029 | The transition period set by Global ACI (formerly ILAC) ends |

NATA's policy is blunt about the end date:

> Those facilities that have not transitioned to ISO/IEC 17020:2026 by 31 March 2029 will have their accreditation suspended.

Multi-site bodies transition as a whole, at the next scheduled assessment of the primary site. Where that falls on or after 1 April 2028, NATA says it will pick another site with an earlier visit.

## How many clauses do you have to answer?

The Implementation Checklist lists 52 entries: 33 rated Major and 19 rated New. NATA's instructions say a response and supporting evidence for each must be provided before your scope is updated, and compliance is confirmed on site.

That is a lot for a small body. Most entries need a sentence and a pointer to a procedure or record. A few need something you may not have yet. The groups below are in clause order, so you can work through them with the checklist open beside you.

## The 52 entries, grouped, in plain English

Our summaries are short paraphrases of NATA's gap analysis. They are a map, not a substitute for it.

| Clauses | Rating | What NATA's gap analysis says changed |
|---|---|---|
| 5.1, A.1, A.2 | Major | Independence moves to Annex A, with two categories: Type A and Type non-A. A body can meet different Types for different activities. For Type A, "parties involved" now includes purchasers and regulators |
| 5.2.4 | Major | Insurance or reserves must match your liabilities: analyse the risks, assess the liabilities, set provisions to suit |
| 5.2.5 | Major | Documented contract conditions, and internal agreements where you inspect for your own legal entity |
| 5.3.1, 5.3.2, 5.3.4 | Major | Define your structure and who manages, performs or verifies work. "Technical management" replaces a single technical manager, with named responsibilities. Someone has the authority to run the management system |
| 6.1.2, 6.1.5 | Major | A documented process for competence, from requirements to authorisation and monitoring. Monitoring follows a programme at a defined frequency |
| 6.2.4 to 6.2.8 | Major and New | Equipment that significantly influences results is identified, checked and calibrated. New 6.2.6: verify equipment before it goes into or back into service. Traceability to the SI, or to another appropriate reference where that isn't possible |
| 6.2.9 | Major | Technology, now including data processing, AI, augmented reality and remote inspection: suitable, data protected, hardware and software maintained |
| 6.3.1 to 6.3.3 | New and Major | Externally provided products and services: only suitable ones are used, with a procedure for requirements, selection and monitoring of providers |
| 7.1.1, 7.1.3 to 7.1.5 | New | Review of requests, tenders and contracts: a procedure, differences resolved before work starts, and records kept |
| 7.2.4 to 7.2.6 | New and Major | Developing methods is planned work for competent people. Methods must cover where judgement relies on technology and results from AI. Non-standard methods are validated, including when technology is used |
| 7.4.3, 7.4.4 | New | Records name the equipment that influenced the result and when it was used. Amendments are traceable, with the original and the change both kept |
| 7.5.1, 7.5.2 | New | The system that handles inspection data is validated, changes are controlled, records are protected, and system failures are recorded |
| 7.6.2, 7.6.6 | Major and New | Minimum report content, and simplified reporting where agreed with the client, with a record of the agreement |
| 7.7.1 to 7.7.3 | Major | Appeals get their own clause. The handling process must be publicly available, not just on request |
| 7.8.1, 7.8.2, 7.8.7 | Major | Complaints likewise, with the process publicly available |
| 8.1.1, 8.1.2, 8.2.2 | Major and New | The management system is restructured: no more Option A/B, and policies must address competence, impartiality and consistent operation |
| 8.4.1 to 8.4.4 | New | Risks and opportunities: consider them, plan actions proportional to their effect on valid results, and seek client feedback |
| 8.5.1 to 8.5.3 | Major and New | Corrective action covers nonconforming inspection work too, including recalling or repeating work and withholding reports where the risk warrants it |
| 8.6.1, 8.6.2 | Major | Internal audits at planned intervals that cover everything. The fixed 12-month minimum goes |
| 8.7.1, 8.7.2 | Major | Management review with a longer list of inputs, including risks, workload and feedback |

## Which changes catch small bodies out?

Four groups stand out for an inspection body of five to thirty people, because they ask for something written down that many small bodies hold in their heads.

**Risk and liability (5.2.4 and 8.4).** NATA's application document says facilities must assess the risks and potential liabilities of their inspection work and show their cover is "adequate and proportionate". The question is how you decided your insurance was enough. Most owners know the answer; few have written it down.

**Contract review (7.1).** Four of the 52 entries are new clauses about reviewing requests, tenders and contracts. If the job request arrives as a phone call and a text message, the record of what was agreed may only exist in someone's memory.

**Data and software (7.5).** NATA's gap analysis summarises new clause 7.5.1 like this:

> The inspection body's system used for the collection, processing, recording, reporting, storage or retrieval of data relevant to inspection activities shall be validated. Whenever there are any changes, including inspection body software configuration or modifications to commercial off-the-shelf software, they shall be authorized, documented and validated before implementation.

NATA's application document adds that commercial off-the-shelf software "may be considered pre-validated when used within its specified application range". That helps, but the update still needs to go through change control. For a body using tablets, cloud report templates and instrument software, that is a lot of changes nobody currently records.

**Technology in methods (6.2.9, 7.2.5, 7.2.6).** These are the clauses that mention AI. We cover them in depth in [Why your inspection body should write down its position on AI](/thinking/inspection-bodies-need-a-position-on-ai). The short version: they apply to technology you use, and NATA's application document says the responsibility "must be revisited whenever changes could affect inspection outcomes".

## An example, made up

A mechanical inspection body of twelve people does lifting-equipment and pressure-vessel inspections. Its reports are written on tablets from a cloud template. In March the template supplier pushes an update that changes how photos are compressed and adds an "AI summary" button.

Under the 2012 edition, nobody would have thought about it. Under 7.5.1, the change needs authorising, documenting and validating before use. Under 6.2.9, if inspectors start pressing the new button, the body is responsible for that technology too. Under 7.4.4, if an inspector edits a finding after the summary is generated, both versions are kept.

None of that needs new software. It needs a short change log, a decision about the button, and a sentence in the method.

## What can you do before your visit?

These are things a careful inspection body might consider. They are not accreditation advice.

1. **Find your date.** Check your assessment programme for your next scheduled visit after 1 October 2026.
2. **Download NATA's three documents.** The transition policy, the gap analysis and the Implementation Checklist are on NATA's website.
3. **Buy the standard.** NATA's policy says you must obtain a copy.
4. **Give every checklist entry an owner and a date.** Start with the New clauses, since they are the ones with no 2012 equivalent to point to.
5. **Start a change log now.** One line per software, firmware or template change: what changed, who authorised it, how you checked it.
6. **Write down your risk and liability reasoning.** Half a page is a start.
7. **Draft your responses in plain sentences.** If you can explain an answer in two lines and point at the record, you are probably ready to talk about it on the day.

## One question

We are trying to learn how inspection bodies are finding the checklist. So, a question with no pitch attached: which of the 52 entries took you longest to answer? [warwick@subfrac.com](mailto:warwick@subfrac.com?subject=One%20question)

## Sources

- [Transition Policy for the implementation of ISO/IEC 17020:2026 (SAC 10.02)](https://nata.com.au/files/2026/08/SAC-10-02-Transition-Policy-for-the-implementation-of-ISO-IEC-17020-2026.pdf) — NATA, Issued August 2026, effective October 2026
- [ISO/IEC 17020:2026 Gap Analysis](https://nata.com.au/files/2026/08/Specific-Accreditation-Guidance-ISO-IEC-17020-2026-Gap-Analysis.pdf) — NATA, Issued August 2026, effective October 2026
- [ISO/IEC 17020:2026 Implementation Checklist (SAF 10.13)](https://nata.com.au/files/2026/08/SAF-10-13-Implementation-Checklist-ISO-IEC-17020.pdf) — NATA, August 2026
- [ISO/IEC 17020 Standard Application Document (GAC 12)](https://nata.com.au/files/2026/08/GAC_12_ISO_IEC-17020_Standard-Application-Document.pdf) — NATA, Issued September 2026, effective October 2026
- [Preparing for ISO/IEC 17020:2026: what inspection bodies need to know](https://nata.com.au/news/preparing-for-iso-iec-170202026-what-inspection-bodies-need-to-know/) — NATA
