API 570 vs. API 1169: Scope errors that increase risk

The comparison API 570 vs. API 1169 makes it possible to distinguish between in-service metallic piping inspection and inspection during the construction of new onshore pipelines. Applying either of these references outside their scope can leave damage mechanisms uncontrolled, accept work with insufficient traceability, or transfer construction defects into operation.

For operators, the difference impacts availability, compliance, repair costs, and the risk of loss of containment. The selection of the reference must start from the asset type, the lifecycle stage, and the decision requiring technical backing. The objective is to assign the correct document to each activity and preserve useful information from the project phase through to operation.

Differences Between API 570 and API 1169 in Terms of Scope

The first document is an inspection code for in-service piping. The second technical reference is a recommended practice to oversee construction activities and structure the relationship between operator, inspector, and contractor.

The fifth edition of API 570 was published on February 29, 2024, and its current version incorporates Addendum 1 dated October 21, 2025. Among its changes are the definition of responsibilities for the Inspection Supervisor, strengthened control over pressure relief devices, and new requirements for reviewing repair recommendations and their deferrals.

API Recommended Practice 1169 remains in its second edition, published on March 3, 2020. This edition expanded its coverage to all pipeline construction activities and reinforced coordination among project parties. API maintains the third edition of API RP 1169 in the editing phase; until it is published and contractually adopted, the second edition continues as the active reference.

API 570 and in-service piping inspection

Inspecting in-service piping must answer how much damage exists, at what rate it progresses, and what action keeps the risk within acceptable limits. The program considers deterioration mechanisms, thickness history, process conditions, external inspection, monitoring locations, repairs, alterations, and associated relief devices.

From thickness data to decision

An ultrasound campaign loses value when it consistently measures the same points without relating them to localized corrosion, mixing zones, injection points, deadlegs, soil-to-air interfaces, or corrosion under insulation. The technique, coverage, and frequency must correspond to the expected mechanism, geometry, and consequence of failure.

The result must lead to a defined action: maintain service, shorten the interval, expand the inspection, repair, rerate, or perform a fitness-for-service assessment. This logic prevents the program from being limited to storing readings without a documented decision.

Integration with mechanical integrity

API RP 574 complements API 570 with practices for the inspection of piping, valves, and fittings. Its fifth edition was published in February 2024 and received Addendum 1 in March 2025. The update expanded guidance for selecting inspection activities and locations, evaluating results, defining follow-up actions, rerating systems, and establishing repairs.

When thickness loss, cracking, deformation, or thermal damage exceeds direct criteria, API 579-1/ASME FFS-1 can support continuity, repair, or retirement. API RP 571 helps identify damage mechanisms, while API RP 580 and API RP 581 allow prioritizing inspections through risk.

API 1169 and pipeline construction inspection

Pipeline construction inspection seeks to prevent a deviation from being buried, coated, pressurized, or handed over to the operations team. The inspector verifies materials, procedures, competencies, calibrations, records, and sign-offs in accordance with the contract and applicable regulations.

Activities requiring oversight

The scope may include pipe receipt, right-of-way preparation, excavation, alignment, welding, Non Destructive Testing (NDT), coating, lowering-in, backfilling, special crossings, pressure testing, and environmental restoration.

PHMSA (Pipeline and Hazardous Materials Safety Administration) identifies recurring construction issues including poor quality control, inadequate welding procedures, coating failures, non-compliant fittings, and defects or damage to the pipe. These deviations must be corrected prior to burial or commissioning.

Welding, NDT, and regulation

API Std 1104, 22nd edition, contains requirements for the welding of pipelines and related facilities. Its changes include clarifications on qualification, mechanized welding, repairs, and ultrasonic or radiographic evaluation of girth welds.

In the United States, 49 CFR Parts 192 and 195 establish requirements for gas systems and hazardous liquid pipelines. PHMSA updated several incorporated references in these regulations in 2025; the main provisions came into force in January 2026. Therefore, the project must verify both the contract edition and the legally incorporated edition.

Which reference to apply based on the asset

The selection can be resolved with three questions:

• Is the system under construction or already operating?
• Is it process piping or a regulated pipeline?
• Does the decision consist of accepting construction or managing integrity?

Operating piping and new projects

Use the inspection code when the issue is thickness loss, damage mechanisms, intervals, remaining life, repair, alteration, or rerating of process piping.

