What an auditor asks to see in an NDT program
The visit is rarely about performing a test in the room. It is about whether the team can show who was qualified, which procedure was current, and which asset the report belongs to.
An auditor walking an NDT program is usually not there to watch a technician shoot a weld. The questions are about the program that made the test mean something. Who was allowed to do it. Which procedure they were following. Which asset the report belongs to. What happened when a date slipped.
This is not a checklist you can staple to every audit. Client specifications, jurisdiction, and the written practice change the details. The questions have the same shape, and that is the shape SpecNDT is built around. The software keeps these records connected, so the team can show the qualification, the procedure revision, and the asset as one compliance trail.
The practice the employer actually uses
The first document is the one the company says it follows. For many US employer-based programs that is a written practice built from the recommendations in SNT-TC-1A. Some clients require CP-189. Some work is done under a central certification scheme such as ISO 9712, with a body like PCN or CSWIP standing behind the certificate rather than the employer.
Those are not interchangeable labels. An auditor who asks "show me the written practice" is asking for the document this employer uses to decide training, experience, examinations, and vision testing. A downloaded copy of a recommended practice, with no evidence it was adopted, is not that document.
If you cannot point to the revision that was in effect, you do not yet have a program record. You have a reference book.
The person, method by method
Personnel records fail in a predictable way. A spreadsheet has a name and a single date. The technician holds two methods. Only one date is tracked. The vision exam sits in a different file, on a different anniversary, and nobody's list includes it.
A record that survives the question is one row per qualification:
- scheme
- method
- level
- the employer or the certifying body, depending on the scheme
- issue and expiry
- the vision examination, on the interval the written practice requires
- the attachment, so the PDF is evidence for the row and not the row itself
Employer-based certification is the employer's act. The certificate is only as current as the file behind it. Central certification still has to be checked against the job. Holding a card is not the same as being assigned inside its scope.
SpecNDT keeps that register. The decision to certify, or to accept a central certificate for a given scope, stays with the people who are supposed to make it. See technician certification records for how the register is structured.
The procedure that was current that day
Auditors ask which procedure applied to the examination, and they mean the revision in force on that date. The revision saved last Tuesday, or the one a technician still has printed from last year, is a different document.
A shared drive is bad at this. It will happily store UT-weld-final.pdf, UT-weld-final-v2.pdf, and UT-weld-USE-THIS.pdf. The inspection record has to point at one of them, and the team has to know which of them people were allowed to use.
Superseded procedures should remain readable. They should stop being the file that opens by default.
The report, attached to an asset
A report with no asset is a story. Oil and gas work is full of assets that will be inspected again: vessels under API 510, piping under API 570, tanks under API 653, and the NDT done in support of that work. The next person needs the earlier report on the equipment, not in a folder named for the year it was scanned.
The report should also name the technician. That name should resolve to a qualification that was valid for the method on that day. If it does not, the audit finding is already written.
SpecNDT ties those together in inspection history. It does not calculate remaining life, and it does not take the place of an authorized inspector.
The gap, already listed
The last thing an auditor asks is some version of "what did you do about the thing that lapsed." An expired certification, a vision exam past its interval, a procedure that was used after it was superseded, a calibration that was out of date. Teams that scramble are teams that discover the gap in the room.
A team that can list what is overdue, before anyone visits, is a team that is already closer to compliant. That is what SpecNDT is for. The week of the audit should look like a normal week. That is the idea behind what audit-ready means.
If that is the problem you have, request access. If you already have it, Login opens the application. This site does not.