Records Retention Schedule for API 510
API 510 names this requirement as "Examiner certification records and current annual eye examinations". The QA manager owns it, and a contracted Level III can author and sign it.
The finding auditors record against this document is: Examiner taking thickness readings and also signing the evaluation against API 510 without written authorisation from the owner-user. API 510 is not a certificate a service company holds; it is the owner-user's programme, and it defines the roles your people fill. It separates the API Authorized Pressure Vessel Inspector, who holds API's central certification and evaluates results against the code, from the examiner, who performs the nondestructive examination and does not evaluate against API 510 unless specifically trained and authorised to do so by the owner-user. Selling into this regime means selling examiner hours plus the paperwork that makes them admissible: an accepted written practice, Level III-approved procedures, current examiner certifications and calibrated equipment. Inspection types are external visual, internal or on-stream, and thickness measurement, each running on its own interval cap, and each producing records the owner-user must be able to defend.
Source: API 510 certification page, api.org, accessed 21 August 2026 — verified for the education and experience eligibility ladder (BS or 3+ years military technical service plus 1 year; 2-year degree or 2 years military plus 2 years; high school diploma plus 3 years; no formal education plus 5+ years, each with a supervision component), the 7.5-hour exam day, 170 questions of which 140 are scored, split 110 closed-book and 60 open-book, the three-year recertification cycle, the 20% time requirement, 24 CPD hours per three-year cycle and the 25-question web quiz every six years. API ICP Schedules & Fees page — verified for $875/$1,125 initial, $745/$855 recertification, $350 reschedule, and the 2026 exam windows. API ICP Policies page — verified that the term of certification is three years and the open-book quiz is required every six years for 510, 570, 653, 936 and 1169. API Standard 510 announcement page — confirms the 11th edition, which added a detailed section for the analysis of inspection results; the October 2022 publication date comes from reseller listings, not from API's own page. Inspection-interval caps commonly cited for the 11th edition (internal or on-stream at the lesser of half the remaining corrosion life or ten years; external visual at the lesser of five years or the internal/on-stream interval) were cross-checked against two independent secondary summaries and NOT against the code text — confirm against API 510 before publishing them as figures.
| Item | What applies | Why it matters |
|---|---|---|
| Regime | API Standard 510, Pressure Vessel Inspection Code: In-service Inspection, Rating, Repair, and Alteration — Owner-User Inspection Programme | Enforced by American Petroleum Institute. API's Individual Certification Programs (ICP) office certifies the Authorized Pressure Vessel Inspector; the inspection programme itself is owned and enforced by the owner-user, and by the boiler and pressure vessel jurisdiction where the state has adopted API 510 |
| Document | Records Retention Schedule | how long each record is kept, where, and who can retrieve it during an audit |
| Owner | the QA manager | The signature an auditor traces back |
| Where it is checked | Inspection report issued, remaining life and next inspection date calculated, and any repair or alteration approved by the. | Usually against a sampled job, not in isolation |
| Common failure | Examiner taking thickness readings and also signing the evaluation against API 510 without written authorisation from the owner-user | The gap between the manual and the job file |
What must a records retention schedule contain under API 510?
It has to satisfy API 510 as American Petroleum Institute. API's Individual Certification Programs (ICP) office certifies the Authorized Pressure Vessel Inspector; the inspection programme itself is owned and enforced by the owner-user, and by the boiler and pressure vessel jurisdiction where the state has adopted API 510 enforces it: how long each record is kept, where, and who can retrieve it during an audit. The test is not completeness on paper but traceability — an auditor picks a finished job and works backwards to this document, so anything it claims must be demonstrable on that job.
Who signs the records retention schedule for API 510?
The QA manager. Because this regime accepts employer-based certification, that role can be filled by a contracted Level III rather than a staff appointment, provided they are qualified in the methods they sign for.
How does a API 510 auditor test this document?
By sampling. They take a completed job, find the technicians and equipment used, and trace each back through this document to the evidence behind it. A document that reads well but cannot survive that trace is the most common finding across every regime, not just this one.
How long must API 510 records be kept?
There is no company certificate to renew. The individual API 510 certificate runs for a three-year term. Recertification requires that the inspector has spent a minimum of 20% of his time over the most recent three-year certification period performing or supervising inspection activities, and has completed 24 CPD hours within each three-year cycle; an online open-book quiz of 25 questions with a four-hour limit is required every six years. API's published fees for the 510, 570 and 653 programmes are $875 USD for members and $1,125 for non-members for initial certification, $745 and $855 for recertification, and $350 to reschedule an exam. The 2026 API 510 exam windows are 2–23 January and 8–29 May 2026. Retention is set by the regime and by the client contract above it, and the longer of the two governs. Firms that set one retention period for everything and document it fare better at audit than firms tracking different periods per record type and losing track.
Does a generic template satisfy API 510?
No. A downloaded template describes a generic firm, and the first question an auditor asks is whether the document describes THIS firm — its methods, its equipment, its people, its actual workflow. Templates are a starting structure; the content has to be the firm's own or the trace fails immediately.
What happens if this document is missing at a API 510 audit?
It is a finding, and depending on the regime it can suspend the certificate rather than merely generate a corrective action. The related finding auditors record most often is: Examiner taking thickness readings and also signing the evaluation against API 510 without written authorisation from the owner-user
Where this sits in the API 510 evidence pack
- Owner-user inspection programme document naming the Authorized Inspector and defining what the examiner is authorised to evaluate
- Current API 510 certificate for each Authorized Pressure Vessel Inspector, with the recertification due date
- NDE written practice, and the Level III approval on each method procedure
- Examiner certification records and current annual eye examinations
- Thickness measurement location and condition monitoring location drawings, and the full reading history against those identifiers
- Corrosion rate and remaining-life calculations supporting the next inspection date
- Inspection report signed by the Authorized Inspector, kept distinct from the examiner's data report
- Repair and alteration records, including welding procedure specifications, procedure qualification records and the Authorized Inspector's acceptance
- Equipment calibration records and certification of ultrasonic calibration blocks
Personnel certification context
Split, and the split is the commercial point. The Authorized Pressure Vessel Inspector must hold API 510 certification — a central, third-party certification examined by API and delivered through Prometric. No employer can issue it and no outsourced Level III can substitute for it. The NDE examiner side is entirely employer-based: examiners are certified under an employer's written practice built on ASNT SNT-TC-1A, ANSI/ASNT CP-189 or ACCP, so an outsourced Level III can write and approve the method procedures, administer and grade examinations and recommend certification, with the employer's designated certifying authority signing. API additionally operates ultrasonic examiner qualification programmes — QUTE, QUSE, QUSE-PA and QUPA — that some owner-users specify on top of ASNT certification for corrosion mapping and weld phased array.
Related: the API 510 overview, outsourced ASNT Level III cover, written practice development, NDT procedure development, a programme gap assessment, interim Level III cover.
API 510 inspection records: what the owner-operator must keep
Short answer: API 510 (11th edition, October 2022) requires pressure vessel owner-operators to keep permanent records for the whole service life of each vessel and pressure-relieving device (PRD), plus progressive records that are updated after every inspection. The records must cover four kinds of information: construction and design, inspection history, repairs, alterations and rerating, and any fitness-for-service documentation. Each inspection report must show the date, the next due date, who did the work, the equipment identifier, what was done, and the results.
A retention schedule only works if everyone knows what it is retaining. This section sets out what the current API 510 actually asks for, how it overlaps with OSHA PSM and Canadian provincial rules, and what an NDE report needs to contain to be usable in the owner's record set. Clause references are to the 11th edition. API standards are copyrighted, so the requirements are summarised here in our own words. Check your licensed copy and any addendum for the exact wording (API standards, api.org).
Need NDE reports that drop straight into your vessel files? Ask for an inspection quote.
Permanent and progressive records
API 510 section 7.8.1 makes the owner-operator responsible for two layers of records for every pressure vessel and PRD in scope:
- Permanent records are kept for the whole service life of the equipment item. These are documents that do not change: the manufacturer's data report, design calculations and nameplate data.
- Progressive records are updated regularly with new inspection and maintenance history, and with operating information that may affect integrity.
The practical consequence for a retention schedule is that a single blanket retention period (for example "seven years") does not match the code. Construction and design documents must survive as long as the vessel does, and they should transfer with it when it is sold or relocated. Inspection data must be kept at least as long as it is needed to calculate corrosion rates. Long-term rates are calculated from the earliest reliable reading, so discarding old thickness data can make long-term rate calculations impossible.
The four types of information API 510 requires
Section 7.8.2 says vessel and PRD records must contain four types of information relevant to mechanical integrity. The examples below are paraphrased from the code's lists.
| Record type | Typical contents | Common gaps found at audit |
|---|---|---|
| Construction and design | Serial number or identifier, manufacturer's data reports (e.g. U-1), fabrication and construction drawings, nameplate photo or rubbing, heat treatment charts, design specification data, vessel design calculations, PRD sizing calculations | Missing data reports for older or second-hand vessels; PRD sizing basis never filed |
| Inspection history | Reports and data for each inspection type (internal, external, thickness), inspection recommendations and their disposition, RBI records where RBI is used | Recommendations closed without a recorded reason; thickness data without CML identifiers |
| Repair, alteration and rerating | Repair and alteration forms (API 510 Annex D gives a sample), reports for equipment kept in service with deficiencies or temporary repairs, rerating calculations, new design conditions and evidence of stamping | Temporary repairs with no follow-up date; rerates without updated stamping evidence |
| Fitness-for-service | Documentation required by API 579-1/ASME FFS-1 for any FFS assessment performed | FFS conclusions filed without the inputs and assumptions |
Fitness-for-service assessment is an engineering evaluation the owner commissions under API 579-1/ASME FFS-1. It is not an NDE activity. Where one has been done, its documentation becomes part of the permanent vessel record.
What every inspection report must state
Within the inspection-history category, API 510 is specific. Inspection reports must document:
- the date of each inspection and/or examination;
- the date of the next scheduled inspection;
- the name of the person who performed the inspection and/or examination;
- the serial number or other identifier of the equipment;
- a description of the inspection and/or examination performed;
- the results.
The records should also show the disposition of each inspection recommendation, including why any recommendation was not implemented. For vessels managed by RBI, the code points to API RP 580 for the RBI records.
That list closely matches OSHA's Process Safety Management standard. Under 29 CFR 1910.119(j)(4)(iv), employers must document each inspection and test on process equipment with the date, the name of the person who did it, the serial number or other identifier of the equipment, a description of the inspection or test, and the results. A report built to satisfy API 510 therefore also covers the OSHA documentation elements. The OSHA list does not include the next scheduled date; API 510 adds that.
Operating records, the 90-day rule, and who approves the results
Section 7.8.3 says site operating and maintenance records should also be available to the inspector. These include operating conditions, process upsets that may affect mechanical integrity, and mechanical damage from maintenance. In practice that means integrity operating window (IOW) exceedances, management-of-change (MOC) records and upset logs need to be retrievable alongside the vessel file. The inspection plan requirements in section 5.1 also expect intervals to take account of recent operating history, IOW exceedances and MOC records.
Section 7.8.4 adds a timeliness expectation that many programmes miss. Documented inspection results must be approved by the responsible owner-operator inspector, engineer or qualified designee. They should be entered into the inspection data management system within 90 days of completing the inspection and/or startup. A retention schedule that only addresses how long records are kept, and not how quickly they are filed, does not cover this expectation.
Before any inspection, section 5.3.2 expects inspectors to review the vessel's history: prior results, prior repairs, the current inspection plan and relevant engineering evaluations. Records that cannot be found at the start of a turnaround are, in effect, records the programme does not have.
Records the inspection plan and CML programme depend on
Section 5.1 requires an inspection plan for every vessel and PRD in scope. The plan should define the inspection types, the next date for each, the NDE techniques, the extent and locations of examination, surface preparation, any pressure test requirements, planned repairs, and changes since the last inspection (MOC, IOW exceedances, other deviations). The plan is itself a controlled record and should be readily accessible from the inspection data system.
For thickness data, the 11th edition adds two recording rules:
- At each examination point, either the thinnest reading or an average of several readings in the area is recorded and used for corrosion rates (5.6.2.4). Use the same convention every time; switching between minimum and average from one survey to the next distorts the rate.
- CMLs and examination points should be permanently recorded, for example marked on inspection drawings and/or on the vessel, so that later measurements are taken at the same spots (5.6.2.5). The code notes that repeat measurement at the same location improves the accuracy of the calculated rate.
Without those two disciplines, a retained thickness history can technically exist and still be unusable. For how the stored readings become a rate and a date, see corrosion rate calculation: long-term vs short-term and API 510 interval calculation explained.
Examiner, deferral and recommendation records
Several other API 510 requirements generate records that auditors trace:
- Examiner qualifications (4.5.3). The NDE examiner's employer must keep certification records for its examiners, including the dates and results of qualifications, and make them available to the inspector. The inspector is responsible to the owner-operator for confirming every examiner is qualified for the work. API 510 gives ASNT SNT-TC-1A, ASNT CP-189, CGSB and AWS QC1 as examples of certifications an owner-operator may require. Examiners do not need API 510 certification.
- Deferrals of inspections, tests and examinations (6.7). A deferral must be documented and approved by the appropriate people, including the owner-operator's inspector and operations management. The vessel or PRD records must be updated with the deferral documentation before the equipment runs past its original due date.
- Deferral of repair recommendation due dates (6.8). The new date must be documented in the inspection records, with the concurrence of the inspector and the inspection supervisor. Recommendations past due without an approved change are considered overdue.
- Changed or deleted recommendations (6.9). If an inspector's recommendation is changed or deleted after review, the records must show the reasoning, the date and the name of the reviewer.
- Repairs and alterations (Section 8). Repairs must be authorised by the inspector before work starts, and alterations and certain repairs also need an engineer's authorisation. Proposed methods, materials, welding procedures and NDE are approved in advance, and the inspector approves the work at hold points and on completion. The authorisations, procedures, NDE results and acceptance all belong in the repair record. Where the jurisdiction requires National Board (NBIC) repair or alteration reporting, those reports are part of the record as well.
For PRD-specific records, see API 510 pressure relief device intervals.
Exploration and production vessels (Section 9)
API 510's Section 9 sets alternative rules for pressure vessels in exploration and production service. Its records provision is lighter. Owner-operators must keep vessel records. Records are preferably kept per individual vessel, but where vessels are grouped into classes the data may be kept by class. Vessel-specific data must still be recorded whenever an individual vessel is inspected, repaired or altered. The code includes a sample inspection record form (Annex C) and a sample alteration or rerating form (Annex D), and recommends including maintenance events that affect integrity. If your fleet includes E&P vessels managed under Section 9, your retention schedule should say so explicitly.
Canada: ABSA AB-506 and provincial record rules
In Alberta, ABSA's AB-506 (Inspection and Servicing Requirements for In-Service Pressure Equipment; Edition 4 was issued in October 2025) requires owners to keep a current inventory of all pressure equipment they own or operate. Owners must also keep equipment records for each item, covering design information, data reports, inspection plans, integrity assessment, repair and alteration records, NDE records, Certificate of Inspection Permits, PRV servicing records and other relevant maintenance and test records. When equipment is sold or leased, the records must go with it, and the acquiring owner must obtain the history and assess the integrity of what it bought. ABSA must be notified of changes in ownership or location for permitted items. The requirement to transfer records on sale is one many US retention schedules do not address. Other provinces (for example, TSSA in Ontario) have their own requirements, so confirm with the regulator where the equipment operates.
In the US, state boiler and pressure vessel laws may set additional reporting and record expectations, especially where the jurisdiction has adopted API 510 or the NBIC for in-service inspection. Confirm with the state chief inspector's office.
What an NDE report must contain to be usable in the owner's record set
From the owner-operator's side, a contractor's NDE report is only useful if it can be filed against the vessel and trended. A practical checklist that maps to the API 510 and OSHA elements above:
- equipment identifier and serial number exactly as in the owner's register;
- date(s) of examination and the examiner's name and certification level, traceable to the employer's certification records;
- procedure number and revision, approved under the employer's written practice by the responsible Level III;
- instrument, probe and calibration block identifiers, with calibration status;
- CML or examination-point IDs that match the owner's inspection drawings, with the reading convention (minimum or average) stated;
- scope actually completed versus scope planned, with any inaccessible areas listed;
- results presented as data (readings, maps, indications), kept separate from evaluation against API 510. Evaluation is the inspector's job unless the owner-operator has authorised otherwise.
Getting those fields right at the source is far easier than reconstructing them later, and it lets the owner meet the 90-day posting expectation.
How Atlantis supports this
Atlantis NDT performs the NDE that API 510 inspections call for: UT thickness and CML surveys, corrosion mapping, phased array UT, TOFD, radiography by licensed crews, MT, PT, VT and ET. The work is done by ASNT-certified technicians under ASNT Level III oversight. Our reports carry the equipment identifier, CML IDs, procedure, calibration and technician certification, and examiner certification records are available to your inspector on request. Record-keeping, evaluation, interval setting and approval stay with the owner-operator and the API 510 authorized inspector. See pressure vessel inspection services and API 510 inspection support, or request a quote.
API 510 records: frequently asked questions
What are permanent and progressive records in API 510?
Permanent records are kept for the whole service life of the vessel or PRD. Progressive records are updated after each inspection with new inspection, maintenance and operating information that affects integrity.
What must a pressure vessel inspection report include under API 510?
The inspection date, the next scheduled date, the name of the person who performed it, the equipment identifier, a description of the inspection or examination, and the results. The disposition of recommendations should also be recorded.
How long must API 510 inspection records be kept?
Permanent records are kept for the equipment's service life. API 510 does not set a fixed number of years for progressive records. Keep thickness history long enough to support long-term corrosion rates, and follow any longer jurisdictional or contractual requirement.
Does API 510 have a deadline for entering inspection results?
The 11th edition says approved results should be entered into the inspection data management system within 90 days of completing the inspection and/or startup.
How do OSHA 1910.119(j) documentation requirements compare with API 510?
OSHA requires the date, the performer, the equipment identifier, a description and the results for each inspection or test. API 510 asks for the same elements plus the next scheduled inspection date and recommendation dispositions.
Who keeps NDE examiner certification records?
The examiner's employer. API 510 requires them to be available to the inspector, who confirms examiners are qualified for the work.
Do records have to transfer when a vessel is sold?
API 510's permanent-record concept implies they should. In Alberta, AB-506 explicitly requires records to go to the new owner and the new owner to assess integrity.
For a broader view of the code, see the API 510 overview. To plan NDE with report fields mapped to your vessel register, contact Atlantis NDT.
Get audit-ready, and stay that way
Auditors read the documents before they watch the work. Atlantis prepares the evidence pack and the Level III documentation behind it, trains the technicians, and Atlantis ERP keeps the records current between audits.
Speak to an ASNT NDT Level III
Discuss your inspection requirements with Atlantis NDT. Include the asset, method, location and documents you need reviewed.