16.1 Interpreting Codes, Standards, and Specifications

ASNT NDT Level III Basic Examination Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Level III Role and Certification Path 1.3 Eligibility, Fees, Scheduling, and Retakes 1.4 Study Strategy and Exam-Day Approach

2 Chapter 2: Materials Fundamentals for NDT

2.1 Ferrous Metals and Iron-Carbon Phases 2.2 Non-Ferrous Metals and Alloys 2.3 Mechanical Properties and Crystal Structure

3 Chapter 3: Manufacturing Processes

3.1 Casting Processes and Cast Discontinuities 3.2 Forging, Rolling, and Forming 3.3 Extrusion, Drawing, and Machining 3.4 Heat Treatment Effects

4 Chapter 4: Welding and Joining Processes

4.1 Fusion Welding Processes 4.2 Weld Metal and HAZ Discontinuities 4.3 Brazing, Soldering, and Mechanical Joining

5 Chapter 5: Discontinuity Classification

5.1 Inherent Discontinuities 5.2 Processing Discontinuities 5.3 Service Discontinuities

6 Chapter 6: Specific Discontinuity Types

6.1 Cracks and Fracture Modes 6.2 Porosity, Inclusions, and Lack of Fusion 6.3 Laminations, Seams, Laps, and Undercut 6.4 Relevant vs Non-Relevant Indications

7 Chapter 7: NDT Method Selection and Inspection Planning

7.1 Method Selection Principles 7.2 Surface vs Volumetric Methods 7.3 Inspection Planning and Flaw Expectations

8 Chapter 8: Ultrasonic and Radiographic Testing

8.1 Ultrasonic Testing Principles and Applications 8.2 UT Limitations, Calibration, and Evaluation 8.3 Radiographic Testing Principles and Applications 8.4 RT Limitations, Image Quality, and Safety Basics

9 Chapter 9: Magnetic Particle, Liquid Penetrant, and Visual Testing

9.1 Magnetic Particle Testing 9.2 Liquid Penetrant Testing 9.3 Visual Testing

10 Chapter 10: Electromagnetic, Leak, Acoustic Emission, and Infrared Testing

10.1 Electromagnetic / Eddy Current Testing 10.2 Leak Testing 10.3 Acoustic Emission Testing 10.4 Thermal / Infrared Testing

11 Chapter 11: Specialty Methods and Method Comparison

11.1 Neutron Radiography 11.2 Magnetic Flux Leakage 11.3 Method Comparison and Supplemental Examinations

12 Chapter 12: SNT-TC-1A Recommended Practice

12.1 SNT-TC-1A Overview and Written Practice 12.2 SNT-TC-1A Training and Experience 12.3 SNT-TC-1A Examinations and Recertification

13 Chapter 13: CP-189 Standard Practice

13.1 CP-189 Overview and Scope 13.2 CP-189 Mandatory Requirements 13.3 SNT-TC-1A vs CP-189 Comparison

14 Chapter 14: CP-105 and NDT Training Programs

14.1 CP-105 Purpose and Topical Outlines 14.2 Developing and Approving NDT Training 14.3 OJT, Mentoring, and Instructor Oversight

15 Chapter 15: Building and Managing Certification Programs

15.1 Building Qualification and Certification Programs 15.2 Administering Examinations and Evaluating Competency 15.3 Program Audits and Managing Certifications

16 Chapter 16: Codes, Standards, Procedures, and Quality

16.1 Interpreting Codes, Standards, and Specifications 16.2 Developing and Approving NDT Procedures 16.3 Acceptance Criteria and Quality Control 16.4 External Audits and Inspection Documentation

16.1 Interpreting Codes, Standards, and Specifications

Key Takeaways Explain This Topic AI

Domain 5.1 expects Level IIIs to interpret NDT requirements embedded in codes, standards, and specifications—not only to perform inspections from a finished procedure.

Document hierarchy is high-yield: codes and invoked standards set mandatory or contractual requirements; specifications and purchase orders refine product rules; employer procedures and work instructions implement the work.

Codes, standards, specifications, and procedures are different document classes; treating them as interchangeable is a common Basic exam trap.

