NDT Consulting for Startups: Building Your First Written Practice From Scratch

The First 90 Days of an NDT Department That Doesn't Exist Yet

Every NDT service provider and every fabricator's in-house inspection department started the same way: zero personnel files, zero procedures, and a founder or quality manager who knows the work needs to be defensible from day one but isn't sure what "defensible" actually requires on paper. The single most consequential document in that first 90 days is the written practice — and it's also the document new companies most often get wrong, because it looks like paperwork when it's actually the decision record for the entire qualification and certification program.

For a first practice written from the beginning by an ASNT NDT Level III, see NDT written practice development.

ASNT SNT-TC-1A is a recommended practice, not a mandatory third-party certification standard — which is exactly what makes it easy to underestimate. Unlike ISO 9712 or PCN, where a central certification body issues the credential, SNT-TC-1A puts the employer in the driver's seat: the company writes its own written practice, using SNT-TC-1A's guidelines as the reference framework, and the company — through its designated NDE Level III — makes the actual certification decisions. That's a real responsibility, and a startup that treats the written practice as a template to fill blanks in usually finds out how much was missing the first time a client or a code body's auditor asks to see it.

This employer-based model is also why two companies performing the same method can have legitimately different certification requirements without either one being wrong. A shop doing UT on structural steel welds to AWS D1.1 and a shop doing UT on pressure vessel welds to ASME Section VIII may reasonably set different experience-hour minimums, different practical exam specimens, and different recertification intervals in their respective written practices — because the risk profile, the code requirements, and the client expectations differ. A startup that doesn't understand this flexibility either over-copies a stricter program it can't practically staff to, or under-builds a weaker one that won't survive a client's technical audit.

Step One: The Written Practice Isn't a Template, It's a Decision Document

SNT-TC-1A's guideline tables — minimum classroom training hours and documented experience hours by method and qualification level — are exactly that: guidelines, not mandates. The company's written practice is where those guidelines become the company's actual requirements, adjusted for the methods it performs, the codes its clients require, and the level of risk in the work. A startup that copies another company's written practice wholesale — hour requirements, method list, and all — has adopted someone else's risk decisions without ever making its own.

What SNT-TC-1A Actually Asks the Employer to Own

At minimum, a written practice needs to define which methods the company covers — UT, RT, MT, PT, VT, ET, and others as applicable — and at which qualification levels; the education, training, and experience requirements for each method and level; the examination structure (general, specific, and practical) required before certification; vision examination requirements and renewal frequency, typically near vision and color contrast verified annually; and the certification period and recertification requirements. None of that is filled in from a generic source — it's a set of decisions the company has to make and be able to defend to a client's quality auditor.

Step Two: Personnel Certification Program Structure

Level I, II, and III Responsibilities — and Who Signs What

The three-tier structure isn't arbitrary. A Level I technician performs specific calibrations, tests, and evaluations according to written instructions, under the supervision of a Level II or III, and doesn't independently decide acceptance or rejection. A Level II sets up and calibrates equipment, interprets and evaluates results against applicable codes and standards, organizes and reports results, and provides direction to Level I personnel. A Level III — the role a startup most often underbuilds — is qualified to establish techniques, interpret codes and standards, designate the particular methods and procedures to be used, and has the training and standing to qualify and examine Level I and Level II personnel. In a startup's early structure, it's tempting to let a strong Level II act as a de facto Level III without ever formally qualifying at that level — a decision that looks fine until a client's quality audit or a code compliance review asks who actually holds Level III authority on file, and the honest answer is nobody does.

The Eye Exam and OJT Hours Mistake Almost Everyone Makes

Two personnel-file gaps show up constantly in first-year NDT departments. The first is certifying technicians without a documented annual near-vision and color-contrast exam on file — not just performed, but dated, filed, and tied to the specific technician's certification record. In practice this means a near-vision acuity check (commonly a Jaeger J1 or J2 equivalent chart) and a color-contrast test (an Ishihara plate test is the usual method), administered annually and signed by whoever administered it, with the result sitting in the personnel file next to the certification it supports — not in a separate binder nobody cross-references. The second gap is logging on-the-job training hours as a lump sum rather than as dated entries with supervisor sign-off, which means when an auditor asks to verify that a Level II candidate actually accumulated the required hours under qualified supervision, there's no way to substantiate it after the fact. Both are cheap to do right from day one and expensive to reconstruct a year later.

Step Three: Procedure Qualification, Not Procedure Copying

A written UT or MT procedure borrowed from a previous employer, a client, or a downloaded template is not a qualified procedure for a new company — it reflects someone else's equipment, someone else's personnel, and someone else's material conditions. A procedure has to be demonstrated to work on the company's own equipment, by the company's own qualified personnel, on representative material or welds, with the results documented as a procedure qualification record. This matters most acutely for fabricators bringing NDT in-house to support welding inspection: a UT procedure qualified for one code's acceptance criteria — say, ASME Section VIII — isn't automatically valid for a different code's criteria, such as AWS D1.1 structural welding, even if the equipment and technician are identical. Each code-and-application combination needs its own qualification trail.

