If our WPS is qualified to AWS D1.1:2025 but the contract says 2020, do we need to requalify?

Not necessarily. If the governing edition is AWS D1.1:2020, your WPS must comply with the 2020 essential variable tables and prequalified joint requirements — not simply carry a 2025 qualification date. In many cases the 2020 and 2025 requirements overlap, and the same PQR test data supports both editions. However, any essential variable that changed between editions must be reviewed for the 2020 compliance picture, and the WPS cover sheet should reference the governing edition.

Can the structural engineer of record (EOR) accept a 2025-qualified WPS on a 2020-governed project?

Yes. The EOR can approve an engineering substitution or equivalency. If the WPS meets all 2020 requirements and the 2025 changes are additive rather than substantive for that process and material combination, many EORs accept a written statement of compliance with the governing edition rather than requiring re-issue of every document.

Which edition governs — the one in the IBC reference or the one in the contract documents?

Contract documents take precedence over the default code reference in the IBC. If the IBC references AWS D1.1:2020 and your contract calls out AWS D1.1:2025, the contract controls for that project. Where the contract is silent, the IBC reference edition governs. When there is a conflict between the contract and the AHJ's edition, the AHJ requirement is typically the floor — the more stringent of the two applies.

How do we document edition compliance on our WPS submittal when editions differ from our shop standard?

Add a compliance note on the WPS cover or in the submittal transmittal letter stating that the WPS was reviewed against the governing edition and listing any parameters that were verified specifically for that edition. The WPS itself does not need to be reissued if the underlying qualification data satisfies both editions; the documentation just needs to make the compliance basis explicit.

Governing AWS D1.1 Edition Conflicts: AHJ, Contract, and Fabricator Obligations

When a contract specifies AWS D1.1:2020 but your shop runs 2025-qualified WPS documents, who governs? This covers how fabricators handle governing-edition conflicts.

Structural fabrication shops do not work on a single code edition. A shop qualified to AWS D1.1:2025 may simultaneously be executing a bridge project under AWS D1.5:2021, a building with a contract that specifies AWS D1.1:2020, and a federal project whose specification references a 2015 edition that predates both. Understanding which edition governs and how to handle the gaps is a recurring compliance question that never fully goes away.

The answer is not always "requalify everything." The answer is: know what changed, compare it to your existing qualification data, and document the compliance picture clearly.

Why Edition Conflicts Happen

AWS D1.1 publishes new editions on a roughly five-year cycle. The most recent edition, AWS D1.1:2025 (ANSI-approved March 2025), supersedes the 2020 edition for new qualifications. But contracts written before 2025 reference 2020 or earlier, and those contracts remain legally operative for the duration of the project — sometimes years into construction.

The International Building Code (IBC) references a specific AWS D1.1 edition in its structural welding provisions. Building permit applications filed before a new IBC cycle tie inspections to an older edition. Project specifications written by engineers of record often name the edition they designed to, and that edition stays in the contract documents even after a new edition publishes.

The result is that a CWI reviewing submittals on a major building project in 2026 may be checking WPS documents against AWS D1.1:2020, not 2025 — and the fabricator's shop standard may already be 2025.

What "Governing Edition" Actually Means

The governing edition is the one the contract documents say controls. In the absence of a contract specification, the AHJ's referenced edition governs. In the absence of both, the latest published edition is typically the default — but that assumption should be confirmed, not assumed.

For a WPS submittal, the governing edition determines:

Which essential variable table applies when evaluating whether a change requires requalification (Tables 6.6 and 6.8 in AWS D1.1:2025 correspond to Tables 6.5 and 6.7 in AWS D1.1:2020 — same concepts, renumbered).
Which prequalified joint details in Annex B (or Annex A in older editions) are allowed without a tested PQR.
Which visual acceptance and NDE criteria govern the completed welds.
Which preheat tables and minimum interpass temperature requirements apply.

Rule library based on AWS D1.1:2025; verify against your governing edition — the AHJ or contract may specify AWS D1.1:2020 or earlier, and table references and rule content differ by edition.

A shop using the 2025 rules on a 2020-governed project may inadvertently reference a table number that does not exist in the governing document, producing a submittal that reviewers cannot verify.

Key Differences Between AWS D1.1:2025 and 2020 That Affect Compliance

Several 2025 changes matter when mapping a 2025-qualified WPS back to a 2020-governed project:

Essential variable tables (Table 6.6 in 2025 / Table 6.5 in 2020):

