Document Control Software for ISO 9001 NDT Companies

When "Rev 3" Isn't What's in the Truck

A UT technician shows up to a refinery turnaround with a laminated procedure in his gear bag — the same one he's used on the last four jobs. What he doesn't know is that the quality manager revised it six weeks earlier after a client audit flagged a calibration reference that no longer matched the equipment fleet. The revision went out by email to a distribution list that hadn't been updated since two technicians left. His copy is Rev 2. The controlled copy is Rev 3. Nobody catches it until the client's inspection engineer cross-checks the procedure number during report review, and now the shop is explaining why three days of UT data may need re-verification against the correct acceptance criteria.

This is not a hypothetical. It's the most common finding an ISO 9001:2015 surveillance auditor or a client pre-qualification auditor writes up against small and mid-sized NDT companies, and it's almost never a competence problem — it's a document control problem, one generic file storage was never built to solve. This piece covers what Clause 7.5 requires in NDT-specific terms, where version control breaks in the real world, how it intersects with your SNT-TC-1A written practice, and what separates a folder of PDFs from a system an auditor will trust.

What ISO 9001:2015 Clause 7.5 Actually Requires

Clause 7.5, Documented Information, is short in the standard's text but expansive in what it obligates a certified NDT company to do day to day. It splits into two jobs: creating and updating documented information (7.5.2) and controlling it once it exists (7.5.3.1, 7.5.3.2). For an NDT shop, "documented information" isn't abstract — it's your UT/MT/PT/RT/ET procedures, written practice, calibration records, inspection reports, certification files, NCR/CAPA forms, and quality manual.

Creating, Updating, and Controlling Documents

7.5.2 requires identification and description (title, date, author, reference number — what lets you tell Rev 2 from Rev 3 at a glance), an appropriate format, and review and approval for suitability before a document goes live. In practice, every revision needs a named technical reviewer (usually your ASNT Level III) and a documented approval step before it reaches a technician's hands — not an approval created retroactively for an audit.

7.5.3.1 and 7.5.3.2 are where most shops fail. The standard requires documented information to be available where and when needed, and protected from loss of confidentiality, improper use, or loss of integrity, through specific controls: distribution, access, retrieval and use; storage and preservation including legibility; control of changes; and retention and disposition. A shared drive with folders named "Procedures" and "Procedures OLD" satisfies almost none of that checklist, because a folder structure doesn't control access, doesn't track who changed what, and doesn't prove an obsolete file was pulled from circulation rather than just renamed.

Retention and Disposition Aren't One Rule

