The short answer: the 2026 National Electrical Code is already in force in Massachusetts, Maine, Wyoming, North Dakota, Colorado, Minnesota, and Texas. Washington has adopted it with a delayed December 31, 2026 effective date. Oregon still describes October 1 as anticipated, not final. But the date alone does not tell you which edition governs a project: the transition can turn on when a permit was filed or issued, when a plan was accepted for review, or when electrical work commenced.
This tracker records only state actions that ChatDiagram could verify against a government source as of September 3, 2026, Pacific Time. It is an evidence ledger, not a claim that every other state is still on an older edition. A missing state means “not verified in this review,” not “not adopted.” City, county, and special-jurisdiction amendments can still control.
Verified 2026 NEC state actions
The “transition trigger” column is deliberately separate from the effective date. It is the fact a design team needs when deciding which code edition to print in a title block, calculation package, equipment schedule, or general note.
| State | 2026 NEC status | Effective | Verified transition rule | Official source |
|---|---|---|---|---|
| Massachusetts | In force with Massachusetts amendments | 2026-04-24 | The state page establishes the code effective date; confirm permit treatment and amendments with the enforcing authority. | Department of Fire Services |
| Maine | In force with Board amendments and exclusions | 2026-07-01 | Applies to electrical installations commencing on or after July 1, plus applicable state, Board, and municipal rules. | Electricians' Examining Board |
| Wyoming | In force | 2026-07-01 | The state update gives an effective date but no project transition rule; verify the permit basis with the AHJ. | State Fire Marshal |
| North Dakota | In force with state wiring standards | 2026-07-01 | The Board lists its 2026 standards as effective July 1; the filed rules apply 2026 NEC requirements with North Dakota provisions, including explicit rules for exposed-room wiring and occupancy changes. | State Electrical Board |
| Colorado | In force statewide; local enforcement still matters | 2026-08-01 | Boulder says the date is based on Colorado adoption and requires permit applications after August 1 to indicate 2026 NEC conformance. | City of Boulder |
| Minnesota | In force with Minnesota amendments | 2026-08-17 | Permits filed before August 17 use the 2023 NEC; permits filed on or after that date use the 2026 NEC. | Department of Labor and Industry |
| Texas | In force with a state amendment to 210.8(F) | 2026-09-01 | TDLR says all non-exempt electrical work starting September 1 must follow the state-adopted 2026 NEC. The rule keeps the listed-HVAC-equipment exception to 210.8(F) without an expiration date. | Texas Register |
| Washington | Adopted; delayed effective date | 2026-12-31 | Normally keyed to the electrical permit issue date, with exceptions for earlier dwelling building permits and plans accepted for review before adoption. | WSR 25-23-069 |
Texas is the newest verified change in this edition of the tracker. The adopted rule was filed August 12, published in the August 28 Texas Register, and became effective September 1. TDLR's implementation bulletin uses the start of non-exempt electrical work—not the drawing date—as its statewide transition instruction. The rule also modifies the model text by keeping the exception from 210.8(F) GFCI protection for listed HVAC equipment without an expiration date.
Minnesota supplies a different trigger. Its notice of adoption was published August 10, the code became effective August 17, and the state distinguishes permits filed before that date from permits filed on or after it. “The state adopted it” is not enough information for either live project; the team still needs the state's exact transition verb and amendments.
Watch list: announced is not the same as adopted
Oregon's Building Codes Division says the 2026 Oregon Electrical Specialty Code process has begun and lists October 1, 2026 as an anticipated adoption date. The current adopted-code page still identifies the 2023 OESC as the electrical code in force. Until the agency posts a final rule and transition instructions, drawings should not label the 2026 OESC as current merely because it appears in a proposed timeline.
Georgia illustrates a different naming trap. Its current state rules call the electrical code the “2023 Edition with 2026 Georgia Amendments.” The “2026” describes the amendment package, not the base NEC edition. A county page or project note that shortens that phrase to “2026 electrical code” can silently change its meaning.
How to decide which NEC edition belongs on a project
Use this procedure before updating calculations or redrawing a one-line:
- Name the enforcing jurisdiction. Start with the authority that will issue the electrical permit or perform the inspection. State adoption may be the baseline, but a city, county, federal facility, tribal authority, or utility can change the answer.
- Find the adoption instrument. Prefer the filed rule, administrative code, state register notice, or agency code page. A training announcement or contractor blog can point you toward the record but should not establish the date.
- Capture the exact transition trigger. Record whether the rule uses application filed, permit issued, plan accepted, building permit issued, installation commenced, or another event. These phrases are not interchangeable.
- Check project history against that trigger. Preserve the relevant receipt, permit number, acceptance notice, or start record. A design created after the effective date can still be governed by the earlier edition if an explicit transition exception applies.
- Read amendments and delayed provisions. Adoption by reference does not mean unamended adoption. A state can retain older language, delete a new section, delay a requirement, or add a local condition.
- Write the result into the drawing record. Put the edition, amendment package, jurisdiction, source URL, and verification date in the project basis—not just “latest NEC.” Identify which calculations and sheets were reviewed when the basis changed.
- Confirm with the AHJ before issue. The tracker narrows the search. It cannot approve a project or resolve an authority's interpretation.
Worked example: two projects, one adoption date
Suppose two Minnesota service-upgrade projects are designed on August 20. Project A's electrical permit was filed August 14; Project B's was filed August 18. The state source says Project A stays under the 2023 NEC while Project B uses the 2026 NEC. The drawing date is the same, but the filed-date trigger produces different code bases.
Now compare Washington. A project with an electrical permit issued after December 31 would normally move to the 2026 NEC, but the rule preserves exceptions for certain dwelling building permits and for plans received and accepted before adoption. Copying Minnesota's “filed date” rule into a Washington checklist would be wrong even though both states adopted the same model-code edition.
Texas uses a third boundary. Suppose a project received a municipal permit in August but the electrician did not begin installing electrical material or equipment until September 2. The permit date alone does not close the code-basis question: TDLR says non-exempt electrical work starting September 1 or later must follow the state-adopted 2026 NEC. The project record should preserve its actual installation-start evidence, then separately record applicable municipal amendments.
The Texas amendment also prevents a subtler documentation error. A reviewer should not copy the unamended model-code expiration into a Texas note or assume the statewide exception removes every project-specific requirement. Record “2026 NEC as adopted by Texas, including 16 TAC §73.100(b)” in the basis, then verify the equipment listing, branch-circuit design, local amendments, and enforcing authority's interpretation for the actual installation.
What changes in the drawing package
An adoption update should trigger a controlled review, not a blind search-and-replace:
- update the code-basis note with edition, amendments, jurisdiction, and verification date;
- rerun calculations affected by substantive code changes instead of only changing section numbers;
- review one-lines, risers, panel schedules, equipment labels, and protection-setting references;
- in Texas, review outdoor dwelling HVAC outlet notes and schedules against the state's non-expiring listed-equipment exception rather than copying the model text unchanged;
- preserve the old code basis when a documented transition exception applies; and
- mark unresolved local amendments as open review items rather than guessing.
The separate 2026 NEC one-line drawing changes guide explains which model-code revisions can alter topology, fault-current annotations, dwelling load calculations, power-control-system documentation, and medium-voltage references. This tracker answers the earlier question: whether that edition applies at all.
Limits and common failure modes
- Treating this table as exhaustive. It intentionally reports verified actions, not an unsupported 50-state “no action” census.
- Confusing adoption with effective date. Washington adopted the code in 2025 but delayed effect until the end of 2026.
- Using the wrong project date. Filed, issued, accepted, and commenced describe different events.
- Dropping the amendment name. “2023 NEC with 2026 amendments” is not the 2026 NEC.
- Assuming statewide means uniform. Local amendments, home-rule authority, utility requirements, and special occupancies can still change the review.
- Using an owned page as evidence. ChatDiagram can help draft a one-line, but only the controlling jurisdiction establishes the enforceable code.
For a first-pass diagram after the code basis is documented, use the ChatDiagram single-line diagram generator, then verify every rating, conductor, protection setting, neutral bond, operating state, and note against the project calculations and the AHJ-approved code basis.
Last checked: September 3, 2026, Pacific Time. This page records government-source evidence available during that review. It is not legal or engineering approval, and it will change as agencies file rules and publish amendments.