16.4 External Audits and Inspection Documentation

16.4 External Audits and Inspection Documentation

Quick Answer: Domain 5.7 expects Level IIIs to participate in external customer audits (and analogous third-party/customer surveillance) of NDT. Domain 2.14 expects proper documentation of inspection results. Audit success is not theater on audit day—it is traceability every day: part ID → procedure/revision → certified person → calibrated equipment → recorded results → disposition, with digital or paper records that can be retrieved and defended.

Sections 16.1–16.3 built interpretation, procedures, acceptance, and QC. This section is how you prove the system works when a customer, authorized inspector, regulatory body, or corporate auditor asks.

Why External Audits Matter for Level IIIs

External audits of NDT programs typically examine:

• Written Practice / certification procedure and implementation evidence
• Method procedures, approvals, and essential variable control
• Personnel certifications, vision, and technique limits
• Equipment lists and calibration certificates
• Sample inspection reports and underlying images/data
• Nonconformance and corrective action history
• Training effectiveness and internal audit results
• Supplier NDT control if work is subcontracted

The Level III is usually the technical host: explaining methods, walking the process, retrieving records, and owning technical corrective actions. Quality managers may own the audit logistics, but shallow technical answers from the Level III fail the customer’s confidence test even if the binders look pretty.

Participating Effectively in External Audits

Before the audit

1. Map the scope — which methods, sites, product lines, and standards are in scope?
2. Pre-audit self-check — pull a vertical slice: one job from PO → procedure → cert file → calibration → report → NCR if any.
3. Fix known gaps — expired vision, uncontrolled procedure copies on the floor, missing calibration stickers, incomplete reports.
4. Prepare an evidence index — so retrieval is minutes, not hours.
5. Brief the team — who answers what; how to escalate unknown questions; no guessing on the record.

During the audit

• Answer accurately; say “I will retrieve that record” rather than inventing.
• Distinguish requirement (what the code/spec/Written Practice requires) from practice (what people actually do)—and close gaps, do not hide them.
• Demonstrate live process controls when asked (system checks, technique setup) without performing unsafe shortcuts.
• Accept findings professionally; argue only with documented evidence, not ego.

After the audit

• Document findings and root causes (not just “retrain everyone” as a default).
• Implement corrective and preventive actions with owners and due dates.
• Verify effectiveness (follow-up audit or metrics).
• Update procedures/training if systemic.
• Communicate closure evidence to the customer when required.

Exam trap: Treating audit participation as pure hospitality. Domain 5.7 is about technical and quality system participation, not coffee service.

Inspection Result Documentation (Domain 2.14)

Documentation is part of the examination, not an afterthought. A complete inspection report package typically includes:

Identity and scope

• Customer / job / PO / drawing revision
• Part, serial/heat, weld or component ID, location description or map
• Quantity and extent examined (100%, sample plan, stage of manufacture)
• Method and technique designation

Controlling documents

• Procedure number and revision
• Acceptance criteria document and revision (or embedded criteria reference)
• Any approved deviations or RFIs affecting the exam

Personnel and equipment

• Examiner name and certification level/method (and unique ID if used)
• Equipment identifiers (instrument serial, probe IDs, densitometer, light meters, yoke, etc.)
• Calibration or performance-check status/date as required

Results and disposition

• Clear statement of results (accept/reject/repair) and listing of recorded indications with measurements
• Sketches, photographs, radiographs/digital images, A-scan/C-scan exports as required by procedure
• Nonconformance number when rejectable conditions are found
• Reviewer/approver signature when dual review is required
• Date/time and, where required, shift or environmental notes

Traceability chain

A useful mental model for Basic and for audits:

Part ID → ITP/hold point → procedure rev → acceptance rev → person cert → equipment cal → raw data/images → report → disposition → shipping/release

If any link is broken, the examination may be technically fine but not defensible.

Calibration Records and Support Documentation

Calibration and system-performance records often make or break audits:

• Master list of NDT equipment requiring calibration or check
• Certificates traceable to national/international standards where applicable
• Due dates and recall process for overdue items
• Out-of-tolerance investigation (what product was examined since last valid check?)
• Daily/shift system performance checks required by procedure (even when annual calibration is current)

Related support records:

• Procedure approval history
• Technique qualification/demonstration packages
• Consumable certifications (for example penetrant batch certifications when required)
• Radiation safety documentation interface for RT (without confusing it with NDT acceptance records)
• Training and OJT logs supporting certifications

Digital Records Discipline

Modern shops store UT data, digital RT, reports, and cert scans electronically. Domain-level thinking still applies:

Digital is not “automatic quality.” Poor digital discipline produces findings as serious as missing paper travelers.

Report Content Quality: Level III Review Habits

When reviewing reports (or teaching Level IIs to write them), check:

• Does the report match the actual technique used?
• Are indication locations unambiguous for repair crews?
• Are units and acceptance comparisons correct?
• Are reject dispositions linked to NCRs?
• Would a customer engineer unfamiliar with your shop understand the result without a phone call?

Level III review is a quality gate, especially where codes or customers require Level III signature on procedures or certain report classes.

High-Yield Exam Traps for This Section

• Believing “the part passed” is enough without a retrievable record.
• Calibration stickers current but system checks required by procedure never performed.
• Certification files complete while floor copies of obsolete procedures remain in use.
• Digital archives that nobody can open because software/licenses disappeared.
• Hiding findings from auditors instead of driving corrective action.
• Confusing personnel program audits (Chapter 15) with product inspection documentation (this section)—both matter; they are not the same evidence set.

Chapter 16 Synthesis for the Basic Exam

Domain 5 end-to-end:

If you can walk from an invoked customer specification to an approved procedure with essential variables, a controlled acceptance decision, a complete report, and an audit evidence trail, you have closed the Basic exam’s codes-and-procedures domain with true Level III judgment—not memorized slogans.