API 598 Valve Testing Scope and Purchase Checklist
Use API 598 as a named inspection and testing basis only after the order identifies the governing edition, valve product standard, acceptance basis, witness points, and required records.
What API 598 establishes
API 598 is an inspection and testing reference for valves, but its citation alone is not a complete test instruction. The purchase documents should identify the governing edition, applicable product standard, valve list, test and acceptance basis, witness or hold points, and required records. Numeric pressures, durations, leakage criteria, and exceptions must come from the licensed standard and approved project documents.
Where this checklist applies
Applies
- Orders that explicitly cite API 598
- Inspection plans built around API 598
- Supplier document reviews before testing or shipment
Does not apply by assumption
- Valves governed only by another test standard
- Project-specific acceptance criteria that override or supplement the base standard
- Qualification or type testing not stated in the purchase scope
Inputs needed before the test scope is released
- Valve tag and quantity
- Valve type size class and materials
- Governing API 598 edition
- Applicable product standard and project specification
- Required tests and acceptance basis
- Witness hold and notification points
- Certificate report photo and traceability requirements
Purchase-to-inspection decision path
| Decision point | Public check | Project-controlled confirmation |
|---|---|---|
| Standard identity | Confirm API lists Standard 598 as Valve Inspection and Testing | Confirm the purchased edition and contractual precedence |
| Test scope | State which valves and records are included | Approve test pressures durations media and acceptance criteria |
| Witnessing | Define the requested witness or hold point | Agree notice period attendance and release authority |
| Records | Name the report certificate photo and traceability deliverables | Approve formats signing and retention requirements |
Separate valve testing from system acceptance
Valve-level evidence
- Valve identity and marking
- Factory inspection and pressure-test record
- Material and traceability records requested by the order
System-level evidence
- Installed piping test
- Commissioning and functional checks
- Site acceptance under the project specification
Common scope mistakes
- Writing API 598 without an edition or precedence rule
- Copying numeric criteria into an inquiry without checking the licensed edition
- Treating a generic certificate as traceable to the ordered valve
- Assuming factory testing proves installed-system performance
- Adding witness requirements after the order without agreeing schedule and cost
What is public and what still requires approval
This page verifies the public identity and procurement role of API 598; it does not reproduce controlled normative tables. The buyer, manufacturer, inspector, and responsible project authority must use the licensed edition and approved purchase documents to confirm every numeric criterion, exception, witness point, and release decision.
Publicly checkable
- Official standard title and listing path
- The need to state edition scope and records clearly
Approval required
- Normative test values and acceptance limits
- Contract precedence and deviations
- Final inspection release