On most structural steel projects, the WPS question surfaces late and under pressure: the inspector arrives, asks for the welding procedures, and nobody is sure whose job it was to produce them. The answer under AWS D1.1 is unambiguous — the contractor performing the welding owns the WPS — but construction contracts have a way of obscuring that line.
What AWS D1.1 Says About WPS Ownership
AWS D1.1:2025 places responsibility for welding procedures squarely on the contractor or fabricator doing the work. The code requires that welding conform to a qualified WPS, that the WPS be supported by a Procedure Qualification Record (PQR) or satisfy the prequalified requirements of Clause 5, and that the WPS be available to the welder and inspector at the point of work.
The code does not specify who drafted the document. It specifies who is accountable for compliance: the entity performing the welding.
This means a structural steel erector cannot look upstream to the GC and say "they gave us this WPS." The erector's crew is holding the stinger; the obligation is theirs.
Rule library based on AWS D1.1:2025; verify against your governing edition.
The Engineer of Record's Role
The engineer of record (EOR) defines what gets built: joint type, base metal, design-basis loading, and acceptance criteria. The EOR may also impose requirements beyond the code minimum — mandatory CVN (Charpy V-notch) testing that invokes the supplementary essential variables of Table 6.8, preheat levels above the D1.1 minimum, or specific filler metal classifications for seismic or demand-critical applications.
What the EOR does not do:
- Qualify welding procedures
- Sign WPS documents
- Own or maintain PQR test records
EOR requirements flow to the fabricator through the contract documents or project specification. It is then the fabricator's job to produce a WPS that satisfies both the base code and those project-specific additions. If the EOR specifies CVN-tested procedures, the fabricator must run CVN coupon tests, document the results in the PQR, and ensure the WPS references those results — but the PQR is still the fabricator's document, not the engineer's.
A common miscommunication pattern: the EOR's specification cites an AWS edition or requires supplementary essential variable testing, but nobody in the procurement chain confirms the fabricator's procedures actually comply. The gap surfaces during third-party inspection or at final audit.
The General Contractor's Position
A GC that self-performs structural welding is itself the "contractor" under D1.1 and owns the WPS. Where the GC subcontracts fabrication or field erection welding, responsibility follows the work.
Some GCs maintain an in-house WPS library for standard fillet weld work and supply those documents to subcontractors. This is permissible under D1.1, but it creates an obligation on the sub: verify that the supplied WPS actually covers the work being performed. If the GC's WPS qualifies SMAW on Group I base metals and the sub's scope involves A572 Grade 50, a Group II material, the WPS does not cover the work regardless of who supplied it.
The sub cannot assume that a document handed to them by the GC is adequate. Responsibility for compliant welding travels with the welding, not the paper.
Specialty Subcontractors and Erectors
Specialty firms — connection erectors, miscellaneous steel subs, ornamental fabricators — are often small enough that they have never built their own WPS library. They commonly rely on procedures supplied by the GC, the fabricator of record, or pulled from the internet. Each sourcing strategy carries risk:
GC-supplied WPS: Adequate only if the GC's procedure covers the specific base metal group, process, filler, and joint type in scope. Requires explicit verification, not just receipt of a document.
Steel fabricator WPS: Shop procedures are often written and qualified for controlled shop conditions and flat-position work. Field erection uses different positions — 3G, 4G, 6G on hollow sections — and shop WPS may not qualify those positions. A fabricator who supplies a WPS to a field sub should confirm the position qualifications match what will actually be performed on site.
Downloaded templates: A template WPS with no PQR behind it is not a qualified procedure under D1.1 unless it meets every requirement for a prequalified WPS under Clause 5. Most templates do not. See WPS template downloads: why they're a search trap for a breakdown of when a template becomes a real procedure — and when it is just paper.