Codes, Standards and Specification Requirements: Hierarchy and Acceptance
What to master
Understand the document hierarchy: statute, code, standard, project specification, procedure and work instruction. A code such as CSA W47.1 or AWS D1.1 sets minimum requirements for qualification and fabrication; a project specification can add stricter requirements but should not silently relax the code. Know how acceptance criteria are tied to inspection method, weld type, loading and service. Learn the roles of referenced standards, mandatory appendices and contract documents. Edition and amendment control matter: a procedure qualified to an older edition may not satisfy a contract invoking a newer one unless the code permits grandfathering.
Traps
Questions often swap acceptance criteria between codes or between fatigue and static loading. Another trap is assuming the code always governs over the specification; contract precedence clauses usually decide. Do not treat a recommended practice as mandatory unless it is invoked. Watch for 'shall' versus 'should' and for requirements embedded in notes or tables rather than the main text. Also distinguish qualification requirements from production acceptance requirements - satisfying one does not automatically satisfy the other.
Worked example
A drawing note says weld quality to AWS D1.1, while the project specification invokes CSA W59. The contract's order-of-precedence clause decides. If it says the specification governs, the inspector applies W59 acceptance criteria; if the code governs, apply D1.1. The practical rule: never choose acceptance criteria by habit - trace the requirement from the contract to the cited document and record the edition.