Twelve methods, field to report
Non-destructive testing
Readings are written on paper on site and retyped into a report days later, in an office, by someone who was not there.
How it works
- 01
Plan the examination
What has to be examined, by which method and to what extent, derived from the code and the ITP rather than decided per shift.
- 02
Capture it in the field
A tablet that works offline in a yard with no signal, and syncs when it finds one. The inspector records what they see, where they see it.
- 03
Evaluate against the acceptance criteria
The criteria come from the governing standard and edition, attached to the examination — not chosen afterwards to fit the finding.
- 04
Issue the report
Sealed, verifiable by a third party, and immutable. A correction produces a superseding revision; the original stays readable.
What it covers
Twelve methods
VT, PT, MT, RT, UT, PAUT, TOFD, ET, LT, PMI, hardness and ferrite.
Offline field capture
Built for a site with no coverage, not for a demo on office wifi.
Inspector qualifications
Method, level and expiry, checked at the point of signing rather than at the audit.
Instrument validity
An examination cannot be recorded on an instrument whose calibration has lapsed.
Indications and disposition
What was found, where, how big, and what was decided about it.
Public verification
A QR on the report resolves to a page that confirms it is genuine and current.
The report is a record, not a template
A great deal of NDT reporting is done by opening last job’s file and editing it. It is fast, and it carries last job’s mistakes forward — the wrong procedure revision, the wrong acceptance criteria, occasionally the wrong client.
An examination record built from the plan cannot inherit those, because it never had them. The procedure, its revision, the acceptance criteria, the inspector’s certificate and the instrument’s calibration are all bound to the examination at the moment it is performed. The report is a rendering of that record, not a document that exists independently of it.
This is also what an ISO 17025 assessment actually looks at. Not the report — how the report came to say what it says.