When a maintenance manager at a Gulf Coast refinery calls about NDT consulting, they usually mean one of three things: they need a written practice reviewed before an audit, they need a second set of eyes on a technician's UT data because something doesn't look right, or they need someone to build a program from scratch because their last Level III retired and took the institutional knowledge with him. Those are three different engagements with three different timelines, and conflating them is why so many consulting relationships start with a mismatched scope and end with a client who feels like they paid for something vague. This post walks through what an ASNT Level III consulting engagement actually looks like at Atlantis NDT, phase by phase, using the kind of project structure we'd propose for a mid-size fabrication shop or a refinery inspection department in the United States.
\nThe goal isn't to sell a template. It's to give inspection managers, QA/QC directors, and plant reliability engineers a realistic picture of what happens between "we have a problem" and "the problem is documented, corrected, and defensible in an audit," so they can evaluate a proposal against something concrete instead of a glossy one-pager.
\n\nEvery engagement starts with a scoping conversation, and the questions in that call determine everything downstream. We ask what triggered the request — a failed API audit, an incident investigation, a new client requiring ISO 9712 or PCN-qualified personnel on a job, a merger that combined two written practices into one, or simply a gap the QA manager already knows exists but hasn't had bandwidth to fix. We ask what codes and standards govern the work: ASME Section V for the examination methods themselves, ASME Section VIII Division 1 or 2 for pressure vessel acceptance criteria, API 510 for in-service pressure vessels, API 570 for piping, API 653 for aboveground storage tanks, or a client specification layered on top of all of it. We ask how many technicians are on staff, what methods they're qualified in, and whether qualification is to SNT-TC-1A, CP-189, or a client-mandated central certification body.
\nThis is also where we clarify a distinction that matters legally and practically: consulting reviews and strengthens a facility's own written practice and personnel qualification records against SNT-TC-1A; it does not issue ISO 9712 or PCN certifications, and it doesn't administer API 510/570/653 inspector exams. Those are separate credentialing bodies with their own exam and renewal processes. Where a client's contracts require ISO 9712 or PCN-qualified personnel for work in Europe or the Middle East, or an API-certified inspector for jurisdictional tank and piping work, we help the client understand exactly what's required and how their existing SNT-TC-1A program interacts with it — but we don't pretend to be the certifying body.
\nIf the scoping call leads to an on-site visit, the first half-day is spent doing three things: pulling a sample of recent inspection reports and comparing the technique used against what the written practice specifies, sitting with two or three technicians while they run an actual exam to watch calibration and scanning discipline, and reviewing the personnel qualification file structure — vision test currency, hands-on and written exam records, experience hour logs, and whether recertification intervals are actually being tracked or just assumed. In a typical mid-size shop with 8-15 NDT technicians, this takes one to two days and tends to surface the majority of the findings that end up in the final report. The remaining findings usually come out during the deeper document review in Phase 2.
\n\nThis is the least glamorous and most consequential phase. We pull the written practice, every method-specific procedure (UT shear wave, UT straight beam, MT wet fluorescent, MT dry powder yoke, PT visible dye, RT film and digital, VT, and TOFD or phased array if in use), and cross-check them against the edition of the code currently invoked in contracts. A recurring finding: shops running a UT shear wave procedure written against an older ASME Section V edition that hasn't been updated to reflect a code edition change referenced in a client's current purchase order. Nobody caught it because the procedure "still works" — the technique hasn't materially changed — but an auditor checking edition traceability will flag it every time.
\nWe also check procedure qualification records. A written UT procedure needs a qualification record demonstrating it was actually validated against a reference block or mockup with known reflectors before it went into production use — not just a procedure someone wrote based on a training manual. This is one of the most common gaps we find: procedures that read correctly on paper but have no qualification record tying them to demonstrated capability, which is exactly the kind of thing an ASME or API auditor probes for during a records review.
\nThe written practice says one thing; the floor does another. Examples from real engagements (details generalized, not tied to any specific named client): a written practice specifying Level II sign-off on all final reports, while in practice a Level I with six months' experience was signing off during a headcount crunch; a calibration interval specified as "daily" in the written practice but logs showing gaps of two to three days during a turnaround; MT yoke lift verification not being recorded at the frequency the procedure requires. None of these are usually the result of bad intent — they're the result of production pressure eroding a paper system nobody's been auditing internally. Part of the value of an outside Level III is that we have no stake in defending the status quo; we just document what's actually happening against what's supposed to happen.
\n\nWith the paper review done, we go back to the floor and watch technique execution against the corrected procedures, focusing on the methods and applications with the highest consequence of error. On a refinery turnaround, that usually means shear wave UT for weld examination on high-pressure piping and phased array or TOFD on critical vessel welds. We watch DAC curve construction, probe angle verification, scan pattern coverage, and whether technicians are actually achieving the required beam path coverage specified in the procedure, or taking shortcuts that happen to still find gross defects but would miss the smaller ones the procedure is designed to catch.
\nWe audit a sample of personnel files against SNT-TC-1A Recommended Practice requirements: initial qualification exam scores (general, specific, and practical), documented vision acuity testing on the required interval (typically annual near-vision and color contrast where applicable), experience hours logged per method, and employer-specific written practice sign-off. A common finding at growing companies: a technician certified Level II in UT six years ago whose file has no record of the required periodic vision retest, or whose experience hours in a newer method (say, phased array added two years after initial UT certification) were never formally logged even though the person has clearly been performing the work. These are the exact records an ASNT SNT-TC-1A program audit, or a client's pre-qualification audit before awarding turnaround work, will ask to see.
\n\nEverything gets written up in a structured findings report, typically organized into three tiers: critical (creates code compliance or safety exposure — for example, a procedure qualification gap on a method actively being used for acceptance decisions), significant (creates audit risk or inconsistent quality — for example, missing calibration frequency documentation), and administrative (needs fixing but low immediate risk — for example, an outdated revision date on a document that hasn't materially changed). Each finding gets a specific corrective action, an owner, and a target date, because a findings report without accountability structure just becomes another document nobody actions.
\nWe also benchmark the program against what we're seeing across the industry — not with invented statistics, but with pattern recognition from repeated engagements. Shops that get audited by major EPCs or oil majors before qualifying for bid lists tend to have tighter documentation discipline than shops that primarily serve smaller fabrication clients, simply because the audit pressure is more consistent. That's useful context for a QA manager trying to decide how much rigor their program actually needs relative to their client base.
\n\nThe report isn't the end of the engagement for most clients — it's the start of implementation. This phase typically includes helping rewrite specific procedures rather than just flagging them as deficient, running a training session with technicians on the corrected practices, and scheduling a follow-up audit 60-90 days later to verify the corrective actions actually stuck rather than reverting once the consultant leaves. This follow-up step is the one clients most often try to skip to save time, and it's the one that most reliably determines whether the engagement produced a durable improvement or a report that sits in a binder.
\nFor shops managing this process across dozens of technicians and multiple facilities, the tracking burden alone — who's due for recertification, which procedures are linked to which code editions, which calibration blocks are due for verification — becomes a real operational problem once you're past a handful of people. This is where a structured system like Atlantis NDT ERP earns its keep: certification expiry tracking, procedure revision control, and equipment calibration schedules in one place instead of spreadsheets that drift out of sync the moment two people are editing them independently.
\n\nA single-site fabrication shop with 10 technicians and two or three NDT methods in use is a different engagement than a multi-site pipeline operator with UT, MT, PT, RT, and ET spread across five facilities in different states, each potentially under a slightly different client specification. Rough guidance on how scope typically scales:
\nEngagements move faster and produce better findings when the client arrives with a few things assembled in advance: the current written practice and all method-specific procedures, a personnel roster with current certification levels and expiry dates, a sample of the last 20-30 completed inspection reports across methods, calibration and equipment maintenance logs, and a summary of any recent audit findings from clients, insurers, or regulatory bodies (jurisdictional inspectors for API 653 tank work, for instance, or a client's own pre-qualification audit). Having this ready doesn't shrink the engagement's thoroughness, but it does mean the time on site is spent on verification and problem-solving instead of hunting for documents that should already exist.
\nIt's also worth being candid with the consultant about what's actually broken versus what management suspects is broken. Engagements where the QA manager pre-briefs the consultant honestly — "our MT program is solid, but I don't trust our PT wet fluorescent line, and I have no idea if our procedure qualification records would survive an audit" — get more targeted, useful findings than engagements framed as a generic "review everything," because the consultant can allocate deeper time to the areas the client already has instinct about.
\n\nA good consulting engagement fixes what's broken and documents why it was broken, but it doesn't prevent drift from happening again on its own — that requires an operational system, not a one-time review. That's the natural handoff point from ASNT Level III consulting into the tools that keep a program compliant between audits: certification and calibration tracking through Atlantis NDT ERP, standardized digital report generation through the reporting platform, and for facilities managing complex assets across a turnaround cycle, a digital twin platform that ties inspection history directly to the physical asset rather than a folder of disconnected PDFs. None of that replaces the judgment of a Level III walking the floor and reading a procedure line by line — but it's what keeps the findings from repeating themselves eighteen months later.
\nFor technicians looking to build the qualifications that make these programs stronger from the inside, structured NDT training aligned to SNT-TC-1A remains the foundation — a consulting engagement can fix documentation and process, but it can't substitute for technicians who understand the physics of the method they're running well enough to catch what a shortcut procedure would miss.
\nThe bottom line for anyone evaluating a proposal: ask for the phase structure, ask what's included in follow-up, and ask what happens to the findings after the report is delivered. An engagement that ends at the report is a snapshot. An engagement that includes implementation support and a follow-up audit is a correction — and in an industry where a missed indication has real consequences, that difference is the entire point of bringing in outside expertise in the first place.
\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