Show Notes
Why emergency communications fail faster than most teams expect
This episode of Built, Wired & Secured opens with a vivid but familiar problem: water is pouring down a stairwell, phones are not connecting, security cannot reach facilities, and tenants are gathering in the lobby asking what to do next. From there, Alex Morgan and Michael Harrington unpack a simple truth that many buildings miss until the worst moment: reliable internal communication is not the same thing as having internet, phones, or a modern cloud platform. When those systems degrade, confusion spreads quickly unless the building has alternate ways to communicate.
The conversation centers on pragmatic planning rather than expensive overhauls. Instead of assuming a single mass-notification platform will carry the day, the episode argues for layered communication paths, clear ownership, and short, repeatable checks that keep the plan usable under stress.
The most common failure modes during partial outages
One of the strongest sections of the episode is the breakdown of predictable failure vectors. Michael explains that communication failures are rarely isolated. Once one dependency breaks, other operational systems start to fray as well.
- Carrier loss, including fiber cuts or core carrier issues, can break data backhaul and phone paths.
- Wi-Fi saturation or controller failures can show up during an incident when everyone tries to use the network at once.
- Power loss can take down network gear if it is not protected by UPS or generator support.
- Design blind spots, such as a single VLAN carrying both tenant traffic and paging, can create hidden single points of failure.
- Cloud-dependent tools may fail at exactly the wrong time if they require internet access or cloud authentication.
The key takeaway is dependency mapping. Before buying anything new, building operators need to know what each communication path actually depends on to keep working.
Low-cost redundancy that actually moves the needle
The episode does not dismiss full redundancy. Duplicate uplinks, multiple carriers, and formal failover still matter. But Michael makes the case for a practical middle tier that is far more achievable for many properties.
He points to simple, low-maintenance tools that can dramatically reduce confusion during an outage:
- Battery-backed paging amplifiers
- A small cache of preconfigured two-way radios
- Laminated message templates for lobby staff
These are not pitched as perfect solutions. They are positioned as low-complexity redundancies that preserve control when carrier, cloud, or Wi-Fi systems become unreliable. That framing matters because the goal is not to eliminate every risk. It is to keep the building functional and the messaging consistent long enough to stabilize the situation.
Coverage versus control: choosing the right mix
Another useful theme in the episode is the tradeoff between broad reach and local control. Mass-notification platforms provide scale and logging, but they rely on third-party networks. Local paging systems may not reach off-site stakeholders, but they can remain usable inside the building if supported by independent power. Two-way radios offer immediate staff coordination without cloud or carrier dependence. Visual alerts such as strobes or signage players can support occupants who may not hear voice announcements.
Rather than championing one system, the discussion recommends mixing channels so that one outage does not wipe out every communication option at once.
Why radios still matter
The conversation also addresses a common objection: that radios feel outdated or operationally burdensome. Michael pushes back on that assumption with a governance model that is intentionally light. He describes one accountable owner, monthly battery checks, programmed channels, and a small set of spares stored in the security office.
That is a useful operational point for property teams. The value of radios is not nostalgia. It is that they remain immediately available when mobile networks are saturated and staff need to coordinate security, facilities, and lobby operations in real time.
Clear messaging prevents tenant confusion
A recurring point throughout the episode is that contradictory messages can become as damaging as the outage itself. That is why the speakers emphasize laminated one-line scripts and a tightly limited sender group. The recommendation is to allow only a small trained group to send messages, typically a security manager, facilities director, and operations lead.
The procedure should include:
- An immediate instruction template
- A short follow-up status update template
- A defined escalation path if the primary sender is unavailable within a set number of minutes
This is operational discipline more than technology. The building does not just need channels. It needs a simple rule set for who speaks, what they say first, and when the backup takes over.
A realistic testing cadence
Testing gets practical treatment too. The episode warns against over-testing in ways that create tenant fatigue, but it also makes clear that an untested plan is only a theory. The recommended cadence is easy to remember:
- Monthly quick physical checks for batteries, radios, and other ready-state items
- Quarterly tabletop reviews with the core team
- One limited live test of key systems each year, clearly announced as a test
Just as important, Michael recommends keeping the log short and repeatable: date, initials, and status. That kind of lightweight recordkeeping makes the process more likely to happen consistently.
A real-world example of modest redundancy paying off
The episode includes a concrete example from a downtown office under renovation. A contractor cut a fiber feed, dropping internet and backhaul. The property did not solve the situation with a complex platform. Instead, staff used two simple assets already in place: laminated lobby announcement scripts and two handheld radios for security and facilities. Those tools gave tenants clear direction and let staff coordinate ingress without chaos. The point is not just that the outage was manageable. It is that a modest setup cost far less than the disruption it prevented.
The one-page checklist listeners can use now
Michael closes with three actions listeners can take this week:
- Map dependencies for internet, carrier backhaul, and local power, and identify single points of failure.
- Create or update two message templates: an immediate instruction and a one-hour status update.
- Stock one low-tech redundancy, such as two radios or a battery-backed paging amplifier, assign an owner, and schedule a quick test within 30 days.
He also outlines what the one-page procedure should contain: named senders, templates, escalation rules, and testing cadence. That is the practical heart of the episode. A basic tested plan with clear ownership and a few inexpensive redundancies can outperform a complex but fragile system.
Listeners who want to move from ideas to action are pointed to the downloadable checklist and sample templates at gdec.io/communications, along with an option for a short readiness review with the GDS team.
Many buildings invest heavily in power resilience, internet connectivity, access control, and modern tenant systems. Yet one of the most overlooked parts of resilience is internal communication during a partial outage. When the usual lines go down, the immediate problem is not only technical failure. It is confusion. Staff cannot coordinate. Tenants do not know what is happening. Routine support workflows stall. And a manageable incident can quickly feel like a loss of control.
That is the central message of this episode of Built, Wired & Secured, where Alex Morgan speaks with Michael Harrington about resilient in-building emergency communications. The discussion stays grounded in real operational tradeoffs rather than abstract continuity theory. The focus is on what actually helps during degraded conditions: understanding dependencies, adding inexpensive redundancies, limiting message ownership, and testing just enough to keep the plan honest.
Communication failures rarely stay isolated
The episode opens with a vivid scenario: water in the stairwell, phones that will not connect, security unable to reach facilities, and tenants clustered in the lobby waiting for instruction. It is an effective setup because it reflects how quickly multiple systems can start failing together.
Michael explains that the breakdown is often driven by a few predictable vectors. Carrier loss can take down backhaul and voice paths. A fiber cut or a problem in the carrier core can ripple through building operations faster than many teams expect. Wi-Fi can also become part of the problem, especially during an incident when everyone grabs for bandwidth at once and controllers begin to struggle. Power loss introduces another layer of risk if network gear is not protected by UPS or generator support. Then there are the design blind spots: a single VLAN carrying both tenant traffic and paging, or a mass-notification tool that depends on cloud authentication during the exact moment when internet access is unstable.
The point is not that every building needs an expensive redesign. The point is that communication systems are full of hidden dependencies. If teams do not map them in advance, they may discover them only when their options are shrinking.
Dependency mapping is the first step
One of the clearest takeaways from the conversation is that dependency mapping should come before product shopping. Before deciding whether to buy another platform, upgrade a controller, or add a new paging component, teams need to know what each communication path depends on.
That means asking practical questions. Does this message path require internet access? Does it rely on a specific carrier? Does it need local power from a circuit that is not backed up? Does a cloud login sit between the operator and the ability to send instructions? Is paging segmented away from general tenant traffic, or are they sharing infrastructure in ways that create avoidable failure points?
Those questions are not glamorous, but they are exactly what separates a resilient building from a fragile one. In many cases, the most valuable discovery is not what technology to add, but where a single dependency is carrying too much weight.
The best middle ground is often simple and inexpensive
When the conversation turns to cost, the answer is refreshingly practical. Yes, duplicate uplinks, multiple carriers, and formal failover are useful. They are also not always realistic as the first move for every property. Instead of treating resilience as an all-or-nothing capital project, Michael describes a high-impact middle tier made up of low-maintenance, low-cost measures.
Three examples stand out. The first is a battery-backed paging amplifier that keeps local voice announcements working even when internet and carrier connections are down. The second is a small cache of preconfigured two-way radios stored in the security office, with spares ready. The third is a set of laminated message templates at the front desk so lobby staff can deliver clear, consistent instructions immediately.
These measures do not eliminate outages. What they do is preserve clarity and control. In the middle of a fast-moving event, that can be the difference between a controlled response and a building full of conflicting answers.
Coverage and control are not the same thing
A useful framework from the episode is the distinction between coverage and control. Mass-notification platforms offer wide reach and logging, which matters. But they also depend on third-party networks. If carriers are degraded or cloud services are unreachable, those tools may not be enough by themselves.
Local paging flips that tradeoff. It may not reach people off-site, but if it is on independent power, it remains within the building team’s control. Two-way radios are even more direct. They do not need cloud services, do not depend on carrier performance, and allow security, facilities, and operations to coordinate instantly. Visual alerts such as strobes or local signage players help ensure instructions are still seen by occupants who may not hear an announcement.
The lesson is to layer channels so a single failure cannot silence every route at the same time.
Why radios remain a practical tool
Some teams still view radios as outdated or administratively annoying. The episode addresses that concern directly. Michael acknowledges the objections around licensing, interference, and upkeep, then reduces the issue to an operational model that is intentionally lightweight: one owner, monthly battery checks, pre-programmed channels, and basic channel discipline.
That is an important point for property leaders. A resilient tool does not need to be complex to be valuable. Radios work precisely because they are simple, local, and immediately available when cellular networks are congested. During an incident, simplicity is an advantage.
Ownership matters as much as equipment
Another major theme in the episode is that communication discipline matters as much as communication hardware. Even with working tools, a building can still create confusion if too many people send messages or if different teams issue conflicting instructions.
That is why the recommended model limits authorized senders to a small trained group, such as the security manager, facilities director, and an operations lead. The group should use tiered templates: a one-line immediate instruction followed by a short status update. The procedure should also define escalation. If the primary sender cannot be reached within a specific number of minutes, a named backup takes over.
This is not bureaucracy for its own sake. It is a way to reduce message proliferation and tenant frustration during moments when clarity matters most.
Short drills beat theoretical plans
The testing guidance in the episode is equally practical. Over-testing can create fatigue, especially in occupied commercial properties. Under-testing creates a false sense of readiness. The proposed rhythm balances both concerns: monthly quick physical checks, quarterly tabletop reviews with the core team, and one limited live test of key systems each year.
That cadence works because it is simple enough to sustain. The monthly checks verify that batteries, radios, and other assets are ready. Quarterly tabletops keep the procedures familiar. Annual live tests expose problems in a controlled way without overwhelming tenants. Michael also recommends keeping the log minimal: date, initials, status.
A small real-world setup that prevented chaos
The episode’s strongest proof point is a downtown office example during renovations. A contractor cut a fiber feed, which dropped internet and backhaul. The building did not rely on a sophisticated rescue system. Instead, staff used laminated announcement scripts over the lobby speakers and coordinated with two handheld radios between security and facilities.
The result was not flashy, but it was effective. Tenants received clear instructions. Staff coordinated ingress. A situation that could have felt chaotic remained orderly. That example reinforces the episode’s broader point: modest redundancy often delivers outsized value when paired with clear procedures and ownership.
What to do this week
Michael closes with a practical three-step checklist. First, map the dependencies behind your communication paths, including internet, carrier backhaul, and local power. Second, create or refresh two message templates: one for immediate instructions and one for a one-hour status update. Third, add one low-tech redundancy such as two radios or a battery-backed paging amplifier, assign an owner, and schedule a test within 30 days.
Just as important, keep the procedure to one page. It should name the approved senders, include the templates, define the escalation path, and state the testing cadence. That kind of plan is easier to maintain, easier to use, and far more likely to perform under stress than a complex document no one can apply in the moment.
For commercial real estate teams, the bigger lesson is straightforward: resilience is not only about keeping systems online. It is also about keeping people informed when systems become unreliable. A basic, tested communication plan with a few inexpensive backups can protect tenant confidence, reduce operational friction, and improve continuity when it matters most.
If this episode surfaces gaps in your own building communications plan, it is worth listening in full and comparing your current approach against the checklist shared in the conversation. Sometimes the most valuable improvement is not a major overhaul. It is a clearer owner, a better script, and one dependable fallback channel ready before the next incident.