For a nondestructive testing (NDT) company, the inspection report is the product. The client paid for a technician to stand at a weld or a part, but what they keep, file and hand to their own auditor is the piece of paper that says what was examined, how, by whom and with what result. If the report is thin, late or wrong, the work behind it might as well not have happened.
This guide covers what a report has to carry, why your own controlled form matters to the people receiving it, how a report should trace back to the technician's certification and the equipment's calibration, and why getting it signed before you leave site saves an argument later.
What the report has to carry
The governing document decides. That may be a construction code, an in-service inspection code, a customer specification or the contract itself, and they differ. ASME Section V is a useful reference point because so much pressure equipment work runs through it, and it sets out record contents plainly.
In the 2025 edition, Article 1, T-190(a) says documentation is prepared as the referencing Code Section specifies, and sets a minimum for every examination record. In outline:
- the date of the examination
- the name or identity of the person who performed it, and their certification level where one applies
- identification of what was examined: weld number, serial number or another identifier
- the method, the technique, and the procedure identification with its revision
- the results
Each method article then adds its own items on top of that minimum. The table below is our own outline of a few of them, to show the kind of detail a generic form tends to miss.
| Method | Where | Examples of what is added |
|---|---|---|
| PT | Article 6, T-692 | Penetrant type; each material's manufacturer, product and batch number; a map or record of indications; material and thickness; lighting equipment |
| MT | Article 7, T-793 | Equipment and type of current; particle type; a map or record of indications; material and thickness; lighting equipment |
| UT | Article 5, T-592 | Instrument and search unit identification with serial numbers; beam angles; couplant; calibration block; reference level and calibration data; what was scanned |
| RT | Article 2, T-291 | Technique details such as number of exposures, source or voltage, source size, distances, material and weld thickness, film type and single- or double-wall exposure and viewing |
Our summary of ASME Section V, 2025 edition. Not complete: read the article for your method and the referencing Code Section before you build a form.
Two more points from T-190 are easy to overlook. How long you keep examination records, and the images or scan files behind them, is set by the referencing Code Section rather than by Section V itself. And digital images and review software have to be kept in a record system that can store and retrieve them securely for that period.
Why your own form matters to clients
It is tempting to think the client only cares about the result. In practice they care a great deal about the form, for reasons that are about their work rather than yours:
- They file it. Your report becomes part of their quality record. A report that arrives in the same layout every time can be reviewed in minutes. One that changes shape from technician to technician has to be read line by line.
- Their auditor reads it later. A controlled form, with a form number and revision printed on it, tells a reader years from now exactly which version of your form the report was written on, and that the form was under control.
- Acceptance wording matters. The line that says what the part was accepted against, and to which revision of which procedure, is the line a client's engineer reads first. It should say the same thing, in the same words, every time.
- It is your name on it. Clients judge a firm by its paper. A clean report on your letterhead with every field filled reads as a firm that has its program under control.
That is why it is worth building the form once, properly, around the code and your procedures, and then keeping it under revision control rather than letting each technician adapt their own.
Traceability: the technician and the equipment
A report is only as good as what stands behind it. Two things in particular get checked when a result is challenged:
The technician's certification
T-190 asks for the examiner's identity and certification level. What an auditor actually wants to know is whether that person was certified in that method, at that level, on that date. A report that names the technician should let you show their certification was current when the work was done, not just today. See the guide to tracking NDT certifications for keeping those records.
The equipment's calibration
The UT and MT articles ask you to record which instrument, search unit or yoke was used, and for UT the serial numbers. That identification is there so the equipment's calibration can be traced. If a piece of equipment is later found out of tolerance, you need to find every report it touched, and a report that names the kit by serial number is how you find them. The equipment calibration guide covers the other half of that.
A snapshot, not a live link
One subtlety: the report should record what was true when it was written. If the procedure is revised next month, the report must still say which revision the work followed. If the form is revised, the report must keep the version it was written on. A digital system that quietly updates old reports when the procedure or template changes is worse than paper.
Sign-off on site
ASME Section V does not list a customer signature among its minimum record contents, but many contracts and customers ask for one, and there are good reasons to get it even when nobody insists:
- The customer's representative sees what was examined and what was found while they are standing next to it.
- Any disagreement about scope, extent or results surfaces on the day, when it can still be checked, rather than weeks later at invoicing.
- A signed report is evidence that the work was delivered, which shortens the conversation when the invoice goes out.
If the customer declines to sign, find out why and write it down. A decline with a reason is useful: it tells you exactly what to fix before you send the report again.
When a signed report turns out to be wrong, do not edit it under the signature. Issue a new report that says which one it corrects, and get that one signed.
Where paper reports go wrong
Most report problems are not technical. They are transcription and memory: a batch number copied wrong, a serial number left blank, a photo that never made it off the phone, a report typed up on Friday from notes made on Tuesday. Writing the report on site, on the form, with the equipment and procedure already filled in from the job, removes most of them.
A short checklist for any report form:
- Does it carry every item your governing code or spec asks for?
- Does it have a form number and revision, printed on every page?
- Does the procedure line record the revision, and stay fixed when the procedure is revised?
- Does it identify the technician, and can you show their certification was current on the day?
- Does it identify the equipment by serial number, and can you show it was in calibration?
- Does it have space for photos and an indication map?
- Is it reviewed and approved before it goes to the client?
- Is it signed by the client, where the contract asks for that?
How TRACE handles it
In the Projects module, every job carries field reports for MT, PT, UT, ET, RT and VT, each with a report and a technique sheet. TRACE ships a base form for each, and you can change any of it or build your own from blank: your sections, your fields, your acceptance wording. Each saved form gets a form number and revision, printed at the foot of every page of the report. The specification line is picked from the procedures on your NDT program register, and what prints is a snapshot of it, so a new procedure revision never rewrites a filed report. Each report also keeps the version of the form it was written on.
A technician crewed on the job and certified in the method writes the report on the TRACE Mobile app, on Android or iPhone, with photos, with or without a signal: a report started out of range waits on the phone and sends itself once there's signal again — within a couple of minutes while the app is open, or when it's next opened. The office approves it, and the PDF pulls in the job's equipment with its calibration standing at the time. The customer can sign on the phone there and then, or by an emailed link, and can decline with a note saying what needs fixing. The signature, name, title and date print on the PDF, and from then on the report is frozen: a correction is made as a revision with the same number and its own signature, and the signed original is kept, marked superseded. Approved reports appear in the client portal, with a button for the client to mark each one received. TRACE keeps the record; what the report must contain is still set by your code, your procedures and your Level III.
Frequently asked questions
What must an NDT inspection report include?
Whatever the code, specification or contract you are working to says. Under ASME Section V (2025 edition), Article 1, T-190(a) sets a minimum for every examination record: the date, who performed the examination and their certification level where one applies, what was examined, the method, technique and procedure with its revision, and the results. Each method article then adds its own items, such as penetrant batch numbers for PT or instrument and search unit serial numbers for UT. Other codes and customer specifications set their own lists, so check the one that governs the job.
Why do clients care whose form the report is on?
Because the report goes into their quality record, not yours. A client who receives the same controlled form, with the same layout, form number and acceptance wording every time can file and review it quickly, and an auditor reading it later can tell which revision of your form it was written on. A report that changes shape from job to job, or that the client has to cross-reference against a spec by hand, costs them time and invites questions.
Is a customer signature on an inspection report required?
Not by the ASME Section V minimum record contents, which do not list one. Many contracts and customers ask for it, and it is useful either way: a report signed on site by the customer's representative settles what was examined and what was found on the day, rather than at invoicing. Check your contract for whether a signature is required and whose it must be.
What happens if a signed report turns out to be wrong?
Do not edit it under the signature, because the signature would then sit on a version the customer never saw. The usual practice is to issue a new or revised report that says which report it corrects, and have that one signed. Keep the original on file.
Checked against
- ASME Boiler and Pressure Vessel Code Section V, 2025 edition: Article 1, T-190 (records and documentation); Article 2, T-291; Article 5, T-592; Article 6, T-692; Article 7, T-793
This guide summarises the documents above in our own words to help you find your way around them. It is not a substitute for them: requirements change between editions and contracts add their own, so check every figure against your own licensed copy and your written practice before you rely on it.
Named for reference only. TRACE is an independent product: it is not affiliated with, endorsed by, sponsored by or accredited by ASME (publisher of the Boiler and Pressure Vessel Code), Google (Android) or Apple (iPhone), or by any other organization whose standards or programs it describes. Their names and marks are their own.