NEC 90.21: after 2023

NEC 90.21 is short, but it changes how you read every other section of the Code. If you're working off a 2023 or 2026 NEC adoption, you need to know what 90.21 says now and how it bumps against the rest of Article 90.

What 90.21 Actually Says

Section 90.21 is titled "Format and Language." It was added to the 2023 NEC to formally describe how the Code is written: the use of mandatory rules (shall), permissive rules (shall be permitted), explanatory material (Informational Notes), and the structural hierarchy of articles, parts, sections, and list items.

Before 2023, this kind of guidance was scattered across 90.5 and the style manual. Now it lives in one place. The practical effect: when an inspector points at a list item under a subsection, 90.21 backs the idea that every level of the hierarchy carries equal enforceable weight unless the text says otherwise.

Pair 90.21 with 90.5 (Mandatory Rules, Permissive Rules, and Explanatory Material) when you're arguing intent. 90.5 tells you which words are enforceable. 90.21 tells you how the document is structured around those words.

Why the 2023 Reorganization Matters on the Job

The 2023 cycle reshuffled Article 90 to align with the NFPA Manual of Style. Old 90.3 (Code Arrangement) became 90.4. Old 90.4 (Enforcement) became 90.6. The Informative Annexes were reordered. If you're cross referencing an older code book against a 2023 or 2026 install, the section numbers will not match.

This matters most when you're citing code on a permit correction or a punch list. A note that says "see 90.4" written against a 2020 book points to enforcement. The same note against a 2023 book points to code arrangement. Verify which cycle your AHJ has adopted before you write anything down.

Field tip: keep the adopted cycle written on the inside cover of your code book. Most state amendments are posted on the AHJ website. If you're working across state lines in a week, that one note saves you from quoting the wrong section to the wrong inspector.

Hierarchy and How to Read a Citation

90.21 formalizes the levels you've been reading for years. From broadest to narrowest: Chapter, Article, Part, Section, Subsection, List Item. A citation like 210.8(A)(7) means Article 210, Section 8, Subsection A, List Item 7. Every level is enforceable.

The first level subdivision under a section uses uppercase letters in parentheses. The second level uses numbers in parentheses. The third uses lowercase letters. When you see something like 250.122(B), you're at subsection B of Section 122 in Article 250, which covers increased size of equipment grounding conductors.

• Chapter: broad subject area, e.g., Chapter 2 (Wiring and Protection)
• Article: specific topic, e.g., Article 210 (Branch Circuits)
• Part: groups sections within long articles, e.g., Part II of 210
• Section: the rule itself, e.g., 210.8
• Subsection and list items: conditions, exceptions, and locations

Mandatory vs. Permissive Language

Read 90.21 alongside 90.5(A) and 90.5(B). "Shall" and "shall not" are mandatory. "Shall be permitted" and "shall not be required" are permissive. Informational Notes are not enforceable, ever. Exceptions modify the main rule and are equally enforceable when their conditions are met.

This trips people up on GFCI and AFCI rules. 210.8(A) says GFCI protection "shall be provided" in specified locations. The list items under it are the locations. If your install is in one of those listed locations, GFCI is mandatory, full stop. The Informational Notes after the list explain intent but do not add or remove requirements.

Field tip: if an inspector cites an Informational Note as the reason for a fail, ask them to point at the mandatory section the note is attached to. The note itself cannot be the violation.

Enforcement Crossover with 90.4 and 90.6

90.21 describes the language. 90.4 (in the 2023 cycle) describes how the Code is arranged. 90.6 gives the AHJ authority to interpret rules, grant special permission, and waive specific requirements when equivalent objectives can be achieved. These three sections work together.

If you're proposing an alternate method, 90.6 is your section. But you'll cite 90.21 to argue that the rule you're working around is in fact a list item under a permissive subsection, not a hard mandatory rule. Knowing the structure lets you frame the request correctly.

1. Identify the section by hierarchy (90.21 framework)
2. Confirm whether the language is mandatory or permissive (90.5)
3. Check exceptions and Informational Notes attached to the rule
4. If you need a deviation, request special permission under 90.6

Practical Takeaways for the 2023 and 2026 Cycles

The 2026 NEC keeps 90.21 essentially intact. Minor editorial changes are expected, but the structure described in 90.21 is now the baseline for every future cycle. Get comfortable with it once and you're set.

On the job, 90.21 is the section you cite when someone misreads the Code. It's the answer to "where does it say that's enforceable?" or "is that exception talking about my install?" Knowing the format means you can read any unfamiliar article fast and trust what you're reading.

Keep a 2023 or 2026 NEC handbook within reach, confirm your AHJ's adopted cycle, and read citations from the outside in: Article, Section, Subsection, List Item. That habit alone catches most of the common misreads on inspection day.