Code navigation wrapper
Why you care (60 seconds)
Knowing where scope and definitions live prevents bad assumptions. Most errors start with skipping the front of an article or missing a definition that changes how a rule applies.
Where people lose time
- Starting in the middle of an article without reading scope notes.
- Missing definitions that change the meaning of a term.
- Treating informational notes as requirements.
This is
The rule in plain language
A process for finding the right rule, its scope, and its defined terms before making a decision.
When it applies
Every time you touch a requirement that relies on a defined term or references another article.
What you must do (checklist)
- Confirm the scope article before diving into details.
- Read all defined terms used in the requirement.
- Track cross-references that narrow or expand scope.
Quick examples
- Look up what a term means before using it in calculations.
- Verify that a rule applies to the equipment type you are sizing.
This is not
Common misreads
- Assuming a common industry term matches the code definition.
- Ignoring a definition because the word feels obvious.
What it doesn't cover
- The full technical content of each article.
- Local amendments or AHJ preferences.
False friends
- Terms that look the same but have a narrower code meaning.
Exceptions & edge cases
- Some articles define terms only for that article. Do not generalize them.
- Informational notes can be helpful, but they are not enforceable rules.
Cross-references (NEC map)
- Primary: 90, 100
Exam traps
- Questions that hinge on a definition rather than a calculation.
- Picking an answer that ignores scope limitations.
Field notes
- Keep a running list of definitions you look up often.
- Flag rules that reference other articles and follow the trail.
AHJ / Local amendments notes (placeholder)
- Add local amendments or interpretations here.
Revision notes
- Draft wrapper created for navigation fundamentals.