The NEC edition enforced by a state is only the first layer of a solar permit code check. A state can adopt an edition, amend it, delegate inspections, and allow local requirements. The permit date can also place one project under a different edition from the next project.
Direct answer. There is no single NEC edition enforced for every United States solar project. As of September 26, 2026, state baselines range from the 2008 NEC to the 2026 NEC. Seven states use a materially local adoption model. New York uses split state and city authority. Confirm the project address, inspection authority, adopted edition, effective date, amendments, and transition rule before drafting the solar plan set.
This guide gives a dated baseline for all 50 states and Washington, DC. It does not replace the ordinance, rule, or written direction that controls one permit. Every matrix row includes an official starting source and still requires an AHJ check.
Research status: The matrix was reviewed against official government sources on September 26, 2026. Alaska, Tennessee, and West Virginia have verified current editions, but the reviewed sources did not settle their adoption effective dates. Treat this as a starting point for research and have a qualified United States electrical-code professional confirm the edition, amendments, and effective date that govern your specific project.
NEC edition enforced by state for solar: quick matrix
Use this matrix to start research, not to finish it. The baseline describes the state position found on the observation date. The project action identifies the remaining check.
On a smaller screen, scroll the matrix horizontally to review all five columns.
| Jurisdiction | Baseline found on September 26, 2026 | Effective date or transition | Authority model and project action | Official source |
|---|---|---|---|---|
| Alabama | 2020 NEC within the Division of Construction Management scope | July 1, 2022 | State scope is limited. Resolve the local authority elsewhere. | Alabama DCM |
| Alaska | 2020 NEC under 8 AAC 70.025 | Effective date unresolved in reviewed source | State minimum covers defined work. Check municipal or association standards. | Alaska regulations |
| Arizona | Edition set by the city or county | Local ordinance controls | Local adoption model. Retrieve the ordinance for the project address. | Arizona municipal authority |
| Arkansas | 2026 NEC | September 3, 2026 | Statewide minimum with amendments. Confirm the inspection authority. | Arkansas rule |
| California | 2023 NEC through the 2025 California Electrical Code | January 1, 2026 | Check filed city or county amendments and local transition rules. | California Building Standards Commission |
| Colorado | 2026 NEC | August 1, 2026 | State minimum with local enforcement. Confirm submission-date treatment. | Colorado Electrical Board |
| Connecticut | 2020 NEC through the 2022 State Building Code | October 1, 2022 | State code with local officials. Confirm the responsible reviewer. | Connecticut codes |
| Delaware | 2023 NEC through Regulation 701 | January 1, 2026 | Local rules may be more stringent. Check the county or city. | Delaware Regulation 701 |
| Florida | 2020 NEC through the Eighth Edition Florida Building Code | December 31, 2023 | State code with local administration. Check department procedures. | Florida Building Commission |
| Georgia | 2020 NEC with Georgia amendments | September 1, 2021 | Current until the planned 2027 cycle. Check approved local amendments. | Georgia DCA |
| Hawaii | 2020 NEC through the Hawaii State Electrical Code | March 15, 2022 | Counties adopt or receive an interim code. Verify the county ordinance. | Hawaii Building Code Council |
| Idaho | 2023 NEC | April 4, 2025 rule annotation | Identify state or authorized local inspection jurisdiction. | Idaho DOPL |
| Illinois | Edition set by the local authority | Local ordinance controls | State guidance sends code questions to the local official. | Illinois code FAQ |
| Indiana | 2008 NEC through the 2009 Indiana Electrical Code | August 26, 2009 | A newer rule was pending, not effective. Recheck before use. | 675 IAC 17-1.8 and the pending replacement rule |
| Iowa | 2023 NEC with statutory exclusions and amendments | June 2, 2026 | State minimum. Confirm the state or local inspection program. | Iowa DIAL |
| Kansas | Edition set by the local authority | Local ordinance controls | City or county adoption governs ordinary construction. | Kansas Corporation Commission |
| Kentucky | 2023 NEC with Kentucky amendments | January 1, 2025 | Some residential provisions changed on July 15, 2026. Check scope. | Kentucky DHBC |
| Louisiana | 2020 NEC through the State Uniform Construction Code | January 1, 2023 | Future 2023 language was not yet treated as effective. Recheck. | Louisiana LSUCCC |
| Maine | 2026 NEC through Chapter 120 | July 1, 2026 | Applies to installations starting on or after that date. Check local rules. | Maine electricians board |
| Maryland | Edition set by the county or municipality | Local ordinance controls | Retrieve the local electrical code and amendments. | Maryland Labor |
| Massachusetts | 2026 NEC through 527 CMR 12.00 | April 24, 2026 | State electrical code with local enforcement. Verify permit treatment. | Massachusetts code |
| Michigan | 2023 NEC for covered work | March 12, 2024 | Residential rules need a separate scope check. Confirm enforcing agency. | Michigan LARA |
| Minnesota | 2026 NEC through Minnesota Rules chapter 1315 | August 17, 2026 | Permits filed on or after the date use 2026. Verify inspection authority. | Minnesota DLI |
| Mississippi | Edition set by the county or municipality | Local ordinance controls | Check local adoption and any statutory opt-out. | Mississippi Insurance Department |
| Missouri | Edition set by the local jurisdiction | Local ordinance controls | State data is informational. Confirm directly with the city or county. | Missouri DNR |
| Montana | 2023 NEC | September 26, 2026 | State code with state or certified local administration. | Montana current codes |
| Nebraska | 2023 NEC with named 2017 provisions retained | August 1, 2024 | State and listed local programs divide inspection authority. | Nebraska adoption notice |
| Nevada | Edition set by the local authority | Local ordinance controls | State-owned work has a separate path. Resolve the project authority. | Nevada statute |
| New Hampshire | 2023 NEC through the state building code | July 1, 2026 | Six-month code election exists without mixing editions. Check application date. | New Hampshire statute |
| New Jersey | 2023 NEC through the Uniform Construction Code | August 17, 2026 | Local agencies enforce the state subcode. Check transition treatment. | New Jersey UCC |
| New Mexico | 2020 NEC through the New Mexico Electrical Code | March 28, 2023 | State code with state or qualifying local enforcement. | New Mexico rule |
| New York | Split authority; New York City uses amended 2020 NEC | City code effective December 21, 2025 | Do not apply the city edition statewide. Resolve the local jurisdiction. | New York State codes |
| North Carolina | 2020 NEC through the North Carolina Electrical Code | November 1, 2021 | State code with local inspections. Confirm interpretations and transition. | North Carolina OSFM |
| North Dakota | 2026 NEC | July 1, 2026 | State standard may interact with qualifying local requirements. | North Dakota board |
| Ohio | 2023 NEC for covered work | October 15, 2025 current rule | Certified local departments administer the code. Check residential scope. | Ohio rule |
| Oklahoma | 2023 NEC for commercial electrical construction | September 14, 2024 | Adopted by the Uniform Building Code Commission, not the Construction Industries Board, which handles licensing. Local permits may use higher standards. Confirm residential scope separately. | Oklahoma OUBCC |
| Oregon | 2023 NEC through the 2023 Oregon Electrical Specialty Code | October 1, 2023 | State code covers nonexempt installations. Confirm inspection authority. | Oregon BCD |
| Pennsylvania | 2020 NEC through the Uniform Construction Code | July 13, 2025, with full enforcement from January 12, 2026 | The 2021 I-Codes took effect separately on January 1, 2026. That is not the NEC date. A contract-based transition closed on January 12, 2026. | Pennsylvania UCC |
| Rhode Island | 2023 NEC through SBC-5 | December 1, 2025 | Municipal departments enforce the state code. Check permit transition. | Rhode Island code office |
| South Carolina | 2020 NEC with approved modifications | January 1, 2023 | Mandatory state baseline with local enforcement. | South Carolina council |
| South Dakota | 2023 NEC | November 12, 2024 | Permits received on or after the date use 2023. Check exceptions. | South Dakota commission |
| Tennessee | 2017 NEC | Effective date unresolved in reviewed source | State inspection has exempt local jurisdictions. Resolve the inspector. | Tennessee adopted codes |
| Texas | 2023 NEC | September 1, 2023 | Municipal permits may apply. State rules address work without a permit. | Texas TDLR |
| Utah | 2023 NEC | July 1, 2026 | State code includes statutory state and local amendments. | Utah Code |
| Vermont | 2023 NEC through the 2025 Electrical Safety Rules | November 5, 2025 | A limited work-in-progress transition exists. Check permit facts. | Vermont codes |
| Virginia | 2020 NEC through the 2021 Virginia code cycle | January 18, 2024 | State code with local officials. Confirm the project transition. | Virginia DHCD |
| Washington | 2023 NEC through WAC 296-46B-010 | April 1, 2024 | Permit-date exceptions exist. The 2026 NEC starts December 31, 2026. | Washington WAC |
| West Virginia | 2023 NEC where the state code is adopted and enforced | Effective date unresolved in reviewed source | Confirm county or municipal adoption and enforcement status. | West Virginia rule |
| Wisconsin | 2023 NEC through SPS 316 | September 1, 2026 | State or delegated municipal administration. State rules limit variation. | Wisconsin SPS 316 |
| Wyoming | 2026 NEC | July 1, 2026 | State or delegated local enforcement. Identify the inspecting authority. | Wyoming fire marshal |
| Washington, DC | 2014 NEC through the 2017 DC Construction Codes | May 29, 2020 | District code with local amendments. Check transition provisions. | DC Department of Buildings |
The oldest baseline in the table does not automatically mean an unsafe project. It means the adopted legal framework has a different model-code starting point. Amendments, product rules, other codes, and project specifications can add requirements.
The newest baseline does not make every earlier design obsolete. A valid transition rule may keep a submitted or accepted project under an earlier code. The permit record must support that choice.
Why the NEC publication year does not decide the permit code
NFPA publishes NFPA 70, the National Electrical Code, as a model code. Publication alone does not enact that edition in a state, city, or county. A government must adopt it through an authorized legal process.
Four layers can affect the code basis:
- Model-code publication. NFPA publishes an NEC edition.
- State adoption. A legislature, board, agency, or code council adopts an edition and amendments.
- Local action. A city or county adopts, administers, or amends the code within its legal authority.
- Project enforcement. The AHJ applies an edition and transition rule to the actual permit.
These layers explain why a web search can return several plausible answers. One result may describe the newest NFPA edition. Another may show a pending state rule. A third may reflect a major city rather than the project jurisdiction.
A code map can help locate the likely baseline. It cannot prove the law for one address. Save the official adoption source and the local confirmation in the project file.
Adoption, enforcement, and inspection are different
Adoption establishes a code in law or rule. Enforcement applies that code to permits and installations. Inspection authority identifies the organization that examines the work.
One agency may handle all three roles. Several agencies may also divide them. Nebraska, Washington, and Idaho show why the inspection boundary belongs in project intake.
The permit issuer may not be the utility. Utility interconnection review can apply separate tariffs, manuals, and equipment rules. A utility approval does not establish the building department’s code edition.
A pending rule is not the current code
Rulemaking pages often display proposals, hearing notices, and planned effective dates. Those documents are useful signals. They are not final adoption unless the legal process has finished.
Indiana illustrates the risk. A 2023-NEC-based replacement was in rulemaking during this review. The research did not find a final effective filing. The matrix therefore retains the 2008 NEC baseline found in the current code.
Louisiana presents a similar timing issue. The code council approved future 2023-NEC language in July 2026. The current package still used the 2020 NEC on the observation date.
Which states rely on local NEC adoption?
Arizona, Illinois, Kansas, Maryland, Mississippi, Missouri, and Nevada use materially local models for ordinary projects in the reviewed sources. Their matrix cells do not assign a statewide NEC edition.
That result is not missing research. It is the correct answer to a different governance structure. The design team must retrieve the city, county, or other local ordinance.
New York requires a split-authority check. New York City has its own electrical code based on the 2020 NEC with city amendments. That city edition should not be assigned to projects elsewhere in the state.
Alabama also needs careful scope handling. Its Division of Construction Management code applies to named public, educational, lodging, and theater projects. It does not govern most private residential and commercial property.
Statewide baseline does not mean identical local process
A statewide edition can coexist with local permit portals, local inspections, and approved amendments. California has a statewide California Electrical Code baseline. Cities and counties may file qualifying local amendments.
Delaware allows consistent local rules that are more stringent. Georgia has a state minimum and an amendment process. Wisconsin takes a different approach and limits more restrictive municipal electrical rules.
The project record should state both the edition and the authority model. Writing only “2023 NEC” hides who adopted it and whether local variation exists.
Tribal, federal, and special-jurisdiction projects need another check
The state matrix does not decide every site within state borders. Tribal jurisdictions, federal property, state-owned buildings, and special districts can follow separate authority paths.
Some states also reserve particular occupancies for a state agency. The ordinary city or county process may not apply. Resolve ownership, occupancy, and permitting authority before selecting the code basis.
How effective dates and transition rules change the answer
The effective date answers when an adoption became operative. It does not always identify which projects must use it. A transition clause may key the decision to application, permit, contract, installation, or accepted-plan dates.
New Hampshire ties its state building code to the building-permit application date. It also provides a six-month election between complete old and new code sets. The applicant cannot mix selected provisions from both.
Minnesota states that permits filed on or after August 17, 2026, use the 2026 NEC. Maine uses installations commencing on or after July 1, 2026. South Dakota refers to permits received on or after November 12, 2024.
Those phrases are not interchangeable. A team that records only the construction date can miss the controlling event.
Record these dates before design starts
Capture each relevant milestone:
- design authorization.
- signed construction contract.
- permit application submission.
- application completeness.
- plan acceptance.
- permit issuance.
- electrical permit filing.
- installation start.
- revision or resubmission date.
The AHJ may use only one milestone. The full sequence still helps explain a later revision or reviewer question.
Never mix editions without written authority
A transition rule may allow the complete earlier code or the complete newer code. It rarely supports choosing favorable clauses from each edition.
Use one stated code basis across the cover sheet, notes, calculations, diagrams, and equipment schedule. If the AHJ authorizes a mixed or special approach, retain that written direction.
Revisions can reopen the code question
A minor correction may remain under the original permit basis. A major redesign, expired permit, ownership change, or new application may not.
Ask the AHJ how it treats the actual revision. Do not infer the result from the original permit date. Save the answer with the resubmission record.
What NEC edition changes can affect a solar plan set?
The adopted edition can change terminology, scope, calculations, marking, and installation details. State and local amendments can alter the model text again.
The code basis should appear consistently across the solar permit package. An isolated cover-sheet note is not enough if the details were copied from another jurisdiction.
PV source and output circuit design
Article 690 is the main photovoltaic system article. Edition changes can affect circuit treatment, conductor decisions, disconnecting means, labels, and installation notes.
The designer should trace each code-dependent note to the selected edition. Manufacturer instructions and listing conditions remain separate inputs. A familiar detail from an older set is not evidence for the current project.
Rapid shutdown and array boundaries
Rapid-shutdown requirements have changed across code cycles. The selected equipment, array configuration, conductor routing, and initiation method must align with the enforced edition.
Review the dedicated rapid-shutdown compliance guide for the drawing coordination workflow. Then confirm the exact project requirement with the AHJ and equipment documentation.
Interconnection methods
Article 705 addresses interconnected electric power production sources. Edition choice can affect calculations, diagrams, markings, and the method shown at the service or distribution equipment.
The utility may use separate interconnection criteria. Coordinate both reviews without treating either authority as a substitute for the other.
Energy storage systems
Article 706 and other adopted fire, building, and product requirements can affect energy storage work. Battery location, disconnects, clearances, ventilation, and protection may involve more than the electrical code.
Use the solar storage plan-set guide to coordinate the package. Confirm which electrical, fire, and building editions the project authority enforces.
Grounding, bonding, and listed equipment
Grounding and bonding details should match the chosen code basis and the actual equipment. Racking, modules, inverters, and accessories also carry installation instructions and listing conditions.
Do not turn a general code note into a claim about an unverified equipment combination. The grounding and bonding guide explains where those decisions belong in the drawings.
Existing services and alterations
An addition to an existing electrical system can raise questions about the scope of required upgrades. The answer can depend on adopted alteration rules, project scope, and AHJ interpretation.
Show existing and proposed conditions clearly. Avoid implying that the entire building has been verified when the design scope covers only the solar connection.
How to verify the NEC edition for one solar project
A repeatable check is faster than resolving code conflicts after drafting. Run it during intake and record the evidence in one place.
1. Resolve the exact project authority
Start with the installation address and parcel. Postal city names can differ from municipal boundaries. Counties can cover unincorporated areas while cities run separate departments.
Identify the building permit authority, electrical inspection authority, fire reviewer, and utility. Note any state agency or special district with jurisdiction.
2. Find the official adoption instrument
Use the matrix source as the state starting point. Then locate the current statute, administrative rule, ordinance, or adopted-code page for the project authority.
Record the instrument title, edition, amendment package, effective date, and source URL. Save a dated copy or screenshot when the system permits it.
3. Identify the transition trigger
Read the effective and transition language. Determine whether application, permit, contract, installation, or another date controls the project.
Do not rely on a portal dropdown by itself. Portal choices can lag a rule change or serve several project types.
4. Check amendments and local interpretations
Retrieve state amendments and any valid local amendments. Search official bulletins, interpretations, and permit checklists for solar-specific direction.
Write each relevant change into the design basis. A hidden amendment has no value to the person checking the drawing.
5. Ask a narrow written question
When sources conflict, send the authority a question with the project facts. A useful request looks like this:
For the solar permit at [address], the state source shows [edition] effective [date]. The local portal shows [different edition]. Which NEC edition and amendment package should the plans cite for an application submitted on [date]? Please identify any transition rule that applies.
Retain the response, contact name, and date. A phone call can resolve urgency, but a written record is easier to audit.
6. Freeze the code basis for drafting
Add the verified edition and amendments to the project intake record. Reference that record in the drawing checklist.
The cover sheet, general notes, diagrams, calculations, and details should use the same basis. Remove inherited notes that cite another cycle.
7. Recheck before submission
Code adoptions can change during design. Recheck the source before the first submission and after a long hold.
Repeat the check for a resubmission if the permit expired or the scope changed. A matrix updated this quarter cannot answer a project-specific transition question by itself.
What should the code-basis handoff contain?
The researcher should give the designer a usable decision, not a folder of unsorted links. A short handoff keeps the source trail beside the drafting instructions.
Start with a one-sentence conclusion. Name the adopted electrical code and amendment package. State the project milestone that places the work under that code.
Follow the conclusion with the evidence. Link the state adoption instrument, local ordinance, and transition notice. Add the AHJ response when published sources did not settle the question.
End with drawing actions. Identify the sheets, notes, calculations, and details that need edition-specific review. State any open question and name its owner.
Example of a bounded handoff
Consider a hypothetical rooftop PV project in a city with a state baseline and valid local amendments. The electrical permit will be filed after a new edition takes effect.
A useful internal handoff follows.
Verified code basis: Use the state-adopted electrical code listed in the attached rule, together with the city’s filed amendments. The electrical permit filing date places this project under the new edition. The AHJ confirmed that active permits filed before the effective date remain under the previous edition. Review the rapid-shutdown diagram, interconnection calculations, grounding notes, and placards against the selected edition. The utility manual remains a separate design input.
This example does not supply an edition because the facts are fictional. Its value is the structure. It separates the conclusion, evidence, transition fact, local amendments, and drawing actions.
A weak handoff would say only, “Use the latest NEC.” That statement does not identify an adopted edition. It also hides the transition rule and local authority.
Assign ownership before work begins
Code research can fail when every person assumes another person completed it. Assign each step to a named role.
The permit coordinator usually resolves the address and permit authority. The code researcher retrieves the adoption instrument, amendments, and transition language. The electrical designer applies the verified basis to the package.
A qualified reviewer checks the interpretation and the project design. The project manager tracks unresolved questions and prevents submission while a critical answer remains open.
One person can hold several roles. The responsibilities should still remain distinct. A source collector should not silently convert an unclear rule into an engineering conclusion.
Mark evidence by confidence
Use simple labels that reveal what remains open:
- Verified primary: A current official source supports the edition and date.
- Verified with local confirmation: Official state evidence is complete, and local evidence resolves project application.
- Local model: The state source establishes local authority, but the project ordinance remains necessary.
- Partial: The current edition is verified, but an effective date or transition field remains open.
- Superseded: The source was valid for an older cycle and remains only for project history.
Do not use “verified” for a search snippet or third-party map. Those sources can locate an official record, but they cannot close the decision.
Keep the handoff synchronized with the drawings
Update the code-basis record when the AHJ answers a question or the project crosses a transition. Then identify every drawing affected by the change.
A note change may not be enough. Edition changes can affect calculations, equipment selection, diagrams, or labels. Route the revision through the electrical QA owner.
If sealed engineering documents are involved, confirm the professional-review boundary. The solar PE stamp guide explains why an AHJ requirement and state licensure rule answer different questions.
For inverter evidence, keep the adopted code separate from product certification and utility eligibility. The inverter compliance guide shows how those evidence paths fit together.
What evidence should the project record contain?
A defensible record shows how the team reached the code basis. It should let another reviewer repeat the decision without relying on memory.
| Record item | Minimum content | Why it matters |
|---|---|---|
| Jurisdiction resolution | Address, parcel, city or county, department | Establishes the authority path |
| Adoption source | Official URL, title, retrieval date | Supports the adopted edition |
| Edition statement | NEC year and adopted code name | Prevents ambiguous notes |
| Effective-date source | Rule or notice and operative date | Separates current from pending rules |
| Transition analysis | Controlling milestone and project date | Explains old-code or new-code treatment |
| Amendment package | State and valid local amendments | Captures changes to the model code |
| AHJ confirmation | Email, ticket, or meeting note | Resolves conflicts or unclear scope |
| Utility basis | Current manual or tariff reference | Keeps interconnection review separate |
| Drawing QA record | Sheets and details checked | Confirms consistent implementation |
| Freshness date | Last review and next recheck | Flags stale evidence |
Name the source, not just the website. A homepage may change without preserving the rule used for design.
The record should also identify uncertainty. For Alaska, Tennessee, and West Virginia, this research did not resolve the edition effective date. A project in those states needs that gap closed before the date basis is stated.
What if official sources disagree?
Conflicts usually come from timing, scope, or authority. Treat them as a research problem rather than choosing the newest-looking page.
Check the dates and document types
A final rule normally carries more authority than a newsletter. A current code page normally outranks an archived handout. A proposal does not displace an effective rule.
Compare publication date, effective date, revision date, and page status. Look for notices that distinguish new applications from active permits.
Check whether both sources cover the same project
One source may cover state-owned buildings. Another may cover private construction. A third may describe residential work only.
Alabama and Oklahoma demonstrate why scope labels matter. Never extend a limited state rule to every solar project.
Escalate the conflict to the enforcing authority
Send the conflicting links and project dates to the AHJ. Ask which source governs and request the applicable transition provision.
If the issue affects engineering judgment or professional responsibility, route it to the qualified reviewer. Do not settle it through copywriting or search-result consensus.
Document the resolution in the plans when useful
The cover sheet can name the adopted electrical code and amendment package. Project notes can identify an approved transition when that context prevents confusion.
Keep internal correspondence out of the public plan set unless it belongs there. Preserve the full evidence in the project record.
Common mistakes that lead to solar permit corrections
Code-basis errors spread across a package. Catching them before drafting protects more than the cover sheet.
Copying the edition from an old project
An earlier project may sit across a city boundary or permit transition. Its notes may also predate a state amendment.
Use the old set as a layout reference only. Rebuild the code basis for the new address.
Treating a national adoption map as legal authority
Industry maps help with discovery. Their summaries can be stale, simplified, or unable to show local exceptions.
Trace the answer to the official rule and local authority. Cite the source retained in the project file.
Assuming the newest NEC controls
NFPA publication is not adoption. Pending rulemaking is not an effective code. A state can remain several cycles behind the newest model edition.
Design to the verified legal basis. Separately address owner standards or specifications that require a newer practice.
Ignoring amendments
Writing “per NEC” leaves out the adopted jurisdictional code. State and local amendments can change the model provisions.
Name the adopted code and amendment package. Make the sheet notes specific enough for a reviewer to follow.
Confusing utility approval with permit compliance
The utility and AHJ can review different concerns. Each may require its own drawings, calculations, and forms.
Coordinate the two paths. Do not cite a utility acceptance as proof of code adoption.
Mixing code cycles in details
Templates can carry outdated labels, calculations, and rapid-shutdown notes. A correct cover sheet does not cure conflicting details.
Run a package-wide search for edition years and code references. Then inspect the electrical notes, SLD, labels, and equipment details.
Leaving the code check until submission
Late discovery can force equipment, calculation, and layout changes. It can also create inconsistent revisions across sheets.
Complete the check during intake. The AHJ rejection guide covers related coordination failures.
How to QA the electrical code basis in a plan set
Use a dedicated review pass after the electrical design is complete. The reviewer should work from the verified project record.
Check these locations:
- cover-sheet code summary.
- electrical general notes.
- single-line or three-line diagram.
- conductor and overcurrent calculations.
- service and interconnection details.
- rapid-shutdown diagram and labels.
- grounding and bonding details.
- equipment schedules.
- battery details, when present.
- placards and field-applied markings.
Search the complete package for four-digit years. This catches a hidden code edition in a copied note. Search for named articles and verify that each reference fits the adopted edition.
The review should also compare the permit plan set with the utility submission. Different purposes are acceptable. Contradictory equipment ratings or connection methods are not.
Use the plan-set contents guide to assign ownership for each check. The AHJ submission guide helps organize the final permit record.
How often should the state matrix be updated?
Review the full matrix at least every three months. Recheck fast-moving states whenever a final rule, council vote, or announced effective date approaches.
Project intake still needs a fresh check. A quarterly article cannot capture every local ordinance, bulletin, or permit transition.
A useful maintenance log records:
- jurisdiction;
- previous edition;
- new edition;
- final adoption source;
- effective date;
- transition language;
- amendment source;
- reviewer;
- review date;
- next scheduled check.
Do not overwrite unresolved history without noting the change. A project started under an earlier code may need the old evidence later.
Frequently asked questions
What NEC edition is currently enforced for solar?
The answer depends on the project jurisdiction and timing. State baselines ranged from the 2008 NEC to the 2026 NEC on September 26, 2026. Some states use local adoption rather than one statewide edition.
Does every city in a state use the same NEC edition?
No. Some states set a uniform baseline, while others preserve local adoption or amendment authority. Inspection and permit procedures can also vary under a statewide code.
Is the latest published NEC automatically required?
No. NFPA publication creates a model code, not state or local law. An authorized government must adopt the edition before it becomes the governing code.
Which date decides the NEC edition for a permit?
The adoption and transition rule decides. It may use the application, permit, contract, accepted-plan, or installation date. Ask the AHJ when the rule is unclear.
Can a project choose between two NEC editions?
Only when an applicable transition rule or authority permits that choice. The project should use the selected code set consistently and retain evidence for the election.
Can a solar designer rely on the permit portal dropdown?
The dropdown is useful evidence but not enough by itself. Confirm it against the official adoption source, amendments, and transition language.
Does the utility decide the NEC edition?
The utility can impose interconnection requirements. The permit authority determines the code basis within its jurisdiction. The two reviews may overlap without becoming interchangeable.
What should a solar plan set say about the code edition?
State the adopted electrical code, relevant amendment package, and any approved transition basis. Keep that information consistent across notes, diagrams, calculations, and details.
Why are three effective dates marked unresolved?
The official sources confirmed the current editions for Alaska, Tennessee, and West Virginia. The reviewed pages did not establish the edition adoption effective dates. Project research must close that gap.
Does this matrix prove that a permit will be accepted?
No. It provides a dated research starting point. Acceptance depends on the project, AHJ, complete adopted codes, amendments, documentation, and reviewer findings.
Use the matrix as intake evidence, not design approval
The safest code answer has six parts: address, authority, edition, effective date, amendments, and transition rule. Missing one part can make a correct-looking plan set wrong for the permit.
Heaven Designs prepares coordinated solar permit design packages within the agreed scope. United States projects still require confirmation of filing, professional-seal, and regulatory-review responsibilities.
If your team needs a coordinated drawing package, share the project address, AHJ, and verified code basis. A qualified United States electrical-code reviewer must confirm project-specific requirements before submission.