Skip to content

Field guide

NEC 2026 Adoption by State: The §110.16 Tracker

Reviewed July 18, 2026 Standards-linked editorial Review policy

NEC editions become law state by state, years apart, and §110.16's expanded arc-flash label rules only bind where NEC 2026 is adopted. This tracker records what we know, when we learned it, and where it came from — no guesses presented as fact. It is refreshed quarterly (next pass: October 2026) and the update log at the bottom records every change.

Last checked: July 18, 2026.

Status at a glance

State / jurisdiction NEC 2026 status §110.16 notes As of
Washington Adoption targeted for December 31, 2026 Would bring the expanded label rule with the edition July 18, 2026
Maine Moving to amend §110.16 out of its NEC 2026 adoption Early evidence the expansion will be fought state by state July 18, 2026
All other states No NEC 2026 adoption at research time Current edition varies by state; the 2026 rules do not bind yet July 18, 2026

That is the whole verified picture. When a state acts, this table grows a row with a source and a date; when a date passes, its row moves to adopted-with-edition or amended, with the paperwork linked.

How to read the gap

Code cycles run roughly three years, and state adoption typically trails publication by one to four years, with amendments. Three practical consequences:

  1. Your obligations today come from your state's current NEC edition plus NFPA 70E and OSHA — and those already produce detailed labels in practice (NFPA 70E §130.5(H), OSHA 29 CFR 1910.333). The 2026 expansion changes the NEC's explicit scope, not the underlying safety logic.
  2. Washington's date matters beyond Washington. First movers set the template other states copy, including their amendments. If §110.16 survives December 31, 2026 intact, expect cleaner adoptions elsewhere; if Maine-style amendments spread, expect a patchwork.
  3. Specifiers move before states. Public project specifications already demand machine-printed, UL 969, no-field-markings labels with study traceability — contract language adopted the detailed label years ago. The requirements page has the field set that satisfies both the code text and the spec language.

What we track, and what we do not

Tracked: state-level NEC 2026 adoption actions and §110.16-specific amendments, each with a dated source. Not tracked: local AHJ interpretations (too granular to keep honest at this cadence), and rumoured adoption bills without official action. If you need your AHJ's position this week, call them — their answer outranks any tracker, this one included.

Update log

  • July 18, 2026 — Tracker created. Washington's December 31, 2026 target and Maine's §110.16 amendment move recorded from EC&M's 2026 code-cycle coverage and Zech Engineering's NEC 2026 section analysis; all other states marked "no adoption at research time."

Background: NEC 2026 arc flash labels (the change package) and NEC 110.16 explained (the section itself). Labels that already meet the 2026 content rules come out of the free calculator.

Direct answers

Frequently asked questions

Has my state adopted NEC 2026?

At the last check (July 18, 2026), no state had adopted it. Washington targets December 31, 2026, and Maine is amending §110.16 out of its adoption. The table on this page records every verified move with a date and a source.

Do the new label rules apply before adoption?

Not via the NEC — but NFPA 70E §130.5(H) and OSHA 1910.333 already produce detailed-label obligations today, and project specifications often require the full field set regardless of the adopted code edition.

How often is this tracker updated?

Quarterly — next pass October 2026 — with an update log recording every change and its source.

Source trail

Sources

Standards references identify the applicable document or section where possible. Standards text may require licensed access. Report a factual issue through the process on our corrections page.