Quality records — calibration certificates, certification records, inspection reports, NCR/CAPA files — typically have retention periods driven by contract terms, client specs, or code requirements (API 510/570/653 inspection records, for example, are often retained for the life of the asset plus a defined period, per the owner-user's fitness-for-service program). Controlled procedures work differently: once superseded, the current revision must be removed from active circulation immediately, but the superseded revision is often retained as a historical record — if a client questions a report from eighteen months ago, you need to show which revision was in force that date, not what the procedure says today. A document control system needs to distinguish those states cleanly: obsolete-and-inaccessible-for-use versus obsolete-but-retained-for-traceability. Conflating them is a common finding.

Controlled vs. Uncontrolled Copies in the Field

The controlled-copy/uncontrolled-copy distinction is old quality-manual language, but it maps directly onto NDT field reality. A controlled copy is one the system guarantees is current — distribution is tracked, and when the document changes, every controlled copy is updated or recalled. An uncontrolled copy is a snapshot, valid the moment it was printed or downloaded, no guarantee after. Almost all NDT field work happens on uncontrolled copies by default: a technician on a shutdown, often without reliable signal, isn't refreshing a live document viewer between shots — he's working from a printed binder, a PDF saved to a tablet before leaving the yard, or a laminated card that's been in his bag for a year.

ISO 9001 doesn't forbid this — it requires the risk be managed. The two accepted approaches: stamp printed copies "UNCONTROLLED COPY — VALID AT TIME OF PRINTING ONLY" and force re-verification against the master before each job; or give technicians live access to the controlled master through a mobile-capable system that checks revision status the moment connectivity is available, even if offline during the inspection itself. The first depends entirely on technician discipline at the point of use — exactly where the refinery scenario above breaks down. The second is what a document-control module inside an NDT ERP platform does: sync the current revision to the device before the crew leaves the shop, flag anything stale, and log the check automatically.

Where Version Control Actually Breaks at NDT Shops

The failure modes are consistent industry-wide, and worth naming specifically because they're what an auditor probes for:

• The turnaround scenario. A procedure revises mid-outage — a new acceptance criterion, a corrected reflector size, a scan pattern change — and the distribution list is stale or the notice sits unopened in a busy supervisor's inbox. Technicians keep working the old revision because nothing at the point of use tells them otherwise.
• The superseded written practice still in a drawer. A company updates its SNT-TC-1A written practice — a re-test interval, an exam matrix for a new method — but old printed copies stay in truck cabs because no formal recall ran. An auditor pulls a random copy off a shelf and it doesn't match current certification records.
• Parallel "master" files. Two people each believe they hold the master calibration procedure because both have edit access to the same shared folder, each making small, undocumented edits over time — no single source of truth, and metadata most cloud drives don't reliably preserve across downloads.

None of these are competence failures. The document was correct and the approval was correct — the control meant to keep the two in sync didn't exist or wasn't followed.

Document Control and the SNT-TC-1A Written Practice

The written practice sits at the intersection of two obligations: it's a controlled document under Clause 7.5, and the governing document for your entire personnel certification program under ASNT's Recommended Practice SNT-TC-1A. Get the document control wrong and you don't just have an ISO nonconformance — you have a defensibility problem for every certification issued under that written practice's authority.

A properly controlled written practice needs its own revision history (a method added, an experience-hour requirement adjusted), formal approval by the person with that authority — typically your Level III — and a documented link between each certification record and the revision in effect when it was issued or renewed. If your written practice moves to Rev 5 and you can't show which certifications were qualified under Rev 4 versus Rev 5, those certifications are hard to defend during an audit or dispute. This is the kind of record a document-control capability inside an operations platform handles cleanly: the revision is timestamped and linked, and the chain is pullable in one query rather than reconstructed from memory. Companies rebuilding certification programs from scratch often lean on outside ASNT Level III consulting to get this linkage right the first time.

The Controlled Forms That Carry the Most Risk

A handful of controlled forms account for most findings and most legal exposure if they're wrong:

• Inspection procedures (UT, MT, PT, RT, ET, TOFD, Phased Array) — the document defining acceptance criteria, and the one most likely to be field-superseded without proper recall.
• Calibration records — equipment-specific and date-stamped, tied directly to the validity of every reading taken during that interval. A missing or expired record can invalidate an entire report's data.
• WPS/PQR references pulled into NDT reports — when RT or UT results are evaluated against a Welding Procedure Specification and its Qualification Record, the report needs the correct, current revision, not whichever version was on file when the job was quoted months earlier.
• Nonconformance and CAPA forms — auditors trust these least by default, because a shop that never generates an NCR reads as either flawless or not looking. A controlled, trackable CAPA form with closure evidence is one of the fastest ways to demonstrate a functioning quality system.

Every one of these forms benefits from being a controlled template rather than something technicians recreate from an old job. When the form lives inside the same system that generates the inspection report, a field revision propagates automatically instead of depending on someone remembering to redistribute a file — one argument for producing reports through NDT reporting software tied to the same controlled-document backbone as the rest of the QMS.

Electronic Signatures and Audit Trails vs. Wet Ink

Wet-ink workflows are still common in NDT, and ISO 9001 doesn't require electronic signatures — but wet ink creates a specific weakness: a signature only proves someone signed paper, not that the signed version is the one currently in circulation. Reconstructing an approval history means physically locating signed originals, which get lost, filed inconsistently across sites, or signed out of sequence when someone's traveling.

An electronic signature with a real audit trail solves a more useful problem: it captures who approved a specific revision, the exact timestamp, and — done correctly — a user-level log of every view, download, and edit taken afterward. When an auditor asks "show me who approved Rev 4 and when," the answer needs to come back in under a minute from a system record, not a filing cabinet. Response time is read as a proxy for whether a control functions daily or only on paper. A system that can also show Rev 3 was pulled from active device caches at the same timestamp Rev 4 was approved closes the loop auditors are trained to test.

Three Ways to Manage Document Control — And What Each Costs You

Most NDT companies land on one of three approaches, each with real tradeoffs rather than an obvious universal winner:

• Generic file-sharing (SharePoint, Google Drive, Dropbox folders). Cheap and familiar — fine for a one- or two-person shop with a small procedure library. The failure is structural: these tools weren't built to enforce single-source-of-truth for controlled documents. Version history isn't organized around approval workflows, nothing forces obsolete files out of active use, and permissions loosen over time. It works until an auditor asks for a controlled-document register with approval dates, and someone spends a weekend reconstructing it by hand.
• A dedicated, standalone QMS document-control module, sold separately from anything else you run. This solves the control problem properly — approval workflows, e-signatures, and audit trails are the whole point. The tradeoff: it's another system of record to keep in sync with operational data. Technician files, job records, and calibration schedules live in one platform while the documents governing them live in another, and someone maintains that mapping manually — reintroducing the sync problem the module was bought to solve, one layer up.
• Document control built into an ERP that also runs scheduling, job costing, and certification tracking. The advantage is a single source of truth: the procedure revision linked to a job is the same record the scheduler pulled the technician's certification from and the report generator cited for acceptance criteria, no manual reconciliation needed. The honest tradeoff: the module must be genuinely built for ISO 9001 compliance, not bolted on as a generic attachment feature — a folder of PDFs inside job software isn't document control just because it lives inside an ERP. Atlantis NDT ERP treats document control as a first-class module — revision approval, controlled-copy distribution to field devices, audit-trail logging — not a file cabinet bolted onto scheduling software.

The right answer scales with company size and audit exposure. A two-person shop doing local plant work may be fine on disciplined shared folders. A shop running turnaround work for major EPCs, or past the point where one person remembers every open revision by heart, carries real risk on folder discipline alone.

What an Auditor Actually Asks at the Document Control Station

Whether it's an ISO 9001:2015 surveillance audit or a pre-qualification audit before awarding turnaround work, this station follows a predictable script:

• "Pull up the current approved revision of this UT procedure and the approval record — who approved it, and when." A fast lookup, not a search.
• "Show me the previous revision has been removed from circulation." The one most shops fail — most systems show the new version exists without proving the old one is gone from every device and binder it reached.
• "Walk me through what happens when a procedure is revised — who gets notified, how do you confirm the field received it." Auditors listen for a repeatable process, not good intentions.
• "Show me this technician's certification record and the written practice revision it was issued under." The SNT-TC-1A linkage question, asked more often than shops expect.

Every question tests the same thing: can the system produce a specific, dated, attributable answer quickly, or does it require memory, a phone call, or a manual search. Speed here is read as evidence of whether the quality system is operated for real or maintained for the audit.

Migrating From Paper or Shared Drives

Moving from paper binders or an unstructured shared drive into a controlled system is a real project, and rushing it creates its own risk. A realistic sequence starts with a document inventory — every procedure, form, and written practice in use, current revision confirmed against the master, not assumed from a filename — which becomes the controlled-document register. Next is formal approval of record for each document entering the new system, even unchanged ones, so there's a clean starting point rather than an ambiguous handoff. Field distribution needs a hard cutover date, with old printed copies formally recalled rather than left to expire naturally — "naturally" is exactly how the turnaround scenario at the top of this piece happens.

Historical records don't need to enter the live system at all; they need archiving somewhere retrievable, tagged with retention/disposition dates, separate from the active register. Most shops find the transition faster paired with broader onboarding, refreshing procedures alongside the new system, where NDT training support and Level III oversight catch outdated content before it's carried forward as a "controlled" version of something already wrong.

Document control isn't the most technically demanding part of an NDT quality system, but it's disproportionately where certifications get put at risk — not because the inspection work was bad, but because nobody could quickly prove which version of the rules it was performed under. Building that proof into daily operations, rather than reconstructing it under audit pressure, is the entire point.

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.