Selective Coordination in Article 700: Stop Forcing a 0.1-Second Rule That Doesn’t Exist
- Posted by Paul Abernathy
- Categories Blog
- Date March 28, 2026
- Comments 0 comment
⚡ Selective Coordination in NEC 700: The 0.1-Second Myth Needs to Go
Selective coordination is one of those topics that sounds simple until people start blending rules from different occupancies and different Code sections. That is where the confusion starts. When it comes to emergency systems, Article 700 says what it says—and it does not say what many people keep repeating.
The Misunderstanding Happens Fast
This is a great topic because it still gets misunderstood far more than it should. A lot of people hear the phrase selective coordination, then immediately start tying it to a fixed time band like 0.1 second or 0.01 second as if that applies everywhere. That is where things start going sideways.
The problem is not that people are trying to do the right thing. The problem is that they are borrowing language from one part of the Code and dropping it into another part where it simply does not belong. That is how bad interpretations get repeated enough times that they start sounding like fact.
What Article 700 Actually Requires
In NEC 2026, Section 700.32 requires emergency system overcurrent protective devices to be selectively coordinated with all supply-side overcurrent protective devices. That is the part many people either skip over or do not fully appreciate. The requirement is not just about downstream branch devices and feeders. It reaches upstream as well.
In plain language, the Code is expecting the protective device closest to the fault to operate first so that the rest of the emergency system stays in service to the greatest extent possible. That is the entire point of selective coordination in an emergency system. When a fault occurs, you do not want a larger upstream device taking out a major portion—or all—of the system unnecessarily.
Where the 0.1-Second Rule Really Comes From
This is where the discussion needs to be precise. Time absolutely is part of the NEC when it comes to selective coordination, but that comes from the definition of Coordination (Selective) in Article 100—not from Article 700 assigning its own fixed time threshold.
In other words, the Code does consider time because selective coordination has to exist over the full range of available overcurrents and the full range of overcurrent protective device opening times associated with those overcurrents. So the issue is not whether time exists in the Code discussion. It does. The issue is whether Article 700 gives you a special fixed value such as 0.1 second or 0.01 second, and it does not.
The 0.1-second concept people often cite comes from Article 517, specifically the healthcare essential electrical system rules. That is a very specific occupancy-based requirement. It applies in that context, but it should not be casually imported into general Article 700 emergency system discussions as though it were the universal benchmark for all selective coordination requirements.
🏥 Article 517
Healthcare essential electrical systems include specific coordination language tied to that occupancy, including the familiar 0.1-second discussion.
🚨 Article 700
Emergency systems require selective coordination, but Article 700 does not create its own standalone 0.1-second or 0.01-second rule. Time remains part of the discussion through the Article 100 definition of selective coordination.
Supply-Side Coordination Is Not Optional Window Dressing
One of the most overlooked parts of this entire discussion is the supply side. People will spend all day looking at branch breakers and feeder devices, but if they ignore the upstream protective devices, they have missed one of the most important parts of the requirement.
That matters because the upstream device is often the one that can wipe out the bigger portion of the system if it operates before the downstream device that should have cleared the fault. When that happens, the emergency system may technically exist on paper, but it is not performing the way the Code intended it to perform when a real-world fault happens.
Why Real-World Examples Expose Weak Coordination Fast
A casino is a great example of why this matters. In a facility like that, loss of emergency system continuity is not a theoretical problem. If one upstream device trips out of sequence, you can lose much more of the system than the original fault ever should have taken down.
That is exactly why the coordination conversation has to go deeper than “did we pass plan review?” A system can look fine in a submittal package and still fail the real test if the protective devices are not actually coordinated the way the Code intends.
Do Not Invite Unnecessary Pushback
One additional point worth saying clearly: this discussion is about the coordination of overcurrent protective devices serving emergency systems. It is not an attempt to blur the differences between emergency systems, legally required standby systems, optional standby systems, or healthcare essential electrical systems. Each of those has to be read in its own context.
It is also important to keep the terminology clean. The phrase essential electrical system is tied to healthcare installations in Article 517. Not every emergency system is part of an essential electrical system, and not every special rule from Article 517 can be dragged over into Article 700.
My Take on It
I think this is one of those areas where the industry sometimes overcomplicates something the Code actually says pretty plainly. Article 700 requires selective coordination. It includes supply-side devices. Time is part of the conversation through the Article 100 definition. But Article 700 itself does not hand you a special fixed 0.1-second or 0.01-second limiter the way some people keep trying to make it.
Once you keep Article 700 in its lane and Article 517 in its lane, the fog starts to clear. Then the conversation gets a lot more productive because now you are dealing with what the Code actually requires instead of repeating a rule from the wrong article.
At the end of the day, this is not just about making an AHJ happy or getting a stamp on a set of drawings. This is about whether the emergency system will perform the way it is supposed to perform when people are depending on it most.
⚡ Final Thought
Selective coordination in emergency systems is too important to be reduced to recycled talking points. Read the actual language, keep the Articles separated, include the supply side, and focus on real system performance. That is how you protect the integrity of the installation—and the people depending on it.
Note: This article is focused on selective coordination requirements for emergency system overcurrent protective devices and the common misunderstanding involving imported time-based interpretations from other NEC Articles.
CEO and Founder of Electrical Code Academy, Inc. A Virginia Corporation located in Mineral, Virginia
You may also like
2026 NEC 250.122(F) Change: New Rules for Equipment Grounding Conductors in Parallel Raceways
Code Change Analysis 250.122(F) in the 2026 NEC: Smarter EGC Sizing or a Step Away from Proven Protection? One of the most discussed revisions in the 2026 NEC involves parallel raceways and the sizing of the equipment grounding conductor. While …
🏇 Friday Night Virtual Race Night: Predict the Winners, Climb the Leaderboard, and Win Custom Engraved Gear
🏇 Friday Night Virtual Race Night: Predict the Winners, Climb the Leaderboard, and Win Custom Engraved Gear Join us every Friday night for a fun, fast-moving livestream event built around the Arlington Horse Racing arcade experience. Viewers watch the odds, …
Why Inductance, Capacitance, and Sequence Impedance Are Not Universal Cable “Data Sheet” Values
Technical White Paper 50/60 Hz Engineering Studies Geometry & Return Path Driven Geometry Drives L, C, and Z0: A Technical Basis for Non-Universal Cable Modeling Parameters Requests for inductance (L), capacitance (C), and sequence impedance (Z0/Z1/Z2) are typically motivated by …