NDT ERP Buyer's Checklist: 25 Questions to Ask Before You Sign

Most NDT companies choose inspection management software the way they choose a truck: they sit through a demo, like what they see, and sign. The problem is that a demo is built to show the software's best day — a clean UT report generating in thirty seconds, a dashboard full of green checkmarks. It is never built to show what happens eighteen months in, when you need to add phased array to a shop that has only ever run conventional UT, when a client auditor asks you to produce a named technician's full certification package in the middle of a turnaround, or when the vendor's pricing changes and you discover your own inspection data is harder to get out of the system than it was to put in.

This is a procurement document, not a sales page. It is 25 specific, sharp questions organized by the risk category they actually protect against, meant to be sent in writing to any vendor you are evaluating — including us. If a vendor cannot answer a question on this list clearly and in writing, that is itself the answer. The goal is not to find software with the most features; it is to find software that will not become a liability the first time an ASNT Level III reviews your quality system or a client runs a for-cause audit after a field failure.

It's worth saying plainly why a checklist beats a demo for this specific purchase. A demo is a controlled environment: clean sample data, a single happy-path workflow, a salesperson who knows exactly which button not to click. Your actual operation is messier — ten technicians certified across six different methods, three client contracts each demanding a slightly different report format, an Epoch 650 that goes out for calibration every six months and a fleet of reference blocks that need their own tracking. The questions below are designed to surface how the software behaves under that mess, not under a curated slideshow. Put them in writing, send them to two or three vendors side by side, and score the written answers — not the enthusiasm of the person answering them.

Data Model and Method Coverage

