Comparison
API 580 vs API 581: What Is the Difference?
Vinit Pandey · Published 28 June 2026
In short: API 580 provides the qualitative and semi-quantitative Risk Based Inspection (RBI) methodology and program management framework. API 581 provides the detailed quantitative risk calculation methodology — probability of failure and consequence of failure models — used to implement an API 580-aligned RBI program with calculated risk numbers.
| Aspect | API 580 | API 581 |
|---|---|---|
| Type of document | Recommended practice — methodology & program management | Recommended practice — quantitative calculation procedure |
| Rigor | Qualitative to semi-quantitative | Fully quantitative |
| Defines | RBI program structure, roles, revalidation cycle | POF and COF calculation models per damage mechanism |
| Use case | Programs without quantitative risk modelling tools | Programs needing calculated risk numbers (e.g., for dollar-risk or detailed prioritisation) |
| Relationship | Can stand alone for qualitative RBI | Implements within an API 580 program framework |
API 580 and API 581 are companion documents, not alternatives — they are commonly confused because both relate to Risk Based Inspection (RBI), but they serve different functions within the same program.
API 580, 'Risk-Based Inspection,' is the foundational recommended practice. It defines what an RBI program is, the qualitative and semi-quantitative methods for assessing probability and consequence of failure, and the program management requirements — roles, data quality requirements, revalidation frequency — needed to run an RBI program credibly over time.
API 581, 'Risk-Based Inspection Methodology,' goes a level deeper. It provides the detailed, quantitative calculation procedures — specific probability-of-failure models for damage mechanisms like thinning, cracking, and external corrosion, and consequence-of-failure models including financial and safety consequence — needed to produce calculated risk numbers (often expressed in risk units or estimated dollar exposure) rather than qualitative risk categories.
A facility can run a fully API 580-compliant RBI program using qualitative or semi-quantitative methods alone. Adopting API 581 on top of that framework is a choice to gain more granular, defensible, quantitative risk ranking — at the cost of requiring more detailed input data per equipment item.
Frequently Asked Questions
Do I need both API 580 and API 581 for an RBI program?
API 580 alone is sufficient for a qualitative or semi-quantitative RBI program. API 581 is adopted in addition to API 580 when a facility wants fully quantitative, calculated risk numbers rather than qualitative risk categories.
Which API standard defines RBI revalidation requirements?
API 580 defines the program management framework, including revalidation cycle requirements, regardless of whether the underlying risk calculations use the qualitative methods in API 580 or the quantitative methods in API 581.