Subfractal
Set the rules

NATA's 2026 NDT Annex: What Changed for PAUT, TOFD, CR and DR Software

NATA's NDT annex to ISO/IEC 17025, issued May 2026 and effective August 2026, puts PAUT and TOFD software under validation and version control, asks CR/DR procedures to control filters, and makes Level 3 endorsement for advanced techniques a requirement. Restated in plain English, checked on 13 November 2026.

For: Owners, Level 3s and quality managers of NATA-accredited NDT laboratories, especially those running PAUT, TOFD, CR or DR

If you run PAUT, TOFD, CR or DR under NATA accreditation, the rules for your software changed in August 2026. They are in NATA's NDT annex to ISO/IEC 17025, a 48-page PDF. This page restates the parts about software, records and technical control, with the section each comes from.

Everything below is taken from NATA's annex. Where we quote, we quote NATA. Read the annex itself, and ask your NATA client coordinator where anything is unclear.

What is the annex, and when did it take effect?

The annex sets out NATA's specific criteria for non-destructive testing under ISO/IEC 17025. It sits under NATA's infrastructure and asset integrity criteria and covers radiography, ultrasonics, magnetic particle, penetrant, visual and electromagnetic testing, plus work sites. The 2026 issue was issued in May 2026 and took effect in August 2026.

NATA's amendment table lists editorial changes throughout, plus a handful of specific ones. For anyone running advanced techniques, the ones that matter most are about people and software.

What does it say about PAUT and TOFD software?

In its requirements for advanced ultrasonic testing equipment (Appendix B), the annex lists what a facility must ensure for PAUT and TOFD. One line covers software:

Software used for data acquisition and analysis is validated and version controlled. Any updates must be traceable and assessed for impact on inspection performance.

Its equipment-check table then sets a frequency:

Item When What NATA's annex asks
Display/analysis software As updated or annually Verify the software revision. Confirm compatibility and performance consistency for flaw sizing and reporting

Read together, that is three things:

  1. Know what version you are on, for acquisition and for analysis.
  2. Treat every update as a change. Record it, and assess whether it could affect detection, sizing or reporting before you rely on it.
  3. Check at least once a year anyway, even if nothing changed.

Analysis software gets updated, sometimes automatically. If the update lands mid-project, the question an assessor could reasonably ask is which version produced which result, and how you know the new one sizes the same way.

What does it say about CR and DR?

For CR and DR techniques, the annex (Appendix A) says procedures must cover image acquisition and processing, including:

controls around the use of digital processing functions (e.g. filters, contrast adjustments)

and requirements for validating techniques, "especially where they are not based on a published standard". The same list asks for documented exposure-parameter selection and image quality requirements: minimum SNRN, sensitivity and basic spatial resolution.

A filter is a judgement made by software. If an operator can sharpen, smooth or stretch contrast before evaluating an image, the procedure should say which settings are allowed, and the record should say which were used.

Which job records now name the software?

Each method's appendix lists the minimum fields a job record must include "to ensure that the test can be replicated, if necessary". The software-related fields are below. Each appendix has other fields too.

Method Software-related fields NATA's annex lists
Radiography, CR/DR (App. A) Detector type/model, pixel size, BSR, minimum SNRN achieved, image processing parameters/filters used, software and version used for acquisition and analysis
Ultrasonics, PAUT/TOFD (App. B) Scan plans and coverage, scan type, focal law parameters, scanner/encoder parameters, software version and analysis method/settings
Electromagnetic testing (App. F) Equipment settings including filters and mixing, detailed instrument setup files and software configuration parameters, software version and settings used

If your report template or job sheet has no field for software version, that is the simplest fix in the whole annex.

What changed for the Level 3?

Two things.

Endorsement for advanced techniques is now a requirement. Where the work includes PAUT, TOFD, or CR and DR for welds, the annex says the person responsible for overseeing those tests "shall hold an independent endorsement for these techniques that is equivalent to ISO 9712 Level 2 or higher". NATA's amendment table says this was "upgraded from an expectation to a requirement".

Level 3 coverage is explicit. The annex says the person responsible for technical control must have direct and ongoing involvement in eight activities:

# Technical-control activity Can be delegated to Level 2?
i Authorising technicians to perform tests and release results No
ii Writing, approving or reviewing procedures, and validating them No
iii Monitoring the need for new procedures No
iv Managing the in-house NDT competency program No
v Monitoring the quality of reporting across the organisation Yes
vi Ensuring field technical control Yes
vii Dealing with technical queries from testing personnel Yes
viii Ensuring the integrity of equipment commissioning and performance checks Yes

