instapreview's picture
Add 2026-11-16 snapshot (DOI 10.5281/zenodo.24289590)
f21280e verified
|
Raw History Blame Contribute Delete
8.56 kB

Methodology

U.S. Building Code Adoption Tracker Version 2026-11-16 (America/Los_Angeles) InstaPreView by Byts & Bytes

This document describes how the deposited spreadsheet and JSON were compiled. The files are a citable snapshot of the public tracker published at https://www.instapreview.co/data/code-adoptions on 2026-11-16. They are not a live legal database and are not a substitute for the adopted code, a licensed design professional, or a determination by the authority having jurisdiction (AHJ).

Scope and row selection

The live tracker is a table of one row per published U.S. city or county. This deposit reshapes that table into one row per code family so that each edition can be cited with its source and last-verified date.

A jurisdiction is included only when all of the following are true:

  1. It appears in the insta-codes corpus (Supabase project tiughylutmuckoorosjq) as an indexable page. The public view seo_jurisdiction_pages sets page_status to index when the jurisdiction is index-eligible: its slug is on the SEO index allowlist (seo_index_allowlist), or its corpus source_quality is recorded as verified, or it has at least five review rules with source_quality = verified. The nationwide stub is excluded.
  2. instapreview-api therefore returns the jurisdiction from GET /api/seo/jurisdiction-pages with page_status other than noindex and index_eligible other than false.
  3. A researched source profile exists in the InstaPreView website repository whose slug, url_slug, and state match that API record, and the jurisdiction has a public, indexable city page.

On 2026-11-16 those rules selected 117 jurisdictions, which is the same set and the same count as the live tracker. Of those 117, 108 were on the SEO index allowlist; the other 9 were already index-eligible through a verified corpus flag or through a sufficient number of verified review rules. Jurisdictions that are only in the corpus, only in a draft profile, or not yet index-eligible are omitted.

The nationwide record is never published. Held jurisdictions (see Hold policy) are omitted entirely. They are not published with estimated editions.

How editions are verified against official adoption sources

Edition strings are never guessed, inferred from a neighboring city, or filled from a model-code cycle that has not been adopted locally.

  • IBC, IRC, IFC, NEC, plumbing (IPC or UPC, or the locally named equivalent), and IEBC edition strings are copied from the insta-codes corpus fields exposed by GET /api/seo/jurisdiction-pages (ibc_edition, irc_edition, ifc_edition, nec_edition, ipc_edition, iebc_edition). Those strings originate in official adoption publications recorded in the corpus. A corpus flag of edition_trust: verified means the corpus recorded the edition under that flag; it is not treated as independent human verification of the public city page.
  • IECC, or the locally named energy code, is taken from the researched profile's official-source statements for the energy slot, and only when those statements name exactly one edition (or a clearly labeled commercial/residential pair). The insta-codes corpus does not have a mechanical or energy field, so energy editions are not copied from the API.
  • The official source URL is the first https URL cited in the profile's building-code statements, or, if none is present there, the first https official-source URL elsewhere in the profile.
  • An effective date is recorded only when the profile's building-code statements name exactly one calendar date as effective. The date is stored as YYYY-MM-DD. If the statements name no date, or name more than one date, the effective-date cell is left blank.
  • Blank cells mean the official source or the corpus did not state a single value. They are not zeroes and are not estimates. In this long-format deposit, a code family with no sourced edition is omitted rather than written as an empty row.

Every fact in a researched profile must carry an official https source URL and an accessed date (YYYY-MM-DD) for the day that page or document was opened. The value may not go beyond what the linked official page says. If a section or edition cannot be opened, it is omitted. Profile slots that cannot be sourced are marked not_found rather than filled by inference.

The last_verified column is the most recent accessed date on the official-source statements for that code family in the jurisdiction's researched profile. If that slot has no access date, the most recent official-source access date on the profile is used. The date is a source-access date in America/Los_Angeles. It is not a claim that a licensed professional independently verified the edition, and public city pages do not display a "Verified" badge on the strength of this date. Most published rows have not been independently human-verified.

Local amendments, phase-in rules, and project-specific applicability are not fully represented. Coverage is a growing subset of U.S. cities and counties, not a complete national inventory.

No-backdating rule

Publication dates, dataset version dates, and source-access (last_verified) dates use the real calendar day, in America/Los_Angeles, on which the work was done or the official source was read. Records are never given an earlier date to appear older or more established. This deposit is versioned and dated 2026-11-16, the day the snapshot was compiled from the live tracker.

Hold policy

A jurisdiction is held out of the tracker and out of this deposit when official sources cannot support a single, publishable edition list. Typical holds include:

  • Official sources conflict (for example, two agencies name different editions or different effective dates) and no winner is chosen.
  • An official page or ordinance PDF cannot be opened or reliably read.
  • A newly adopted edition has been approved but is not yet in effect locally.
  • A city is still in transition between code cycles, or the local ordinance has not caught up with a statewide adoption.

When two official readings disagree, the researched profile records both statements and marks the slot as a conflict; the compiler does not pick a winner in the data. Held cities are omitted until the official record is clear. Examples current as of this version include jurisdictions whose official PDFs could not be opened, whose city websites could not be read, or whose 2024 or later editions were adopted but not yet locally effective. Those held records are not included here and should not be inferred from nearby cities in the deposit.

Update cadence

New and updated jurisdiction research is performed daily, including weekends, in America/Los_Angeles. A jurisdiction is added to the public tracker only after official sources have been opened, a researched profile has been written, the city page has been deployed, and the jurisdiction is index-eligible as described above.

The public tracker table is regenerated at site build time from the insta-codes corpus and the researched profiles. It is not queried live at page request. This Zenodo deposit is a snapshot of that built table as it stood on 2026-11-16. Later corrections and additions will appear first on https://www.instapreview.co/data/code-adoptions. Code editions change; confirm the current adoption with the AHJ before relying on a value.

File layout

File Contents
us-building-code-adoption-tracker.csv Long-format table, one row per sourced code edition
us-building-code-adoption-tracker.json The same rows, with dataset metadata
LICENSE.txt Creative Commons Attribution 4.0 International (CC BY 4.0)
METHODOLOGY.md This document
metadata.md Values to enter in the Zenodo upload form; not part of the dataset proper

Columns: jurisdiction, state, code (IBC, IRC, IFC, IECC, NEC, IPC/UPC, or IEBC), edition, effective_date, source_url, last_verified.

This snapshot contains 738 code-edition rows covering the same 117 jurisdictions as the live tracker on 2026-11-16.

License and citation

This dataset is dedicated to reuse under the Creative Commons Attribution 4.0 International license. You may copy, redistribute, and adapt it, including commercially, as long as you give appropriate credit.

Suggested citation:

InstaPreView. (2026). U.S. Building Code Adoption Tracker (2026-11-16). Byts & Bytes. https://www.instapreview.co/data/code-adoptions. Licensed under CC BY 4.0.

InstaPreView does not issue permits.