The A5.36 electrode classification was removed from the GMAW/FCAW allowed filler metal list in 2025. A WPS that qualifies under 2025 without A5.36 will also comply with 2020 on that row.
The electrode-to-supplemental-filler ratio rule now uses a ±10% threshold in 2025; the 2020 version had different content on the same row.
The –G designator rule changed in 2025. A WPS designed around the 2025 –G rule must be checked against what 2020 required for that row.

CVN supplementary essential variables (Table 6.8 in 2025 / Table 6.7 in 2020):

The minimum thickness floor for CVN exemption moved from 5/8 in. (16 mm) in 2020 to 1/2 in. (12 mm) in 2025. If your project requires CVN testing and the governing edition is 2020, the 5/8 in. floor applies.
Preheat is no longer in scope for CVN supplementary essential variables in 2025; it was in 2020 (old row 36, the standalone interpass decrease rule). A CVN-qualified WPS under 2020 would have required a separate entry for that preheat variable.

For a complete breakdown of what changed between editions, see AWS D1.1:2025 vs. 2020 — changes that affect WPS qualification and AWS D1.1:2025 Table 6.6 changes from the 2020 edition.

How to Handle a Submittal When Your WPS References the Wrong Edition

When a submittal reviewer returns your WPS because it cites AWS D1.1:2025 and the contract calls for 2020, you have three practical paths:

Option 1: Issue a revised WPS cover referencing the governing edition. If your underlying qualification data (the PQR) supports compliance with the 2020 essential variable requirements, revise the WPS cover sheet to reference AWS D1.1:2020, map the parameter entries to the 2020 table designations, and resubmit. The PQR test data does not change; only the code reference on the cover changes. This is the most common approach for material/process combinations where the two editions are substantively identical.

Option 2: Submit a compliance matrix. Prepare a column-by-column comparison of the essential variable table for your process and material (e.g., GMAW on A572 Gr 50) showing the governing-edition row, the 2020 rule, and your WPS entry for each. This is useful when the qualification was done to 2025 and the reviewer needs to verify row-by-row that all 2020 requirements are met without requiring you to reissue the WPS itself.

Option 3: Request an engineering substitution. If the two editions produce different requirements for a specific row and your qualification satisfies the 2025 rule but not the 2020 rule, the EOR can accept the 2025 approach as an approved substitution. Get it in writing — an email from the EOR confirming the substitution is acceptable, or a formal RFI response.

For context on how essential variable categories determine what triggers a requalification in the first place, see WPS essential variables vs. non-essential variables under AWS D1.1.

Organizing Your Shop's WPS Library for Multi-Edition Projects

A shop running simultaneous projects under different governing editions benefits from a WPS numbering and indexing scheme that tags each document with the edition it was issued under. At minimum, the WPS cover sheet and the submittal log should note:

The code edition the WPS was qualified to
The governing edition for each project this WPS is used on
Any noted differences and how they were resolved (compliance matrix, EOR substitution, or revised cover)

Maintaining this record reduces re-review time when the same WPS is submitted to a new project with a different governing edition. For how long WPS and PQR records should be retained across projects and edition cycles, see how long is a WPS valid across edition transitions.

What the AHJ Can and Cannot Require

The Authority Having Jurisdiction (AHJ) — typically the building official or the jurisdictional inspection agency — enforces the edition adopted by the local jurisdiction. For building construction in jurisdictions that have adopted the 2021 IBC, that likely means AWS D1.1:2020. For newer adoptions, it may be 2025.

The AHJ can require that completed welds comply with the adopted edition's acceptance criteria and that the WPS submittal demonstrate compliance with that edition's qualification requirements. The AHJ cannot require you to tear up and requalify procedures that already comply with the governing edition simply because your shop also runs a newer standard. Compliance with the governing edition is the test; having a 2025-dated document does not fail that test if the underlying data satisfies 2020.

Where a project inspector (a special inspector under IBC Chapter 17, for example) is working to the IBC-referenced edition and your submittal references 2025, a brief transmittal note explaining which edition governs and that the submitted WPS was reviewed against it avoids back-and-forth rejections that come from the reviewer assuming the edition on the cover is the edition being enforced.

Edition conflicts are a documentation and communication problem more than a technical one. In most cases, the weld qualification data is sound; the gap is in making the compliance basis explicit for reviewers working from a different code year. A well-organized submittal transmittal, a compliance matrix, and a clear note on which edition governs — matched to your actual WPS entries — resolves the large majority of edition disputes before they become delays.

Managing a WPS library across multiple concurrent projects and code editions is one of the clearest use cases for purpose-built WPS management software for structural fab shops. Version control, edition tagging, and audit-packet export in one place eliminates the spreadsheet-based tracking that misses these cross-edition issues until a submittal comes back rejected.