Field Inspections for NDT Technicians

Technicians receive job details by phone or text and hand back paper or word-processor reports. Required readings, photographs, and documents go missing, and the office cannot see what was actually captured on site.

• Field technicians
• Inspectors
• Coordinators

Used by the technician on site, and in the office while writing up, from mobilization until the report is submitted.

• Assigned work request
• Customer, site, asset, scope, and method details
• Inspection date and location
• Overall result
• Findings and observations

• Review assigned work with the approved scope in context
• See customer, site, asset, and method details on the job
• Record inspection date, location, overall result, and findings
• Save a report in progress and submit it for review
• See submitted and returned reports

• Required report fields must be completed before submission
• Submitted reports enter the review workflow and are no longer editable as drafts
• Submission is recorded in the audit trail

Draft

Being written, private to your organization.

Submitted

In the review queue.

Rejected

Returned with a recorded reason for correction.

1. 01

   Input

   Approved scope and records arrive

2. 02

   User action

   Review assigned work with the approved scope in context

3. 03

   Validation

   Required report fields must be completed before submission

4. 04

   Output

   The module's recorded outcome

5. 05

   Next step

   Handed to Inspection Reports, Review and Approval

A submitted field report that lands in the review queue with the requesting context attached.

Photo and file attachment per reading, structured method-specific forms, and offline capture are planned. Today the technician experience is browser-based and requires a connection.