Tracking ASNT Certification Expiry Across a Whole Technician Base

The failure mode is never one certificate. It is the interaction between method, level, vision exam, on-the-job hours and a client-specific approval — across a hundred people.

Every inspection company starts with a spreadsheet of technicians and expiry dates, and every one of them eventually gets caught by the same thing: the certificate itself was current, but the annual vision exam had lapsed, or the technician was certified in UT and dispatched to a PAUT scope, or the written practice revision they were certified against had been superseded. This is a data-model problem, not a diligence problem, and it starts to bite somewhere around thirty technicians.

What the written practice actually obliges you to hold

Under ASNT SNT-TC-1A the employer certifies, which means the employer carries the evidence. For each technician and each method you need the certification level and date, the general, specific and practical examination records with scores, documented training hours, documented on-the-job experience hours, the annual near-vision acuity and colour-contrast examination, and the revision of the written practice under which certification was granted. ANSI/ASNT CP-189 tightens several of these; NAS 410 and EN 4179 add aerospace-specific requirements including outside-agency involvement in some cases; ISO 9712 shifts certification to a third party but leaves you holding the employer-side authorisation record.

The practical consequence is that "is Ahmed certified?" is not a yes/no question. It is a question about a specific method, at a specific level, on a specific date, against a specific written practice revision — and a spreadsheet column cannot represent that.

Why the spreadsheet fails, predictably

One row per person cannot hold five methods at different levels with different expiry dates.
Vision exams are annual while method certifications are typically on a longer cycle, so the two drift out of sync and the shorter one is the one everyone forgets.
Client-specific approvals — an operator-specific qualification, a site induction, a CBT screening — expire on their own schedule and are usually tracked in a different file entirely.
Nobody checks the spreadsheet at the moment of dispatch, which is the only moment that matters.
When a client asks for the qualification record of the technician who signed a report eighteen months ago, the spreadsheet holds today's state, not that day's state.

The control that actually prevents the incident

Reminder emails do not prevent lapses; they inform people about lapses that already happened. The control that works is a hard dependency between the qualification record and the dispatch action: if the certification, the vision exam, the client approval or the instrument calibration is not current for the scope being assigned, the assignment cannot be made. That single constraint converts certification management from an administrative task that competes for attention into a property of the system.

The second control is point-in-time recovery. Every report should carry the certification state applicable on the date of inspection, frozen, so that an audit eighteen months later reconstructs what was true then rather than what is true now.

A practical migration if you are on spreadsheets today

Export what you have and reconcile it against the written practice — most companies discover 5–15% of records are incomplete at this step, which is itself the finding.
Model per method and level, not per person. Accept that one technician generates several qualification records.
Load vision exams and client-specific approvals as first-class records with their own expiry, not as notes.
Wire the dispatch check before you wire the reporting dashboard. The dashboard is nice; the check is what stops the incident.
Freeze certification state onto issued reports from day one, so your point-in-time history starts accumulating immediately.

Frequently Asked Questions

At what size does spreadsheet certification tracking stop working?

In practice around thirty technicians, or earlier if you run more than three methods or work for more than two clients with their own approval regimes. The trigger is not headcount alone — it is the number of independent expiry clocks. A twelve-technician company running five methods, annual vision exams and two operator-specific approvals is already tracking well over a hundred separate expiry dates.

What does a client audit actually ask for?

Typically: the written practice in force, the certification record for named technicians including examination and vision-exam evidence, documented training and on-the-job hours, and the ability to tie a specific issued report back to the qualification state of the person who signed it on the day they signed it. The last item is the one that catches most companies, because their system holds current state only.

Can this be handled inside a generic HR system?

Partly, and it usually goes wrong at the same place. HR systems model people and roles, not method-level technical qualification against a written practice revision, and they have no concept of dispatch. You can store certificates in HR; you cannot enforce that an uncertified technician is undispatchable, which is the control that matters.

How long does it take to get a certification register clean?

Two to four weeks for a typical mid-size inspection company, and most of that is chasing incomplete historical records rather than configuring software. Budget for the discovery that some records genuinely cannot be reconstructed, and decide deliberately how to treat those rather than leaving gaps in the register.

See it running on your own workflow

Thirty minutes, your job types and your reporting formats, co-presented by an ASNT NDT Level III. Affordable, accessible, fully customizable — request a demo and a tailored quote.