One connected workspace for your inspection operation
NDT Pilot is a workflow platform for non-destructive testing companies. It connects customer requests, job planning, field records, technical review, controlled report release, asset history, and billing, so information is entered once and reused at every stage.
What NDT Pilot is built to do
Capture trustworthy field information
Move reports through controlled technical review
Deliver approved documents faster
Give customers an organized inspection and asset history
Without forcing every inspection company into the same rigid process
NDT Pilot supports and documents the inspection workflow. Physical inspections and technical decisions remain the responsibility of appropriately qualified and authorized personnel.
Enter approved job information once and reuse it across scheduling, fieldwork, reports, delivery, and billing.
Give technicians a clear assigned job package with customer, site, asset, scope, and method details in one place.
Connect readings, evidence, findings, and reports so every conclusion traces back to its job. (Per-reading photo attachment is planned.)
Make review queues visible so required corrections and waiting approvals are obvious, not buried.
Preserve approval and revision history with recorded reviewer, dates, and signature on every report.
Give customers self-service access to their permitted released reports and asset history.
Connect completed work to quotations and invoices so billing follows the job instead of someone's memory.
Let administrators configure workflows without creating uncontrolled document versions.
Maintain a searchable audit history of who did what, to which record, and when.
Why inspection companies choose NDT Pilot
Connected request-to-report records: scope entered once flows to every stage.
Configurable inspection workflows rather than one rigid process for every company.
Role- and tenant-scoped access: your records stay yours.
Controlled review and approval history with recorded sign-off.
A field-focused technician experience with assigned job packages.
Personnel qualification and equipment calibration visibility before dispatch.
Customer access to permitted released reports.
Traceable quotation and invoicing handoff from completed work.
Governed technique sheets and document libraries with revisions.
Transparent implementation and migration, staged with your review.
A searchable audit history behind every workflow action.
Reduced dependence on Word, Excel, email, and shared drives.
What runs automatically in the background
These automations run on the platform today. Each one leaves a record your team can review, and none of them approves, releases, or issues anything without a person.
Calibration & certification alerts
Runs on a daily schedule
Checks equipment calibration due dates and technician certification expiry dates, then emails administrators and the company contact about anything due within 30 days or already overdue.
Items also appear in the dashboard's Needs attention strip until resolved.
Technician availability sync
Runs when a work request changes, plus a daily check
Marks technicians as on assignment when they have a scheduled or in-progress job, and returns them to available when the work is complete.
Off-duty technicians are left untouched, and each technician can hide their on-site status from the dashboard.
Draft invoice on approval
Runs when a report is approved
Creates one draft invoice per work request from the linked customer, PO number, and quotation amount.
Invoices are always drafts for finance review. It can be switched off in company settings, and duplicates are skipped.
Approval notification
Runs when a report is approved
Emails the customer's contact that their report is approved, with the report number and a plain-language result summary.
Skipped when no customer contact email is on file.
Review, approval, and document control
Review queues and corrections
Submitted reports wait in a visible queue. Rejection returns the report with a recorded reason, no silent rework.
Approval authorization
Approval records the signature entry, reviewer, review date, and approval date on the report. The typed-name signature is traceable but is not a certificate-based regulated e-signature, validate it against your QMS requirements.
Controlled release
Only approved reports are delivered. Drafts never reach customers.
Revision and withdrawal history
Superseded technique sheets and report statuses are preserved, not overwritten.
Audit events
Every submit, review, rejection, approval, and delivery is logged with user and timestamp.
Customer-visible vs internal
Customers see approved deliverables and permitted findings, never internal QA comments, staff-only evidence, or drafts.
What your customers see
Authorized customers can:
View their active inspection requests
Track understandable statuses
Access their approved reports and search report history
Review their associated assets and permitted findings
Retrieve their permitted invoices
Contact your inspection company
What customers never see
Drafts, internal QA comments, staff-only evidence, internal costs and margins, and other customers' information.
Customer portal | NDT Pilot
My requests
WR-2026-014 · UT thickness survey
Active
Released reports
RPT-2026-085 · approved Sep 16, 2026
Available
My assets
Pressure vessel PV-207 · inspection history
History
Synthetic preview data shown for illustration.
The field inspection experience
In the technician portal, crews can:
Review assigned work with the approved job information in context.
See customer, site, asset, scope, and inspection-method details on the job.
Enter readings and observations as structured findings.
Record the overall result, conclusion, and recommendations.
Save drafts and submit the completed report for review.
See returned reports and required corrections from the reviewer.
Keep working when the signal drops: changes are saved on the device and synced when a connection returns. The job must be opened once while online.
Downloadable job packs and photo annotation: Planned.
The modules
Each module carries an outcome, not just a feature name. Labels show what is available today versus planned.