Method Competence Versus Code Authority: Two Different Jobs

The difference in one signature line

Put both credentials against a single question: whose name goes on the disposition? An ASNT NDT Level II signs an examination report — this weld, this technique, these indications, accept or reject against the criterion in the procedure. That is a technical statement about a test. An API 510 inspector signs something categorically different: this vessel continues in service, on this interval, with this repair accepted. That is a statement about the equipment, and it carries the code, the owner-user programme and the insurer behind it.

The confusion arises because both people say 'accept' and 'reject'. The Level II accepts an indication against a procedure written and approved by a Level III. The code inspector accepts the equipment against a published code and a documented integrity case. One judgment is bounded by a procedure; the other is bounded by a code and by professional judgment about degradation the procedure never anticipated. Identical vocabulary, entirely different exposure when the decision is examined afterwards.

Every downstream difference follows from that split: who issues the certificate, what the examination tests, how long it stays valid, what happens when it lapses, and whose professional liability responds if a disposition proves wrong. Career paths diverge there too — method depth leads toward Level III and procedure ownership, while code authority leads toward fixed-equipment inspection, integrity engineering and programme ownership. The ASNT certification path and the API ICP path are parallel ladders, not two rungs of one.

Who issues the certificate is the tell

An ASNT NDT Level II under the SNT-TC-1A route is certified by the employer, not by ASNT. SNT-TC-1A is a recommended practice that tells an employer how to build its own certification programme through a written practice covering training hours, experience, examinations and vision testing. The certificate travels with the employer, not the person. Change employers and the new one re-certifies you under its written practice, normally on the strength of your documented training history and logged experience.

ASNT also runs a central examination programme carrying the ASNT NDT Level II name, with published prerequisites per method. Ultrasonic and radiographic testing each require 12 days of training, 120 days of experience in the method and 229 days of total NDT experience, against 2 days of training and 30 days in method for penetrant testing. That programme renews every five years, and the employer still administers the visual acuity, practical and job-specific examinations under its own written practice. Central examination does not remove employer responsibility.

API ICP works the other way round. API certifies the individual centrally, the certificate is portable between employers, the programme is ANSI-accredited to ISO/IEC 17024, and the term is a fixed three years regardless of who you work for. The difference between an employer-based scheme and a central one is the whole subject of SNT-TC-1A versus CP-189, and the same axis explains why a code inspector's certificate follows the person while a Level II's often does not.

What an ASNT Level II can and cannot sign

A Level II selects the technique, calibrates the equipment, performs the examination, interprets and evaluates the results against the code, standard or specification named in the procedure, and writes the report. In practice they also brief Level I technicians and verify their work. In a plant, a UT Level II is the person whose thickness data feeds every corrosion rate the integrity programme uses, which makes their competence load-bearing for decisions they themselves do not make.

A Level II cannot approve the procedure they work to, cannot certify another technician, and cannot set an inspection interval or accept a repair on the equipment itself. The first two belong to a Level III; the third belongs to a code inspector. Nothing in SNT-TC-1A grants a Level II any authority over the equipment, because the certificate scope runs to the examination method and stops there. Training hour requirements differ sharply by method for exactly this reason — the technique is what is being certified.

That boundary is why method choice matters so much on a CV. Twelve training days and 120 in-method days for UT or RT against two or three days for PT and MT reflects the difficulty of the interpretation, and it maps straight through to pay. The full breakdown sits in NDT training hour requirements by method, and the pay consequence of that difficulty gradient shows up clearly in the NDT Level II salary data for the US market.

What a code inspector can and cannot do

An API 510 holder judges a pressure vessel against the code: whether inspection findings support continued service, what the next internal or on-stream interval should be, whether a repair or alteration meets the code, whether a rerating is justified. API 510 defines the authorized pressure vessel inspector as an employee of an authorized inspection agency, qualified and certified under the code, which means the authority is organisational as well as personal. The certificate alone does not confer it outside that structure.

What the certificate does not do is qualify anyone to perform an NDT method. An API 510 holder with no UT certification cannot take the thickness readings their own decision depends on. This surprises people who assume the higher-authority credential contains the lower one. It does not, at any point. The two are examined separately, recorded separately, and expire on different cycles — a fixed three years for API ICP, an employer-set or five-year cycle for the method certificate.

The same non-containment applies to welding. An API 570 inspector judging a piping repair relies on weld acceptance work an AWS CWI performs against a welding code, and on metallurgy knowledge that API 577 covers as a supplemental certification. Where those three credentials overlap and where they emphatically do not is set out in the comparison of AWS CWI, API 577 and ASNT Level II, which is the fastest way to see the boundaries side by side.

The stack senior fixed-equipment inspectors actually hold

The common stack in a US refinery or terminal is a code certification against the equipment class, at least one NDT method certification at Level II, and a welding inspection credential. A tank specialist carries API 653 plus UT Level II plus CWI. A piping specialist carries API 570 plus UT and often RT interpretation, plus CWI. Each addition buys a different signature rather than a better version of the same one, which is why the stack grows sideways instead of upward.

