UL 864 Listed vs. UL 864 Compliant: What Fire Alarm Migration Actually Requires

Here's a sentence I hear constantly: "We bought a UL 864-listed communicator, so we're compliant." That sentence is wrong in a way that usually surfaces at the annual inspection — after the panel has already been closed up and everyone's moved on.
There's a real difference between equipment that carries a UL 864 listing and an installation that's UL 864 compliant. Miss it, and you'll pass a purchase order but fail a fire marshal's walkthrough.
Listed is about the box. Compliant is about the whole job.
UL 864 is the standard for fire alarm control units and accessories. When a communicator says "UL 864 listed," that's a statement about the device itself — it was tested against the standard's construction and performance requirements in a lab.
Compliance is something else entirely. It's the outcome you get when listed equipment is installed, configured, supervised, and monitored the way the standard and your AHJ require. You can buy the most compliant box on the shelf and still end up with a non-compliant installation. The listing is necessary. It is not sufficient.
That gap is where most migrations go sideways, and it's almost always invisible until someone tests it.
The three things a listing can't do for you
Supervision is configured, not purchased. UL 864 requires the communication path to be supervised — the panel has to detect a dead link and report it as a trouble condition within a defined window. A listed communicator is capable of that. Capability is not the same as configuration. If nobody wires the trouble output into the panel or programs the supervision timer, the panel has no idea the communicator lost its path. The device is listed. The installation is not compliant.
The monitoring station has to actually receive the signal. This one trips people up because it lives outside your building. Your central station has to be set up to accept the communicator's format — Contact ID, SIA, whatever the panel speaks — and the account has to be tested end to end after the swap. A communicator that dials into the void is not a supervised fire alarm. It's a decorative box with a listing sticker.
Your AHJ has to sign off. The local fire marshal doesn't care that the spec sheet has a listing number. They care that the supervision test was run and documented, and that the monitoring station confirms it's receiving signals. Walk in with a receipt and you'll be sent back. Walk in with a test report and you'll get approved.
The ten-minute test that catches all three
There's a simple way to find out whether you're actually compliant, and it takes ten minutes.
Disconnect the communicator — pull the network cable, pop the SIM, kill the path however it runs. Then watch the panel. It should go into trouble within the supervision window (typically 90 seconds for a DACT, 200 seconds for an IP communicator). Then restore the path and confirm the trouble clears and the monitoring station logged both events.
If that sequence doesn't happen exactly, you're not compliant — you just have a listed device bolted to the wall. Do this before the fire marshal does it during inspection, when the consequence is a reinspection fee and a scramble instead of a calm afternoon.
Why this matters more in 2026
The POTS sunset is doing the heavy lifting here. The copper lines under legacy fire alarm panels are being retired by carriers, not maintained, so migration isn't a choice anymore — it's a timeline. When you migrate under a deadline, the temptation is to move fast and assume the listing covers you. That's exactly when the listed-vs-compliant gap bites, because the supervision test and the monitoring-station handoff are the two steps most likely to get skipped in a rush.
Bottom line
UL 864 listed is what you buy. UL 864 compliant is what you verify. The difference is a supervision test, a monitoring station confirmation, and an AHJ sign-off — all of which are your job, not the manufacturer's.
Buy listed equipment. Then prove the installation is compliant before anyone asks. If you want help making sure your fire alarm migration actually holds up to inspection, get in touch — we'll walk you through the test.
Carter Dewey
Carter Dewey leads solution architecture at TrustedNetworx, helping multi-site organizations navigate telecom modernization, POTS replacement, and AI-powered operations. With deep experience across property management, senior living, hospitality, and healthcare, Carter translates complex infrastructure challenges into practical, phased migration roadmaps.