How Employers Should Structure an In-House ASNT Training Program

Why Employers Build In-House Training Programs At All

Sending technicians out to third-party training courses works fine at small scale, but once an inspection company, fabricator, or owner-operator's maintenance department is running a dozen or more technicians through initial certification and recertification every year, the economics and logistics of an in-house program start to make sense — no travel time lost to off-site courses, no waiting on an external provider's course calendar to line up with a shutdown schedule, and training content that's built around the specific equipment, materials, and code requirements your technicians actually encounter rather than generic curriculum. The decision to build in-house isn't really about saving money on course fees; it's about control — control over scheduling, control over content relevance, and control over the documentation trail that a client audit or a certification challenge will eventually test.

That said, building an in-house program badly is worse than not building one at all. A program that produces a stack of certificates without genuine competency behind them creates liability exposure the moment a signed-off inspection gets challenged, and a written practice that exists on paper but doesn't reflect what's actually happening in training sessions is a documentation trap waiting to be discovered during a pre-qualification audit or, worse, after an inspection failure.

The Written Practice Is the Foundation — Get It Right Before Anything Else

Every other decision in an in-house program flows from the written practice, and employers who skip straight to curriculum design before nailing this down consistently end up rebuilding the program later. The written practice defines which methods and levels the program certifies, the training-hour and experience-hour requirements for each, the qualifying examination structure (general, specific, and practical components), vision testing requirements and frequency, recertification intervals, and the criteria for suspension or revocation of certification. It needs to be specific enough to be defensible under audit — vague language like "sufficient training" invites exactly the kind of scrutiny that sinks a program's credibility — while still being realistic enough that your organization can actually deliver against it consistently, year after year, not just for the first cohort when everyone's paying close attention.

SNT-TC-1A vs CP-189: Choosing Your Governing Document

Most employers build their written practice around ASNT SNT-TC-1A, a recommended practice that gives significant latitude for the employer to define specifics within its framework. A smaller number of employers, particularly those serving clients with stricter contractor qualification requirements or operating in nuclear, aerospace, or other high-consequence sectors, adopt ANSI/ASNT CP-189 instead — a full American National Standard rather than a recommended practice, with more prescriptive requirements around examination content, instructor qualification, and documentation. CP-189 compliance is more rigorous to build and maintain, but for an employer whose client base demands it, or whose risk profile justifies the extra rigor, it's worth the additional structure. Deciding between the two early — rather than building around SNT-TC-1A and discovering two years in that a major client's contractor qualification spec effectively requires CP-189-level documentation — saves a costly program rebuild.

Instructor Qualification: Why a Level II Can't Run the Program Alone

A working Level II technician can be an excellent hands-on mentor for OJT, but SNT-TC-1A and CP-189 both place responsibility for the overall training program, examination content, and certification decisions on a qualified Level III — someone with the depth of code knowledge, examination-writing competency, and program-oversight experience to defend the program's structure and outputs under scrutiny. Employers who let a Level II technician write exams, set pass criteria, or make final certification calls without genuine Level III oversight are building a program with a structural weakness that surfaces exactly when it matters most — during a client audit, a certification dispute, or a legal challenge following an inspection failure. If you don't have an in-house Level III with the bandwidth to own this role properly, bringing in ASNT Level III consulting to build the program architecture and review examination content is a more defensible starting point than stretching an internal Level II beyond their actual scope of authority.

Curriculum Design: Matching Training to Your Actual Scope of Work

Generic method training — teaching ultrasonic testing theory in the abstract — is a weaker foundation than curriculum built around the specific materials, geometries, and code requirements your technicians will actually face. A fabrication shop running mostly carbon steel pressure vessels to ASME Section VIII needs different curriculum depth than a refinery maintenance department running API 510/570/653 in-service inspection on decades-old equipment with known degradation histories, and a curriculum that tries to cover everything generically ends up covering nothing deeply enough to be useful. The strongest in-house programs build core method theory once, then layer application-specific modules on top — a nozzle-to-shell weld inspection module, a heat exchanger tube inspection module, a corrosion-under-insulation screening module — matched to the actual job categories technicians will be assigned to after certification.

Facilities, Equipment, and the Real Cost of a Functional Training Lab

Classroom theory only gets a trainee partway there — practical competency requires hands-on time with representative equipment, calibration standards, and reference flaw samples that match what technicians will encounter in the field. Building this out means budgeting for calibration blocks and reference standards across the methods you're certifying, a stock of flawed and unflawed welded and machined samples for practical assessment (genuinely flawed samples are harder to source than most first-time program builders expect — many employers end up commissioning intentionally flawed weld samples from a fabricator specifically for training use), and dedicated space that doesn't compete with production work for equipment access during a training cycle. Employers who try to run practical training on borrowed production equipment during slow periods consistently find the program gets deprioritized the moment a real job comes in, which turns a planned training cadence into a reactive, constantly-delayed one.

Exam Administration and Maintaining Defensibility

