Codes, Standards and Specifications
What you must know
Candidates must distinguish a code (a mandatory body of rules adopted by law or contract), a standard (a consensus technical document), and a specification (project-specific requirements). Know the roles of the applicable structural, pressure, and pipeline codes and how they reference filler metal and consumable classifications. Understand the hierarchy: contract documents, code, referenced standards, and approved procedures. Be able to read a clause and identify whether it is mandatory (shall), recommended (should), or informative (may).
Traps in questions
- Treating a recommended practice as legally binding.
- Assuming the latest edition applies without checking the contract or jurisdiction.
- Confusing acceptance criteria in a code with the manufacturer's data sheet.
- Overlooking that a code may permit alternatives only with engineer approval.
- Mixing up qualification requirements for procedure versus performance.
Worked example
A drawing calls for full penetration groove welds but cites a code whose default acceptance for that joint permits partial penetration unless otherwise specified. The inspector resolves the conflict by precedence: the contract drawing governs over the general code note, and the engineer confirms in writing. Rule of thumb: specific project documents override general code defaults; the more restrictive requirement wins unless formally waived.
Inspection link
Always cite the clause you are enforcing. An inspector who cannot name the governing clause cannot defend a rejection.