EOR Weld Specification Drawings — What to Specify vs What to Leave to the Fabricator
For AWS D1.1 projects, the Engineer defines required outcomes in Documents contractuels, while the Entrepreneur controls qualified execution details in the WPS. Holding that boundary prevents Code-vs-WPS disputes, reduces rework loops, and keeps Fabrication flowing with clear approval authority and Inspection expectations.
Start With Role Separation, Not Symbol Debates
Most EOR-Fabricant friction starts when process instructions get embedded in drawing callouts while essential project outcomes remain vague. AWS D1.1:2025 fixes this at the responsibility layer: Clause 1.5.1 defines Engineer responsibility for contract documents; Clause 1.5.2 defines Contractor responsibility for WPS preparation and execution.
Practical implication: the EOR should specify what must be achieved and what project constraints apply, while the fabricator should specify how qualified Soudage variables are executed inside the WPS.
"Remember the Symbole de soudure is for details of the physical weld, the WPS is for the process information."
@Slagtastic on r/Welding — permalink
What the EOR Must Carry in Contract Documents
Clause 1.5.1 allows the Engineer to add to, delete from, or modify D1.1 Exigences for the specific structure. That authority is not informal; changes must be incorporated in contract documents. The same Article enumerates categories to specify when applicable, including additional NDT, Critères d'acceptation beyond Clause 8, and toughness criteria.
When these items are missing, projects drift into "field interpretation mode." That is where inspectors and fabricators begin arguing from memory instead of contract language.
What the Fabricator Must Own in the WPS
Clause 1.5.2 assigns responsibility for WPSs, qualification of welding personnel, contractor inspection, and conformance execution to the Contractor. Clause 5.2.1 requires Préqualifié WPSs to be prepared as written documents. This is the operating instruction layer for welders and QC personnel.
Drawings are not the place to replicate every process parameter. If the drawing prescribes method details that conflict with a qualified WPS, production stalls and NCR volume rises without improving weld quality.
When 5 Notes Beat 500 Weld Symbols
AWS A2.4 gives drafters more than one clean way to communicate weld requirements. AWS A2.4:2020 Clause 6.12.3 allows a single TYP symbol for repetitions of identical Symboles de Soudage, and AWS A2.4:2020 Clause 6.12.6 allows drawing notes to provide weld information that does not need to be repeated in every symbol.
The trap is using a broad note to hide engineering decisions. If the welds are truly identical, a TYP symbol or keyed drawing note can reduce clutter. If the joints only look similar, separate the requirements by joint group, Taille, side, length, inspection scope, and Acceptation level so the fabricator is not forced to infer design intent.
HSS vs Tubing Belongs in the Member Callout
Do not use the weld-symbol tail to fix unclear member terminology. In D1.1, tubular product forms are part of the structural member definition and drawing/material-list layer; Symboles de Soudage carry Dimension de soudure, length, type, side, contour, process notes, and inspection references. If the part is an HSS, pipe, mechanical tube, or other tubular product, identify the product form, ASTM designation, grade, wall Épaisseur, and location in the member callout or material list.
The distinction matters because AWS D1.1 treats tubular structures as their own code family. Clause 1.1 names tubular and nontubular product-form members in the design scope, and Clause 10 contains exclusive tubular requirements. A drawing that says only "tube" in a cut list while the weld symbol tries to carry the real requirement pushes a material decision into the wrong layer.
CJP Is a Design Decision, Not a Drafting Default
AWS D1.1:2025 Clause 4.3.5.3 says contract documents must show CJP or PJP Soudure sur chanfrein requirements, but they do not need to show groove type or groove dimensions. That keeps the EOR focused on required performance while leaving qualified joint-detail execution to the shop drawing and WPS layer.
"If fillet welds meet the Résistance requirements they would be more cost effective and easier for the welders. CJPs welded from one side without Support envers require skilled tradesmen and tightly controlled weld procedures."
@Misconformance on r/Welding — permalink
That is the practical reason not to use CJP as a default answer. Specify CJP when the design demands it. Otherwise, check whether fillet or PJP requirements can communicate the same structural outcome with less fabrication risk.
Drawing Discipline Liste de Contrôle for EOR Teams
- Specify required structural performance and acceptance outcomes.
- State project-specific additions to baseline D1.1 requirements explicitly.
- Reference WPS by number where process control belongs in fabrication docs.
- Use TYP only for identical weld symbols with all applicable joints clearly identified.
- Use keyed notes for repeated weld groups, not as a substitute for unresolved engineering decisions.
- Call out CJP, PJP, and fillet outcomes intentionally instead of using CJP as a drafting default.
- Avoid embedding shop-sequence micromanagement unless engineering-critical.
- Define escalation path for approval decisions per
Clause 1.6authority model.
Frequently Asked Questions
AWS D1.1:2025 Clause 1.5.1 makes the Engineer responsible for the contract documents and gives the Engineer authority to modify code requirements for the specific structure through contract documents. Clause 1.5.1 also lists categories that must be specified when applicable, including additional NDT, acceptance criteria beyond Clause 8, and CVN toughness criteria. In practice, this means the EOR must define outcomes and acceptance expectations explicitly so fabrication and inspection are aligned before welding starts.
Drawings and project specifications should define required outcomes: structural intent, inspection scope, acceptance level, and any project-specific restrictions. The WPS should define execution details and qualified variable ranges the contractor uses to deliver those outcomes. AWS D1.1:2025 Clause 1.5.2 assigns WPS responsibility to the Contractor, and Clause 5.2.1 requires prequalified WPSs to be prepared as written documents.
No. AWS D1.1:2025 Clause 1.5.2 requires the Contractor to perform work in conformance with both the code and the contract documents. If contract documents are stricter than baseline code language, the WPS must be revised to align with the stricter project requirement. A WPS is an execution document, not a mechanism to relax contract-level requirements.
AWS D1.1:2025 Clause 1.6 states that references to approval mean approval by the Authority Having Jurisdiction or the Engineer. Contractors, inspectors, and QC staff can identify issues and recommend changes, but project-level requirement changes must be approved through the Engineer or AHJ path established in the contract framework.
Use TYP only when the repeated weld symbols are genuinely identical and the drawing clearly identifies every applicable joint. AWS A2.4:2020 Clause 6.12.3 allows a single TYP symbol for repetitions of identical welding symbols, and AWS A2.4:2020 Clause 6.12.6 allows drawing notes to provide weld information without repeating it in every symbol. That is different from using one broad note to cover similar but non-identical joints. If weld size, length, side, contour, inspection, or joint group changes, use separate symbols or a keyed note schedule.
Specify CJP when the design truly requires a complete joint penetration groove weld or when project requirements make that outcome mandatory. AWS D1.1:2025 Clause 4.3.5.3 says contract documents must show CJP or PJP groove weld requirements; it does not require contract documents to show groove type or groove dimensions. If a fillet or PJP weld can satisfy the design intent, the EOR should avoid defaulting to CJP as a drafting shortcut because CJP selection affects fabrication cost, access, qualification, and inspection planning.
Disputes reduce when responsibility layers are explicit: the EOR defines required outcomes in contract documents, the fabricator defines qualified execution in the WPS, and inspection verifies against both. Most code-vs-WPS conflicts come from mixing these layers, such as embedding process micro-instructions on drawings while leaving acceptance requirements ambiguous. Clear role separation shortens NCR cycles, keeps submittals focused, and prevents production delays.