Open a spreadsheet on any ISO/IEC 17025-accredited calibration lab manager's desktop and you will usually find the same thing: a master equipment list with columns for last-cal date, interval, next-due date, and a status cell someone updates by hand. It works fine at twelve pieces of equipment. It starts leaking at eighty. By three hundred assets spread across a home lab, two field crews, and a rental fleet, the spreadsheet is not a system anymore — it is a liability with a due date nobody fully trusts.
\nThat gap is exactly why "calibration lab management software" has become a real search category instead of a niche one. Two names come up constantly in RFPs and lab-manager forum threads: Metquay, a purpose-built SaaS calibration management platform, and GageList, a lighter gauge-and-calibration tracker aimed mostly at manufacturing QA teams. Both are legitimate, standards-literate tools built around ISO/IEC 17025 record-keeping. Neither one, by itself, solves the problem a non-destructive testing (NDT) inspection company actually has — because for an NDT firm, calibration is not the whole business. It is one workflow embedded inside a bigger one, where crew scheduling, technician certification, exposure device control, and inspection report generation all have to reference the same equipment record. Get that wrong and someone eventually ships a UT thickness report citing a transducer that went out of tolerance three weeks earlier.
\n\nThe failure mode is rarely dramatic. It is death by a thousand small gaps. A gauge gets loaned to a field crew and the "location" column never gets updated, so the recall notice goes to an empty bench. A technician performs an intermediate check between full calibrations, writes the result on a paper tag, and the tag gets thrown away with the packing crate. An auditor asks for the calibration history of a specific ultrasonic thickness gauge used on a job eleven months ago, and reconstructing it means cross-referencing three spreadsheets, a filing cabinet of PDF certificates, and someone's memory.
\nNone of that shows up as a problem until an assessor from A2LA or ANAB sits down for a reaccreditation audit, or a client's quality department runs a supplier audit and asks a simple question your system cannot answer in under thirty seconds: "Show me every equipment record touched by nonconformance report 2026-014." A spreadsheet answers that question with someone's afternoon. Purpose-built software answers it with a filtered query.
\n\nMost labs read the standard as a documentation requirement. It is also, implicitly, a software requirement — because the clauses assume a level of retrieval speed and cross-referencing that paper cannot deliver at scale.
\nClause 6.4 (Equipment) requires that equipment be uniquely identified and that records be kept covering identity, manufacturer, serial number, location, calibration dates, calibration results, adjustments, acceptance criteria, next due date, and any maintenance or repair history — for every piece of equipment significant to the results you produce. Clause 6.4.9 is the one that actually breaks spreadsheets: when equipment is found to be defective or outside specified limits, the lab must evaluate the effect on previous results and take appropriate action, which in practice means identifying every certificate, report, or job that used that instrument since its last known-good calibration. Try doing that impact analysis by hand across a year of field data and you understand why labs pay for software instead of discipline alone.
\nClause 6.5 (Metrological Traceability) requires an unbroken chain of calibrations linking your working standards back to the International System of Units (SI), typically through a National Metrology Institute like NIST or an accredited calibration provider recognized under the ILAC Mutual Recognition Arrangement. Your software has to store and surface that chain — not just "calibrated," but calibrated by whom, against what reference standard, with what stated uncertainty, and traceable to what NMI.
\nClause 7.8.4 governs calibration certificate content specifically: measurement results with units, conditions under which the calibration was performed, and a statement of the measurement uncertainty. Clause 7.11 covers control of records — retention, backup, and controlled retrieval, including protection against unauthorized alteration. An accreditation assessor is going to ask how records are protected from being edited after the fact without a trace. "Nobody would do that" is not an answer that passes an audit; an immutable change log is.
\n\nClause 6.4.10 requires intermediate checks between full calibrations wherever confidence in equipment status needs to be maintained — a mid-interval verification against a reference standard, logged and reviewed against defined criteria. This is the requirement that separates a real calibration management system from a due-date calendar. A due-date calendar tells you when the next full calibration is scheduled. It says nothing about whether a gauge drifted out of spec on day 47 of a 90-day interval and someone caught it, or didn't. Software that only tracks the full-cycle due date is only doing half the job the standard actually describes, and it is usually the half an assessor spends the least time checking — which makes the gap easy to carry for years before it surfaces.
\n\nStrip away the marketing language and every serious calibration lab management platform needs to do six things well:
\nMetquay is built for metrology-first organizations: it handles calibration scheduling, uncertainty calculations, and certificate generation with real sophistication, and it is a reasonable choice for a lab whose entire business is calibration services. GageList leans lighter and cheaper, aimed at manufacturing quality departments tracking gauges, calipers, and torque wrenches against a production quality system rather than a field inspection operation.
\nBoth tools answer the calibration question well. Neither answers the operational question an NDT inspection company has to ask alongside it: which technician is certified to use this instrument on this job, is that technician's SNT-TC-1A certification current, is the exposure device's leak test and source inventory record up to date for the radiography crew going out Monday, and does the inspection report the client receives automatically pull the correct calibration reference for the gauge that produced the reading? A standalone calibration platform does not know your job schedule. Your job schedule, in an NDT company, is downstream of your equipment status — a crew cannot legally or defensibly use a probe, a densitometer, or a radiographic source whose paperwork has lapsed.
\n\nA general manufacturing QA team calibrates a gauge and moves on. An NDT inspection company's calibration lab exists to keep a fleet of ultrasonic thickness gauges, phased array probes and wedges, magnetic particle yokes, penetrant black lights, radiographic exposure devices, densitometers, and IQI (image quality indicator) sets legally usable on client sites — often for refineries and petrochemical plants running their own contractor-management systems like ISNetworld or Avetta that will suspend a company's approved-vendor status the moment a calibration record looks stale during an audit.
\nThat means the calibration record cannot live in isolation. It has to connect to: the job it is being deployed on, the technician assigned to use it (and that technician's current SNT-TC-1A level and eye-exam expiration), the client's own equipment-acceptance requirements, and the final inspection report, which typically has to cite the specific serial-numbered instrument and its calibration date as part of the deliverable. When those four things live in four different systems, someone eventually has to reconcile them manually before every report goes out — and manual reconciliation is exactly where audit findings come from.
\n\nLabs generally land in one of three positions. A pure calibration service provider with no field inspection arm is usually well served by a dedicated platform like Metquay, because its entire revenue depends on calibration throughput and certificate accuracy, and it has no adjacent job-scheduling or technician-certification workload to integrate. A manufacturing QA department with a modest gauge fleet and no client-facing certificate obligations can often get by with something closer to GageList's lighter footprint.
\nAn NDT inspection company running its own internal cal lab for its probes, gauges, and exposure devices sits in a different category entirely. For that company, bolting a standalone calibration tool onto a separate project-management system and a separate reporting tool means three logins, three sources of truth, and a recurring reconciliation job that falls on whoever is least busy that week. The more defensible architecture is an NDT inspection management ERP with equipment calibration built in as a first-class module — so the calibration due date, the technician certification record, the job assignment, and the final report all read from the same underlying data instead of four exports stitched together in a spreadsheet.
\n\nBefore signing anything, run every calibration software vendor through the same five questions: Can it perform an automatic impact analysis showing every job touched by a specific instrument since its last valid calibration — live, in the demo, not "we can build a report"? Does it generate a certificate with the full SI traceability chain and stated uncertainty without manual re-entry? Does it enforce a hard block preventing a technician from being scheduled onto a job with equipment that is currently out of cal? Does the audit trail satisfy an ANAB or A2LA assessor's question about record integrity without needing an IT export? And critically for an inspection company specifically: does the calibration record talk to the job scheduling and reporting modules, or does someone have to manually copy a calibration date from one screen into another every time a report goes out?
\nThat last question separates a calibration tool from an operations platform. A lab manager evaluating software purely on price-per-asset or interface polish will miss it every time — and pay for the gap eighteen months later during the audit that actually matters.
\n\nWhatever platform a lab chooses, the hardest part of the project is rarely the software itself — it is migrating years of paper and spreadsheet history into it without losing the chain of custody an assessor will eventually ask about. A realistic migration plan brings in active, in-cycle equipment first, back-fills recent calibration history for anything currently deployed on a live job, and treats fully retired or decommissioned equipment as a lower-priority archive task rather than a blocking requirement before go-live. Labs that try to digitize a decade of history before turning the new system on for daily use typically never finish the migration at all.
\n\nNone of this is an argument against dedicated calibration platforms — they are good at what they do, and for a standalone calibration lab, that is usually the right call. It is an argument for matching the tool to the shape of the business. An NDT inspection company is not a calibration lab that occasionally inspects things; it is an inspection company that happens to run a calibration lab to keep its own fleet legally deployable. Software chosen for that business needs to treat calibration as one integrated function alongside technician certification tracking, job scheduling, and report generation — not as a separate system that everyone has to remember to check.
\nAtlantis NDT's Atlantis NDT ERP and configured specifically for inspection companies, folds equipment calibration tracking into the same platform that manages technician certifications, project scheduling, and report delivery, so an out-of-cal gauge cannot quietly slip onto a job sheet. Combined with ASNT Level III consulting on your quality system and procedures, and reporting software that pulls calibration references directly into the finished deliverable, the goal is one system a lab manager trusts instead of three that have to be cross-checked by hand.
\n\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