ok so class A vs class B comes up on basically every job where the spec says "all SLC wiring shall be class A" and you're trying to figure out if the engineer actually means it or just copy-pasted from the last hospital project. short answer: they usually mean it. here's the actual difference and when it's required.
What the return path actually buys you
Class B is a dead-end run. Wire leaves the panel, devices are tapped or daisy-chained along it, and a supervised end-of-line sits at the far end. One open anywhere on that run and everything downstream of the break goes offline. The panel can see there's a fault, but it loses supervision of every device past the break.
Class A adds a return path. The wire goes out from the panel, hits all the devices in the loop, and then routes back to a separate set of supervised terminals on the same card or module. Single open fault anywhere in the loop? The panel drives signal from both ends simultaneously and keeps reporting on all devices. No dark zones.
That survivability is the whole point. In a real fire, physical damage to a conduit run is possible. Class A eats a single open and keeps the whole loop alive. NFPA 72 Chapter 12 defines these by style. Style 4 is your standard Class B SLC. Style 6 and 7 get you to Class A performance. Check which edition your AHJ has adopted before you start designing.
Where AHJs actually require it
High-rise is the most common trigger. Once a building crosses the high-rise threshold (typically 75 ft measured to the highest occupied floor above grade, but check your local code), AHJs frequently mandate Class A on all SLC loops, and often on NACs too. The logic makes sense. You can't safely evacuate 25 floors if a broken wire takes out half your devices.
Healthcare facilities are the other big one. Hospitals, surgery centers, and outpatient facilities under NFPA 101 and Joint Commission oversight tend to require full single-point survivability throughout the fire alarm system. Class A wiring is usually written into the specs or the local amendment without exception.
Some AHJs require it on everything, period. I've run into plan reviewers who mark "class A wiring required throughout" on routine low-rise commercial jobs where the code doesn't technically demand it. It happens. Check your plan review comments before you order wire, not after you've pulled it.
If you're designing a large occupancy and you're not sure, ask the AHJ before the submittal. Easier than getting it kicked back.
A real SLC loop example
Here's a comparison from a mid-size commercial job: single-story 40,000 sq ft office building, one SLC loop, 38 addressable devices (smokes, pulls, monitor modules). Panel is a Fire-Lite ES-200X.
| Item | Class B | Class A |
|---|---|---|
| SLC conductors at panel | 2 | 4 (out + return terminals) |
| Home run to first device (ft) | 180 | 180 |
| Total SLC wire estimated (ft) | 1,240 | 1,840 |
| End-of-line device required | Yes, at last device | No, loop returns to panel |
| Single open fault result | Devices past break go offline | All 38 still supervised |
| Wire cost delta (18 AWG, approx) | baseline | +$90 to +$150 |
The wire cost difference is not usually the argument. The real cost is in conduit fill and labor. That return home run adds conductors to every section of conduit between the last device and the panel. On a single-story with a short return run it's manageable. On a multi-floor building where the loop ends on the 10th floor, that return pull gets expensive fast.
The cost tradeoff in plain terms
Class B is fine for most low-rise, lower-occupancy work when the spec and AHJ are silent on wiring class. It's simpler to design and faster to pull.
Class A is the right call when survivability is the priority, and it's required when the occupancy type, the spec, or the AHJ say so. The cost difference between the two is usually not big enough to fight over on a job where class A is genuinely warranted.
If the spec says class A and you want to value-engineer it out, get written direction from the engineer of record. Do not just wire it class B and hope plan review doesn't catch it. They usually do, and then you're redoing the device matrix, the voltage drop calc, and the drawing set.
One thing to watch on the submittal
Class A loops add a wrinkle to the paperwork side. Your voltage drop calculation needs to account for both the outbound and return conductors, and the device matrix should reflect the return path supervision. The math doesn't change much, but the format matters to a thorough plan reviewer.
Running those calcs by hand for 38 devices is doable once. Full disclosure, I built a tool called FireDeck that handles the voltage drop and battery calcs for submittal packages automatically, so I'm biased. The calc above is the calc either way, tool or no tool. If you're grinding through class A submittals manually and it's eating your evenings, worth a look. Free trial at firedeck.app.
anyway. hope this helped before the plan checker got to it first.