When the Signal Dies: What Actually Happens to Your Evacuation Technology in a Blackout
By Dr. Rashid Khan, Founder of EvacTracker
I get asked this question in almost every building briefing I run, usually by the most experienced facilities manager in the room, the one who has seen enough systems fail to be sceptical of any new one. “What happens to EvacTracker when the power goes out? When there’s no signal? When the basement floods and the server room goes with it?”
It’s the right question to ask, and I want to answer it properly, not with a marketing line about redundancy, but with an honest account of what technology can and can’t do when conditions are at their worst.
The Uncomfortable Truth About Connectivity
No system, ours included, can guarantee a connection during every possible failure mode. A severe enough event, one that takes out mobile towers, building Wi-Fi, and backup power simultaneously, will degrade any digital communication tool. Anyone who tells you otherwise is selling you something they can’t deliver.
What I can tell you is what EvacTracker does with the remaining connectivity, because in the vast majority of real incidents, some connectivity remains.
Designed for Degraded Conditions, Not Just Ideal Ones
Basements often retain Wi-Fi even when mobile signal drops away entirely. Buildings with backup power frequently keep core communication systems running well after general power fails. Floods and structural damage tend to affect specific zones of a building rather than every system in it at once.
EvacTracker is built around that reality. When a device loses connection, the app keeps trying, quietly, in the background, to send and receive information the moment any connection becomes available again, whether that’s a flicker of mobile signal, a building’s emergency Wi-Fi, or a backup network kicking in. It doesn’t need a perfect connection. It needs a connection, even an intermittent one, and it will use every opportunity it gets.
“A system that only works in ideal conditions isn’t built for emergencies. It’s built for demonstrations.”
Why We Never Position EvacTracker as the Only Line of Defence
This is the part I feel strongly about, and it’s the part that sometimes surprises people expecting a sales pitch. EvacTracker is not, and should never be treated as, your only emergency communication system.
Your wardens, your emergency plan, your training, and the emergency services who respond on the night remain the primary line of defence. They always have been, and no piece of software changes that.
What EvacTracker adds is an extra layer, real-time information and accountability whenever connectivity allows it, on top of a foundation that has to exist regardless of what technology you use.
I’ve seen organisations make the opposite mistake with other systems: treating a single piece of technology as a replacement for trained people and tested procedures. When that technology has a bad night, so does the building.
What This Means for the Building Manager Asking the Question
If you’re the person responsible for a building, here’s what I’d actually want you to take from this. Ask any provider, including us, exactly what happens to their system when the signal drops. Ask what your fallback is if the technology goes dark entirely. If the answer is vague or assumes a best-case scenario, treat it as a serious gap in your emergency plan, not a minor technical detail.
For our part, EvacTracker is designed to keep working at the edges of connectivity, and to be honest about the moments where nothing digital can help. Your plan, your wardens, and your training exist precisely for those moments. That’s not a limitation we’re apologising for. It’s the reason we’ve never designed EvacTracker to stand alone.
The question isn’t whether technology can survive every conceivable disaster. It’s whether the people in your building have real information for as long as possible, and a solid plan for the moments when they don’t.