A practical example makes this concrete. Suppose a new fabricator's NDT department writes a UT procedure for inspecting groove welds on a specific joint configuration. Qualifying that procedure means running it on a mockup weld with known reflectors — side-drilled holes or notches at documented depths — built in the same material and thickness range the production welds will actually use, and demonstrating that the procedure, in the hands of the company's own certified technician, correctly detects and sizes those known reflectors within the code's acceptance criteria. Only once that demonstration is documented does the procedure count as qualified for that application. Doing this once at startup, for every method-and-code combination the company expects to use in its first year, is far cheaper than doing it retroactively after a client's quality department rejects a report because the underlying procedure was never actually qualified.

Step Four: Equipment Calibration Program

A calibration program needs three things a startup rarely has all of on day one: reference standards traceable to a national standard (NIST, in the US), a defined calibration frequency for each instrument type — commonly annual, with per-use or per-shift verification layered on top — and a documented process for what happens when a piece of equipment is found out of tolerance, including how to handle results generated with that equipment before the out-of-tolerance condition was caught. Skipping that last piece is common and dangerous: without it, a single miscalibrated gauge can quietly invalidate weeks of inspection results with no clean way to identify which reports are affected.

Different instrument types carry different verification routines, and a written practice should spell each one out rather than treating "calibration" as one generic requirement. A UT thickness gauge needs a documented reference block check — typically before each shift and whenever the probe or couplant changes — in addition to its periodic full calibration. A magnetic particle yoke needs a documented lift-test (commonly a pull test against a specified minimum weight) on a defined schedule, not just once at purchase. Penetrant systems need sensitivity verification against a reference panel with known indications on a defined interval, and UV light sources used for fluorescent methods need intensity checks logged against a minimum threshold. A calibration program that only tracks "annual cal due" dates in a spreadsheet, without these method-specific interim checks, is missing exactly the layer that catches equipment drift between full calibrations — which is usually when it actually matters in the field.

Step Five: NDE Level III Oversight — Who's Actually Accountable

Every written practice needs a named, qualified Level III behind it — someone with the standing to write and sign the written practice, resolve interpretation disputes, and take responsibility when a client or code body asks hard questions about a certification decision. Startups without an in-house Level III have two real options: qualify someone internally as the company grows, or bring in Level III oversight as a consulting relationship until that internal capability exists. Neither option is a shortcut around the requirement — a written practice with no genuine Level III behind it is a document that won't survive its first serious audit.

Where This Connects to ISO 9001 and Welding Code Compliance

Most NDT startups eventually run into ISO 9001 from the client side — an EPC or fabricator client requiring its inspection suppliers to operate under a certified quality management system — and the written practice, calibration records, and personnel files built correctly from day one become the objective evidence an ISO 9001 auditor expects to see, rather than a separate project to build later. The same is true for welding inspection specifically: AWS D1.1 and ASME Section IX both reference NDT personnel qualification and procedure requirements as part of weld acceptance, which means a fabricator's in-house NDT department needs its procedures qualified against the exact code its welding program operates under, not against NDT in the abstract. Getting this sequencing right the first time — written practice, then personnel program, then procedure qualification tied to the actual codes in use, then calibration — saves a company from redoing all four once a client's audit or a code compliance review forces the issue.

Common First-Year Mistakes We See Walking In

• Personnel certified with a training course completion certificate mistaken for the employer's actual SNT-TC-1A certification — the training vendor certifies attendance and competency demonstration; the employer's Level III makes the certification decision.
• Procedures copied from a previous employer or a generic template with no site-specific or code-specific qualification record behind them.
• No documented Level III oversight structure — a strong Level II informally treated as the final technical authority with nothing on file to support it.
• Vision exams performed but not dated, filed, or linked to the specific certification record they're supposed to support.
• Calibration records kept, but no documented process for what happens to results generated before an out-of-tolerance condition was discovered.
• A written practice built once at company formation and never revisited as new methods, new codes, or new clients are added.

How an Atlantis Consulting Engagement Sequences This

When a startup NDT provider or a fabricator's new in-house department engages Atlantis's ASNT Level III consulting service, the work is sequenced deliberately rather than tackled all at once: first the written practice itself, built around the company's actual methods and client codes rather than a generic template; then the personnel certification program structure, including the Level I/II/III responsibility matrix and the documentation trail for vision exams and OJT hours; then procedure qualification tied to the specific codes the company's clients require; then the equipment calibration program; and throughout, establishing — or providing, as an interim consulting relationship — genuine NDE Level III oversight. Where it makes sense, that program also gets built directly into Atlantis NDT ERP from the start, so personnel certification expiry, calibration due dates, and procedure qualification records live as linked data instead of a folder of PDFs the company has to reconstruct at audit time, and new technicians coming up through the program can be trained toward ASNT SNT-TC-1A through Atlantis's own NDT training pathway rather than starting that search from scratch.

Building It Once, Correctly

A startup NDT department has one real advantage over an established one: nothing has to be unwound. There's no legacy written practice full of decisions nobody remembers making, no personnel files missing documentation because "that's just how it's always been done here." Getting the sequence right, from the first written practice through the first calibration program, means the company is building a defensible structure from day one instead of retrofitting one under audit pressure two years in — and that difference shows up every time a client's quality team, a code compliance reviewer, or a new prospective customer asks to see how the program actually works.

If you're standing up an NDT department for the first time — or inheriting one that was never built with this structure — that's exactly where a consulting engagement like this starts.

Atlantis NDT Products & Services