Valve Codes & Standards Map: API, ASME, ISO and EN (Inspector Guide)

Valve projects fail in predictable ways: the wrong standard is referenced, the right standard is referenced but misapplied, or the test record doesn’t clearly show which acceptance basis was used. This guide gives you a practical map of the most common API / ASME / ISO / EN valve standards—and how inspectors should use them during vendor documents review, FAT, and dossier release.

If you haven’t read the Valve Hub 101 yet, start here first:
What Is Industrial Valve Inspection & Testing?

• Think in layers: Design code (what the valve must be) vs Test standard (how it’s proven) vs Inspection evidence (what gets documented).
• Most inspection disputes happen because the vendor can’t show an unbroken chain from PO/spec → standard → test method → acceptance → record.
• API 598 and ISO 5208 are often used for acceptance, but you must confirm which one the project requires and what leakage class applies.
• For pipeline valves, design/product standards such as API 6D / ISO 14313 often sit “above” acceptance testing choices.
• Your FAT goal is simple: every critical requirement has a traceable evidence line item in the dossier.

For a structured training pathway on valve inspection, acceptance, and FAT evidence:
Industrial Valve Inspection and Testing Training Course

 

Abbreviations

• API — American Petroleum Institute
• ASME — American Society of Mechanical Engineers
• ISO — International Organization for Standardization
• EN — European Standards (European Norms)
• QA/QC — Quality Assurance / Quality Control
• FAT — Factory Acceptance Test
• PO — Purchase Order
• ITP — Inspection and Test Plan
• NCR — Nonconformance Report 

 

The valve standards “stack” (how to stop mixing apples and oranges)

In real vendor packages, standards appear everywhere: datasheets, ITPs, procedures, and test reports. To keep it clean, classify each standard into one of these buckets:

1) Design / construction standards (what the valve must be)

These standards define the valve’s design basis: pressure rating, wall thickness rules, allowable materials, end connections, and (often) basic manufacturing requirements.

2) Product / application standards (what type of valve and for what service)

These standards define valve requirements for a specific application class—pipeline, subsea, critical service, etc.

3) Test / acceptance standards (how performance is proven)

These standards define test methods and acceptance criteria for shell, seat leakage, and other checks.

4) Dimensional / interface standards (what “fits”)

Standards that define face-to-face, flange dimensions, end prep, and interface geometry.

5) Documentation and evidence expectations (what must be recorded)

Not always a single “valve standard” — but your acceptance decision relies on consistent evidence: certificates, traceability, calibration references, and complete test records.

A practical inspection overview (lifecycle + evidence) is here:
What Is Industrial Valve Inspection & Testing?

 

The inspector’s rule: the PO/spec controls, standards are the method

A standard is not automatically applicable just because it exists. The governing order for inspectors should be:

1. PO / purchase specification / project spec
2. Datasheet and drawing package (controlled revision)
3. Stated governing standards (edition/date matters)
4. Vendor procedures (must match the above)
5. Test reports and inspection records (must cite the acceptance basis)

When a test record says “PASS” but doesn’t cite the acceptance basis, you don’t have acceptance-grade evidence yet.

If you need a checklist-driven view of what evidence must exist, use:
Valve Inspection Checklist (PDF): Visual, Dimensional & Testing

 

Quick map: which standards answer which questions?

Use this table as a mental shortcut during document review.

Question you’re answering	Typical standard family	What you must see in evidence
What is the valve design basis and rating rules?	ASME / API / ISO design & construction codes	Datasheet references + nameplate alignment + design doc references (as required)
What product standard governs this valve type/application?	API / ISO product standards	Correct standard in PO/spec + correct valve type/scope
How do we test shell integrity and seat leakage?	API / ISO/EN test standards	Procedure + medium + pressure + duration + acceptance class + signed records
What interface dimensions must it match?	ASME B16 / ISO / EN interface standards	Dimensional records (measured values) + drawing references
What documents must be in the dossier?	Project spec + QA/QC requirements	Certificates + traceability mapping + test records + NCR close-out

 

Testing and acceptance: API 598 vs ISO 5208 (the most common confusion)

Two standards get mixed constantly in vendor packages:

• API 598 (widely used for valve inspection and testing acceptance language in many projects)
• ISO 5208 (widely used for leakage rate classification and acceptance)

The practical issue isn’t “which is better.” The issue is: what does your PO/spec require, and what leakage class is defined.

If you want a side-by-side acceptance breakdown with inspector implications, use:
API 598 Vs ISO 5208: Valve Testing Acceptance Guide

What inspectors should enforce on every test record

Your test report should explicitly state:

• Standard used (e.g., API 598 or ISO 5208)
• Test method (shell/hydro, seat leak, etc.)
• Medium (water/air/gas) and temperature range if relevant
• Pressure and hold time
• Acceptance criteria (leakage class / allowable leakage statement)
• Instrument identification and calibration reference (when required by project QA/QC)

If you need the conceptual separation of test families (and what each proves), read:
Hydrostatic Vs Seat Leak Tests For Valves

 

Pipeline valves: how API 6D / ISO 14313 typically fit into the map

For pipeline service, projects often reference a product standard such as:

• API 6D
• ISO 14313 (often aligned with pipeline valve requirements)

These product/application standards typically define:

