A system can be NEC-compliant and still be inconvenient, inefficient, or poorly prepared for future loads. That distinction - between minimum safety compliance and complete engineering design - is one of the most useful lessons in Article 90, and it is the subject of Part 3.
Plain-English Highlights
90.2(B) Practical Safeguarding establishes the NEC's core purpose: practical protection of people and property from electrical hazards. But the NEC is not intended to be a design specification or an instruction manual for untrained persons. 90.2(C) Adequacy makes another important distinction: compliance with the Code, combined with proper maintenance, should result in an installation essentially free from electrical hazards - that does not automatically mean the installation is efficient, convenient, adequate for good service, or sized for future expansion.
The related informational note highlights a real design issue: insufficient initial wiring can lead to overloaded systems as electrical usage grows, which is especially relevant in MEP coordination - a mechanical equipment schedule may satisfy today's connected load, but future tenant equipment, added HVAC capacity, controls, heat tracing, pumps, EV charging, or other loads can change the electrical demand, so NEC minimum does not equal a complete engineering strategy.
90.2(D) Relation to Other International Standards recognizes IEC 60364-1 as addressing fundamental electrical-safety principles similar to those contained in the NEC.
Why It Matters
Plan review should distinguish between two related but different questions: is the installation safe and compliant, and will it also function reliably, accommodate the intended equipment, remain maintainable, and reasonably address known future needs? Compliance with a general provision answers the first question. It does not automatically answer the second.
Where To Show It
E-001: design criteria and electrical basis. E-701: distribution architecture and planned capacity. Panel schedules: connected loads and available spaces. MEP schedules: coordinated voltage, phase, MCA/MOCP, and equipment loads.
Do
Treat the NEC as a safety baseline, not a complete design standard. - Coordinate actual equipment requirements early, before distribution is finalized. - Consider reasonably foreseeable system growth in panel and feeder sizing. - Separate code requirements from engineering recommendations explicitly in project documentation.
Do Not
Assume "code compliant" means optimally designed. - Use future capacity as a substitute for required calculations. - Oversize systems without a documented engineering basis. - Treat 90.2(D)'s IEC reference as authorizing IEC installation practice on an NEC-governed project.
Masterbuild QA Lens
The most common gap this section exposes is not a code violation - it is a distribution system sized to exactly clear today's connected load with no panel space, spare capacity, or pathway for equipment that is already known to be coming. Ask the growth question during design, not after the panel schedule is finalized.
Drawing / Submittal Check
Compare the panel schedule's available spaces and spare capacity against any documented future tenant, equipment, or system-expansion plans. Confirm the design basis distinguishes minimum NEC compliance from the owner's or engineer's own reliability and capacity decisions.
Common Review Risk
A panel schedule shows zero spare spaces and zero spare capacity on a project where the owner's program already describes a phased buildout - the design is compliant today and will require a full panel replacement, not an addition, the moment the next phase proceeds.
When To Escalate
Escalate any project with a known future phase, tenant improvement, or equipment addition where the current distribution design provides no documented spare capacity or pathway space, and any instance where "code minimum" is being presented to an owner as equivalent to "complete design."
Field Tip
Ask two questions separately: Does it comply today? What happens when the building changes tomorrow? Verify the locally adopted NEC edition and AHJ amendments before applying this post to a real project.