NEC 90.22: plain language explanation

What NEC 90.22 Actually Covers

NEC 90.22 is short, and most electricians never read it. It points to the formal interpretation process that the NFPA uses to clarify ambiguous or disputed code language. It is not about how to wire anything. It is about how the rulebook itself gets clarified when two qualified people read the same article and walk away with different answers.

The article references the NFPA Regulations Governing Committee Projects. That document spells out who can request a formal interpretation, what gets published, and how those rulings are tracked. Formal interpretations are published in NFPA News and become part of the historical record for that code cycle.

For a working electrician, the takeaway is simple. When the code is unclear and the AHJ and contractor cannot agree, there is an official channel above the local inspector that can issue a binding clarification.

Formal vs. Informal Interpretations

Most code disputes on a jobsite get resolved informally. The inspector reads the article, the contractor reads it, the engineer of record weighs in, and someone makes a call. That is an informal interpretation. It governs that one job, that one inspector, that one project. It does not bind the next inspector down the road.

A formal interpretation under 90.22 is different. It comes from the NFPA technical committee that owns the article in question. It applies broadly, gets published, and carries weight in any jurisdiction that adopts that edition of the NEC. If your dispute is going to repeat itself across many projects, a formal interpretation has more leverage than a one-off ruling.

Field tip: 95 percent of code arguments end at the AHJ. Do not chase a formal interpretation over a single receptacle dispute. Save that process for the patterns that keep biting you across multiple jobs.

When a Formal Interpretation Is Worth Pursuing

Formal interpretations are slow. They go through committee review, can take months, and apply to a specific code edition. By the time you get an answer, the job may already be closed out. So pick your battles.

Situations where the process actually pays off:

• Recurring disputes between contractors and AHJs in your region over the same article (for example, GFCI scope under NEC 210.8 or working space under NEC 110.26).
• Engineering or design firms that need a definitive ruling before standardizing a detail across many projects.
• Manufacturers needing clarity on whether their product complies with a listing or installation requirement.
• Major commercial or industrial work where rework costs justify the wait.

For a service call or a single house, you will solve it faster by talking to the inspector, citing the article, and moving on.

How the Process Works

The formal interpretation request goes to NFPA, not to your local building department. The request must be specific. You name the code edition, the exact section (for example, NEC 250.122(B)), and frame the question so it can be answered yes or no, or with a clear narrative. Vague questions get rejected.

Once submitted, the relevant Code Making Panel reviews the request. There are three categories of formal interpretation:

1. Interpretations on the meaning of a specific provision.
2. Interpretations on the intent of the committee when the language was written.
3. Interpretations on the applicability of a section to a specific situation.

The committee votes. If the response gets the required majority, it becomes an official formal interpretation. If not, the request fails and you are back to working with your AHJ.

Formal Interpretations vs. TIAs and Code Changes

Do not confuse 90.22 formal interpretations with Tentative Interim Amendments (TIAs) or full code revisions. A TIA changes the code text mid-cycle, usually to fix a safety issue or correct an error. A formal interpretation does not change any text. It only clarifies what the existing text already means.

If the code language is genuinely broken or unsafe, a TIA or a public input for the next cycle is the right path. If the language is technically correct but reads two different ways depending on who is holding the book, that is what 90.22 exists for.

Field tip: when you submit a public input for the next code cycle, attach photos and one-line examples from real installations. Committees respond to concrete field problems, not abstract complaints.

What This Means on the Job

Day to day, 90.22 will not change how you bend pipe or terminate conductors. It is in the back of the book for a reason. But when you hit a wall with an inspector and you are convinced the code language supports your install, knowing the formal interpretation process exists changes how you negotiate.

You can ask: has this article ever been the subject of a formal interpretation? Searching NFPA News for the article number sometimes turns up an existing ruling that settles the question on the spot. If one exists, print it and bring it to the next inspection.

Beyond that, 90.22 is a reminder that the NEC is a living document maintained by people. When the language fails you, there are channels. Use them on the patterns, not the one-offs, and you will get the right kind of mileage out of the process.