Existing PQR coverage matrix: row guide

This original working aid supports an evidence review before drafting a production WPS based on existing qualification records. It is not an AWS form or an automatic coverage determination.

Row grain

Use one row for each PQR × coupon × process segment × coverage branch as needed. Repeat the shared PQR fields for clarity or maintain stable identifiers in your spreadsheet. Do not place several process segments in one row when their actual values or support differ.

Three range columns

Column group	Meaning
Actuals and locators	Facts copied from the actual readable PQR, weld log or report, with units and page/file reference. Unknown values stay unknown.
Supported production range	Range derived from the applicable code qualification branch, conditions, notes and applicable contract basis. Cite the exact rule and retain the reasoning separately when needed.
Final WPS range	Narrow production range selected for the real job. It must fit the evidence, applicable support, parameter source and project requirements together.

Separate the dimensions

Record each base-metal side and thickness independently.
Record coupon position separately from intended production position; include plate or tubular test type.
Record each process's actual deposited weld-metal thickness. Do not substitute the total coupon thickness or apply a generic multiplier.
Keep filler, diameter, gas, transfer mode, polarity, waveform, parameter, CVN and PWHT conditions linked to their supporting process segment.
When multiple PQRs are combined, link each segment to its real PQR and check that the target combination is jointly supported. Do not assemble unrelated maxima into an invented envelope.

Evidence rules

Use exact file names and page/sheet/report locators. An old WPS alone does not establish what was tested. Preserve the actual test edition and date; do not rename historical qualification as a different edition. Identify failures, retests and the final adopted record exactly as documented. A missing source or unreadable report remains unresolved.

Status is not a code conclusion by itself. “Supported” should be used only after the applicable clause/table path and all relevant conditions have been checked. Record a specific gap and limit the corresponding WPS field when evidence is incomplete.

Project basis

This guide follows Cavoren's AWS D1.1/D1.1M:2025 base-edition WPS preparation references and its 2026-07-28 base-edition errata record; AMD1 is excluded. The contract edition and full applicable requirements govern.