Above that, API 571 for corrosion and materials and API 580 for risk-based inspection turn an inspector into someone who can design the programme rather than execute it, while an ASNT Level III turns them into the person who owns the procedures and certifies the technicians. Those are two different careers heading in different directions, and the NDT Level III salary data separates the procedure-ownership track cleanly from Level II execution work.

Stacking carries a maintenance cost that policies routinely underestimate. Each credential runs its own clock: API ICP renews every three years with 24 CPD hours and a web quiz every sixth year, AWS CWI renews at three and six years with a nine-year recertification requiring an examination or 80 professional development hours, and method certificates renew independently. A three-credential inspector has three unrelated expiry dates, which is why holding them in a certification tracking register beats a spreadsheet.

Should QA inspectors hold both a vessel and a piping certification?

Cross-training and certification are not the same thing, and the question usually conflates them. If your internal QA inspectors sign dispositions on both pressure vessels and piping circuits, they need both API 510 and API 570, because the certificate is what the code and your owner-user programme point at. Cross-training without the certificate produces a person who is genuinely competent and cannot sign, which is the worst of both worlds — you have paid for the capability and still cannot use it.

If they sign on one class and support the other — reviewing data, coordinating scope, escalating findings — then one certification plus documented cross-training is sufficient, provided the programme names who signs for the second class and that person is reachable on the timescales your intervals demand. Build the coverage matrix first: equipment classes down one axis, shifts and turnaround phases across the other, certified signatories in the cells. The certification requirement falls out of the empty cells rather than out of a headcount rule.

The overlap argument for holding both is real and worth acting on. API 510 and API 570 share substantial ground in damage mechanisms, NDE selection, welding and repair rules, and both examinations are 170 questions over 7.5 hours with the same closed-book and open-book split. A candidate who has just passed one is at their strongest for the second, and taking them in consecutive exam windows costs considerably less preparation time than spacing them years apart.

The time and cost decomposition, in published third-party figures

API publishes its ICP fees openly, which makes half the budget easy to fix. Initial certification for API 510, 570 or 653 is $875 for API members and $1,125 for non-members; recertification is $745 and $855. API 1169 and 1184 are $435 and $580 initially, $310 and $435 to recertify. Those figures cover the examination and the certification, and nothing else — not preparation, not travel, not the standards the open-book half is sat against.

AWS publishes its own list. The CWI nine-year recertification course is $2,130 for members and $2,395 for non-members, and the Prometric endorsement examinations for MT and PT sit at $1,295 for members and $1,560 for non-members each. ASNT's Level II prerequisites are counted in training days and experience days rather than dollars, and that is where the real cost sits: 12 training days plus 120 in-method days for UT is most of a year of deliberately assigned work.

That asymmetry is the planning insight most employers miss. The code certification is a money-and-scheduling problem measured in weeks. The method certification is a time-and-supervision problem measured in months of logged experience against a written practice. Employers who treat both as 'send them on a course' get the first and miss the second entirely, and the missing piece is documented on-the-job hours — the mechanics of which are in our guide to OJT hours log requirements.

Writing the distinction into job descriptions and the written practice

Job descriptions cause most of this confusion in the market. A posting asking for an 'API 510 certified NDT inspector' collapses two roles into one line and attracts applicants who hold one credential and assume it implies the other. Split the requirement into two statements: the code certification required for the dispositions the role signs, and the method certifications required for the examinations the role performs, each marked required or preferred. Recruiters screen better, candidates self-select accurately, and the audit file matches the posting.

Your written practice does the same job internally. It defines your qualification levels, training and experience requirements, examinations and recertification intervals for NDT personnel, and it is the document an auditor reads to test whether your Level II certifications mean anything at all. Code certifications sit outside it and are evidenced by the API certificate itself. Keeping the two documents distinct is what stops an auditor finding a Level II signature on a code decision, which is a finding nobody argues their way out of.

The third document is the coverage matrix, and it is the one most programmes lack. Certificates in a folder prove individuals are qualified; a matrix proves the programme is covered, and auditors ask the second question. Building or rewriting all three is what written practice development covers, and where a company has no internal Level III to hold the technical pen, an outsourced ASNT Level III can sign and maintain them.

Which one to get first

Get the method certification first, in almost every career. It is the entry credential, it generates the field experience API eligibility counts, and it pays from the first day. API ICP eligibility is written in years of experience: one year of inspection activity for a candidate with an engineering degree or three-plus years of technical military service, two years with a two-year technical degree, three years with a high school diploma, five or more with no formal education — all acquired within the last ten years while employed by or under contract with an authorized inspection agency.

The exception is the engineering graduate entering integrity work directly. With a degree and one year of qualifying inspection activity, API 510 or 653 is reachable early, and a method certification added afterwards makes that person credible in the field rather than only on paper. That order is unusual and it works only where the employer can supply supervised inspection experience quickly, which most contract shops cannot and most owner-operators can.

For welders moving across, the sequence is method certification, then CWI, then code certification once the experience clock has run — the route mapped in the welder to NDT inspector career path. Whichever order you take, the credentials never substitute for one another. Atlantis delivers ASNT method training and employer programme support rather than API ICP training; see NDT training in the USA for the method side of that path.

Request a consultation