{"id":"1371","title":"NDT ERP Buyer's Checklist: 25 Questions to Ask Before You Sign","slug":"ndt-erp-buyer-s-checklist-25-questions-to-ask-before-you-sign","date":"September 20, 2026","snippet":"A 25-question NDT ERP buyer's checklist: what to ask any vendor about data ownership, certification tracking, calibration, and support before signing.","content":"<p>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&apos;s best day &#x2014; 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&apos;s full certification package in the middle of a turnaround, or when the vendor&apos;s pricing changes and you discover your own inspection data is harder to get out of the system than it was to put in.</p>\n<p>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 &#x2014; 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 <a href=\"/consulting\">ASNT Level III</a> reviews your quality system or a client runs a for-cause audit after a field failure.</p>\n<p>It&apos;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 &#x2014; 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 &#x2014; not the enthusiasm of the person answering them.</p>\n\n<h2>Data Model and Method Coverage</h2>\n<p>The first failure mode in NDT software isn&apos;t security or support &#x2014; it&apos;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&apos;t query five years of RT reports for a specific IQI sensitivity level when a client disputes a weld).</p>\n<ul>\n<li><strong>1. Does the system support every NDT method we currently run as a native, structured data type</strong> &#x2014; 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 &quot;notes&quot; box will not hold up under a client&apos;s technical audit.</li>\n<li><strong>2. When we add a method later &#x2014; say phased array to a shop that has only run conventional UT &#x2014; does that require a paid change order to the vendor, or can our own admin configure the new field set?</strong> This tells you whether you&apos;re buying a product or subscribing to a permanent consulting relationship.</li>\n<li><strong>3. Can the system output reports in the format conventions our clients already require</strong> &#x2014; API 510 thickness survey layout, ASME Section V Article 4/5 UT report format, AWS D1.1 weld inspection report format &#x2014; without us rebuilding templates from a blank page?</li>\n<li><strong>4. Does the system separate raw inspection data (readings, indications, scan data) from the report document itself,</strong> so a narrative correction doesn&apos;t require altering the underlying data record? This distinction is what makes a report defensible in an audit trail sense &#x2014; readings should be immutable once captured, while report language can go through review and revision with its own history.</li>\n<li><strong>5. Can we restrict what non-technical staff (schedulers, billing admins) see</strong> &#x2014; job status and scheduling without exposure to restricted technical data &#x2014; and can we configure that boundary ourselves without a support ticket?</li>\n</ul>\n\n<h2>Certification and Personnel Qualification Tracking</h2>\n<p>This is the category where spreadsheets fail most visibly, and where auditors look first. An NDT company&apos;s core deliverable is the qualified judgment of a certified technician; if the software can&apos;t prove that judgment was qualified at the moment the report was signed, everything downstream is exposed.</p>\n<ul>\n<li><strong>6. Does the system track certification by method AND level individually</strong> &#x2014; PT Level II and UT Level II are separate qualifications with separate expiration dates &#x2014; rather than a single &quot;certified&quot; flag per employee?</li>\n<li><strong>7. Will the system automatically block report sign-off by a technician whose certification in that specific method has lapsed,</strong> rather than relying on someone remembering to check?</li>\n<li><strong>8. Does it distinguish between certification types as separate, non-interchangeable fields</strong> &#x2014; 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.</li>\n<li><strong>9. Can it track the annual near-vision acuity check separately from the 3-to-5-year method recertification cycle,</strong> since SNT-TC-1A recommends annual vision screening independent of the broader recertification interval?</li>\n<li><strong>10. If a client&apos;s QA representative asks to see a specific technician&apos;s full certification package during a turnaround, can we produce it in under two minutes</strong> &#x2014; training hours, exam scores, experience log, vision test date &#x2014; rather than by pulling physical folders from a filing cabinet three states away?</li>\n</ul>\n\n<h2>Calibration, Equipment, and Traceability</h2>\n<p>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 &#x2014; not guess.</p>\n<ul>\n<li><strong>11. Does the system track calibration due dates for every serialized instrument</strong> &#x2014; Epoch 650s, OmniScan units, reference blocks, yokes &#x2014; with the NIST-traceable calibration certificate attached, not a note in a shared spreadsheet someone has to remember to update?</li>\n<li><strong>12. Will the system prevent a technician from closing out a report against an instrument whose calibration date has expired,</strong> the same way it should for a lapsed certification?</li>\n<li><strong>13. Can probe and cable serial numbers be logged as line items against specific inspections,</strong> 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?</li>\n<li><strong>14. Does it handle consumable and reference-standard traceability</strong> &#x2014; couplant batch numbers, IQI serial numbers, penetrant and developer lot certificates &#x2014; where a client specification requires it, which is routine on nuclear and aerospace-adjacent work and increasingly requested on major refinery turnarounds?</li>\n</ul>\n\n<h2>Integration, Data Portability, and Exit Terms</h2>\n<p>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.</p>\n<ul>\n<li><strong>15. Can we export our complete historical data</strong> &#x2014; every report, every reading, every certification and calibration record &#x2014; in a non-proprietary format (CSV, JSON, searchable PDF) on demand, at any point, not just at contract termination?</li>\n<li><strong>16. What is the actual mechanism and realistic timeline for migrating our existing archive into the new system,</strong> and will migrated historical records remain searchable and reportable, or do they just become static, unindexed PDFs sitting in a folder?</li>\n<li><strong>17. Does the system offer a documented API or integration path</strong> to our accounting platform, a client&apos;s asset management system, or a <a href=\"/digital-twins\">digital twin platform</a>, without custom development billed at an hourly rate every single time we need to connect something new?</li>\n<li><strong>18. If we terminate the contract, what exactly do we retain, in what format, and on what timeline &#x2014; in writing, in the agreement itself?</strong> A vendor who won&apos;t put this in the contract is telling you something about how confident they are you&apos;ll want to stay.</li>\n</ul>\n\n<h2>Security, Audit Trail, and Data Ownership</h2>\n<p>Oil and gas clients increasingly run their own vendor security questionnaires before they&apos;ll accept a service provider&apos;s software into their workflow. You need answers to these before that questionnaire arrives, not during it.</p>\n<ul>\n<li><strong>19. Who legally owns the inspection data we enter into the system &#x2014; us or the vendor &#x2014; and does the contract state that explicitly,</strong> rather than leaving it implied?</li>\n<li><strong>20. Does every report carry an immutable, timestamped audit trail</strong> &#x2014; who created it, who reviewed it, who approved it, every subsequent edit &#x2014; sufficient to survive an internal ISO 9001:2015 audit or a client&apos;s for-cause investigation following a field failure?</li>\n<li><strong>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?</strong> This has become a standard line item on client vendor-qualification forms in the past two renewal cycles.</li>\n</ul>\n\n<h2>Implementation, Support, and Vendor Viability</h2>\n<p>Software that&apos;s technically correct but impossible to actually roll out is not a win. This is where &quot;affordable, accessible, fully customizable&quot; gets tested against reality.</p>\n<ul>\n<li><strong>22. What does implementation actually look like week by week</strong> &#x2014; who loads our historical data, who trains our field technicians, and how many hours of our own staff&apos;s time does it consume before we&apos;re live?</li>\n<li><strong>23. What is the support SLA for a production outage</strong> &#x2014; a technician stranded in the field mid-turnaround, unable to submit a report &#x2014; versus a cosmetic bug, and is that response time written into the agreement rather than described informally in the sales call?</li>\n<li><strong>24. How many NDT companies has this vendor actually implemented this software for, and can we speak directly to one as a reference,</strong> not read a polished case study on a marketing page?</li>\n<li><strong>25. Is the product roadmap driven by how NDT operators actually work</strong> &#x2014; certification cycles, calibration logic, multi-method reporting &#x2014; 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.</li>\n</ul>\n\n<h2>Scoring the Answers: A Simple Framework</h2>\n<p>Once you have written answers from two or three vendors, resist scoring them purely on feature count. Weight the compliance-critical categories &#x2014; certification tracking, calibration traceability, audit trail, data ownership &#x2014; 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&apos;t get back.</p>\n<p>It&apos;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&apos;s certification lapsed before a turnaround is the person best positioned to know whether a vendor&apos;s answer actually solves the problem or just sounds like it does. If you&apos;d rather have this checklist run against a specific shortlist of vendors, an <a href=\"/erp\">NDT ERP</a> evaluation session with someone who has implemented these systems for inspection companies specifically &#x2014; not generic field-service software &#x2014; tends to surface the gaps faster than doing it solo.</p>\n<p>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 &#x2014; a request that happens on almost every long-running refinery or pipeline contract sooner or later. If the answer involves &quot;we&apos;d have to check&quot; or a callback the next business day, that&apos;s a data point. A system built around how NDT work actually happens should be able to answer that question live, on the call.</p>\n<p>None of this is complicated once it&apos;s written down. What&apos;s expensive is discovering the gaps after the contract is signed, the data is loaded, and switching costs have quietly become the vendor&apos;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 &#x2014; and that confidence, more than any single feature on a demo screen, is what you&apos;re actually buying.</p>\n<nav class=\"post-footer\" aria-label=\"Related Atlantis NDT pages\">\n  <a href=\"/consulting/ndt-consulting-level-iii\">ASNT Level III consulting</a> &#xB7;\n  <a href=\"/atlantis-academy\">Atlantis NDT Academy</a> &#xB7;\n  <a href=\"/erp\">Atlantis NDT ERP</a> &#xB7;\n  <a href=\"/digital-twins\">Digital Twin platform</a> &#xB7;\n  <a href=\"/best-ndt-reporting-software-2026\">Reporting Software</a> &#xB7;\n  <a href=\"/contact\">Free consultation</a>\n</nav>\n<section class=\"products-services\" aria-label=\"Atlantis NDT products and services\">\n  <h2>Atlantis NDT Products &amp; Services</h2>\n  <p>Atlantis NDT pairs field expertise with software: <a href=\"/erp\">NDT inspection management software &#x2014; Atlantis ERP</a>, a <a href=\"/digital-twins\">digital twin platform for asset integrity</a>, and <a href=\"/best-ndt-reporting-software-2026\">NDT reporting software</a>. Build your team with <a href=\"/training\">NDT training &amp; certification</a> (ASNT SNT-TC-1A) and <a href=\"/asnt-certification\">ASNT certification pathways</a>, or bring in <a href=\"/consulting\">ASNT Level III consulting</a>. Affordable, accessible, fully customizable &#x2014; <a href=\"/contact\">book a free consultation</a>.</p>\n</section>","author":"Anoop Rayavarapu, ASNT NDT Level III","order":1371,"createdAt":"2026-09-20","updatedAt":"2026-09-20","metaDescription":"A 25-question NDT ERP buyer's checklist: what to ask any vendor about data ownership, certification tracking, calibration, and support before signing."}