Plain English:
Project Basis Gate
This article explains the 2024 IMC model-code path. Before project use, confirm the adopted code edition, local amendments, controlling administrative provisions, permit-application date, and current AHJ procedures. The locally adopted requirements control.
Local structure (113.1): Do not assume a five-member board, staggered terms, or specific member qualifications. Confirm the current ordinance, roster, appointing authority, terms, and vacancies.
Quorum and decisions: Confirm the local quorum, voting, record, written-decision, and service requirements. A model-code description is not a substitute for the current local procedure.
Hearing administration: Confirm who presides, who maintains the record, where submissions must be delivered, and who issues the decision under the local rules.
Decision effect: Confirm whether the decision is final, subject to rehearing, administrative review, or judicial review. Obtain legal guidance when property, enforcement, or appeal rights are at stake.
On Plans: Why It Matters in Design & Construction
Appeal outcomes depend on the current local hearing body, record, rules, and evidence. Research the active roster and prior written decisions, but do not assume prior membership, procedure, or precedent remains controlling.
Code Path: What to Show
M-001: If the project includes systems not covered by the IMC, note the code gap, the code-official resolution, and the standard applied.
For board decisions affecting your project: document the decision and reflect it in drawings and specifications.
Confirm the applicable board roster and term status before filing any appeal.
Check: Before You Appeal
Confirm the current board roster, term expiration dates, and the hearing calendar.
Verify which board member has expertise relevant to your technical issue.
Check that any board decision precedent does not conflict with your system type or application.
Review Risk:
Don't act on code gaps without AHJ input - self-interpretation of code gaps is a frequent redline source.
Do not assume a board decision is automatically final or binding in every jurisdiction; verify the local effect and review path.
Don't rely on precedent from an expired-term member without confirming it still applies.
Field Tip:
Before filing an appeal, ask the clerk for the current board roster, term expiration dates, and the hearing calendar. Use that info to plan: avoid filing right before a membership change, and tailor your brief to the board's established reasoning (pull prior written decisions if available).
Masterbuild QA Lens
Code gaps are resolved by the code official using approved test data, technical opinion, or published standards - not by the design team acting unilaterally. If the project has equipment or systems not addressed by the IMC, get written AHJ guidance before issuing the construction set. Undocumented assumptions become costly RFIs.
Drawing / Submittal Check
If the project has systems or equipment not covered by the IMC, M-001 must note the gap, the proposed compliance path, and the AHJ coordination method (written request for interpretation, pre-application meeting, or alternative means and methods submission). Do not leave code gaps undisclosed - the reviewer will find them and the response will take longer than a proactive disclosure.
Common Review Risk
Code gaps handled without AHJ input - where the design team decides the code does not apply or applies differently - are a significant risk in permitting. If the AHJ disagrees with the design team's interpretation of a gap, the result is a plan review
When To Escalate
Escalate when a Board of Appeals decision introduces a precedent that conflicts with your system type, requires attorney involvement to protect the owner's interests, or needs to be formally recorded in the project's legal file.