NEC Edition and Local Code Adoption Guide
Find the applicable NEC edition through NFPA and local authorities, record amendments and effective dates, and avoid confusing publication with adoption.
Last updated:
Find the governing authority
The most recently published NEC is not automatically the enforceable code for a project. A state or local authority adopts an edition, may amend it, and may specify effective dates or transition rules.
- Start with NFPA’s NEC enforcement maps to locate the state-level adoption context.
- Open the actual state electrical licensing, building-code, or labor department source. For a project controlled locally, identify the city or county authority having jurisdiction (AHJ).
- Check the rule or ordinance, adopted edition, effective date, amendments, permit timing, and any project-specific transition provisions.
- Confirm uncertain scope with the permit/inspection authority and retain the source with the project record.
A national map is a starting point, not a permit determination. Local amendments, utility requirements, and equipment instructions can add conditions that a map does not describe.
Read adoption information
The linked authority pages below illustrate two different pieces of the lookup. They are not a complete 50-state edition table and should be rechecked for a new permit.
| Authority | What the retrieved page states | What still needs project confirmation |
|---|---|---|
| Texas TDLR | The electricians compliance guide identifies the 2023 NEC adoption, effective September 1, 2023. | Current amendments, local authority requirements, project scope, and subsequent rule changes. |
| Minnesota DLI | The electrical codes page identifies the 2026 NEC, effective August 17, 2026. Permits filed before that date use the 2023 NEC; permits filed on or after it use the 2026 NEC. | Permit application timing, special conditions, current rules, and any later adoption notice. |
Open the Texas authority page or the Minnesota authority page to read the actual rule context. A future edition announcement and an effective adoption are different events.
Record the project basis
| Field | What to retain |
|---|---|
| Project location and scope | Address, occupancy, installation type, and the work covered by the permit. |
| Authority | State and local permit/inspection authority and contact reference. |
| Adopted edition | The edition established by the governing rule, not merely the newest book available. |
| Effective / transition dates | The event that controls applicability, such as a permit application date, when the rule specifies one. |
| Amendments | Rule/ordinance identifier, amendment document, and any applicable local provisions. |
| Evidence and confirmation | Official URL, retrieval date, and any written clarification from the responsible authority. |
Download a code-adoption record (CSV)
Blank fields for project jurisdiction, adopted edition, dates, amendments, official sources, and authority confirmation.
If a calculator or reference cites a different edition, verify the actual method and section mapping before using it. Changing an edition number in a heading does not establish that its rules are unchanged.
Keep the document references in the job card; record actual test methods separately in the test record.