8.6 Inspection Records, Reports, and Documentation

8.6 Inspection Records, Reports, and Documentation

Inspection records are not administrative paperwork—they are the evidence chain that proves a piping system was examined, found fit for continued service, or appropriately repaired. API 570 places the authorized inspector at the center of this chain. On the certification exam and in owner-user audits, missing or inconsistent records are treated as missing inspections: if it is not documented, it did not happen in a defensible way.

Why Records Matter for API 570

Records support four core functions:

1. Interval setting – next inspection date derives from remaining life, corrosion rate, and circuit class
2. Fitness-for-service – MAWP calculations require historical thickness and damage mechanism context
3. Regulatory and insurance defense – demonstrate due diligence after incidents or OSHA reviews
4. Turnover continuity – new inspectors inherit circuits without re-baselining from scratch

Incomplete records force conservative reinspection (shortened intervals) or operational shutdown because RBI and interval extension arguments cannot be substantiated.

Thickness Databases and CML History

A thickness database is more than a spreadsheet of numbers. API 570 and API RP 574 expect:

• Unique circuit identification tied to P&IDs and isometrics
• CML numbering with physical location (e.g., "EL-3 outer radius downstream of CV-101")
• Nominal thickness, t_minimum (retirement thickness), and each inspection reading with date
• Examiner identity and NDE method (UT point vs. scan, profile RT)
• Calculated corrosion rates (long-term and short-term) with remaining life
• Basis for next inspection (half-life rule, RBI, maximum interval cap)

Common Database Failures

• Readings without location—cannot correlate future loss
• Mixing nominal and actual thickness in MAWP calculations
• Single reading with no trend—corrosion rate assumed zero (unsafe)
• Failing to update after repairs that change wall thickness locally

Inspectors reviewing records should verify the controlling CML (minimum remaining life) is flagged and drives the circuit schedule.

Interval Justification Documentation

When an inspector sets or extends an interval beyond default tables, the record must show:

• Damage mechanism identification (uniform thinning vs. localized)
• Corrosion rate derivation with dates and formula
• Remaining life calculation to retirement thickness
• RBI assessment reference if used (POF, COF, team approval, 5-year update)
• Inspector and engineer approval signatures where required

An exam question may present valid thickness data but no half-life calculation—the correct answer is that the interval is not code-supported.

Repair, Alteration, and Rerating Documentation

Each repair or alteration file should be a standalone package cross-referenced to the circuit history:

• Work request and inspector authorization before work
• Engineering design (calculations, drawings, PCC-2 method reference)
• Material test reports (MTRs) and API RP 578 material verification (PMI, hardness, duplicate heat checks when required)
• Welder/WPS qualifications, NDE reports (RT, UT, PT, MT), pressure test or Article 10 leak test records
• Post-repair thickness baseline at repair zone
• Final inspector sign-off and return-to-service date

Temporary repairs (lap patches, composite wraps in restricted service) require expiration dates and permanent repair plans in the record.

Material Verification Records (API RP 578)

API RP 578 requires positive material identification and traceability for critical service and when material mix-ups are plausible. Records include:

• PMI results (XRF or OES) with instrument calibration
• Heat number linkage to MTRs
• Hardness testing after PWHT or suspected embrittlement
• Resolution procedure when specified chemistry does not match drawings

An inspector who accepts a wrong-grade spool without PMI documentation shares audit liability with maintenance.

PRD Service Records (API RP 576)

The February 2026 API 570 Body of Knowledge tests API RP 576 pressure-relief device inspection for Section 5, Sections 6.1 through 6.5, and Section 7—not the older limited scope of 6.1–6.3, 8, and 10. Inspectors must know PRD documentation tied to protected piping systems.

RP 576 Section 5 – Inspection Planning

Records link each PRD tag to protected equipment, set pressure, capacity, fluid service, and inspection interval.

RP 576 Sections 6.1–6.5 – Examination and Testing

Documentation of on-stream inspection, shop overhaul, pop test or bench calibration, seat tightness, gagging prohibition, and sticker/tag application after service.

RP 576 Section 7 – Record Keeping

Permanent files per device:

• Identification and location on protected system
• Manufacturer, model, orifice area
• Set pressure, cold differential test pressure (CDTP) if applicable
• Inspection and test dates, findings, parts replaced
• Reason for change if set pressure or service changed (ties to rerating)

Piping inspectors cross-check that PRD records match piping MAWP and relieving contingency scenarios after rerates or process changes.

Inspection Reports: Minimum Content

Field inspection reports (on-stream, internal, RBI) should include:

• Unit, circuit, and equipment IDs
• Inspection type and extent (percentage of circuit, CMLs examined)
• Damage mechanisms observed or ruled out
• Thickness data and visual findings (CUI, leaks, supports, insulation condition)
• Recommendations (repair priority, follow-up NDE, interval)
• Inspector signature and certification number

Photographs and sketches of localized damage accelerate future comparisons.

Table: Minimum Record Elements by Topic

Why Incomplete Records Fail Exams and Audits

Exam writers deliberately omit authorization dates, corrosion-rate math, or flange rating checks in scenario questions. The correct choice is almost always "reject / reinspect / shorten interval / do not return to service" because the record chain is broken.

In field audits, the same gaps trigger API 510/570 compliance findings, OSHA PSM documentation citations, and insurance carrier recommendations. Records are how inspectors prove they exercised professional judgment—not just walked the line.

Worked Scenario: Record Review Before Interval Extension

An inspector is asked to extend a Class 1 circuit from 5 to 8 years using RBI. The file contains UT readings and an RBI spreadsheet, but:

• Two CMLs lack 2022 readings (COVID skip) with no justification
• A 2024 split-sleeve repair has NDE but no inspector authorization in the file
• PRD protecting the circuit was bench-tested in 2023, but RP 576 Section 7 file shows set pressure still listing pre-rerate MAWP

Correct actions: Do not grant extension until gaps are closed—backfill missed CML rationale or re-inspect, obtain repair authorization documentation, and update PRD records per RP 576 to match current relieving design. Partial data means unacceptable risk under API 570.

Treat documentation as the final nondestructive examination—one that never gets skipped.