NEC 90.13: exceptions explained

Exceptions in the NEC aren't loopholes. They're narrow carve-outs written into the code to handle situations where the main rule would be impractical, unnecessary, or unsafe. If you work off the main rule without checking for an exception, you either overbuild or miss a legitimate compliant path. If you lean on exceptions without reading them word for word, you fail inspection.

This post breaks down how exceptions are structured, how they interact with the main rule, and where electricians most often misread them in the field.

What an exception actually is

Per NEC 90.5(B), exceptions to requirements are permissive departures from the rule that immediately precedes them. They're printed in italics to make them easy to spot. An exception only modifies the specific paragraph, subsection, or list item it follows. It does not float across the whole section.

That scope matters. If 210.8(A) has three exceptions, each one attaches to the parent rule of 210.8(A). They don't modify 210.8(B) or 210.8(F). Read the hierarchy before you apply.

Field tip: before citing an exception to an inspector, trace it back up the page. Identify exactly which rule it hangs under. If you can't point to the parent paragraph, you're not ready to defend the install.

How to read an exception in the field

Every exception has conditions. Miss one condition and the exception doesn't apply. The conditions usually include equipment type, location, ampacity, voltage class, or a physical barrier like a listed cover. Read them as an AND list, not an OR list, unless the code explicitly says "or."

Work through an exception like this:

1. Read the main rule in full. Know what you'd have to do without the exception.
2. Read the exception word for word. Underline every qualifier.
3. Confirm the install meets every qualifier, not just the obvious one.
4. Check if the exception references another article (for example, "installed per 250.30"). Go read that article too.
5. Document it on the drawing or in your notes. Cite article, section, and exception number.

Exceptions numbered 1, 2, 3 are independent. You can use any one that fits. You do not have to satisfy all of them.

Where exceptions trip electricians up

A handful of sections generate repeat questions on jobs. Know these cold.

NEC 210.8 GFCI requirements. The main rule requires GFCI protection for nearly all 125V through 250V receptacles in listed locations. Exceptions used to exist for things like dedicated appliance circuits in garages and basements. Most of those exceptions have been removed in recent cycles. If you're working from memory based on the 2014 or 2017 NEC, you will miss GFCI requirements that are now mandatory. Pull the edition your AHJ enforces.

NEC 250.32 grounding at separate structures. The main rule requires a grounding electrode conductor and supplementary electrode at detached structures fed by a feeder. The exception for a single branch circuit with an equipment grounding conductor is narrow, and inspectors will check the feeder vs. branch circuit distinction.

NEC 300.4 protection of cables and raceways. Multiple exceptions govern when a nail plate, bored hole distance, or RMC sleeve is required. The exception language depends on the wiring method, so NM cable exceptions don't automatically extend to MC.

NEC 404.2(C) grounded conductor at switch locations. The exceptions allow omission of the neutral in specific retrofit and raceway conditions. New construction rarely qualifies.

Exceptions, permissive rules, and informational notes

These three look similar on the page but carry different weight. NEC 90.5 separates them.

• Mandatory rules. Use "shall" or "shall not." Enforceable.
• Permissive rules. Use "shall be permitted." Optional compliant methods. Not exceptions.
• Exceptions. Italicized. Modify the preceding mandatory rule when conditions are met.
• Informational notes. Explanatory. Not enforceable. Do not cite them as permission to deviate.

If an inspector says "that's an informational note, not a rule," they're right. Informational notes point you to related articles or give context. They grant nothing.

Documenting exception use

When you rely on an exception, write it down. On commercial work, note the exception on the as-built or in the inspection request. On service calls, note it on the invoice or jobsheet. Two reasons: it protects you if the install is questioned later, and it forces you to actually verify the exception applies before the drywall goes up.

Field tip: if you can't write the full citation (article, section, exception number, and the conditions you meet) in one sentence, you don't understand the exception well enough to install from it. Stop and read it again.

Exceptions are one of the most useful tools in the NEC when you read them carefully, and one of the fastest ways to fail inspection when you don't. Treat them with the same discipline as the main rule. Read the parent paragraph, read every qualifier, confirm each condition, and cite the full path when you submit the work.