Codes, Standards, and Regulations
What this domain tests
Codes, Standards, and Regulations tests how legal requirements reach a design: model codes adopted by statute, referenced standards, the authority having jurisdiction (AHJ), and the edition in force. You must know that a standard is not law until adopted, and that local amendments can override the model text.
Core rules
- A model code (for example, a building code) becomes enforceable through adoption by a jurisdiction.
- Referenced standards take effect through the edition cited in the adopted code.
- When documents conflict, the more stringent requirement generally governs, subject to the AHJ.
- The AHJ interprets and enforces; approvals and permits come from that office.
- Keep the project's code edition fixed at permit application unless the AHJ states otherwise.
Worked example
An assembly has an occupant load of 200. The adopted code requires 0.2 in of egress width per occupant for corridors and other level components, with a minimum corridor width of 44 in. What width is required? Calculated width = 200 × 0.2 = 40 in. The minimum of 44 in is greater than 40 in, so 44 in governs. The answer is 44 in, not 40 in. Reasoning check: the per-occupant formula sets the size for large crowds, but the absolute minimum protects small occupancies. Both must be satisfied; the larger value controls.
Traps
- Using a newer or older edition than the one adopted for the project.
- Treating an ASTM or ISO standard as legally binding without adoption.
- Missing local amendments that are stricter than the model code.
- Applying the per-occupant width and forgetting the minimum width.
- Assuming the designer, rather than the AHJ, resolves a code conflict.