NEC 90.14: exceptions explained

What Article 90 says about exceptions

Article 90 is the foundation of the NEC. It defines scope, enforcement, and how the Code is structured. Exceptions are part of that structure, called out in NEC 90.5(B), which treats them as permissive rules that modify a mandatory requirement in specific situations.

An exception is not a loophole. It is a conditional allowance written into the Code by the CMP because the base rule does not fit every real-world installation. If the conditions of the exception are met, the exception controls. If even one condition fails, the main rule applies.

Read the parent rule first. Then read the exception. Then read it again. Most violations tagged to exceptions come from electricians applying the exception without verifying the parent rule still governs the rest of the installation.

How exceptions are formatted

Exceptions appear directly below the rule they modify. They are indented, printed in italics, and numbered when more than one applies. Per NEC 90.5(C), informational notes and explanatory material do not carry the same weight as exceptions, so do not confuse the two.

Some exceptions are narrow, addressing a single conductor type or a single occupancy. Others are broad, covering entire categories of equipment. The language is precise. Words like "listed," "identified," "readily accessible," and "supervised" are defined in Article 100, and those definitions control how the exception is applied.

• No. 1 Exceptions: numbered when multiple exceptions modify the same rule.
• Conditional phrases: "where," "provided that," and "if" signal the trigger.
• Italicized text: visual cue that you are reading permissive language, not a new rule.
• Scope limits: exceptions apply only to the rule they follow, not to the whole section.

Common exception patterns in the field

Certain exceptions come up constantly on service calls and rough-ins. GFCI requirements under NEC 210.8(A) carry exceptions for specific refrigeration and fire alarm circuits. AFCI requirements in NEC 210.12(A) have exceptions for certain extensions and branch-circuit replacements. Working space rules in NEC 110.26(A) include exceptions for existing installations and assemblies rated under 1.2 meters.

Box fill in NEC 314.16 has exceptions for conductors that pass through without splicing. Bonding and grounding in NEC 250 is full of exceptions covering isolated grounds, separately derived systems, and equipment bonding jumpers. Know the ones in your daily work cold.

Tip from a journeyman: highlight the exceptions in your code book in a different color than the main rules. When an inspector asks why you ran it that way, you can cite the exception by number without flipping back and forth.

Applying exceptions on the job

Before you rely on an exception, confirm three things. First, the exception exists in the edition of the NEC adopted by the jurisdiction, not the edition you happen to own. Adoption dates vary by state and city. Second, every condition inside the exception is satisfied, not just the convenient ones. Third, the AHJ agrees with your reading, because NEC 90.4 gives the authority having jurisdiction the final call on interpretation.

Document your reasoning. Write the section, the exception number, and the conditions on your as-builts or in your change order notes. If the job gets re-inspected two years later by a different inspector, your written trail is the difference between a passed inspection and a tear-out.

1. Identify the parent rule you are working under.
2. Check whether an exception applies to your exact condition.
3. Verify every condition of the exception is met.
4. Confirm the local code amendment has not deleted the exception.
5. Document the citation on the job record.

Pitfalls and misreads

The most common mistake is stacking exceptions. An exception to one section does not carry into another. If NEC 210.52 has an exception for a specific room type, that exception does not also modify NEC 210.8 GFCI requirements. Each section stands on its own.

Another trap is treating an Informational Note as permission. Informational Notes, per NEC 90.5(C), are explanatory only. They are not enforceable. If the note says "see also" or "for additional information," that is guidance, not an allowance.

Local amendments also delete or modify exceptions regularly. Chicago, New York City, and several California jurisdictions strike specific exceptions from the adopted code. Always check the local amendment list before citing an exception on a permitted job.

Inspector's reminder: "I cannot approve an exception you cannot prove. If you cite 210.8(B) Exception No. 2, I need to see that the receptacle is not readily accessible and that it serves only the equipment listed. Show me both."

Quick reference for the truck

Keep a short list taped inside your code book cover of the exceptions you use most. For residential, that usually means GFCI, AFCI, and box fill. For commercial, working space, grounding, and conductor ampacity adjustments. For industrial, supervised installations and engineered solutions under NEC 90.4(C).

When in doubt, call the exception out before the rough-in inspection rather than after. A two-minute conversation with the inspector beats a week of rework. Article 90 sets the rules for how the Code is read, and exceptions are the Code's own way of telling you where flexibility lives.