NDT Consulting for EPC Contractors: Managing Multi-Site Written Practices

One Written Practice, Five States, Three Client Codes: The EPC Problem

An EPC contractor running simultaneous fabrication and field-erection work across multiple sites — a modular skid shop in Texas, a field crew erecting piperack at a Gulf Coast petrochemical expansion, and a separate crew doing tank work at a Midwest terminal — does not have one NDT problem. It has as many NDT compliance problems as it has active contracts, because each owner-client may specify a different edition of ASME Section V, a different acceptance criteria reference (ASME B31.3 versus a client's own more conservative internal specification), and a different personnel qualification expectation, all while the EPC's own quality department is trying to maintain one coherent, auditable NDT program across a workforce that rotates between sites. NDT consulting for EPC contractors is fundamentally a governance problem before it is a technique problem: how does a contractor maintain a single, defensible written practice under ASNT SNT-TC-1A that flexes correctly to satisfy each client's specific contractual NDT requirements, without either fragmenting into a different ungoverned practice per project or forcing every project into a one-size-fits-all scope that fails to meet a specific client's more stringent requirement.

One practice that holds across several sites is a common brief for written practice development.

Atlantis NDT's ASNT Level III consulting work with EPC contractors most often surfaces this exact tension: a corporate quality department with a solid, SNT-TC-1A-compliant written practice on paper, and multiple project sites where the actual qualification records, procedure revisions in use, and client-specific acceptance criteria have drifted from that corporate baseline — not through negligence, but because each project's site quality lead adapted the practice locally to satisfy an immediate client requirement and never fed that adaptation back into a controlled, centrally reviewed revision.

Structuring a Written Practice That Survives Multi-Client Variation

The written practice itself, per SNT-TC-1A guidance, is the employer's document establishing qualification and certification requirements for NDT personnel — training hours, experience, examination requirements, vision testing, and recertification intervals by method and level. For a single-site fabricator, one document suffices. For a multi-site EPC contractor serving varied clients, the more durable structure separates the document into two tiers:

• A corporate-level written practice establishing the baseline personnel qualification framework — the training hours, experience logging, and examination standards that apply company-wide regardless of project, controlled through a single revision-controlled document that every site references.
• Project-specific procedure addenda that layer each client's specific requirements — a particular ASME Section V edition, a client's internal acceptance criteria that is more conservative than the base code, a specific NDT method the client mandates (for example, a client requiring PAUT on all shop butt welds above a certain thickness where the base code would permit RT), or a client-mandated third-party personnel certification requirement — on top of the corporate baseline, without altering the baseline document itself.

This structure lets a technician qualified once under the corporate written practice work across multiple project sites without requalification, while each project's specific procedure package captures what makes that client's requirements different from the baseline. It also gives the corporate quality department a single point of control: when a new project's addendum reveals a genuinely better practice — a more effective acceptance criterion, a technique that catches indications the baseline procedure would miss — that improvement can be evaluated for adoption into the corporate baseline itself, rather than staying trapped in one project's local paperwork.

Procedure Qualification Records: The Other Half of the Governance Problem

Personnel qualification is only half of what an EPC's NDT program needs to govern centrally — the other half is the NDT procedures themselves, each of which requires a Procedure Qualification Record (PQR) or equivalent demonstration that the written procedure reliably detects the indications it claims to, on the actual material thickness, joint configuration, and access conditions found at that site. An EPC running PAUT on both thin-wall shop-fabricated piping and thick-wall field-erected vessel nozzles cannot use a single PAUT procedure qualified only on the thin-wall case and expect it to be valid, or defensible to a client's inspector, on the thick-wall application. Centralizing procedure qualification records — which procedures exist, what material range and joint geometry each is qualified for, which sites are currently using which revision — in a system the corporate Level III can review is what prevents a site from defaulting to "the procedure we always use" when the actual joint configuration in front of them falls outside that procedure's qualified range.

Client Specification Reconciliation: Reading the Contract Before the Steel Arrives

A recurring and expensive failure mode on EPC projects is discovering a client's NDT specification conflict mid-fabrication rather than during contract review — for example, a client specification requiring 100% volumetric examination on a weld category the EPC's standard procedure treats as spot-examination only under the governing code's default sampling rate, or a client acceptance criteria table that is measurably tighter than ASME Section VIII Division 1 Appendix 4 or B31.3 Table 341.3.2 default acceptance limits. Reconciling the client's project specification against the EPC's standard NDT scope and acceptance criteria needs to happen during proposal or early engineering, when a scope gap can still be priced and scheduled, not discovered by a field NDT technician mid-shift comparing the client spec to the shop traveler for the first time. Atlantis Level III consultants engaged during EPC contract mobilization typically perform exactly this reconciliation — a line-by-line comparison of the client's NDT and acceptance criteria requirements against the contractor's standard procedures — and flag every gap that needs either a new procedure qualification, a client-specific acceptance criteria overlay, or a scope clarification back to the client before fabrication starts.

Rotating Workforce, Consistent Qualification: The Practical Mechanics

EPC contractors move NDT technicians between sites as project demand shifts — a Level II ultrasonic technician finishing a shop fabrication scope in one state may be needed on a field erection crew in another within days. That mobility only works cleanly if qualification records, examination results, and recertification due dates are tracked centrally and accessible to whichever site quality lead is receiving the technician, rather than living in a folder at the technician's home site that the receiving project has to request and wait for. Recertification lapses — a technician arriving at a new site with an eye examination or a method recertification that expired weeks earlier without anyone noticing — are one of the most common and entirely avoidable findings in EPC quality audits, and they happen almost exclusively when qualification tracking is decentralized. A corporate personnel qualification database with automated recertification alerts, tied into inspection and workforce management software, removes the dependency on any single site remembering to check before a technician's badge is issued for a new project.

Multi-Site Visibility for Corporate Quality and Client Audits

Owner-clients auditing an EPC contractor's NDT program — whether as part of a pre-award qualification audit or a routine project quality audit — increasingly expect the contractor to demonstrate program consistency across sites, not just compliance at the one site being audited. A contractor that can produce, on request, a real-time view of every active NDT procedure in use across every site, cross-referenced to which client contract requires it and which personnel are currently qualified to execute it, answers that expectation directly. A contractor reconstructing that picture manually from site-level spreadsheets when the audit request lands — which is still the norm at many mid-size EPC firms — spends the audit preparation window doing data reconciliation instead of substantive quality review, and frequently discovers the same drift-from-baseline gaps described earlier in the process. A digital twin or centralized asset and inspection visualization layer that lets corporate quality and a visiting client auditor see inspection status and procedure compliance across every active site from one dashboard turns what used to be a week of audit-prep data-gathering into something a quality manager can pull up in the meeting itself.

Subcontracted NDT Firms: Governing Quality You Don't Directly Employ

Large EPC contractors rarely perform every scope of NDT with directly employed personnel — specialized techniques like automated PAUT corrosion mapping, TOFD crack sizing, or advanced UT backscatter screening are frequently subcontracted to specialist NDT service providers, sometimes different providers on different projects depending on regional availability and client preference. This introduces a third layer of qualification governance beyond the EPC's own workforce and its corporate written practice: verifying that a subcontracted NDT firm's personnel hold qualification equivalent to what the EPC's own written practice requires, that the subcontractor's procedures are reviewed and accepted (not merely assumed compliant because the subcontractor is a reputable firm), and that the subcontractor's reports integrate into the EPC's own project documentation and traceability system rather than existing as a separate, disconnected record set the client's auditor has to request separately. EPC contractors that formalize a subcontractor NDT qualification checklist — applied consistently at every new subcontractor engagement, regardless of how well-known the firm is — avoid the recurring audit finding of a subcontracted scope that technically met the letter of the contract but cannot produce qualification records in the same format and level of detail as the EPC's own workforce.

Onboarding a New Project Site Without Starting From Zero

When an EPC wins a new contract and mobilizes a new site — particularly in a region or for a client type the contractor has not worked with before — the temptation is to build the NDT quality plan for that project from a blank template, because no existing project quite matches the new client's specification set. A more efficient approach, once the two-tier written practice structure described above is in place, is to treat every new project mobilization as a delta against the corporate baseline: identify specifically what this client's specification requires beyond the baseline, draft the addendum covering only those deltas, and qualify only the procedures and, where necessary, the third-party personnel certifications that the delta actually requires. This keeps mobilization timelines shorter and keeps the corporate quality department's oversight burden proportional to what is genuinely new about each project, rather than re-reviewing an entire NDT program from scratch every time the company wins a new contract in a new region or industry vertical.

What to Ask an Outside Level III Consultant to Deliver

EPC contractors evaluating outside Level III support for multi-site written practice governance should expect a scope covering: a corporate written practice review and, where needed, restructuring into the two-tier baseline-plus-addenda model; a procedure qualification record audit confirming every procedure in active use across sites is qualified for the actual material and joint conditions it is being applied to; a client specification reconciliation process built into project mobilization rather than discovered mid-fabrication; and a personnel qualification tracking system that gives every site real-time visibility into a mobile workforce's current qualification status. The objective is not a single rigid program that ignores legitimate client-to-client variation, but a governed program where variation is documented, controlled, and traceable — so the next client audit, and the next project mobilization, both start from a known-good baseline instead of a reconstruction exercise. NDT training aligned to the corporate written practice, delivered consistently across the workforce rather than site by site with local variation, is what keeps that baseline actually reflected in the field once the consulting engagement ends.

Measuring Whether the Governance Model Is Actually Working

A multi-site written practice program is only as good as the evidence a corporate quality department can produce that it is functioning, and a handful of simple metrics tell that story more reliably than a policy document alone: the percentage of active project sites whose local procedure inventory has been reconciled against the corporate baseline within the current review cycle; the number of recertification lapses caught proactively by the central tracking system versus caught reactively during a client audit; and the average time between a new client specification requirement being identified during contract review and the corresponding procedure addendum being issued to the receiving site. Tracking these consistently gives the corporate quality department an early warning when governance is drifting — for example, a rising number of reactive recertification catches signals that the central tracking system's alerts are not reaching site leads in time to act on them — well before that drift shows up as a finding in a client's own audit of the program.