Skip to main content
NDT Pilot

A controlled path from signup to production

Implementation is a staged review, not a big-bang switch. Every step is confirmed with you before the next begins, and production activates only after a reviewed pilot.

Ultrasonic flaw detector, thickness gauge, probes, and calibration block on a workbench

The onboarding process

  1. 01

    Discovery and workflow review

    We review how your company handles requests, scheduling, field records, review, release, and billing today, and map it onto NDT Pilot's workflow.

  2. 02

    User and role definition

    We define who needs access and at what role: administrators, coordinators, technicians, reviewers, and finance.

  3. 03

    Customer, site, and asset setup

    Your customers, sites, and assets are set up in the registers so work requests reference them instead of retyping them.

  4. 04

    Template and technique-sheet configuration

    Existing procedures and technique sheets are organized in governed libraries with revisions and approval status.

  5. 05

    Data import and reconciliation

    Existing customer, asset, and personnel records are imported and reviewed with you for accuracy before use.

  6. 06

    Sample inspection workflow

    We run a representative request through the full cycle, request, assignment, field report, review, approval, using synthetic or sandbox data.

  7. 07

    Report output review

    You review the resulting report records, statuses, and audit history against your customer and quality requirements.

  8. 08

    User training

    Coordinators, technicians, and reviewers each get a focused walkthrough of their own views and actions.

  9. 09

    Pilot launch

    A first real workflow runs in production with close support, starting with a limited scope.

  10. 10

    Controlled production activation

    Once the pilot is reviewed, the full team activates with the workflow configuration confirmed during the pilot.

What implementation effort depends on

There is no fixed timeline that would be honest to quote here. Implementation effort depends on:

  • The number and variety of report types you use
  • How far your workflow differs from the request → review → release cycle
  • The number of users and their roles
  • The NDT methods in scope
  • The volume of customer, asset, and report records to migrate
  • Any integrations with existing systems
  • Customer-specific requirements, formats, and approval rules

We scope this with you during discovery so the effort estimate reflects your company, not a generic average.

Start with discovery

Request a demo and tell us about your current process, discovery is the first step of the demonstration itself.

Book a demo