How Codes and Licensing Rules Actually Get Made

Why this matters

A tech who says "the code changed" usually means three separate events that happened years apart: a model code organization published a new edition, a state or city adopted it with its own amendments, and an inspector started enforcing it. Each event has its own process, its own calendar and its own point where an ordinary contractor can be heard. A shop that does not know which stage a change is in will either panic over a proposal that never passes or ignore a rule that is already law.

This card owns the process. Why a shop should bother taking part is its own card (see related: The Shop as a Citizen of Its Trade), and so are the practical how-tos for commenting and testifying.

The first thing to know: model codes are not law

The International Residential Code, the International Plumbing Code, the National Electrical Code and their siblings are written by private standards organizations, the International Code Council (ICC) and the National Fire Protection Association (NFPA). Nothing in them binds you until a government adopts them. That is why every citation in this library reads "as adopted by your jurisdiction", and why the edition matters: your county may be enforcing an edition two or three cycles old, with local amendments that change the section you are looking at.

Both organizations publish on a three-year cycle. The I-codes carry edition years like 2021 and 2024; the NEC (which is NFPA 70) carries 2020, 2023 and 2026. The cycle is long because the process is open, and the openness is what gives a small shop a way in.

The ICC process

Anyone may submit a code change proposal to the ICC; you do not need to be a member. The proposal names the section, gives the exact new wording with deletions struck and additions underlined, and states a reason. Proposals with evidence get taken seriously; proposals that say "this is common sense" mostly do not.

The steps, as the ICC has run them in recent cycles:

1. Proposals are published for each code group. The ICC splits its codes into groups heard in different years of the cycle, so any given code has one proposal window per edition. The grouping and calendar have been adjusted between cycles, and the current schedule is posted on the ICC's site.
2. Committee Action Hearings. A code development committee, appointed by the ICC with a balance of code officials, industry and other interests, hears testimony on each proposal. Anyone may testify, usually for a couple of minutes. The committee votes a recommendation: approve, approve as modified, or disapprove.
3. Public comment. The committee's results are published and anyone may submit a public comment asking for a different outcome, or for a modification.
4. Public Comment Hearings. Proposals that drew public comments are heard again. Here the voters are not the committee: they are governmental member voting representatives, meaning code officials and other employees of member governments.
5. Online Governmental Consensus Vote. Governmental members who could not attend vote online. The combined result is the final action, and the approved changes go into the next edition.

The point that surprises contractors: final decisions on most I-codes are made by government code officials, the same people who enforce them. Industry testifies; officials vote. That is why field evidence carries weight and why a reputation with your local building department matters even at the national level.

One exception worth knowing: the ICC moved the energy code, the IECC, to a standards-development process run by consensus committees, starting with the 2024 edition. Its proposals and votes follow that committee process rather than the governmental vote above, so check which process a code uses before you plan a comment.

The NFPA process

The NEC and other NFPA documents (NFPA 54, the National Fuel Gas Code, is developed jointly with the American Gas Association; NFPA 58 covers LP-gas) follow a different sequence with its own vocabulary:

1. Public Input stage. Anyone may submit public input, a proposed change, through the document's page on the NFPA site.
2. First Draft. The responsible technical committee (for the NEC, one of its code-making panels) meets, acts on every public input, and produces the First Draft. The committee is balanced so that no single interest category, such as manufacturers or installers, holds more than one third of its votes.
3. Public Comment stage. Anyone may comment on the First Draft.
4. Second Draft. The committee acts on the comments and balloted results produce the Second Draft.
5. The Technical Meeting. At NFPA's annual Technical Meeting, members may make certified amending motions on the Second Draft, but only if someone filed a Notice of Intent to Make a Motion by the published deadline. Then the Standards Council issues the document, after hearing any appeals.

The practical difference from the ICC: under NFPA, the technical committee's balloted vote decides almost everything, and the floor of the Technical Meeting is a narrow, deadline-gated last chance rather than a second hearing.

The timeline, drawn

Here is how one change travels from an idea to your inspector, with the stage where a contractor's voice is cheapest to use marked.

MODEL CODE (ICC or NFPA), about 2 to 3 years
  proposal or public input  <- easiest place to be heard
    -> committee hearing / First Draft
    -> public comment       <- second window
    -> final vote / Second Draft and Technical Meeting
    -> edition published
STATE OR LOCAL ADOPTION, about 0 to 3 more years
  notice of proposed adoption, with amendments
    -> comment period and hearing <- local window
    -> adopted, with an effective date
ENFORCEMENT
  permits applied for after the effective date
    -> inspector applies the adopted edition