The first failure mode in NDT software isn't security or support — it's a data model that was designed for generic field service work and has NDT methods bolted on as free-text fields. That shows up quietly at first (a UT report missing a dedicated field for couplant type or scan pattern) and expensively later (you can't query five years of RT reports for a specific IQI sensitivity level when a client disputes a weld).

• 1. Does the system support every NDT method we currently run as a native, structured data type — not an unstructured attachment? UT, RT, MT, PT, VT, ET, TOFD, and phased array each require different mandatory fields: RT needs film or digital density and IQI sensitivity per ASME Section V Article 2; UT needs calibration block ID, reference reflector size, and scan pattern; MT needs field strength, yoke spacing, and demagnetization confirmation. A system that treats all of this as one generic "notes" box will not hold up under a client's technical audit.
• 2. When we add a method later — say phased array to a shop that has only run conventional UT — does that require a paid change order to the vendor, or can our own admin configure the new field set? This tells you whether you're buying a product or subscribing to a permanent consulting relationship.
• 3. Can the system output reports in the format conventions our clients already require — API 510 thickness survey layout, ASME Section V Article 4/5 UT report format, AWS D1.1 weld inspection report format — without us rebuilding templates from a blank page?
• 4. Does the system separate raw inspection data (readings, indications, scan data) from the report document itself, so a narrative correction doesn't require altering the underlying data record? This distinction is what makes a report defensible in an audit trail sense — readings should be immutable once captured, while report language can go through review and revision with its own history.
• 5. Can we restrict what non-technical staff (schedulers, billing admins) see — job status and scheduling without exposure to restricted technical data — and can we configure that boundary ourselves without a support ticket?

Certification and Personnel Qualification Tracking

This is the category where spreadsheets fail most visibly, and where auditors look first. An NDT company's core deliverable is the qualified judgment of a certified technician; if the software can't prove that judgment was qualified at the moment the report was signed, everything downstream is exposed.

• 6. Does the system track certification by method AND level individually — PT Level II and UT Level II are separate qualifications with separate expiration dates — rather than a single "certified" flag per employee?
• 7. Will the system automatically block report sign-off by a technician whose certification in that specific method has lapsed, rather than relying on someone remembering to check?
• 8. Does it distinguish between certification types as separate, non-interchangeable fields — an employer-based SNT-TC-1A certification, an ASNT NDT Level III credential, and, where a client contract specifically requires it, an ISO 9712 or PCN certification? These schemes are not the same thing and conflating them in a personnel file is a documented audit finding on refinery and pipeline work.
• 9. Can it track the annual near-vision acuity check separately from the 3-to-5-year method recertification cycle, since SNT-TC-1A recommends annual vision screening independent of the broader recertification interval?
• 10. If a client's QA representative asks to see a specific technician's full certification package during a turnaround, can we produce it in under two minutes — training hours, exam scores, experience log, vision test date — rather than by pulling physical folders from a filing cabinet three states away?

Calibration, Equipment, and Traceability

Equipment traceability is where a paper trail becomes a legal document. If an instrument is later found out of calibration tolerance, you need to know, immediately, every report that instrument touched — not guess.

• 11. Does the system track calibration due dates for every serialized instrument — Epoch 650s, OmniScan units, reference blocks, yokes — with the NIST-traceable calibration certificate attached, not a note in a shared spreadsheet someone has to remember to update?
• 12. Will the system prevent a technician from closing out a report against an instrument whose calibration date has expired, the same way it should for a lapsed certification?
• 13. Can probe and cable serial numbers be logged as line items against specific inspections, so that if a probe is later found defective or out of tolerance, you can pull a complete list of every report where it was used, in minutes rather than days?
• 14. Does it handle consumable and reference-standard traceability — couplant batch numbers, IQI serial numbers, penetrant and developer lot certificates — where a client specification requires it, which is routine on nuclear and aerospace-adjacent work and increasingly requested on major refinery turnarounds?

Integration, Data Portability, and Exit Terms

The single most consequential question in this entire list is what happens to your data the day you decide to leave. Vendors rarely volunteer this, and it belongs in a contract clause, not a verbal assurance from a sales rep.

• 15. Can we export our complete historical data — every report, every reading, every certification and calibration record — in a non-proprietary format (CSV, JSON, searchable PDF) on demand, at any point, not just at contract termination?
• 16. What is the actual mechanism and realistic timeline for migrating our existing archive into the new system, and will migrated historical records remain searchable and reportable, or do they just become static, unindexed PDFs sitting in a folder?
• 17. Does the system offer a documented API or integration path to our accounting platform, a client's asset management system, or a digital twin platform, without custom development billed at an hourly rate every single time we need to connect something new?
• 18. If we terminate the contract, what exactly do we retain, in what format, and on what timeline — in writing, in the agreement itself? A vendor who won't put this in the contract is telling you something about how confident they are you'll want to stay.

Security, Audit Trail, and Data Ownership

Oil and gas clients increasingly run their own vendor security questionnaires before they'll accept a service provider's software into their workflow. You need answers to these before that questionnaire arrives, not during it.

• 19. Who legally owns the inspection data we enter into the system — us or the vendor — and does the contract state that explicitly, rather than leaving it implied?
• 20. Does every report carry an immutable, timestamped audit trail — who created it, who reviewed it, who approved it, every subsequent edit — sufficient to survive an internal ISO 9001:2015 audit or a client's for-cause investigation following a field failure?
• 21. Where is data physically hosted, is it encrypted both at rest and in transit, and does the vendor carry its own cyber liability coverage? This has become a standard line item on client vendor-qualification forms in the past two renewal cycles.

Implementation, Support, and Vendor Viability

Software that's technically correct but impossible to actually roll out is not a win. This is where "affordable, accessible, fully customizable" gets tested against reality.

• 22. What does implementation actually look like week by week — who loads our historical data, who trains our field technicians, and how many hours of our own staff's time does it consume before we're live?
• 23. What is the support SLA for a production outage — a technician stranded in the field mid-turnaround, unable to submit a report — versus a cosmetic bug, and is that response time written into the agreement rather than described informally in the sales call?
• 24. How many NDT companies has this vendor actually implemented this software for, and can we speak directly to one as a reference, not read a polished case study on a marketing page?
• 25. Is the product roadmap driven by how NDT operators actually work — certification cycles, calibration logic, multi-method reporting — or is this a generic field-service or work-order platform with an NDT skin applied after the fact? The difference shows up the first time you hit a workflow the generic tool never anticipated.

Scoring the Answers: A Simple Framework

Once you have written answers from two or three vendors, resist scoring them purely on feature count. Weight the compliance-critical categories — certification tracking, calibration traceability, audit trail, data ownership — more heavily than convenience features like a nicer dashboard. A practical approach: mark each of the 25 questions red (no clear answer, or answer is unfavorable), yellow (partial answer, needs a written follow-up), or green (clear, specific, and in writing). A vendor with three or more reds in the certification, calibration, or data-ownership categories should not advance to contract negotiation regardless of how good the demo looked, because those are the categories where a gap turns into an audit finding, a lost bid, or data you can't get back.

It's also worth having your operations lead, not just your IT or purchasing contact, sit in on the technical answers. The person who will spend a Tuesday morning tracking down whether a UT technician's certification lapsed before a turnaround is the person best positioned to know whether a vendor's answer actually solves the problem or just sounds like it does. If you'd rather have this checklist run against a specific shortlist of vendors, an NDT ERP evaluation session with someone who has implemented these systems for inspection companies specifically — not generic field-service software — tends to surface the gaps faster than doing it solo.

It also helps to pressure-test the answers against a real event, not a hypothetical one. Ask the vendor to walk through, step by step, exactly what the system shows if a client calls on a Friday afternoon asking for the full inspection history and personnel file on a specific weld from eighteen months ago — a request that happens on almost every long-running refinery or pipeline contract sooner or later. If the answer involves "we'd have to check" or a callback the next business day, that's a data point. A system built around how NDT work actually happens should be able to answer that question live, on the call.

None of this is complicated once it's written down. What's expensive is discovering the gaps after the contract is signed, the data is loaded, and switching costs have quietly become the vendor's real product. A vendor confident in its own data model, its own audit trail, and its own exit terms will answer all 25 of these questions in writing without hedging — and that confidence, more than any single feature on a demo screen, is what you're actually buying.

Atlantis NDT Products & Services

Atlantis NDT pairs field expertise with software: NDT inspection management software — Atlantis ERP, a digital twin platform for asset integrity, and NDT reporting software. Build your team with NDT training & certification (ASNT SNT-TC-1A) and ASNT certification pathways, or bring in ASNT Level III consulting. Affordable, accessible, fully customizable — book a free consultation.