How building codes get adopted

A model code is a document, not a law

The International Codes are published by the International Code Council, a private organisation. On the day a new edition is published it has no legal force anywhere. It is a book.

It acquires force when a government adopts it: a state legislature, a state agency under delegated authority, a county, or a municipality. Adoption happens at several of those levels, and the ICC records adoptions by states and by individual jurisdictions for that reason. [1]

Everything confusing about American building regulation follows from that single arrangement. The technical content is written once, centrally, by a consensus process. The legal force is granted thousands of times, separately, by governments that are under no obligation to act at the same time or in the same way.

The two variables that make neighbours differ

The first is edition. New editions are published on a cycle, and jurisdictions adopt on their own timetable. Some adopt promptly, some lag by a cycle or several, and some adopt on a schedule fixed in their own legislation. At any moment the country is running a mixture of editions, and two counties sharing a boundary can easily be several years apart.

The second is amendment. A jurisdiction adopting a model code may modify it, and many do. Amendments respond to local conditions that a national document cannot anticipate: seismic exposure, hurricane wind, frost depth, expansive soils, wildfire, or a local decision about what is worth requiring. They can add requirements, remove them, or replace a provision entirely.

The combination is what defeats general advice. A statement beginning the code requires is incomplete unless it names an edition and a jurisdiction, because those two variables can change the answer within a fifteen minute drive.

How adoption actually happens

The mechanics vary but the shape recurs. A state agency or a local government proposes adoption of a specific edition. There is a review period in which affected parties comment: builders, trade associations, fire officials, building officials, energy advocates, manufacturers of things the code would require or exclude. Amendments are proposed, argued and either accepted or dropped. The adopting body votes, and the adoption takes effect on a stated date, often with a transition period during which projects already in permitting continue under the previous edition.

That transition provision matters more to a project than almost anything else in the process. It means the code governing your building is generally the one in force when your permit application was made, not the one in force when your building is finished, and where the boundary falls is a question for the building department rather than a matter of principle.

The comment stage is also where a great deal of the variation originates. Energy provisions in particular attract organised argument, because they impose costs on builders that are recovered over time by occupants, which is a structure that invites disagreement about who should carry them.

Who writes the model, and how

The technical content arrives through a consensus development process rather than from an authority. Proposals to change a provision are submitted, heard in public, argued, voted on and either incorporated into the next edition or not. The people doing the arguing are building officials, engineers, fire officials, manufacturers, trade associations and advocacy organisations, and their interests do not align.

That process has two properties worth understanding, and they pull in opposite directions.

It is genuinely open, which is unusual for a document that becomes law. Anyone may submit a proposal and the hearings are public, so a provision that survives has been argued against by people with a reason to dislike it.

It is also slow and it favours participants who can afford to be present continuously. Manufacturers and national associations attend every cycle. A local building official or a small builder generally does not. That asymmetry is the standard criticism of the model code process and it is a fair one, though the alternative arrangements proposed for it have their own version of the same problem.

The practical implication for a reader is modest but real. A provision in a model code is a negotiated outcome rather than a technical optimum, and knowing that makes it easier to understand why a requirement sometimes looks like a compromise. It usually is one.

Why the fragmentation persists

It is easy to describe this arrangement as inefficient, and every so often somebody proposes replacing it with a national code. It survives for reasons that are not merely inertia.

Building regulation in the United States is a police power exercised by the states rather than a federal function, which is a constitutional arrangement rather than a policy preference. States delegate to local governments in varying degrees. A national residential building code would require a change to that structure, and the one significant exception, the federal standard governing manufactured housing, exists under a specific federal statute rather than as a general power.

There is also a substantive argument for local variation, and it is stronger than the fragmentation complaint usually allows. A code adequate for a temperate inland county is not adequate on a hurricane coast or in a seismic zone or in a wildland interface, and the entity that knows which of those conditions applies is local. The model code accommodates that with climate zones and hazard maps, but not exhaustively, and amendment is the mechanism for the remainder.

What this means for a project, concretely

Three consequences, and they are the reason every page on this site that touches a code carries the same note.

Advice from another jurisdiction is a hypothesis, not an answer. A contractor who worked for years in the next state is describing a code that may differ from yours in ways neither of you will notice until plan review.

The edition is a project parameter, not a technicality. It belongs alongside the site conditions in the earliest project documents, because it can change the energy specification, the structural provisions and the electrical requirements, and it is knowable in one phone call.

And a published requirement without an edition and a jurisdiction attached is not a requirement, it is a fact about somebody else. That includes everything on the contents sheet, which is why this publication states what quantities mean and sends readers to the authority having jurisdiction for the values.

There is a fourth consequence that surfaces only on larger projects, and it is worth naming because it catches people out. A jurisdiction that adopts a new edition partway through a long project creates a boundary, and where a particular building falls relative to that boundary is a question of dates rather than of merit. Transition provisions exist for exactly this and they are ordinary, but they have to be relied on deliberately: knowing which edition your permit was issued under, and having that in writing, is what turns a potential argument into a filed document. Nobody thinks to ask for it at the time, and everybody wishes they had it later.