API 570 Piping Inspection Record

An editable Excel template for documenting an API 570 in-service piping circuit inspection. Captures CML thickness readings, short and long-term corrosion rates, remaining life, RBI risk scoring, and prioritized recommendations.

API 570 — Piping Inspection Code governs the in-service inspection, repair, alteration, and rerating of metallic piping systems. The template provides a structured record covering each CML in the circuit, calculated corrosion rates, remaining life and next inspection date, plus a simplified RBI worksheet for risk-based interval setting.

Use the workbook to plan a thickness survey, capture field measurements, and document the engineering analysis required for an API 570 inspection report. Inspectors can extend the CML range, add additional damage mechanisms, or tie the RBI cell back to the company risk matrix.

Atlantis NDT can deliver a fully integrated version connected to your CMMS / RBI database with automated remaining-life and risk-cell updates.

Atlantis NDT can deliver an API 570 record linked to your CMMS, with auto-updated risk cell and dossier handover.

What this page covers

Overview
Sheets Included
Related Free Templates
Need a customized version?

Key points covered

Cover sheet — circuit ID, P&ID reference, design / operating data, materials, RBI interval
CML readings — 30 condition-monitoring locations with previous vs current thickness, short / long-term corrosion rate, remaining life
Corrosion-rate & remaining-life summary — by section and component (elbows, tees, dead legs, valves)
RBI score — damage mechanism, POF, COF (safety / environmental / financial), risk cell
Recommendations / repairs / re-inspection — tied to API 570 clause references
Sign-off — API 570 Inspector, piping engineer, RBI specialist, Owner/User

What the API 570 record must hold

Piping records rise and fall on circuit integrity: the circuit definition (bounded by service, material and corrosion behaviour) is what makes CML data comparable across campaigns, so the record must carry circuit identity, class per API 570's consequence-based classification, and the injection/deadleg/CUI susceptibilities that drive extra attention. Thickness data needs the same discipline as vessels — location identity stable across campaigns, instrument and examiner attribution, rates calculated on true like-for-like comparisons. Class determines external interval; measured rate determines thickness-driven interval; the record should show both and take the shorter.

The finding that recurs in piping audits: CMLs relocated without cross-reference after insulation or scaffolding constraints, splitting the history into two unjoinable halves. The template should force a mapping note whenever a location moves.

Where this document sits in the wider system

Templates fail as loose files and work as parts of a system: this document should cross-reference the records that feed it and the decisions it feeds, carry a revision history like any controlled document, and live where the whole team retrieves the CURRENT version — not the copy someone improved privately last year. Companies running their inspection operations on a single system of record generate most of these documents from live data rather than filling them by hand; that is the practical difference between managed records and managed paperwork. Browse all templates and resources, or ask how the generated version works.