Use the construction practice when the decision corresponds to materials, welding, coating, trenching, testing, or closing non-conformances for a new onshore pipeline.

Brownfield projects require a defined boundary. A new line inside a refinery can be executed in accordance with the design code and quality plan; after startup, it must be incorporated into the corresponding integrity program.

Applicability matrix

At plant-to-pipeline interconnections, battery limits, jurisdiction, and custody transfer must be established before approving procedures. A concise matrix prevents duplicate inspections and contradictory criteria. It should indicate:

• Asset and physical boundaries.
• Lifecycle stage.
• Governing document and edition.
• Party responsible for inspection.
• Acceptance criteria.
• Required records.
• Authority to release work.

The matrix also allows reviewing whether a change in material, pressure, service, or scope modifies the inspection strategy prior to commissioning.

From the construction baseline to in-service management

The transition between construction and operation requires preserving drawings, materials, welds, NDT results, repairs, tests, and accepted deviations. When this information remains distributed across independent documents and systems, the API 570 program begins without a reliable baseline and loses the ability to compare the initial condition with subsequent deterioration.

Integrity management platforms such as IntelliSuite, developed by AsInt, allow centralizing inspections, findings, repairs, and compliance requirements for piping and static equipment. Their integration with corrosion data, RBI, and remaining life helps turn records received during asset handover into traceable actions during operation.

Turn inspection records into traceable actions: Learn how AsInt solutions enable managing findings, repairs, corrosion locations, and regulatory compliance within an integrated digital environment.

API 570 and API 1169 certification

API 570 certification validates knowledge of inspection, repair, alteration, and rerating of operating metallic piping. API RP 1169 certification is aimed at inspectors of new onshore pipeline construction and evaluates responsibilities, safety, environment, and regulatory references.

Both credentials are valid for three years. Documented experience, professional activity, and recertification requirements form part of competency management. Holding both certifications can facilitate the transition between construction and operation, but it does not automatically expand contractual authority.

Piping inspection standards

Applicable standards must be selected based on asset type, lifecycle stage, evaluated threat, and jurisdiction. For operating process piping, API 570 can be complemented with API RP 571, API RP 574, API RP 580/581, API 579-1/ASME FFS-1, and ASME B31.3 to identify damage mechanisms, define inspection practices, prioritize using risk, and evaluate fitness for service.

For new onshore pipelines, API RP 1169 must be related to API Std 1104, ASME B31.4 or ASME B31.8, operator specifications, and 49 CFR Parts 192 or 195, depending on the fluid and jurisdiction. The organization must document the applicable contractual or regulatory edition, including addenda, errata, and effective dates.

Errors that increase cost and exposure

Scope errors

Applying process piping criteria to a regulated pipeline simply because it is already operating can displace requirements from the competent jurisdiction. It is also incorrect to use a construction guideline to establish corrosion rates, inspection intervals, or remaining life.

Inspection and data errors

Selecting an NDT technique before identifying the expected damage mechanism or discontinuity can result in insufficient coverage and findings that are difficult to substantiate. The technique must address a threat, a geometry, and a verifiable acceptance criterion.

Receiving materials, welds, NDT results, repairs, or tests with incomplete records makes it difficult to reconstruct the initial baseline condition and limits comparisons during subsequent inspections.

Conclusions

The primary risk in API 570 vs. API 1169 arises when an organization transfers acceptance criteria between lifecycle stages that demand different decisions. A defect accepted during construction does not automatically define its in-service behavior, and an indication evaluated during operation cannot be resolved using construction criteria.

The boundary must be established through jurisdiction, design code, operational condition, damage mechanisms, and authority to approve repairs, deviations, or sign-offs.

For the operator, API 570 gains value when it integrates the construction baseline with corrosion rates, monitoring locations, repair history, and FFS evaluations. Standards for piping inspection should function as a decision architecture with controlled editions, verifiable responsibilities, and traceability from construction through asset retirement.

References

1. American Petroleum Institute (API). (2024). API 570: Piping Inspection Code—In-service Inspection, Rating, Repair, and Alteration of Piping Systems (5th ed.). American Petroleum Institute.
2. American Petroleum Institute (API). (2020). API Recommended Practice 1169: Pipeline Construction Inspection (2nd ed.). American Petroleum Institute.
3. American Petroleum Institute (API). (2021). API Standard 1104: Welding of Pipelines and Related Facilities (22nd ed.). American Petroleum Institute.

Frequently asked questions