Client NDT requirements may invoke personnel documents (SNT-TC-1A or CP-189), method standards, acceptance criteria, and hold points—the Level III maps those invocations into shop capability.

When requirements conflict or are silent, escalate through the engineering/contract interface rather than inventing unofficial acceptance or skipping required examinations.

Last updated: July 2026

16.1 Interpreting Codes, Standards, and Specifications

Quick Answer: On the Basic exam, Domain 5.1 tests whether a Level III can interpret NDT requirements that live inside codes, standards, and specifications —not merely run a procedure already written by someone else. Master the document hierarchy (code/standard → specification/PO → procedure/work instruction), recognize where NDT typically appears (method, extent, personnel, acceptance, documentation), and know when to escalate conflicts instead of inventing shop rules.

Chapters 12–15 covered personnel qualification documents and how to build a certification program. Domain 5 shifts the lens from who may inspect to what the product and contract require . A Level III who cannot read a code invocation, a fabrication specification, or a customer PO will write the wrong procedure, approve the wrong technique, or accept work that fails audit—even if method physics is excellent.

Document Hierarchy: Codes vs Standards vs Specifications vs Procedures

Basic exam items love word games. Treat these classes as distinct , even though real projects pile them into one package.

Document class Typical role NDT angle

Code Legally or contractually invoked body of rules for design, fabrication, inspection, or service (often with enforcement through jurisdiction or customer contract) May mandate examination methods, stages, acceptance, and personnel qualification

Standard Consensus or industry document defining practices, methods, or quality systems (ASTM, ISO, ASNT, EN, etc.) Method practices, equipment, calibration, procedure content, personnel frameworks

Specification Product-, project-, or owner-specific requirements that refine or add to codes/standards Extent of exam, hold points, extra methods, tighter acceptance, reporting format

Procedure Employer or supplier document describing how NDT will be performed for defined scope Technique parameters, calibration, evaluation steps, acceptance reference, records

Work instruction / technique sheet Narrow, job-level instructions derived from the procedure Probe, technique, coverage map, part-specific setup

Codes

A code is typically a structured set of rules adopted for design, construction, inspection, or in-service integrity. Examples Level IIIs encounter conceptually (without needing memorized paragraph numbers on Basic):

Pressure equipment and piping construction/inspection codes that require volumetric or surface NDT at defined stages

• Structural welding codes that prescribe visual and nondestructive examination of welds by category
• In-service inspection frameworks that set examination methods and intervals for equipment in operation

Codes often invoke standards by reference (method practices, personnel recommended practices, material standards). When a code says examination shall be in accordance with a named standard, that standard becomes part of the contractual or jurisdictional package.

Standards

Standards (including recommended practices) define how methods are practiced or how systems are organized. For Basic thinking:

Method standards (for example ASTM-type practices for PT, MT, UT, RT, ET) describe equipment, materials, procedure elements, and evaluation concepts.

Personnel documents (SNT-TC-1A recommended practice; CP-189 when invoked as a standard) control qualification and certification.

Quality system standards may require documented procedures, calibration control, and record retention without specifying every weld examination.

A standard may be mandatory by invocation even if it is not “law” on its own. The Level III’s job is to know what was invoked and which edition the contract or Written Practice locks to.

Specifications

A specification is often the owner’s or project’s custom layer: material specs, welding specs, NDT specs, painting specs, or a master project specification that points to codes and then adds extras. Purchase orders and data sheets can carry the same force for that order.

Specifications commonly control:

• Extent of examination (100%, percentage, random, critical locations only)
• Method selection beyond code minimums (for example adding UT where the base code only required VT/MT)
• Acceptance tighter than the base code, or mapping which code table applies
• Personnel extras (CP-189 instead of SNT-TC-1A, third-party oversight, specific Level III approval)
• Documentation (digital archive format, report fields, photographic evidence)
• Procedures and work instructions

Procedures implement the above for the organization. They do not outrank a code or customer specification when those documents are invoked—they must comply with them. Work instructions translate a general procedure into a part family or job number. Domain 5.2–5.4 (next section) covers writing and approving them; Domain 5.1 is the reading skill that precedes writing.