The qualifying examination — general, specific, and practical components — is where a program's credibility gets tested most directly, and the details that separate a defensible exam process from a vulnerable one are procedural: secure exam administration with controlled access to questions beforehand, documented grading criteria applied consistently across candidates, retained exam records showing exactly what was tested and how it was scored, and a clear, written policy on retake eligibility and waiting periods that gets applied the same way for every candidate regardless of who they are or how the supervisor feels about them personally. Programs that let exam administration get informal — the same questions reused indefinitely, grading that varies by who's reviewing the answer sheet, retake policy applied inconsistently — are building a credential that won't hold up if a certified technician's competency is ever challenged in a dispute.

Documentation Systems: The Part That Breaks Down First

Even a well-designed written practice and a well-run training curriculum fail in practice if the documentation supporting it lives in scattered personnel files, individual supervisors' notebooks, or an aging spreadsheet nobody consistently updates. The records that need centralized, auditable tracking include: training hours per technician per method, experience hours logged and verified, exam scores and dates, vision test results and renewal dates, certification and recertification dates with expiry tracking, and any suspension or revocation history. This is exactly the operational gap that Atlantis NDT ERP is built to close — centralizing technician qualification records so that a recertification deadline, a lapsed vision test, or an incomplete training-hour requirement surfaces as a proactive alert instead of a surprise discovered during a client audit or, worse, after a technician has already been deployed on a job they weren't actually qualified for.

Build vs. Buy: When In-House Doesn't Make Sense

In-house programs make sense once technician volume and recurring training need justify the fixed cost of curriculum development, instructor time, and facility setup — roughly speaking, an organization certifying and recertifying a steady double-digit number of technicians annually across a stable set of methods. Below that volume, the fixed cost of building and maintaining a defensible in-house program, including keeping a Level III's attention on it consistently rather than as an occasional side project, often exceeds what it would cost to send technicians to an established external program through something like Atlantis NDT Academy and reserve internal effort for OJT mentorship and written-practice administration rather than full curriculum ownership. Employers should run this comparison honestly rather than defaulting to in-house because it feels like it should be cheaper — a half-built in-house program that produces weakly documented certifications is a worse outcome than a smaller, fully external training relationship executed well.

Common Pitfalls That Show Up Again and Again

Across employers standing up in-house programs, the same handful of mistakes recur often enough to be worth naming explicitly rather than leaving them to be discovered the hard way:

• Treating the written practice as a one-time document. Codes get revised, client specifications change, and a written practice that isn't reviewed and updated on a defined cycle drifts out of alignment with what the program actually needs to certify against.
• Underestimating how much Level III time the program actually requires. Program oversight isn't a once-a-quarter check-in — exam content review, sign-off on certification decisions, and periodic curriculum review add up to real recurring hours that need to be protected on a Level III's calendar, not squeezed in around other priorities.
• Letting practical assessment quality slide once the novelty wears off. The first cohort often gets careful, well-supervised practical assessment; by the third or fourth cohort, assessment quality frequently degrades as it becomes routine — this is exactly when defensibility gaps start accumulating unnoticed.
• No clear ownership when a certified technician's competency is later questioned. Programs need a defined process for investigating a challenged certification — who reviews it, what triggers a requalification requirement, and how it's documented — decided in advance rather than improvised under pressure after an incident.
• Building the program around today's scope of work only. A program that can't flex to add a new method or application when the business wins a contract requiring it becomes a bottleneck on growth rather than an enabler of it.

Budgeting the Real Cost Categories

Employers evaluating whether an in-house program pencils out should budget across several distinct cost categories rather than thinking of it as a single line item: Level III oversight time (the most persistently underbudgeted category), calibration standards and reference/flawed sample inventory that needs periodic replenishment as samples wear from repeated use, dedicated facility or equipment time that doesn't compete with billable production work, exam administration and record-keeping overhead, and ongoing curriculum maintenance as codes and client specifications evolve. None of these costs are fixed one-time expenses — they recur every training cycle, and employers who budget only for the initial buildout and not the ongoing maintenance are the ones who end up with a program that quietly decays after its first year or two of strong execution.

A Phased Rollout Plan

Employers building an in-house program from scratch generally do better phasing the rollout rather than launching everything simultaneously: finalize the written practice and choose SNT-TC-1A or CP-189 as the governing framework first, secure genuine Level III ownership of the program second, build curriculum and source practical training materials for your highest-priority one or two methods third, and only then expand to additional methods once the first cohort has been trained, certified, and — ideally — successfully audited by a client or reviewed internally against the written practice. Trying to stand up a full multi-method program in one sprint is how the written practice ends up disconnected from what training actually delivers, which is the single most common reason in-house programs get flagged during their first serious external audit.

Measuring Whether the Program Is Actually Working

A program's success isn't measured by how many certificates it issues — it's measured by whether certified technicians perform reliably once they're deployed independently, and whether the program's documentation survives contact with an external audit. Employers should track a handful of concrete indicators over time: how often newly certified technicians require correction or re-training in their first six months of independent work, how the program's documentation performs against internal mock audits run before a client ever asks to see it, and whether recertification cycles are being completed on schedule or slipping. A program generating steady certificates but showing rising correction rates in the field is a warning sign that curriculum or practical assessment rigor has quietly eroded, and it's far cheaper to catch that through internal review than through a failed inspection downstream. Building this kind of feedback loop into the program from the start — not bolting it on after a problem surfaces — is what separates a training program that actually improves technician competency over time from one that just produces paperwork.

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.