Codes, Standards, Regulations and Permitting
The Hierarchy
Regulations are law; codes and standards are adopted into law by reference. The Ontario Building Code and Electrical Safety Code are examples of documents given legal force. Standards bodies include CSA Group, ASTM, ISO, and IEEE. When a code references a standard, compliance with that standard becomes mandatory for the scope described.
Reading and Applying Documents
Know how to locate the applicable edition, amendment, and any local bylaws or utility requirements that layer on top. Understand the difference between mandatory language ("shall") and advisory language ("should"). Permits are separate from compliance: even a code-compliant design requires the correct permit and inspection before use.
Permitting Workflow
Typical sequence: determine the authority having jurisdiction (AHJ); prepare drawings and calculations to the required standard; submit for permit; respond to review comments; build; arrange inspections at hold points; obtain final approval and occupancy or energization clearance. Skipping a hold point can void insurance and create liability.
Traps
Questions often offer a "newer standard" that was not in force when the permit was issued-generally the code edition in force at permit time governs, unless the AHJ directs otherwise. Another trap: assuming a manufacturer's literature substitutes for a code requirement. Also watch for confusion between an AHJ's interpretation and the written code; the AHJ's interpretation governs in practice, but you may seek clarification.
Rule of Thumb
Code edition, AHJ, permit, inspection-confirm all four before you build. Worked example: a design references a standard updated after permit issuance. The technologist documents the edition in force at permit time, notes the discrepancy to the AHJ, and proceeds per the AHJ's written direction rather than unilaterally adopting the newer edition.