The two lags add up. A proposal filed early in a cycle can reach your county's permits five or more years later, and a state that skips an edition stretches that further.

Adoption: where the national code becomes your code

Adoption is a government act, and it follows that government's own rulemaking law. Three patterns cover most of the country:

• Statewide mandatory adoption. A state building code council or agency adopts an edition for the whole state, often as both a floor and a ceiling, so localities cannot add stricter rules without permission.
• Statewide minimum with local amendments. The state sets a floor; cities and counties may add to it.
• Local adoption only. Some states leave residential code adoption largely to localities, so two neighboring counties can be on different editions or one may have none for some work.

Which pattern your state uses is the single most important thing to find out, because it tells you which body to watch. Amendments made at adoption are where most residential-specific fights happen: a state may delete a requirement it considers too costly, change a threshold, or add a local rule. The adoption itself usually goes through notice and comment, so there is a window here too, and it is the one where a local contractor's evidence is most persuasive because the audience is local.

Electrical adoption runs on its own track in many states, often through an electrical board, and NEC adoption commonly lags publication by a year or more, with some states several editions behind.

Licensing rules: a statute, then a rule

Licensing works in two layers, both set by the state, and confusing them sends people to the wrong place.

The practice act is a statute. The legislature decides that a license is required, what classes exist, what work is exempt (handyman thresholds live here, where they exist) and what the board may regulate. Changing any of that means a bill, which means legislators, committee hearings and usually an association's lobbyist.

The board's rules are regulations. Within the statute, the licensing board writes rules: exam content, experience hours, continuing-education requirements, apprentice supervision ratios where the statute lets it, insurance and bonding, disciplinary procedure. Boards make rules under the state's administrative procedure act. The pattern is broadly similar across states, though deadlines and steps vary:

1. Notice of proposed rulemaking published in the state register (and often on the board's site), with the text and a comment deadline.
2. Comment period, during which anyone may file written comments; many states also hold a hearing, either automatically or on request.
3. Board consideration of the comments at a public meeting.
4. Final adoption, sometimes followed by review by a legislative rules committee or the governor's office, and an effective date.

Two more features matter. Many states put licensing boards through periodic sunset review, where the legislature decides whether the board should continue and in what form; that is the moment to argue about the structure itself. And board meetings are generally open under state open-meetings law, so you can attend and, at most boards, speak during public comment.

The federal version of notice and comment, under the Administrative Procedure Act, works the same way with the Federal Register in place of the state register. It reaches your shop through agencies like the EPA (refrigerant rules, lead renovation rules) and the Department of Labor.

A worked example: one proposal, traced

A drain-cleaning and plumbing shop owner thinks the plumbing code's cleanout spacing language is being read inconsistently between two inspectors in her county. She traces where a fix could happen.

Is it the model code or the adoption? She reads her county's adopted plumbing code and finds the county adopted the model code edition from two cycles ago with no amendment to that section. So the wording is the model code's, and the inconsistency is in interpretation.

Option 1, the model code. She could submit a proposal to clarify the wording. The plumbing code's next proposal window opens in about a year. If it passes, it appears in the edition published roughly two years after that. Her county, which runs about two cycles behind, would adopt it perhaps three to six years after publication. Total: plausibly six to nine years before her inspectors read the new words.

Option 2, local amendment or interpretation. Her county's building official can issue a written interpretation now, and the county will hold a hearing on its next code adoption, which the department says is planned for next year.

She does both, in order of speed: asks the building official for a written interpretation, which arrives in five weeks, and files the model code proposal through her state association's code committee so it carries the association's support and evidence from several shops. The interpretation fixes her county now. The proposal fixes it for everyone, eventually.

What would change the answer: if her county had amended that section locally, a national proposal would do nothing for her, and the local adoption hearing would be the only route.

What gets missed

Deadlines are absolute. A comment filed a day late is generally not considered at either the ICC, the NFPA or a state agency. Each body publishes its calendar; see related: The Community Commitments Calendar SOP.

Testimony without wording. At a code hearing, saying a proposal is bad accomplishes less than offering a modification with the words you would use instead.

Arguing at the wrong layer. Telling a licensing board it should eliminate a license class wastes everyone's time; that is the legislature's call. Telling the legislature how many continuing-education hours renewal should require is usually the board's call.

References

• International Code Council, code development process and current cycle schedule
• National Fire Protection Association, Regulations Governing the Development of NFPA Standards
• Federal Administrative Procedure Act, 5 U.S.C. 553 (notice and comment)
• See related: How to Submit a Public Comment on a Proposed Rule
• See related: How to Represent Your Shop on a Code Proposal