• What valve types are within scope
• Baseline design, manufacturing, and testing expectations for pipeline service

Inspectors should confirm:

• The PO/spec explicitly calls the relevant product standard
• The vendor’s ITP/test procedure aligns with the required acceptance basis (don’t assume—verify)
• The valve marking, documentation, and traceability match the scope of the product standard and the project spec

When this goes wrong, you often see “API 6D” on the datasheet but test records that cite a different acceptance basis without approval.

 

ASME: where it usually shows up in valve inspection packages

ASME standards show up frequently in:

• Pressure design philosophy (depending on project)
• Flange/end connection interfaces
• Materials and fabrication expectations where referenced by project spec

The inspector’s practical focus is not memorizing ASME clauses. It’s verifying that:

• The correct interface and rating are used (and measured)
• Marking/nameplate information is consistent with the datasheet
• The evidence package supports compliance claims

Dimensional misses and interface mismatches are common rejection drivers—especially around flanges and face-to-face. A discipline-first approach is to tie dimensions to drawings and interface standards, then record measured values.

A structured inspection flow for FAT readiness is covered here:
What Is Industrial Valve Inspection & Testing?

 

EN / ISO (Europe-heavy projects): how they usually appear

On European projects (or projects that specify EN/ISO), you’ll often see:

• EN-based leakage and test methods referenced via ISO/EN test standards
• EN/ISO documentation expectations (often aligned with project QA/QC requirements)
• Dimensional and interface standards depending on the valve and connection type

Inspector reality check:

• Confirm the exact standard and edition listed in the PO/spec
• Confirm the vendor test procedure explicitly aligns to it
• Confirm the test record cites it—not “tested to standard” as a vague claim

 

Document control: the standard is useless if the revision is uncontrolled

Even when the right standard is listed, quality breaks when:

• The vendor uses an outdated edition
• The ITP references one standard, the procedure references another
• Acceptance criteria are stated inconsistently across documents

What to verify in a document review (before FAT)

• PO/spec lists standards and editions
• Vendor ITP lists the same standards (no conflicts)
• Test procedure cites the same acceptance basis
• Test report template includes acceptance fields (standard + class + hold time + pressure)

If you’re using an inspection report template, make sure it forces the vendor to fill these fields. A practical template guide is here:
Write A Valve Inspection Report (With Sample Template)

 

The “standards-to-evidence” checklist (what must appear in the dossier)

A valve dossier becomes acceptance-grade when every “standard claim” has a corresponding evidence item:

Identification and scope

• PO number, tag numbers, quantities
• Datasheets/drawings used (revision-controlled)
• Standards list (with edition/date when required)

Materials and traceability

• Certificates for pressure-containing parts and specified trims
• Heat number mapping and marking verification
• Any specified verification (e.g., PMI) documented as required

Inspection records

• Dimensional check sheets with measured values
• Visual findings and dispositions (damage, surface condition)
• Assembly condition checks as required

Test records

• Shell/hydro test: pressure, duration, medium, acceptance basis
• Seat leak test: method, medium, leakage class, acceptance basis
• Functional checks where required
• Instrument identification and calibration references when required

Nonconformities and closure evidence

• NCRs recorded against requirement references
• Disposition approvals documented
• Closure evidence included before release

A valve can “pass testing” and still fail acceptance if the evidence chain is broken. That’s why standards mapping is a dossier discipline—not trivia.

 

Common mistakes inspectors should flag immediately

Mistake 1: “API 6D” on datasheet, unclear acceptance basis on test record

Fix: require test record to explicitly cite the acceptance standard and leakage class.

Mistake 2: Mixing API 598 and ISO 5208 language in the same dossier

Fix: choose the contractually required acceptance basis and make every document consistent.
Use: API 598 Vs ISO 5208: Valve Testing Acceptance Guide

Mistake 3: Test method is described, but pressures/hold times are missing

Fix: no acceptance without complete test parameters.

Mistake 4: “PASS” is recorded without stating what was tested

Fix: test record must include standard, method, medium, pressure, time, acceptance criteria.

Mistake 5: Safety treated as an afterthought

Pressure testing is hazardous; safety controls must be part of the procedure and FAT setup.
Use: Valve Pressure Testing Safety

 

Frequently asked questions

Do I need to memorize all valve standards to inspect valves well?

No. You need a reliable map and a discipline: always tie the inspection decision to the PO/spec and the stated acceptance basis, then verify the evidence chain in the dossier.

Can a vendor test both API 598 and ISO 5208?

Only if the project spec allows it and the acceptance logic is explicit. Otherwise, mixing acceptance language creates disputes and re-tests.

What’s the fastest way to prevent standards-related disputes?

Enforce consistency across: PO/spec → ITP → procedure → test record. If any one of those conflicts, fix it before FAT.

Where should I start if I’m new to valve inspection?

Start with the lifecycle and evidence model, then go deeper into tests and acceptance.
What Is Industrial Valve Inspection & Testing?

 

Next steps

If you want to inspect valves with confidence—connecting standards, acceptance criteria, FAT workflow, and dossier evidence into one repeatable method—start here:

Industrial Valve Inspection and Testing Training Course

And for the most common acceptance confusion, continue with:
API 598 Vs ISO 5208: Valve Testing Acceptance Guide