Security and 911 work better when they know what to expect from each other
When a security officer calls 911, two dispatch operations start working the same incident. Each one has expectations about what the other knows and what it will do next, and the call goes better when those expectations were set in advance. The 911 center has the facility's address. It doesn't know which entrance is open at 2am, what the staff call each building, or who answers the callback number, unless somebody from the facility has told it.
Spectrum-H Standard 17, the 911 PSAP Liaison Protocol, covers that relationship for hospitals. This is from its Practical Context section.
The premise information package is the tangible output of the liaison relationship that produces immediate operational value. A CAD record showing the facility name and address is the minimum. A CAD record that includes a current map with building labels, emergency access point locations, a 24/7 contact number that goes to a live person, and known hazard notations about the behavioral health unit and pharmacy location is what enables effective dispatch and first-responder orientation. Dispatchers who have this information can give responding units better guidance before they arrive on scene. That matters when the seconds between the 911 call and effective police action are what protect a staff member.
The quarterly meeting cadence feels excessive until the first time something changes at the facility without the PSAP knowing about it. A new building entrance that replaces the one in the CAD file. A new Security Director whose cell phone number is not the one law enforcement has been calling. A security monitoring company change that the PSAP was not notified about. These are the gaps that create communication failures during real emergencies. The quarterly meeting is the maintenance cycle that catches these updates before they matter in the worst possible moment.
Post-incident review with the PSAP is where the liaison relationship produces actionable intelligence that internal review cannot generate. Security's internal after-action review can identify internal process failures. Only the PSAP can tell the facility whether its 911 calls were comprehensible and useful to dispatch, whether the facility's description of the incident matched what officers found on arrival, or whether the callback contact was reachable when dispatchers tried to call back for updates. That external perspective cannot be obtained any other way, and it is the perspective that produces the improvements that actually reduce harm.
Under Kari's Law, a phone system installed after February 16, 2020 has to notify a central location, such as a security desk, when someone dials 911, and the FCC says that notification is intended to help first responders get into the building. Who goes to meet them is up to the facility.
A response plan also has to get responders to the patient, not just into the building. In one high-rise corporate building, first responders always go to the same entrance. An elevator is waiting there to take them to the incident floor, and someone is there to guide them the rest of the way.
Touring
Don't assume your phones reach 911, test them
A phone system's 911 setup gets checked when it's installed, if it gets checked at all. After that, phones get moved and departments trade floors, and the location record that goes to the 911 center stays where it was.
The call taker sees whatever the phone system sends. That might be the right room, or the building's street address with no floor, or the address of a corporate office in another state. The callback number might ring a switchboard that nobody answers after hours. Nobody finds any of this out until a real call, when the call taker is trying to find the person who needs help.
Testing it starts with a call to the 911 center's administrative line, because an unannounced test call ties up a real call taker and can send a real response. They'll give you a window. Then you place 911 calls from a handful of phones, a desk phone, a conference room, the lobby courtesy phone, the emergency phone in the parking garage, and ask the call taker what came up on their screen.
Anything that doesn't match goes to whoever owns the phone system, with the call taker's name and the time of each call. Next time you're touring, pick a few phones and find out what the 911 center sees.
Signals
21 of 23 cities studied cut off police response to properties with too many false alarms
Interface Systems released a report on October 8 finding that 21 of the 23 cities it examined, including Los Angeles, San Francisco, and Houston, suspend or revoke police dispatch for a property once it passes a false alarm threshold. Six days later Security Sales & Integration ran a column asking when suppressing alarms and logging communication failures without acting on them became normal practice.
What false alarms cost
The report, "The Real Cost of Alarm Failure," models a 10-store retailer averaging 3 false alarms per location. Municipal fines for that retailer come to $1,220 a year. Adding guard dispatches, managers responding after hours as keyholders, and lost labor brings it to $7,230, and the report puts a single event at $150 to $500 even when the city waives the fine. If each store has one break-in after losing police response, the modeled total is $37,230. The report also reviews cases where insurers denied six-figure burglary claims on appeal because the operator let a monitored alarm system or its permit lapse.
The figures are Interface's own model, built from fee schedules in 25 cities, dispatch policies in 23, federal labor data, and vendor repair costs. Interface sells remote video monitoring and says its operators clear 95% of commercial alarm events as false before anyone is dispatched.
Suppression and log only
The column's title asks when alarm suppression and log only handling of communication failures became normalized. A communication failure means the panel has stopped reporting to the monitoring center, and a log only setting records that event without anybody acting on it. The column frames the question around "foreseeably dangerous," a condition where a reasonable person can predict that harm is likely.
What links them
Both items are about what happens to a signal before a person acts on it. The Interface report puts a dollar figure on dispatching for alarms that turn out to be nothing, and the city policies it counts are one reason operators filter more before they dispatch. Suppressing an alarm or logging a communication failure is also filtering. The report doesn't measure what it costs when a filtered signal turns out to be real.
Passdown
dictated by Ricky Portezzo, Senior Security Supervisor in Center City, Philadelphia
Garage gate arm is stuck up again, I coned it off and Dennis knows.
Mikey had me do 911 test calls tonight off every phone in the building. I told him in 11 years I never once saw anybody pick up one of those phones to call 911, they all use their cell. He says do it anyway.
So I call the county on the regular number first so they don't send the whole fire department, and the lady gives me 0100 to 0130. Then I go phone to phone dialing 911 and asking the dispatcher what she's got on her screen.
Most of them came up right. Even Mikey's office.
Conference room on 3 comes up as the 2nd floor. They moved that whole department in March and nobody told the phone.
Then the garage phone, the yellow one on the pillar by the elevator with EMERGENCY painted on it. Dispatcher says she's got an address in Columbus, Ohio. We don't have nothing in Ohio. And the callback number rings the switchboard, which after 2300 is nobody.
I walk past that phone every round.
Wrote it all up for the phone guy in IT with the dispatcher's name and the times. Taped a sign on the garage phone that says USE YOUR CELL till IT fixes it.
Gate arm's still up, Dennis says maybe Thursday.
Find out what the 911 center sees before somebody needs it.
SCC Spectrum Security Almanacs. www.gsoc911.com/products
