Model code adoption processes, drafting local amendments, establishing local modifications, and appendix procedures. Covers legal requirements for code adoption and documentation of local requirements.
2
hours
0.2
CEUs
Administrative, Legal & Management
1.7.4
This course covers material relevant to the following ICC certification exams:
Model code adoption processes, drafting local amendments, establishing local modifications, and appendix procedures. Covers legal requirements for code adoption and documentation of local requirements.
Format
On-Demand Online
Delivery
Self-Paced
Access
24/7 After Enrollment
Certification
Certificate of Completion
Have questions about this course or our platform?
Contact our support teamDraft code adoption ordinances with proper legal language
A companion course, *Understanding Your Jurisdiction*, teaches practitioners how to find and apply the edition and amendments a jurisdiction has already adopted. This course starts a step earlier: how a model code becomes law in the first place, and what a governing body must do to adopt or amend it. The audience here is the building official, department head, or elected body drafting and enacting the ordinance — not the inspector looking something up later.
The starting legal fact is easy to overlook: a model code published by a private organization such as ICC has no independent legal force anywhere. It remains a technical document until a government body with police power — the authority to regulate for public health, safety, and welfare — formally enacts it as law, and that authority doesn't exist automatically. States generally grant it to municipalities and counties through enabling legislation. Under the traditional framework often called Dillon's Rule, a local government has only the powers expressly or implicitly granted to it by the state; many states have nonetheless recognized building-code adoption as an inherent municipal power even without a specific enabling statute, but a prudent jurisdiction confirms its authority rather than assumes it. States with home-rule provisions flip that default: a home-rule charter, typically adopted by local referendum under state constitutional authorization, gives a local government broad latitude to legislate in areas the state hasn't specifically claimed, including building regulation. Either way, confirming exactly what legal authority the jurisdiction is acting under is the first step in drafting an ordinance, because that authority defines what the ordinance can validly do.
Once authority is confirmed, jurisdictions almost universally adopt model codes "by reference" rather than reprinting the full text into the municipal code — reproducing hundreds of pages in a newspaper of record or code book is prohibitively expensive and serves no one but the printer. Adoption by reference lets an ordinance simply name the code and incorporate it as though fully set out, but only if the ordinance satisfies the same due-process purpose full publication would have served. A legally sound adoption ordinance generally needs: an enacting ordinance passed under confirmed authority; a reference to one specific, dated edition — never "the current edition" in the abstract, since edition ambiguity is one of the most common defects found in later legal challenges; copies of the code filed and available for public inspection, typically with the clerk; advance public notice and a hearing before the governing body; and a clearly recorded effective date. Skip any of these and the resulting "code" is vulnerable — jurisdictions have discovered years into enforcement that a code staff had been applying was never validly adopted at all.
A county with no building code is considering adopting one after a series of construction-quality complaints. The county attorney drafts a short ordinance stating the county "adopts the International Building Code for regulation of construction." Reviewing it before the vote, the building official flags several gaps: no edition year, so it's unclear which version would actually be law; no provision for filing a public copy anywhere for inspection; and an agenda posting that skipped the specific hearing notice the state's municipal code requires. Rather than let the vote proceed, the official works with the attorney to confirm enabling authority, insert the edition date, add the filed-copy and notice provisions, and reschedule for a properly noticed hearing. The revised ordinance takes an extra month, but it is the difference between a code the county can actually enforce and one a contractor's attorney could unravel on a technicality.
A frequent drafting error is referencing "the current edition" or omitting the edition date, leaving ambiguity about which text was actually adopted. Another is treating adoption by reference as a formality that doesn't need the filed-copy, notice, and hearing steps a full-text ordinance would require — those steps are what make the reference legally sufficient in place of publishing the full text. A third is assuming municipal authority to adopt a building code without confirming it against the state's enabling legislation or home-rule status. The correction in each case is the same: treat an adoption ordinance as legislation with its own due-process requirements, and verify authority, edition specificity, public access, notice, hearing, and effective date before it goes to a vote.
Code Reference: IBC Introduction — The I-Codes are written and formatted specifically to be adopted by reference by ordinance; the introductory material anticipates that a jurisdiction's own adopting legislation, not the published text alone, is what converts the model code into locally enforceable law.
Develop and document local amendments and modifications
Local amendments are legislation, not editorial notes, and must be produced the way legislation is produced. Typically the process starts with the building official or staff identifying a provision that needs local modification — a climate, seismic, wind, water-supply, or policy reason to be more or less stringent than the base code allows. Staff (sometimes through a technical advisory committee) draft the amendment language and prepare a recommendation, with supporting rationale, for the governing body, then the amendment follows the same lawmaking path as the original adoption: public notice, a hearing before the elected body, and a formal vote. That elected body is the same one a building official works with continually on budgets and policy — the working relationship covered in the course on working with elected officials and boards carries directly into how amendment recommendations get framed and presented. No amendment, however minor it looks, remains enforceable if it skips this sequence; an amendment adopted through a shortcut has no more legal standing than no amendment at all.
That rigor exists because of pitfalls jurisdictions run into repeatedly. Best known is the "automatic future adoption" clause — language stating the jurisdiction adopts the code "and all future editions and amendments" published by the sponsoring organization. It reads as a convenient way to stay current without repeating the hearing process every cycle, but courts in multiple states have found it has no legal validity: a private organization's editorial decisions cannot substitute for a jurisdiction's own legislative act. A second pitfall is adopting a code edition without also carrying forward the standards it references, leaving gaps between what staff believe is required and what the ordinance actually adopted. A third is a conflict between state and local law: under the doctrine of preemption, a local amendment that contradicts a state statute or state-mandated minimum will not survive a challenge, so drafting has to check what the state allows a locality to change. A fourth is the transition gap when a jurisdiction updates editions — projects already filed under the old code need a clear governance decision, typically a savings clause, about which edition governs their completion.
A jurisdiction is preparing to move from its current code edition to the newest one. Two draft ordinances circulate. The first, prepared by the building official with legal counsel, names the exact new edition and date, lists which amendments and appendix chapters carry forward or are revised, sets a future effective date, includes a savings clause for projects already under permit, and is scheduled for the required notice and hearing. The second, floated by a council member who remembers the process as burdensome, proposes amending the original ordinance to read that the jurisdiction "adopts the International Building Code, as amended from time to time by the International Code Council," so the council never has to revisit the question again. Legal counsel rejects the second draft immediately: automatic-future-adoption language of this kind has been struck down elsewhere, and adopting it would leave the entire building code vulnerable the first time it mattered — for instance, if a permit denial or code-violation prosecution were challenged on the ground that no version of the code was ever validly adopted. The governing body proceeds with the first draft.
A common mistake is treating a local amendment as a minor tweak that doesn't need the full notice-hearing-adoption sequence because it "just" changes a familiar provision — every amendment needs that sequence to be enforceable. Another is directing staff to enforce an ICC-published errata or interim change informally, on the theory it will probably be adopted eventually — until the governing body acts, it carries no legal weight. A third is including automatic-future-adoption language for convenience without recognizing it as a defect that has repeatedly failed legal review. The correction in each case is procedural discipline: route every amendment, however small, through the same legislative steps as the base adoption, and address referenced standards and transition rules explicitly rather than leaving them implied.
Code Reference: IBC Introduction — Because the model code is revised on a regular publication cycle, any adoption package intended to stay current must name the specific edition in force and be renewed through the jurisdiction's own legislative process at each cycle, rather than relying on language that tries to adopt future changes automatically.
Manage adoption of appendices and supplemental requirements
Appendix chapters sit outside the base text a jurisdiction adopts by default. The model codes make clear, in their own front matter, that an appendix becomes part of the enforceable code only if the adopting ordinance specifically lists it — adopting "the code" does not, by itself, pull every appendix chapter along with it. A governing body deciding to adopt a code edition needs an explicit list of which appendix chapters are being adopted and which are left out, so the choice is a deliberate legislative one rather than a gap discovered later during a plan review or an appeal.
Getting an adoption or amendment package to a vote involves several distinct roles, and confusing them is a recurring source of trouble. The building official functions as technical advisor: identifying what needs to change, drafting or reviewing language, and explaining the practical and life-safety consequences of different options. The governing body is the lawmaker: it alone has authority to enact, amend, or repeal the code, and staff conviction that a change is good never substitutes for that vote. Legal counsel reviews the ordinance for the validity issues covered earlier in this course — proper authority, edition specificity, notice, and the automatic-adoption trap among them. The public and affected stakeholders — design professionals, contractors, trade groups, residents — have a role in the hearing itself, and their input on record is part of what makes the ordinance defensible if it's challenged later.
Keeping the adopted code current is an ongoing governance responsibility, not a one-time project. Model codes are revised on a predictable publication cycle, and each cycle raises the same question: whether, when, and how to move to the new edition. That decision carries costs beyond the ordinance itself — staff training on what changed, updated checklists, and public communication so the design and construction community isn't caught unprepared. Building officials who plan for a code-update cycle the way they plan other department initiatives — the kind of forward planning covered in the course on strategic planning for building departments — are far better positioned than those who treat each update as a scramble once a hearing is finally scheduled. A realistic adoption calendar builds in time for staff review, drafting amendments, coordination with legal counsel, the hearing itself, and a transition period before the effective date.
A mid-size jurisdiction's building official is preparing the recommendation package for the next scheduled code-edition update, roughly three years after the last one. Rather than forwarding the new edition with a short cover memo, the official assembles a full package: a summary of what changed and why it matters locally, a review of the jurisdiction's 40-plus existing amendments against the new edition (several are now redundant because the base code addresses the same issue, and a few reference provisions that shifted in the renumbering), a recommended list of appendix chapters to carry forward, an estimated staff-training and public-notice timeline, and draft transition language for projects already under permit. The council schedules the required hearing, stakeholders comment, and the ordinance passes with a clean, current amendment package rather than three-plus years of accumulated, partly obsolete local changes.
A common mistake is assuming an appendix chapter is automatically part of the code once the base edition is adopted — it is not, and a governing body should make an explicit, on-the-record decision about each appendix it wants enforced. Another is a building official presenting a recommendation as though already decided, rather than as a recommendation subject to the body's own vote — blurring that distinction weakens the legislative record if later challenged. A third is letting old local amendments carry forward automatically without reviewing them against the new base code, accumulating redundant or conflicting provisions over successive cycles. The correction is the same discipline running through this course: treat appendix selection, staff recommendation, governing-body vote, and implementation planning as deliberate parts of the legislative process, not afterthoughts.
Code Reference: IBC Introduction — The code's own structure separates the base chapters from its appendices precisely so that a jurisdiction can adopt the two independently; a governing body's ordinance should reflect that separation explicitly rather than assuming appendices are included by default.
This course covers the legislative and governance side of code adoption: how a privately published model code becomes locally enforceable law, and how a jurisdiction runs that process soundly from first adoption through every later amendment and edition update. It starts from the legal foundation — a model code has no force until a government body with confirmed police-power authority enacts it, whether under Dillon's-Rule-style enabling legislation or broader home-rule authority — and moves through the specific mechanics of adoption by reference: a dated edition, filed public copies, notice, a hearing, and a recorded effective date. It treats the amendment process as legislation in its own right, subject to the same rigor every time, and works through the recurring pitfalls that have gotten adoption ordinances invalidated in practice, chief among them the automatic-future-adoption clause. It closes with the governance work of managing appendices, coordinating the distinct roles involved — technical advisor, lawmaker, legal counsel, public — and treating a code-cycle update as an ongoing planning responsibility rather than a one-time vote. A companion course, *Understanding Your Jurisdiction*, picks up from the practitioner's side: once an ordinance like the ones described here is properly enacted, how a building official confirms and applies exactly what was adopted on a given project. The two together cover the full life of an adopted code, from the governing body's ordinance to the counter and the field.