NDT Pilot vs. basic document portals
Document portals solve delivery: customers log in and download files. But the documents had to come from somewhere, a portal does not produce, review, approve, or control them.
| Criteria | NDT Pilot | Basic customer document portals |
|---|---|---|
| Connected customer, site, asset, and inspection records | Available | Documents only |
| Work-request lifecycle | Available | Not applicable |
| Scheduling and dispatch | Available Date-based assignment with qualification visibility; visual calendar planned | Not applicable |
| Field usability | Partially available Browser-based technician portal; photos and offline are planned | Not applicable |
| Qualification visibility | Available Register with levels, methods, expiry; auto alerts planned | No |
| Equipment and calibration tracking | Available Due dates and certificates; auto alerts planned | No |
| Evidence traceability | Partially available Linked records today; per-reading photos planned | Files stored but unlinked |
| Technical review workflow | Available | No |
| Report approval | Available Recorded typed signature with reviewer and dates | No |
| Revision control | Available Status lifecycle, superseded documents retained | Upload discipline |
| Customer access | Partially available Scoped portal live; external accounts in current release | Core purpose, download only |
| Quotation management | Available | No |
| Invoicing | Available Status tracking; payment processing not included | No |
| Audit history | Available | Download logs |
| Implementation requirements | Guided onboarding Scope-dependent, see Implementation | Light, upload documents |
Basic customer document portals: genuine strengths
- Simple, purpose-built customer file delivery
- Familiar download-style user experience
- Straightforward permissions on folders
Basic customer document portals: where it strains
- No request intake, scheduling, field capture, review, or approval, delivery only
- Version clarity depends on upload discipline
- No asset history, files sit flat, not connected to the asset they describe
- No audit trail of workflow events behind each document
- The provider still produces and controls documents somewhere else
When basic customer document portals is the right choice
As a delivery channel for finished documents when producing and controlling those documents is already solved.
Migrating from basic customer document portals
The delivery role is replaced by the customer portal, which is connected to the live workflow rather than fed by manual uploads. Customers see released reports, statuses, and asset history.
See the onboarding processFrequently asked questions
Alternatives are described generically; no named competitor claims are made. Validate any platform against your own requirements. See also the main comparison and the permissions documentation.
Bring your current tools to a demonstration
We will map your existing process onto NDT Pilot honestly, including where staying with your current tool makes sense.
Book a demo