Codes, Standards, and Regulatory Requirements
This domain tests whether you know which document governs and how it applies. Distinguish a code (a body of rules adopted into law or contract, e.g., a boiler or pressure-vessel code) from a standard (a consensus technical document, e.g., an ASTM or ISO method) and a regulation (government-enforced). Standards become mandatory only when incorporated by reference into a code, contract, or regulation. A specification states requirements a product must meet; a test method prescribes how to measure; a practice describes a procedure without pass/fail criteria. Mixing these is the classic trap.
Understand hierarchy and precedence: contract documents typically control, then the referenced code, then referenced standards, then general practices - but the contract's stated order governs. Know that standards are revised; the edition cited in the contract is the one that applies unless an invoked code mandates a later edition. "Latest edition" is a frequent wrong answer when the contract pins an edition.
Other must-knows: shall (mandatory) versus should (recommendation) versus may (permissive); normative (binding) versus informative (guidance) annexes; the role of an authority having jurisdiction (AHJ) who may impose stricter local requirements; and accreditation (e.g., ISO/IEC 17025 for testing labs) versus certification of personnel versus registration of a quality system (ISO 9001).
Rule of thumb: when two documents conflict, the more stringent requirement generally prevails unless the contract specifies precedence - and the contract wins. Worked example: a contract cites ASTM method edition 2018; a newer 2022 edition exists. The 2018 edition applies because the contract references it, unless the governing code explicitly requires the current edition.