- Capture the method-specific fields at the point of test, not at the office desk.
- Every result needs the technique, equipment, calibration or reference block and procedure reference behind it, recorded per test point.
- Weld evidence is photographic and location-specific, so the photograph has to carry the location.
- The report should be generated from the captured record instead of retyped from notes.
What good NDT and welding reporting captures
The best workflow for NDT and welding inspection reporting captures the method-specific record while you are still at the joint: technique, equipment, calibration or reference block, procedure reference, acceptance criteria and a result for each test point, each one linked to its evidence. The report is then generated from that record rather than retyped from notes. Much of the work happens where there is no signal, in a fabrication shop or on a remote spread, so the capture has to be local first, which is the case an offline inspection app has to cover.
That sounds obvious until the fields change with the method. Dye penetrant, magnetic particle, ultrasonic and radiographic examination do not share one field set, even on the same joint, so the record has to flex without becoming a different document.
- A field set that changes with the method, not one generic checklist
- Technique and equipment identification recorded against the result
- Calibration or reference block details for the equipment used
- The procedure reference and the acceptance criteria the result is judged against
- A result for each test point, not one verdict per weld
- Traceability from the report line back to the record
Where generic checklist software breaks down
Checklist software is built for routines that repeat identically. NDT is not one of them: the method dictates the fields, and the fields change with the technique, the client specification and the job. A developer asking exactly that question on r/nondestructivetesting ran into the same answer from several directions.
The test is not how many fields a tool ships with. It is whether you can define your own field set once and reuse it, which is the ground a custom inspection checklist app has to cover. Those questions are worth settling before you commit, and they sit alongside the wider criteria for choosing inspection software.
Weld evidence is photographic and location-specific
No weld result means much without the joint it belongs to. Weld 14 on a spool is not weld 14 on the next spool, and an indication photographed with no location caption proves very little later. The evidence has to carry the location: the joint identifier, the item, the area photographed, and the test point the image supports. Keeping an inspection report photo tied to the finding it proves is the same discipline.
A second photograph of the setup, showing the equipment and the reference block in position, is often what makes the first one credible. Both have to be taken while you are standing there.
- Weld or joint identifier in the caption, not only in the filename
- The item and the area the photograph shows
- The test point or reading the image supports
- A setup shot showing the equipment and reference block
A field-to-report example
A pipe spool leaves a fabrication shop with butt weld W-14 on a 168 mm carbon steel line. The specification calls for ultrasonic examination of the full weld length, so the inspector sets up at the joint.
On the phone the technique is set to ultrasonic examination. Equipment serial, probe details and the reference block are entered once, with a calibration check before the scan and after it, and the procedure reference attached at the same time.
Three test points are recorded separately, each with its result and reading. The middle point carries an indication at a stated offset from the datum. The inspector photographs the weld cap with the location marked and the setup with the reference block, links both images to that point, records a measurement in millimetres, and raises a finding recommending repair and re-examination. The report then follows that field record, and the shape a client expects to read is set out in an inspection report example.
| Approach | What it holds | Where it costs you |
|---|---|---|
| Paper field book, typed up later | Fast to write at the joint | Method fields, calibration and photographs are rebuilt at the desk, so the report can drift |
| One fixed checklist template | Consistent structure on routine jobs | Breaks as soon as the technique changes or a client wants different fields |
| Photographs in a folder plus a spreadsheet | Cheap and flexible | The link between image, reading and weld number lives in someone's memory |
| Inspection Report | Guided and custom checklists, photographs tied to the result, measurements, findings with evidence, signatures, PDF and Word export with Pro | A general record: you define the method fields, and it holds no standards library |
How Inspection Report handles this
Inspection Report is built around one continuous record. Start from a template or build a custom checklist in Pro with typed fields and required responses, so method-specific parts are defined once and reused. Photographs are captured or imported, captioned and linked to checklist items or findings, and Pro adds annotation. Measurements hold a value and its unit next to the result. Findings keep their evidence and can be resolved or reopened later.
Where it stops matters too. It does not calculate, does not hold a standards library and does not decide acceptance criteria. It records what the inspector enters and does not certify a weld. There is no assignment of corrective actions and no integration with other systems. If you need an NDT package with technique libraries, this is not that. It produces a branded PDF or editable Word report from the field record with Pro.
Test it on one real joint
Pick the next weld that needs examination, build or choose the checklist you would actually use, and run the inspection from capture through to export without leaving the app to type anything up. Time it from opening the inspection to holding the finished report, then compare it with what the job costs you today.
If the field set will not fit the form, you have learned something useful before paying. If it fits and the report comes out in the order your client expects, the question is settled. The same principle runs through a construction safety inspection app, where location replaces the joint.
