Regulations, Codes, and Compliance Requirements
What you must know
Understand the hierarchy: statute (enacted by a legislature) → regulation (adopted by an agency under statutory authority) → code or standard (technical text, which has legal force only once adopted, typically by incorporation by reference). A model code published by a standards body is advisory until a jurisdiction adopts a specific edition, with or without local amendments.
Key mechanics: effective dates, grandfathering and nonconforming-use provisions, permits and plan review, inspection authority, enforcement remedies (notice, stop-work, fine, license action), and mandated recordkeeping. The authority having jurisdiction (AHJ) interprets and enforces; where code and manufacturer instructions conflict, the stricter applicable requirement generally governs unless the code says otherwise.
Traps
- Applying the edition in force today to work permitted years earlier. Generally the edition in force at permit application governs, unless an amendment or transition clause says otherwise.
- Reading “shall,” “should,” and “may” as synonyms. Shall is mandatory; should is advisory; may is permissive.
- Assuming a national standard is law everywhere.
- Missing that a local amendment overrides the model text.
- Overlooking licensure, notification, or reporting deadlines that are shorter than the project schedule.
Worked example
A permit is issued in November under the 2018 edition; a new edition takes effect in January. Unless the adopting ordinance states a different transition rule, the project is reviewed against the 2018 edition.
Rule of thumb
Before answering any compliance question, name three things: the jurisdiction, the edition in force, and the specific section cited.