An electrical contractor installs the same commercial system, to the same drawings, using the same methods, in two jurisdictions. One passes. The other gets a correction notice.
The instinctive reading is that one inspector is wrong. Usually neither is. What has happened is that two authorities having jurisdiction have applied different interpretations to code text that permits more than one reasonable reading — and both interpretations are enforceable, because the code grants the AHJ the authority to interpret it.
This is one of the most persistent frustrations in multi-market commercial electrical work, and it is also one of the most manageable, once you understand where the spread comes from and which categories of installation it affects most.
Key takeaways Interpretation spread is structural, not accidental. The NEC uses discretionary language — approved, acceptable to the authority having jurisdiction, suitable for the purpose — that intentionally delegates judgment to the AHJ. The widest spread appears in grounding and bonding, working clearances, support and routing methods, and specialty systems like PV, energy storage, and emergency power. AHJs communicate interpretations through four channels of decreasing reliability: published bulletins, website FAQs, plan-check comments, and verbal direction at inspection. The documentation strategies that hold up across interpretations are written confirmation of verbal rulings, explicit code citations in submittals, pre-submittal meetings, and photographic records before cover. |
Why Does the Same Code Text Produce Different Answers?
Because the NEC is written as a hybrid of prescriptive rules and performance requirements, and the performance requirements use discretionary language that explicitly delegates judgment to the authority having jurisdiction. Different AHJs exercising that delegated judgment reach different conclusions in good faith.
There are three structural reasons the spread exists, and none of them is inspector error.
The code delegates judgment on purpose
Substantial portions of the NEC use language that requires an authority to make a determination rather than apply a fixed rule. Terms that require something be approved, or acceptable to the authority having jurisdiction, or suitable for the conditions, are not vague drafting. They are deliberate delegation, recognizing that the code cannot anticipate every field condition and that local officials are better positioned to evaluate specific installations. That delegation is exactly where interpretation spread originates.
Local amendments modify the base text
Even where the base code is prescriptive, local amendments can modify the requirement — and amendments cluster in a predictable set of areas. Two jurisdictions on the same NEC edition can have materially different requirements because of what each attached at adoption.
Interpretive practice accumulates locally
Inspectors build interpretive practice through experience with local conditions, local construction methods, and local failure history. A jurisdiction that has dealt with a specific failure mode will often interpret related provisions more conservatively than one that has not. This is institutional learning, and it is reasonable — but it means the same text produces different practical requirements in different places.
Interpretation spread is not a defect in the code. It is a feature the code is built around, and it is enforceable everywhere it appears.
Which Commercial Installs Show the Widest Interpretation Spread?
Grounding and bonding, working clearances and dedicated equipment space, support and routing methods, and specialty systems — photovoltaic, energy storage, EV charging, and emergency and standby power — consistently show the widest spread across jurisdictions.
Grounding and bonding
Consistently the widest spread in commercial electrical work. Grounding electrode system composition, supplemental electrode requirements, bonding of structural steel and metallic piping systems, and the treatment of separately derived systems all involve field judgment about local conditions. Because soil resistivity, water system materials, and building construction methods vary so much geographically, jurisdictions develop meaningfully different expectations about what constitutes an adequate grounding system.
Working clearances and dedicated equipment space
Requirements for clear working space around electrical equipment and for the dedicated space above and around switchgear generate frequent disagreement — not about the dimensions, which are prescriptive, but about what constitutes an encroachment, how the space is measured in irregular rooms, and what other building systems may or may not pass through the dedicated space. Coordination conflicts with mechanical and plumbing routing make this a recurring plan-check comment in nearly every market.
Support, routing, and securement methods
Cable tray fill and support intervals, raceway support methods, and securement of conductors in accessible spaces involve judgment about what constitutes adequate support for the specific installation condition. Different jurisdictions accept different support hardware and different intervals for comparable conditions.
Photovoltaic, energy storage, and interconnection
These systems combine rapidly evolving code provisions, strong fire service opinions about access and shutdown, and utility interconnection requirements that operate outside the electrical code entirely. The result is the widest spread of any specialty category. Rapid shutdown implementation, labeling requirements, equipment location, and access clearances all vary substantially.
EV charging infrastructure
Load calculation methodology, treatment of energy management systems, and requirements for future capacity infrastructure vary widely — partly through electrical code amendment and partly through building policy adopted outside the electrical code, which contractors do not always think to check.
Emergency, legally required standby, and optional standby systems
Separation requirements between emergency and normal power circuits, transfer equipment arrangements, and circuit integrity and survivability requirements generate substantial interpretation spread, often coordinated with local fire code amendments that the electrical contractor may not have reviewed.
Install Category | Why the Spread Is Wide |
Grounding and bonding | Local soil, water system materials, and construction methods drive divergent expectations |
Working clearance / dedicated space | Dimensions are prescriptive; encroachment and measurement are judgment calls |
Support and routing methods | Adequacy of support for a specific condition is inherently discretionary |
PV, storage, and interconnection | Fast-moving code plus fire service preferences plus utility standards outside the NEC |
EV charging | Load calc methodology plus building policy adopted outside the electrical code |
Emergency and standby power | Separation and survivability coordinate with locally amended fire code |
How Do AHJs Communicate Interpretation Differences?
Through four channels of decreasing reliability and increasing project-specificity: published bulletins and policy memos, website FAQs, plan-check comments, and verbal direction at inspection. Only the first two are visible before you submit.
Published bulletins and policy memos — most reliable, least common
Some jurisdictions maintain a formal archive of interpretation bulletins that document how the department reads specific provisions. Where these exist they are the single best resource available, because they are written, dated, attributable, and visible before you design. Ask whether they exist. Many contractors never do.
Website FAQ and handout documents — moderately reliable
Building department websites frequently carry handouts, submittal checklists, and FAQ pages that encode interpretive expectations without labeling them as interpretations. A commercial electrical submittal checklist that asks for something the code does not explicitly require is telling you about a local interpretation. These documents are underused by contractors, who tend to read them as administrative rather than as substantive.
Plan-check comments — most common, project-specific
The dominant channel. Most interpretation communication happens through plan review comments on a specific submittal, which means the interpretation only becomes visible after you have submitted and only for the specific condition flagged. This is why the same organization can work in a jurisdiction for years and still encounter new interpretations — the comments are project-triggered.
Verbal direction at inspection — least reliable, hardest to defend
The weakest channel from a documentation standpoint. A verbal ruling at inspection is enforceable in the moment but leaves no record, cannot be relied on for future projects, and does not survive an inspector change. If the only place an interpretation exists is in a conversation on a job site, it effectively does not exist for any purpose other than that inspection.
The single highest-value habit When you receive a verbal interpretation at inspection or over the phone, send a short confirming email the same day: here is what I understood, here is how we intend to proceed, please correct me if I have this wrong. Silence is not agreement, but a dated email in the file is a far stronger position than a recollection — and it converts a one-inspector ruling into an organizational record. |
What Documentation Strategies Hold Up Across Multiple Interpretations?
Four practices hold up consistently: written confirmation of every verbal ruling, explicit code citations in submittals, requesting a pre-submittal meeting on unusual scope, and photographic documentation before anything is concealed.
- Confirm verbal rulings in writing. Confirm verbal rulings in writing, same day. A short email restating the interpretation and the intended approach. This converts an unrecorded conversation into a project record and gives the AHJ an opportunity to correct a misunderstanding before it becomes installed work.
- Cite the code section in submittals. Cite the code section in your submittals. When a design approach relies on a specific code provision or an exception, cite it explicitly in the submittal rather than leaving the plan reviewer to infer your reasoning. This shifts the conversation from what did you do to here is the basis, and it substantially reduces plan-check comment volume on discretionary provisions.
- Request a pre-submittal meeting. Request a pre-submittal or pre-construction meeting on unusual scope. For specialty systems or unusual conditions, many jurisdictions will meet before submittal to discuss approach. This surfaces interpretation differences at the cheapest possible moment — before design is complete and before anything is installed.
- Photograph before cover. Photograph before cover. Comprehensive photographic documentation of grounding connections, support methods, and concealed routing before anything is closed up is the only defense available when an interpretation question arises after concealment. It is also the fastest way to resolve a question without opening work.
- Maintain an interpretation library. Maintain a jurisdiction interpretation library. Every interpretation your organization receives, in any jurisdiction, should be recorded somewhere that the next project manager in that jurisdiction will find it. Most contractors do not do this, which is why the same organization re-learns the same interpretation repeatedly.
What This Means Across a Portfolio
Interpretation knowledge is the most valuable and most poorly retained asset in multi-jurisdiction electrical contracting. A project manager who has run four jobs in a jurisdiction knows how that jurisdiction reads the ambiguous provisions. That knowledge is worth real money in avoided rework and avoided plan-check cycles.
And in most organizations, it lives entirely in that project manager’s head. When they move to a different market, or leave, the organization pays to learn it again.
The organizations that handle this well do something structurally simple: they make interpretation capture part of the permit process rather than a separate documentation task, and they store it against the jurisdiction rather than against the project. That way the next job in that market starts from what was already learned.
Where Permie fits Permie tracks permits by jurisdiction and by project manager across your entire portfolio — so the record of what happened in each market stays with the jurisdiction rather than disappearing when a PM changes roles. For contractors working across multiple AHJs with different interpretive practices, that continuity is the difference between institutional knowledge and repeated re-learning. 14-day free trial. No contract. Start at permie.app or book a strategy call at calendly.com/mistro/strategy-session. |
Frequently Asked Questions
Can two cities enforce the same NEC section differently?
Yes, and both can be correct. The NEC uses discretionary language in many provisions that explicitly delegates judgment to the authority having jurisdiction. Where the code requires that something be approved or acceptable to the AHJ, different authorities reaching different conclusions are both exercising authority the code grants them.
Which electrical installations vary most between jurisdictions?
Grounding and bonding shows the widest spread, followed by working clearance and dedicated equipment space questions, support and routing methods, and specialty systems including photovoltaic, energy storage, EV charging, and emergency and standby power.
How do I find out how a specific AHJ interprets a code provision?
Ask whether the jurisdiction publishes interpretation bulletins or policy memos, which is the most reliable source where it exists. Review submittal checklists and department handouts, which often encode interpretations without labeling them. For unusual scope, request a pre-submittal meeting before design is complete.
Is a verbal approval from an inspector binding?
It governs that inspection, but it leaves no record and does not reliably carry to future projects or survive an inspector change. The practical approach is to send a same-day email confirming your understanding of any verbal ruling, which creates a dated record and gives the AHJ a chance to correct a misunderstanding before work proceeds.
How can a contractor reduce plan-check comments on discretionary provisions?
Cite the specific code section or exception your approach relies on directly in the submittal rather than leaving the reviewer to infer the basis. Reviewers issue fewer comments when the reasoning is stated explicitly, because the question shifts from what did you do to whether the stated basis is acceptable.