NEC 90.15: code citations

What 90.15 Covers

Section 90.15 addresses how the NEC organizes and presents its citations. Every rule in the Code lives inside a strict hierarchy, and 90.15 tells you how to read that hierarchy correctly. Miss a subdivision letter or a parenthetical number and you are citing the wrong rule.

The practical value is simple. When an inspector cites 210.8(A)(7), you need to know exactly what scope that citation covers, what exceptions apply, and whether an Informational Note is tagging along. 90.15 sets the ground rules for that reading.

How NEC Citations Are Structured

Every NEC citation follows the same pattern. Chapter, then Article, then Section, then subdivisions. The Code is broken into nine chapters, and each chapter contains numbered Articles. Articles are divided into Parts (I, II, III, etc.), and Parts contain numbered Sections.

A citation like 210.8(A)(7)(a) breaks down this way. Article 210 (Branch Circuits), Section 210.8 (GFCI Protection for Personnel), first-level subdivision (A) (Dwelling Units), second-level subdivision (7) (Sinks), third-level subdivision (a). Each level narrows the scope.

• Chapter: broad topic grouping (Chapter 2 covers wiring and protection)
• Article: specific subject (Article 250 covers grounding and bonding)
• Section: a numbered rule within the article
• Subdivisions: (A), (1), (a), (i) drill down further

Reading Subdivisions and Exceptions

Subdivisions matter. A rule that applies under 210.52(C)(1) does not automatically apply under 210.52(C)(2). Each subdivision is its own enforceable requirement. Inspectors cite to the deepest applicable level, and you should too.

Exceptions are numbered directly under the rule they modify. If you see "Exception No. 2 to 250.118(6)," that exception only modifies 250.118(6), not the rest of 250.118. Exceptions are narrow by design. Do not stretch them.

Field tip: when an inspector red-tags you and cites a section without the subdivision, ask for the full citation before you start tearing out work. A vague cite often means they are not sure which subdivision applies.

Mandatory vs Permissive vs Explanatory

Per 90.5, the Code uses three types of language, and 90.15 reinforces how to identify them in citations. "Shall" is mandatory. "Shall be permitted" or "shall not be required" is permissive. Explanatory material appears in Informational Notes and is not enforceable.

Informational Notes are numbered (Informational Note No. 1, No. 2) and sit directly below the rule they inform. They often point to NFPA 70E, UL standards, or other NEC sections. Useful context, but not enforceable as Code. If an inspector cites an Informational Note as the violation, push back.

• Shall: required, no wiggle room
• Shall be permitted: allowed but not required
• Informational Note: reference only, not enforceable
• Exception: a narrow carve-out from the main rule

Citing Code in the Field

On permits, plan reviews, and inspection appeals, write citations the same way the Code does. Full section with subdivisions, and the NEC edition year if the jurisdiction is running a specific cycle. Example: "2023 NEC 210.8(F)" is unambiguous. "210.8" is not.

Jurisdictions adopt NEC editions on different schedules. A city on 2020 NEC does not enforce 2023 changes. Before you cite, verify the adopted edition with the AHJ. Article and section numbers have shifted between editions, and what was 210.8(A)(10) in one cycle may be 210.8(A)(11) in another.

Field tip: keep the adopted NEC edition written on the inside cover of your code book or pinned in your app. When you argue a citation on a jobsite, edition year is the first thing the AHJ will ask.

Navigating Tables and Annexes

Tables are cited by their section number. Table 310.16 lives under Section 310.16. The table carries the same enforceable weight as the section text, including any notes printed directly under the table. Those notes are mandatory, not informational.

Annexes A through J sit at the back of the Code. Per 90.3, Annexes are not part of the enforceable Code unless the AHJ specifically adopts them. Annex C (conduit fill tables) is commonly referenced, but it is a calculation aid, not a rule. The enforceable rule for conduit fill is in Chapter 9, Table 1.

Quick Reference Checklist

Before you cite or accept a citation, run through this list. It takes ten seconds and saves callbacks.

1. Confirm the adopted NEC edition with the AHJ
2. Read the full citation including all subdivisions
3. Check for exceptions directly below the cited rule
4. Verify mandatory language ("shall") vs permissive ("shall be permitted")
5. Distinguish the rule from any Informational Notes
6. If a table is cited, read the notes printed under the table

Clean citations win arguments on the jobsite. Sloppy ones cost you time and material. 90.15 is short, but it sets the foundation for every other reference in the Code.