Most NDT companies start the same way. A founder with an ASNT Level II or Level III background wins a few refinery turnaround contracts, hires two or three technicians, and runs the business out of QuickBooks, a shared Excel workbook for calibration due dates, and a folder of Word-based report templates. It works. Then the company adds a UT crew, picks up a pipeline integrity contract that requires API 1163 documentation, wins a marine survey line of business, and suddenly the owner is chasing down which gamma source is due for its quarterly leak test, whether a technician's PT Level II is still current for a job starting Monday, and why the job-costing numbers in QuickBooks don't match what the crew actually billed in the field.
\nThis is the point where \"we'll figure it out with more spreadsheets\" stops being a viable strategy. An NDT inspection company is not a generic professional services business — it is a business built on regulated personnel qualifications, traceable equipment, radioactive material licensing in some cases, and reports that have legal and safety weight. Generic ERP or plain accounting software has no concept of any of that. This guide walks through what to actually evaluate when shopping for ERP software built for — or configurable to — an NDT, inspection, or calibration services company in 2026.
\nEnterprise resource planning, in the generic sense, means finance, inventory, and sometimes HR in one system. For an NDT company, that's the floor, not the ceiling. The system also needs to model the things that make this industry different from a landscaping company or a marketing agency.
\nUnder ASNT SNT-TC-1A (the recommended practice most US NDT companies write their written practice around) or the ASNT Central Certification Program (ASNT 9712), a technician's authority to perform and sign off a given method — UT, RT, MT, PT, VT, ET, or an advanced method like Phased Array or TOFD — depends on documented training hours, experience hours, vision exam currency (near and far acuity, typically re-verified annually per SNT-TC-1A recommendations), and a passing exam score at the correct level. A spreadsheet can hold this data. It cannot stop a scheduler from assigning a technician whose PT Level II lapsed eleven days ago to a Monday job, or flag that a technician's annual vision exam is due before a shutdown starts. An ERP built for this industry ties certification records directly to the scheduling and dispatch module, so the system itself throws a hard stop — not a \"hopefully someone remembers to check the binder\" soft stop.
\nEvery UT flaw detector, thickness gauge, radiation survey meter, and MT/PT accessory has a calibration interval, usually annual for instrument function calibration with NIST-traceable reference standards, plus daily/per-shift verification the technician logs in the field. If your company holds or is pursuing ISO/IEC 17025 accreditation for a calibration lab function, or your client base requires ISO 9001:2015 clause 7.1.5 (monitoring and measuring resources) evidence, you need calibration records that are queryable, not buried in a binder that lives in whichever truck last used the gauge. This is one of the most common gaps we see when auditing a new client's systems — equipment goes into the field with an expired cal sticker because nobody had a single source of truth linking asset ID, cal due date, and current job assignment.
\nCompanies running industrial radiography under a 10 CFR 34 or equivalent state Agreement State license carry real regulatory exposure here. Source inventory, leak test intervals (typically every six months per NRC/Agreement State rules), transport documentation, and radiographer certification all have to reconcile constantly. An ERP that treats a Co-60 or Ir-192 source like a generic inventory SKU is not solving the actual problem — it needs a dedicated radiation safety module or at minimum custom fields and automated alerts an RSO can rely on.
\nA turnaround job might run three UT technicians, one Phased Array specialist, and a Level III reviewing reports, billed at different rates, with per diem, equipment rental, and consumables layered in. Generic accounting software gives you a single job total. What operations managers actually need is margin visibility by method and by crew so they know that the PAUT line of business is running healthy margins while the basic MT/PT work on a fixed day-rate contract is bleeding money on travel time.
\nInspection reports carry signatures, calibration references, and acceptance criteria tied to a code — ASME Section V, API 510/570/653, AWS D1.1, or a client-specific procedure. When a report gets revised, there has to be a controlled trail: who changed it, what changed, and which revision the client actually received. This is a natural integration point between ERP and dedicated NDT reporting software — the ERP should own the job, the crew, and the client relationship, while the reporting tool owns the technical document, and the two need to talk to each other rather than live as two disconnected silos.
\nFilm, chemicals for MT and PT, couplant, replaceable probes, TOFD wedges — these get consumed on jobs and need reordering before a crew shows up to a site without them. Inventory modules built for retail or manufacturing usually assume a warehouse-to-shelf flow that doesn't match a truck-and-jobsite reality.
\nThe temptation for a growing NDT company is to reach for a recognizable name — NetSuite, a QuickBooks Enterprise upgrade, or an SAP Business One reseller pitch. The problem isn't that these platforms are bad software; it's that none of them ship with a concept of an ASNT certification record, a calibration due date tied to an asset, or a radiation source register. Every one of those gaps becomes a custom development project, usually billed at a systems integrator's hourly rate, and every future change to how you track qualifications becomes a change order.
\nThis is where a flexible, open platform like Atlantis ERP has a structural advantage for a services business this specific: the underlying framework is built to be extended, and the cost of building an NDT-specific certification tracker, calibration module, or radiation source register on top of it is a one-time configuration effort rather than a locked proprietary black box. It's also why \"generic ERP\" and \"NDT-specific ERP\" aren't really two categories — the real question is whether the platform and the implementation partner understand the domain well enough to configure it correctly the first time. Our own Atlantis NDT ERP is built on exactly this premise: a proven, extensible ERP core configured specifically around certification tracking, calibration management, and NDT job costing, rather than a generic system with NDT bolted on as an afterthought.
\nOnce a company operates across more than one office or branch — say a Houston headquarters with a Gulf Coast field office and a satellite crew based out of Corpus Christi — the ERP conversation shifts from \"does it track certifications\" to \"does it give leadership one consolidated view while still respecting who should see what.\" A branch manager needs visibility into their own crews, equipment, and jobs. A company owner or COO needs a rolled-up view across every location: total active jobs, aggregate margin by method, and a company-wide certification expiration calendar that doesn't require logging into three separate systems or calling three separate office managers for a status update. Role-based permissions matter here for a second reason beyond convenience — client data separation. If your company works for two competing refiners in the same market, contractual confidentiality terms often require that each client's job data, pricing, and scope details stay walled off from anyone outside that account team, and the ERP's permission model needs to support that without becoming an administrative burden every time a new job gets created.
\nData ownership deserves equal weight in the decision. Ask directly: if you terminate the contract in three years, what do you walk away with? A vendor that can only hand you a generic CSV export of customer names, stripped of certification history, calibration records, and job-level detail, is not offering real data portability — it's offering a courtesy gesture. A platform built on an open core, where your data lives in a standard, documented database schema rather than a proprietary format only the vendor's own tools can read, gives you a fundamentally stronger negotiating position for the life of the relationship, not just at the point of exit.
\nBecause Atlantis doesn't publish flat pricing — every implementation depends on technician count, method mix, number of locations, and how much of the existing spreadsheet and paper-based history needs to be migrated — the useful exercise isn't comparing a headline number across vendors. It's comparing total cost of ownership over a realistic five-year horizon: license or subscription cost, implementation and configuration cost, the cost of any custom development needed to fill gaps the platform doesn't cover out of the box, and the ongoing cost of change requests as your certification matrix or reporting requirements evolve. Enterprise suites built for a much larger generic industrial customer base — SAP Business One, Microsoft Dynamics 365 Business Central, and comparable platforms — are frequently quoted to mid-market industrial services companies with implementation budgets that run into six figures once industry-specific customization is scoped in, according to figures commonly cited across the ERP consulting industry for comparable vertical builds. A configurable, open-core platform built by a team that already understands NDT certification structures and calibration compliance generally arrives at the same functional outcome without that same custom-development premium, because the domain-specific configuration is additive rather than a ground-up build. Whatever platform you're evaluating, ask every vendor for a project-scoped quote that specifically covers certification tracking, calibration management, and radiation source compliance — not just a generic per-user licensing number — because that's where the real cost difference between platforms actually shows up.
\nBefore signing anything, put these questions in front of every vendor you're evaluating, including us:
\nThe single biggest failure mode isn't the software — it's treating ERP selection as an IT project instead of an operations project. Systems get selected by an office manager or a finance lead without input from the Level III who knows what a real qualification record needs to contain, or from the scheduler who knows that crews get reassigned mid-week and the system has to handle that gracefully. The second most common failure is under-scoping data migration: certification histories, calibration logs, and open job data from the old spreadsheet system need to land in the new system accurately, or technicians stop trusting it within the first month and quietly go back to their own tracking methods.
\nA realistic implementation for a company in the 10-75 technician range runs through discovery (mapping your actual certification matrix, equipment fleet, and job types), configuration, data migration, a parallel-run period where both systems operate together, and a cutover — typically eight to sixteen weeks depending on how much custom configuration is needed and how clean the source data is. Vendors who promise a two-week turnkey rollout for a multi-method NDT company are usually underestimating the qualification-and-calibration data model, not moving faster than everyone else.
\nAdoption is the failure mode that gets the least attention in vendor sales conversations and causes the most quiet damage after go-live. A field technician who's used a paper daily log for fifteen years is not automatically going to trust a tablet-based data entry workflow, especially if the first version they see is clunky, slow on a jobsite with weak cell signal, or requires more taps than the paper process did. If office staff and technicians don't trust the new system in the first few weeks, they build workarounds — a shadow spreadsheet \"just in case,\" a habit of texting the dispatcher directly instead of updating job status in the app — and those workarounds quietly reintroduce the exact data fragmentation the new system was bought to eliminate. The fix isn't a one-time training session at launch; it's involving a handful of respected senior technicians and the office staff who'll use the system daily in the configuration process itself, so the workflow reflects how they actually work rather than how a sales deck assumed they work, and so they have a stake in making it succeed rather than a reason to resist it.
\nThe right ERP for an NDT company is the one that treats certification tracking, calibration management, and radiation source control as first-class data — not custom fields bolted onto a generic services template — while still giving you real financial visibility and a system your office staff and field technicians will actually use. If you're evaluating platforms, it's worth walking through your specific certification matrix, equipment fleet, and job mix with a team that has actually run NDT operations rather than one learning the industry from your requirements document. Affordable, accessible, and fully customizable only means something if the vendor understands what \"customizable\" needs to include for a business built around ASNT qualifications and calibrated equipment — not just invoicing and payroll.
\nPairing the right ERP with disciplined NDT training and certification tracking practices and sound ASNT Level III consulting on your written practice closes the loop between what your system says a technician is qualified to do and what your written practice actually requires.
\nChoosing the right ERP is a foundational decision — pair it with the right people and processes behind it:
\n\nAtlantis 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.
\n