How to Compare Two Building Code Editions Without Missing Anything

Direct answer

Comparing two code editions is a sequence, and the order matters more than the effort. Start with the adoption record: which edition the jurisdiction adopted, when it takes effect, and what the vesting rule is for permits already filed — a project may never face the new edition at all. Then read Chapter 2, because a changed definition moves the scope of every section that uses the term and does so without appearing in any technical chapter. Then check the tables your own calculations depend on, since a factor such as the business occupant load allowance can change without any surrounding text changing. Then map section numbering, because a renumbered provision breaks every cross-reference in your specification and code-analysis sheet. Finally, read the jurisdiction's adopting ordinance, which can amend or delete anything above. Working the other way round — technical chapters first — reliably misses the changes that matter most.

Content and cited inputs reviewed by Scott Barrington, Harth founder and architectural technology specialist · Published 2026-09-07 · Updated 2026-09-07.

What must be verified before using this guidance?

1. Confirm the adoption record and the effective date

Before comparing anything, establish whether the comparison is needed. Find the adopting instrument, its effective date, and the jurisdiction's vesting rule for applications already filed. A project that vests under the previous edition needs no comparison; a project straddling the date needs the date in writing.

2. Read Chapter 2 of both editions, side by side

This is the step people skip and the step that pays. Definitions are the switches that decide which requirements apply. A term whose definition is narrowed pulls the scope of every section that uses it, and no technical chapter records the edit. Work through the defined terms your project actually relies on — occupancy, storey, grade plane, mezzanine, fire area, habitable space — and read both versions.

3. Check the tables your calculations depend on

Factors change without narrative. The business occupant load allowance moved from 100 to 150 square feet per occupant between the 2015 and 2018 IBC, and nothing in the surrounding text announces it. List the tables your code-analysis sheet actually reads — occupant load, allowable area, travel distance, fixture counts, fire-resistance ratings — and compare the specific cells you use.

4. Map the section numbering

Renumbering is not a change in requirement, but it breaks everything that points at the requirement: specifications, code-analysis sheets, review comments, standard details, office templates. Build a small cross-reference table of the sections you cite by number, and update the templates once rather than project by project.

5. Read the adopting ordinance

Local amendments sit on top of everything above and can add, modify or delete any provision. A jurisdiction that adopts a new edition and simultaneously carries forward an old amendment can produce a combination that exists nowhere in the model code.

What to record

A comparison is only useful if it survives the project. Keep the result as a short register rather than as a reading exercise — one row per change that touches your work, with the section, the effect and the drawing or specification affected.

Where the comparison usually bites

Across recent I-Code transitions, four areas account for most of the practical impact:

• Occupant load factors and egress sizing — small factor changes propagate into stair width, exit count and fixture counts at once.
• Construction types and allowable height and area — a new construction type or a restructured table changes what is buildable on the site.
• Energy compliance paths — renamed or restructured paths change the submission, not just the performance target.
• Definitions — the quiet one, and the reason this list starts where it does.

Edition-comparison register

One register per project, filled in once when the jurisdiction changes edition. The point is the last column: a change with no drawing consequence still belongs in the register, recorded as none.

This register records a comparison, not a compliance determination. The authority having jurisdiction decides which edition applies and how an amendment reads.

Where can you explore related guidance?

• Explore all code changes guidance
• IBC 2015 to 2018: The Changes That Move a Drawing
• IBC 2018 to 2021: Mass Timber and the New Construction Types
• IBC 2021 to 2024: What Changed for Design Teams
• IECC 2018 to 2021: How Much More Efficient, and What Changed

Sources and method

Method assembled from the structure of the I-Codes themselves and from the published edition-change record: ICC's code-change and Significant Changes programme, the ICC code library for reading two editions side by side, and the state adoption record at iccsafe.org/adoptions. Examples cited are sourced on the individual edition pages in this collection. The adopting jurisdiction's ordinance controls.

Source links

• codes.iccsafe.org

• iccsafe.org