Classify a standby power system correctly under NEC 700, 701, or 702 before design
domain: nfpa.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Determine if the system protects people trying to evacuate or respond to an emergency (egress lighting, fire alarm, etc.) — this is Article 700 Emergency Systems territory, the strictest tier.
Determine if the system instead supports emergency responders or controls a health/safety hazard during an emergency (e.g., smoke control, sewage lift pump) — this is Article 701 Legally Required Standby.
If the system exists only to protect property or avoid financial loss, with life safety not depending on it, classify it as Article 702 Optional Standby.
Match wiring separation requirements to the classification: Article 700 requires fully independent wiring; Article 701 allows more flexibility with AHJ approval; Article 702 permits shared raceways with normal wiring.
Confirm the transfer time and load-shedding priority requirements appropriate to the classification (700 systems generally must restore power fastest; 701 allows more time), and set load-shedding priority with emergency loads first, then legally required standby, then optional standby.
Known gotchas
Misclassifying a job as 702 Optional Standby when the building/fire code actually requires legally required standby (701) or emergency (700) power for a specific load leaves that circuit non-compliant regardless of how well the generator itself is installed.
Article 700/701 wiring separation rules are stricter than 702 — retrofitting proper separation after the fact (conduit, boxes, panels) is far more expensive than designing to the correct classification from the start.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?