State Adoptions of the IBC and NFPA Codes: How U.S. Code Geography Works

Unlike most countries, the United States does not have a single nationally enforceable building code. The U.S. Constitution reserves building regulation to the states, and each state has historically chosen which model code to adopt, which edition of that code to adopt, and what local amendments to add. The result is a patchwork: a project designed to comply in one state can be non-compliant across the state line, and a project designed to the most recent model edition can be over- or under-built relative to the actually adopted edition. The International Code Council (ICC), publisher of the IBC, and the National Fire Protection Association (NFPA), publisher of NFPA 101 and NFPA 1, both publish model codes on three-year cycles. Each state then decides whether to adopt the new edition, skip an edition, or stay on an older edition for an extended period. Federal law overlays additional requirements for specific occupancy types — CMS for healthcare, the FAA for airports, the U.S. Department of Defense for federal facilities — that may differ from the state code.

State adoption typically follows one of three models. First, statewide mandatory adoption: the state legislature or a state building board adopts a specific edition of the IBC (and possibly NFPA 101, NFPA 1 and other related codes), with state-specific amendments. Local jurisdictions must enforce at least the state minimum but may add local amendments that increase but not decrease the minimum. Florida, California, New York, Texas, Massachusetts and most other large states use this model. Second, statewide voluntary adoption: the state recommends a code but lets local jurisdictions adopt or modify as they choose. Some southern and western states fall in this category. Third, no statewide code: only a handful of states still take this approach, leaving adoption entirely to local government. Most code adoptions go through a public comment process that takes 12 to 36 months from publication of the new model edition to legal effect at the state level. Because of this lag, the model code published in 2024 may not be the enforced code anywhere until 2026 or 2027, and many jurisdictions are still on the 2018 or 2021 edition years after the 2024 edition is published.

State amendments range from minor administrative tweaks (rewriting Chapter 1 to fit the state's permitting process) to substantive technical changes. Common technical amendments include: sprinkler requirements expanded to smaller buildings than the model code; energy-conservation provisions modified to fit local climate; seismic provisions modified for state-specific hazard maps; high-wind provisions modified for coastal areas; specific high-rise provisions modified for particular cities; healthcare-specific overlays incorporating CMS or state department-of-health rules; and specific occupancy chapters reorganised to reflect state licensure schemes (assisted living, adult day-care, group homes). California in particular maintains a heavily amended state-specific Building Code (Title 24) that diverges substantially from the IBC in fire-safety, energy and accessibility. New York and New York City both maintain their own code documents that incorporate the IBC by reference with substantial amendments. Massachusetts uses the IBC with a state-specific amendment package known as the Massachusetts State Building Code (780 CMR). Most states publish a free or low-cost summary of their amendments on the state building department or fire marshal's website.

Many states adopt the IBC for new construction (governed by the building department) and the NFPA 1 Fire Code or the IFC for existing-building maintenance and fire prevention (governed by the fire marshal or fire department). The two codes overlap heavily and are usually well-coordinated, but they can occasionally conflict — for example, on retroactive sprinkler requirements for existing buildings or on operational permits for hot work. When the IBC and NFPA 1 conflict, the practical resolution is jurisdiction-specific; some states formally adopt one as the primary and treat the other as supplementary, while others leave the conflict to be resolved by the AHJ on a project-by-project basis. NFPA 101 sits alongside both codes and is adopted in some states as a parallel life-safety reference. For healthcare facilities, the federal CMS Conditions of Participation require compliance with a specific edition of NFPA 101 (currently the 2012 edition for most CMS purposes, with a slow transition toward the 2018 edition) regardless of what edition the state has adopted, which means a healthcare designer must satisfy three codes — the state building code, the state fire code and the CMS-specified NFPA 101 edition — simultaneously.

Use this checklist to identify the codes in force on any U.S. project. First, identify the state and city (or county) where the project sits. Second, look up the current state building code on the state building department or state fire marshal website — this will identify the adopted IBC edition and the state amendment package. Third, look up the current state fire code, which is often the IFC or NFPA 1 with state amendments. Fourth, check whether the city or county has added local amendments — these are usually on the municipal building department or fire department website. Fifth, identify any federal overlays that apply: CMS for healthcare, the Joint Commission accreditation requirements (which incorporate NFPA 101 by reference), the Americans with Disabilities Act and the ADA Standards for Accessible Design, the U.S. Access Board's Architectural Barriers Act for federal buildings, and the FAA, FRA or DoD for transportation and military projects. Sixth, contact the local AHJ early in design to confirm the code reference list — most AHJs will respond promptly to a written request for code references, and getting their list in writing prevents disputes during plan review.

Changes between IBC editions tend to be evolutionary rather than revolutionary, but consequential changes accumulate over multiple cycles. The 2018 IBC introduced significant changes to mass timber construction (Type IV-A, B and C). The 2021 IBC continued the mass timber expansion and added provisions for tall wood construction, expanded mid-rise modular construction, and refined accessibility requirements. The 2024 IBC continued these trends, added expanded provisions for two-way communication systems in residential buildings, refined exit-route signage requirements and reorganised some fire-resistance tables. NFPA 101 also evolves on a three-year cycle: the 2021 edition expanded carbon monoxide alarm requirements in residential, refined occupant evacuation elevators, and added two-way communication system requirements; the 2024 edition continued these expansions. For evacuation planning, the most consequential changes between editions are usually in occupant evacuation elevators, two-way communication, voice evacuation triggers and accessibility — each of which can change which equipment must appear on the posted plan and how it must be labeled. EvacPlan Generator (www.evacplangenerator.com) keeps its icon library and route-drawing tools aligned with the most current NFPA 170 edition so posted plans remain consistent with the adopted code regardless of which edition the project is built under.

Designers working across multiple states should maintain a small reference table for each active project listing the adopted state and local code editions, the specific amendments that matter for the project type, and the contact information for the AHJ. Some firms standardise on the most recent model code edition and design every project to that standard, then adjust only for the small number of state amendments that are more restrictive than the model — this approach avoids re-learning the code on every project at the cost of occasionally over-designing. Other firms design strictly to the adopted edition in the project's jurisdiction, which produces the most efficient design but requires constant code-edition awareness. Posted evacuation plans should reference the specific code edition cited by the project's code analysis, so reviewers know which set of rules the plan was prepared to satisfy. The MAP KEY and any code-reference annotations on the plan should align with the adopted state and local codes, not with the most recent model code, unless the two coincide. Keeping an internal cheat-sheet of state adoptions and updating it with each three-year cycle is one of the highest-leverage uses of time for a multi-state designer.