Exam trap: Calling a shop technique card a “code,” or treating an informal email as a “specification,” collapses the hierarchy and breaks audit defensibility.

Where NDT Appears in Requirements Documents

When you open a code, standard, or specification package, search systematically for NDT content. Typical locations (conceptual map—not invented paragraph numbers):

Scope and applicability — which components, thickness ranges, service categories, or weld classes require examination.

Examination methods and stages — fabrication, after heat treatment, before hydro, in-service intervals; surface vs volumetric methods.

Extent and sampling — full coverage, percentage, lot sampling, progressive examination rules.

Personnel qualification — invocation of SNT-TC-1A, CP-189, ISO schemes, or owner-approved programs; sometimes Level III procedure approval language.

Procedure and technique requirements — written procedures, demonstration/qualification, essential variables, calibration blocks.

Acceptance criteria — size, length, amplitude, density, or “no cracks” type rules; sometimes deferred to referenced standards.

Repair and re-examination — how rejected discontinuities are removed and re-inspected.

Documentation and retention — report content, traceability, film/digital image retention, calibration records.

A Level III reading for implementation builds a requirements matrix : document → clause theme → method/extent/acceptance/personnel → shop action. That matrix becomes the checklist for procedure development and audit readiness.

Client NDT Requirements and the Contract Interface

Most commercial NDT work is driven by client requirements , not by the shop inventing its own rules. Clients express NDT needs through:

• Invoked codes and standards listed on drawings or in the PO
• Project NDT specifications or quality plans
• ITPs (inspection and test plans) with hold/witness points
• Approved vendor lists and procedure submittal requirements
• Supplemental quality manuals for nuclear, aerospace, defense, or pressure equipment markets
• Level III interpretation duties

Domain 5.1 frames the Level III as the person who can interpret those requirements for the organization:

Confirm the organization is qualified and equipped for the methods and techniques demanded.

Identify gaps (for example customer requires TOFD but the shop only has conventional pulse-echo UT capability).

Determine whether personnel certifications match the invoked personnel document and any technique limits.

Resolve ambiguous language with the client’s engineering/quality representative in writing , not by tribal knowledge on the floor.

Ensure acceptance criteria exist before production inspection starts—or escalate when they do not (Domain 5.5).

Common conflict patterns

Pattern Level III response

Code minimum vs tighter customer spec Follow the more restrictive requirement unless a formal deviation is approved

Two standards with different procedure content Define which governs; document hierarchy in the project quality plan

Spec silent on acceptance Do not invent criteria alone—interface with engineering/owner (see 16.3)

Spec requires a personnel standard not in the Written Practice Update the program or obtain controlled exception before certifying work

Drawing note conflicts with written specification Seek written clarification; freeze work at hold points if needed

Interpreting Without Inventing Paragraph Numbers

Basic exam questions rarely require reciting a specific ASME or AWS clause number from memory. They do require you to reason about:

• Whether a requirement is mandatory because it is invoked
• Whether the Level III owns procedure approval and technique validation
• Whether acceptance is already defined or still needs engineering input
• Whether personnel rules come from SNT-TC-1A-style employer programs, CP-189, or central certification language
• Whether records must support traceability from part to procedure to calibration to inspector

If a question asks “who interprets NDT requirements of codes and standards for the employer’s program,” the Level III is the correct technical owner—not the Level I technician and not an unguided sales quote.

High-Yield Exam Traps for This Section

Treating SNT-TC-1A or a method ASTM as if it automatically applies without invocation or Written Practice adoption.

Confusing product acceptance codes with personnel qualification documents.

Assuming a procedure can override a customer specification.

Believing Level II “experience” replaces the need to read the governing documents.

Inventing acceptance criteria when the package is silent instead of using the engineering interface.

Ignoring edition control (which year of a standard is invoked can change method or personnel details).

If you can take a fictional PO that invokes a construction code, a PT method standard, SNT-TC-1A, and a customer NDT specification—and produce a clean requirements matrix of methods, extent, personnel, acceptance, and records—you are operating at Domain 5.1 Level III level.