API 510 Pressure Vessel Inspection Report

A code-aligned, multi-sheet Excel template to record an API 510 pressure-vessel internal / external inspection. Includes shell UT thickness CMLs, nozzle inspection, weld inspection, FFS screening (API 579), and prioritized recommendations with sign-off.

API 510 — Pressure Vessel Inspection Code defines the requirements for in-service inspection, repair, alteration, and rerating of pressure vessels and pressure-relieving devices. This template captures the data, calculations, and decisions an authorized API 510 inspector needs to record per an inspection cycle: from cover-page asset identification through CML thickness readings to recommendations and sign-off.

Use this template at the start of every internal or external API 510 inspection campaign. Fill the Cover sheet during pre-mobilization planning, the CML and nozzle sheets during field work, the Weld and FFS sheets back in the office during evaluation, and close out with Recommendations and Sign-off before issue.

The XLSX is fully editable — change column headers, add CML rows, or insert custom corrosion-rate formulas. Atlantis NDT can deliver a tailored version with your customer's report numbering, auto-calculated corrosion rate, embedded P&ID hyperlinks, and digital signature support.

Atlantis NDT can deliver an API 510 report template branded for your QA system with auto-calculated corrosion rate, RBI linkage, and dossier handover.

What this page covers

Overview
Sheets Included
Related Free Templates
Need a customized version?

Key points covered

Cover sheet — vessel ID, design data, MAWP / MDMT, materials, inspection dates
Shell / head UT thickness — 20 CML readings with corrosion-rate calculation
Nozzle / manway inspection — 10 nozzles + manway entries with reinforcing pad checks
Weld inspection — longitudinal and circumferential seams with method, coverage, and acceptance
FFS screening — 12 damage mechanisms with Level 1 / Level 2 trigger logic per API 579
Recommendations — prioritized follow-up actions tied to API 510 clauses
Sign-off — API 510 Inspector, Owner/User engineer, independent reviewer, jurisdiction

What a defensible API 510 report contains

An API 510 vessel inspection report is the legal memory of the vessel's condition: it must let a stranger reconstruct what was examined, how, by whom, and why the verdict followed. The load-bearing fields are the ones commonly rushed — CML identity that matches the previous campaign exactly (a renamed CML orphans its history), instrument and calibration references per reading, the corrosion-rate calculation shown rather than asserted, and the inspector's determination of next internal and external intervals with its basis. The remaining-life arithmetic drives the interval; if the report shows the interval without the arithmetic, an auditor will ask, and "the software did it" is not an answer the code accepts.

Common audit findings against vessel reports: thickness locations not tied to drawings, corrosion rates computed across repairs as if continuous, and reports signed by an inspector whose API 510 certification lapsed between examination and signature. Structure the template so those failures are impossible, not merely discouraged.

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.