The annex says the designated Level 3 can delegate v to viii to people holding at least Level 2 in the primary method. It also says each facility must define the nature and frequency of Level 3 involvement, and keep records of it. Software validation sits naturally under ii and viii. A software update is both a procedure question and an equipment question.

Where could AI touch this?

We could find no mention of AI in the annex. But AI features are arriving in exactly the places it controls: automated defect recognition in radiography and ultrasonic analysis, auto-sizing, and report drafting.

The annex's software line doesn't care what the software does inside, so the same rules apply to an AI feature as to any other. If it does acquisition or analysis, it is validated and version controlled. If it changes with an update, the update is assessed. If it processes an image, the record names it. And the Level 3 activities above are where a firm decides whether AI is allowed to help at all. Authorising a technician to release results is not something to hand to a tool.

If your firm also holds ISO/IEC 17020 inspection accreditation, the new 17020 edition has its own technology clauses. We set them out in ISO 17020 2026 changes, in plain English.

An example, made up

A ten-person NDT lab runs PAUT on pipeline girth welds. Halfway through a shutdown, the analysis software on one laptop updates itself overnight. The new version changes a default gate setting.

Under the annex, the lab would want to show three things. First, which welds were analysed on which version. Second, that someone with the authority to do so assessed the update before more results were released. Third, how they confirmed sizing was consistent, for example by re-running a reference scan on both versions. A one-page change record, kept with the job, covers all three.

Is there a 17025:2025?

You may have read that a new edition of ISO/IEC 17025 was published in 2025. As at 13 November 2026, NATA's ISO/IEC 17025 page describes "the current version, ISO/IEC 17025:2017", and we could not find a 2025 edition in NATA's listings. The change NDT labs did get in 2026 is this annex. Check NATA's page and ISO's catalogue for the latest position before acting on anything you read elsewhere.

What can you do this month?

These are things a careful NDT facility might consider. They are not accreditation advice.

  1. List every piece of software that acquires, analyses, processes or reports NDT data, with its current version.
  2. Turn off automatic updates where you can, so updates happen when you decide.
  3. Keep a change record for each update: old and new version, what could affect detection or sizing, the check you ran, who accepted it, and the date.
  4. Add the record fields from the table above to your job sheets and report templates.
  5. Write down your CR/DR filter rules. Which processing functions are allowed, and who can change them.
  6. Check your endorsements for anyone overseeing PAUT, TOFD or CR/DR on welds.
  7. Write down how your Level 3 is involved, how often, and what you will keep as a record.

One question

A question with no pitch attached: who signs off a software update on your PAUT or DR kit today? warwick@subfrac.com

Questions people ask

Does NATA require PAUT software to be validated?
Yes, for accredited NDT work. NATA's May 2026 NDT annex says software used for PAUT and TOFD data acquisition and analysis is validated and version controlled, and updates must be traceable and assessed for impact on inspection performance.
How often should NDT analysis software be checked?
NATA's annex lists display and analysis software for advanced UT as checked 'as updated or annually': verify the software revision and confirm compatibility and performance consistency for flaw sizing and reporting.
What must a CR or DR job record include?
Among other fields, NATA's annex lists detector type or model, pixel size, basic spatial resolution, minimum SNRN achieved, image processing parameters or filters used, and the software and version used for acquisition and analysis.
What are the NDT Level 3's responsibilities under NATA?
NATA's annex lists eight technical-control activities, from authorising technicians and approving procedures to equipment checks. The designated Level 3 can delegate the last four to people with at least Level 2 certification in the primary method.
Is there an ISO/IEC 17025:2025?
As at 13 November 2026, NATA's ISO/IEC 17025 page describes ISO/IEC 17025:2017 as the current version, and the NDT annex is written against it. Check NATA's page and ISO's catalogue for the latest position.
Does the annex mention AI?
We could find no mention of AI in the annex. Its software requirements apply to whatever software does the acquisition, analysis or processing, so an AI feature inside that software would be part of what is validated and version controlled.

Sources

  1. ISO/IEC 17025 Application Document, Infrastructure and Asset Integrity, Annex: Non-destructive Testing (SAC 03.3)NATA, Issued May 2026, effective August 2026
  2. Specific Accreditation Criteria: Non-destructive Testing Annex for public commentNATA
  3. Laboratory accreditation, ISO/IEC 17025NATA, Page checked 13 November 2026

Facts last checked:

Subfractal is not affiliated with or endorsed by NATA, and nothing here has been reviewed by it. This is general information, not accreditation or legal advice.

Who wrote this

Dom O'Carroll is a co-founder of Subfractal.