Report turnaround
Why your inspection reports reach the client late
NDT reports run late because the delay sits in hand-offs, not in the field: re-typing readings, chasing a reviewer, hunting for the latest template and the right probe serial. Capture method-specific data once against the job, route it through inspector, reviewer and approver stages everyone can see, and issue it in the client's own format.
Each report moves from field data to Level II draft, Level III review and issue. Select a report and advance it.
- Field data: Module B butt welds (RT, ASME Section V).
- Level II draft: Tank floor screening (MFL, API 653); Exchanger bundle (ECT, ASME Section V).
- Level III review: Crude unit piping (UT thickness, API 570); Sphere shell nozzles (MT, ASME Section V).
- Issued: Pipe rack welds (VT, AWS D1.1).
Panels in the preview: Certifications, Calibration, Reports, Jobs, Sales & cash. Names and statuses are sample data.
Where a finished scan turns into a late report
The technician usually knows the result before leaving the weld. What follows is the slow part: readings in a notebook or on a wet clipboard, photos on a personal phone, then an evening in the site cabin or a morning in the office re-keying everything into a Word or Excel template that has been edited by too many hands. The Level II signs a printout, the Level III reviews it when they reach it, and the client receives a PDF well after the crew has moved on.
During a turnaround the problem compounds. Reports from several methods pile into the same review queue, the reviewer is also on the unit, and nobody can say which reports are drafted, which are waiting for review and which are approved but sitting unsent. The client chases by email, the office chases the technician, and the technician is already mobilising for the next job.
Late is often the lesser problem. Re-keying is where a thickness reading gets transposed, last week's probe serial is copied forward, or the acceptance standard in the header belongs to a different client. A report that arrives late and wrong costs far more than one that is merely late.
Evening re-typing
Technicians or office staff rebuild each report from field notes, which delays issue and invites transcription errors.
Invisible review queue
Nobody can see at a glance which reports wait on a reviewer and which are approved but not yet sent.
Template drift
Several versions of the client's format circulate, and the wrong one goes out often enough to be noticed.
Equipment from memory
The instrument and probe on the report are typed from recollection rather than from what was actually issued.
Clients doing the chasing
The client's engineer asks for reports before your office even knows they are overdue.
What slow reporting does to the business
Delayed payment
Many clients will not approve an invoice until they hold the report, so every report left waiting is cash left waiting too.
Rework and re-issue
Transcription errors caught by the client mean corrected revisions, fresh signatures and an awkward explanation of what changed.
Reviewer exhaustion
Your Level III spends evenings formatting and chasing rather than checking technique, coverage and sizing, the part only they can do.
Lost tender ground
Report turnaround is something clients compare between contractors, and a reputation for slow paperwork follows you into the next bid.
Capture once, review in the open, issue in their format
The NDT Reports app opens a method-specific report against the job, with work order, client request, contract, drawing, WPS and procedure references carried across. Each method has its own fields and numbering: a probe calibration table for UT, source, technique and IQI details for RT, focal laws for PAUT, readings by direction for thickness surveys. The field app is an installable web app that works offline and syncs when signal returns, and it shows the technician the equipment actually issued to them.
Every report moves through draft, in progress, review, approved and sent, with inspector, reviewer and approver signatures and a field for a third-party or authorised inspector. Because the stages are tracked, operations and QA can see which reports are stuck in review, which are approved but unsent and which jobs have no report yet. Output uses your versioned company templates in Excel, Word, PDF or HTML, with Excel fields mapped to the cells your clients already recognise.
Software cannot make a careful review faster than the reviewer. What it removes is the waiting around the review: the re-typing, the template hunt and the uncertainty about where a report sits. The Level III still checks technique and acceptance against the code, such as ASME Section V or AWS D1.1, and still decides whether a report goes back to the technician.
Open from the job
The report is created from the work order, so job, site and code references arrive filled in rather than retyped.
Record at the weld
The technician picks the method, captures readings, weld lines and photos, signs on screen and previews the PDF before submitting.
Work the review queue
Reviewers see submitted reports in one queue and approve or return them with comments, with the stage visible to everyone.
Issue in their template
Approved reports go out in the client's versioned format, and the record shows when each one left the building.
Watch the backlog
Operations checks reports approved but unsent and jobs with no report, and clears them before the client asks.
Before and after
| Without a system | With Atlantis NDT |
|---|---|
| Readings re-keyed from a notebook into an old template. | Method-specific fields filled once at the weld, offline if needed. |
| Reports waiting in a reviewer's inbox nobody else can see. | A shared review queue with a visible stage on every report. |
| Several versions of the client's format in circulation. | Versioned templates, with a record of which was in use and when. |
| The client chasing reports by email. | Approved-but-unsent reports listed for operations to clear. |
The modules doing the work
Each module is part of the same platform, so a certification, an instrument, a job and a report are linked records rather than files in different places.
- NDT Reports
Method-specific report types, a staged review workflow, offline field capture and versioned client templates.
- Project
Holds the job's PO, codes, scope, acceptance criteria and task-level procedure and WPS references the report draws on.
- Asset Management
Supplies the instruments and probes issued to the technician, so the report names the kit actually used.
- Procedures
Provides the approved procedure revision the report quotes by number.
Questions owners ask
Why are our NDT reports late even when the field work is on schedule?
Usually because each report passes through manual hand-offs after the scan: transcription, formatting, printing for review and chasing signatures. Removing the re-typing and making the review stage visible attacks the delay where it actually sits.
Can technicians complete reports without signal on site?
Yes. The NDT Reports field app is an installable web app that stores drafts and photos on the device and syncs when a connection returns.
Can we keep the report layouts our clients insist on?
Yes. Company templates can be Excel, Word, PDF or HTML and are versioned. Excel templates are filled by mapping report fields to cells, so the client keeps the layout they know.
Who signs off the report?
Inspector, reviewer and approver each sign within the workflow, and a third-party or authorised inspector can be recorded where the client's inspector witnesses the work. Who may hold each role follows your written practice.
Does faster reporting mean less review?
No. The technical review stays with a qualified Level II or Level III. The aim is to take the clerical waiting out of the process, not the check. Send a redacted sample report and we will rebuild it in a demo.
See it on your own records
Bring a sample of your certifications, equipment list or reports and we will show the workflow configured to how your company runs. Demo on request.
Speak to an ASNT NDT Level III
Discuss your inspection requirements with Atlantis NDT. Include the asset, method, location and documents you need reviewed.