CODEX
220

Article 220 — Branch-Circuit, Feeder & Service Load Calculations

The math that tells you how big the service, feeders, and circuits must be for a given building.

Introduced
1937
Level
NEC (National)
Why this code exists
Standardization
Current status
Current; the basis for every service and feeder size.

Why this code exists

Guess the load too low and you overheat wire; guess too high and you waste money — the Code gives repeatable methods so results are consistent.

Article 220 is the calculation engine of Chapter 2. It defines how to add up lighting, receptacle, appliance, motor, and HVAC loads, and where you are allowed to apply demand factors because not everything runs at full load at once. It provides both a standard method and an optional method for dwellings.

The output feeds every sizing decision: service size, feeder ampacity, and the number of branch circuits. Getting the demand factors right is what separates a right-sized 200 A service from an oversized, overpriced one — or an undersized one that trips.

When it applies

Article 220 is the calculation backbone for the whole service. Any time you size a panel, a feeder, or the branch circuits behind it, this is where the numbers come from. You total the lighting by area, add fixed and appliance loads, then apply demand factors so the result reflects realistic simultaneous use instead of everything at full tilt.

Common mistakes

In the field

On every service upgrade I do a clean Article 220 calc and keep it with the permit. It is the document that proves the service is right, and inspectors respect a load sheet that shows the work.

Field note
I run the standard and the optional dwelling calc both ways and take the one that is honest for the house — a clean load calc on paper is what gets the permit signed without a fight.
— Ray · Master Electrician · 35 yrs
Ad

See full history

Related codes

Open interactive version →

Codex is an independent educational reference. Not the National Electrical Code® and not affiliated with the NFPA. Always verify against the adopted code and your AHJ. · Privacy