ASME Section V Compliant Reporting: What Your Software Template Must Include

Section V Is a Framework, Not a Fill-in-the-Blank Form

ASME Boiler and Pressure Vessel Code, Section V, "Nondestructive Examination," doesn't hand a shop a report template. It defines a set of requirements — general requirements in Article 1, and method-specific requirements in the articles that follow — that a report has to satisfy, and it leaves the actual document format up to the organization performing the examination, subject to whatever the referencing Code Section (Section VIII for pressure vessels, B31.3 for process piping, B31.1 for power piping, and so on) additionally requires. That flexibility is exactly why so many shop templates drift out of compliance without anyone intending it to happen: nothing forces a Word document to include every element Section V actually calls for, and a report can look complete — formatted nicely, signed, delivered on time — while quietly missing a required element that only becomes a problem when a client's QA department or a third-party auditor checks it against the code.

Article 1: The General Requirements Every Report Needs

Article 1 sets the baseline that applies across every method. At minimum, a compliant record needs to identify the examination procedure used and its current revision, the acceptance criteria applied (and where that criteria comes from, since Section V itself generally doesn't set acceptance standards — the referencing code section does), the personnel who performed and interpreted the examination along with their qualification level, the equipment used including model and serial number, the calibration standard and its traceability, and the actual results in enough detail that someone reviewing the record later can reconstruct what was found without having to guess. A template missing any one of these — a UT report with a results table but no reference to which acceptance criteria was applied, for instance — is a template that looks finished and isn't.

Personnel Qualification

Article 1 requires the report to identify who performed the examination and their qualification level, consistent with the employer's written practice — typically structured around ASNT SNT-TC-1A or an equivalent recommended practice such as ASNT CP-189. This isn't a courtesy line item; a client reviewing the record needs to be able to confirm the person who signed off was actually certified to perform that specific method at the time the exam was done, which is precisely why a report template should pull certification data from an actual personnel record rather than accepting free text a technician types from memory.

Equipment and Calibration Traceability

Every method article under Section V requires calibration against a known reference — a calibration block for UT, a step wedge or penetrameter for RT, a shim or ring standard for MT. The report needs to identify the specific calibration standard used, and that standard itself needs to be traceable, typically to NIST or an equivalent national standard, through the shop's own calibration records. A report that lists "Cal Block: IIW" with no serial number or calibration date attached leaves an auditor with no way to verify that the reference standard used on this specific job was itself in current calibration.

Method-Specific Requirements a Generic Template Misses

Article 2: Radiographic Examination

RT records need to capture source-to-film (or source-to-detector) distance, the specific radiation source and its activity or the X-ray equipment's kilovoltage settings, exposure time, the image quality indicator (IQI) type and the sensitivity actually achieved, and film or digital detector identification. For digital radiography, Article 2 requirements extend to establishing the equivalent sensitivity and density (or equivalent grayscale value) requirements appropriate to the digital system, which a template built for film-only RT often fails to account for. A shot map tying each exposure to a specific weld location and technique is also essential documentation, particularly for reshoots and repair tracking.

Article 4: Ultrasonic Examination of Welds

A compliant UT weld report needs the calibration block identification and its essential dimensions, the reference reflector used to establish the Distance-Amplitude Correction (DAC) curve or Time-Corrected Gain (TCG) settings, transfer correction values where applicable, transducer frequency and size, scanning sensitivity, and actual coverage achieved relative to the required scan plan. A generic "results" text field that just says "no relevant indications found" without documenting the calibration and scan parameters behind that conclusion doesn't meet the article's intent, even if the finding itself was accurate.

Article 5: Ultrasonic Examination of Materials

Distinct from weld examination, Article 5 governs UT of base materials — plate, forgings, castings — and requires its own calibration and coverage documentation appropriate to the geometry being examined. A shop template built only around weld UT (the far more common recurring scope) frequently isn't structured correctly for the different essential variables that apply to material examination, which becomes a problem the first time a client requests forging UT ahead of a fabrication job.

Articles 6 and 7: Liquid Penetrant and Magnetic Particle Examination

PT records under Article 6 need penetrant type and, where relevant, batch or lot identification, dwell time for both penetrant and developer, method (visible or fluorescent), and surface preparation. MT records under Article 7 need magnetization method (yoke, prod, coil), current type and amperage, field direction and coverage relative to the required two directions, and the examination medium (dry powder or wet suspension, fluorescent or visible). Both are fast, high-volume methods, which is exactly why shops running high daily report counts on these methods are most likely to let essential-variable documentation slip in favor of speed — a risk a structured template with required fields closes off by not allowing the report to be completed without those fields populated.

Article 9: Visual Examination

Visual examination records need to specify direct or remote visual method, lighting conditions and measured illumination where required, and the specific surface condition and access achieved. VT is often treated as the least demanding method to document, which is precisely how its records end up thin — a one-line "no defects noted" entry with none of the supporting detail a code-compliant record actually calls for.

Common Gaps Found When Existing Templates Get Audited

Reviewing a shop's legacy Word or Excel templates against Section V article by article tends to surface the same handful of gaps repeatedly, regardless of which shop's templates are under review. Scanning sensitivity is documented as a pass/fail statement ("adequate sensitivity achieved") rather than the actual dB value used. Calibration block serial numbers are referenced by type only ("IIW block") with no traceable ID linking to a specific physical block and its own calibration record. Acceptance criteria is cited generically ("per code") without the specific paragraph or edition year that actually governs the job. Coverage percentage on a UT scan plan is implied by the absence of a note about incomplete coverage, rather than stated explicitly as a positive number. None of these gaps are dramatic on their own, and none of them typically get caught by the shop's own internal review process, because the reviewer is used to seeing the same shorthand and reads past it. They get caught by a client's own inspection department, or by a third-party auditor doing a documentation review ahead of a plant turnaround, at a point where fixing them retroactively is far more disruptive than building the requirement into the template from the start.

Linking Section V Records to the Referencing Code's Acceptance Criteria

Section V tells you how to examine and how to document the examination; it generally does not set pass/fail criteria on its own. Acceptance criteria come from the referencing code section — ASME Section VIII, Division 1 for pressure vessels, B31.3 for process piping, B31.1 for power piping, or an owner's engineering specification layered on top. A report template that documents examination results without explicitly citing which acceptance standard was applied leaves a gap that becomes obvious the moment someone tries to verify a disposition independently. This is a common failure point precisely because it's invisible in day-to-day use — the report looks complete, the finding looks reasonable, and the missing citation only surfaces during an audit or a fitness-for-service review years later.

Article 23: Standardized Calibration Procedures Behind the Report

Article 23 of Section V houses the standard units used across the method articles to qualify and calibrate equipment — standard reference blocks, calibration procedures for specific instrument types, and the mandatory appendices that method articles point back to when they call for a particular calibration approach. A report doesn't usually cite Article 23 directly, but the calibration steps a technician performs before touching the part being examined trace back to it, and a shop's internal calibration procedures should be written to align with it rather than improvised independently. When a template's calibration section asks only for "cal date" and "block ID" without capturing the specific standard unit or procedure the calibration was performed against, it leaves out the link that actually ties the day's calibration back to a controlled, code-referenced method — a detail that matters far more to an auditor than it does in day-to-day shop use.

Essential Variables: Why a Free-Text Box Isn't Enough

Each method article defines essential variables — parameters that, if changed beyond a specified range, require re-qualification of the procedure. A generic reporting template that captures these as unstructured free text makes it functionally impossible to verify at a glance whether a given exam was actually performed within its procedure's qualified range. A structured template, by contrast, can validate that entered values fall within the procedure's documented essential variable ranges and flag it when they don't — catching, for example, a UT scan performed with a transducer frequency outside what the cited procedure actually qualifies, before the report goes out the door rather than after a client catches it.

Record Retention and Future Fitness-for-Service Reviews

Inspection records built today frequently get used years or decades later — a fitness-for-service assessment under API 579-1/ASME FFS-1 draws directly on historical UT thickness data to calculate corrosion rates and remaining life. A record that's technically Section V compliant but locked in an unstructured PDF, with no way to extract the raw thickness grid data for trending, delivers far less value to that future analysis than a structured record where the underlying data can be pulled and compared directly against prior surveys. This is one of the strongest practical arguments for moving report generation onto structured NDT reporting software rather than a document-based workflow — code compliance today and usable data tomorrow aren't separate goals, they're the same design requirement viewed from two different points in time.

What a Compliant Template Checklist Should Actually Look Like

• Procedure number, revision, and date, tied to a controlled procedure library rather than typed fresh each time.
• Named acceptance criteria, citing the specific referencing code section, edition, and applicable paragraph.
• Technician and reviewer identification with certification level, verified against an active personnel record.
• Equipment identification with model, serial number, and current calibration status pulled from a calibration record, not typed manually.
• Calibration standard identification and its own traceability.
• Method-specific essential variables captured as structured, validated fields rather than free text.
• Results documented with enough detail — location, dimensions, orientation — to be independently reconstructed later.
• A locked, tamper-evident record once signed, with a retrievable audit trail.

Building Compliance Into the Template, Not Relying on Memory

The shops that stay clean under audit aren't the ones with the most experienced reviewers catching every gap by eye — they're the ones whose report template structurally can't be submitted with a required Section V element missing. That shift, from relying on a person to catch every gap to building the requirement into the software itself, is the single highest-leverage change a shop can make to its reporting process. It's also exactly the kind of gap analysis worth bringing an outside ASNT Level III consulting engagement in to review — an independent read on whether a shop's existing templates actually satisfy Article 1 and the relevant method article, before a client's auditor finds the gap first.

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.