When the Lines Go Down: Resilient In‑Building Emergency Communications

Why emergency communications fail faster than most teams expect

In this episode of Built, Wired, and Secured, Alex Morgan and Michael Harrington dig into a problem that hides in plain sight inside many buildings: what happens when normal communication channels fail during a real incident. The scenario they open with is intentionally familiar and uncomfortable. Water is pouring down a stairwell. Phones are not connecting. Security cannot reach facilities. Tenants gather in the lobby looking for direction. In that moment, the issue is not simply a phone outage. It is a coordination failure that spreads quickly across operations.

Michael explains that when phones and backhaul fail, the impact reaches much further than missed calls. Elevators, access control, vendor alerts, and tenant help desk workflows can all start to fray. What looks like a narrow technical failure often becomes a building-wide communications problem in minutes. That is why the first step is not buying more tools. It is understanding dependencies and mapping what each system needs in order to keep talking.

• Phone outages can trigger broader operational confusion, not just inconvenience.
• Critical building functions may depend on backhaul, carrier connectivity, local power, or Wi-Fi stability.
• Dependency mapping is the foundation for any practical resilience plan.

The most common failure modes inside buildings

Michael lays out several predictable ways communications break during incidents. Carrier loss is one of the clearest examples. A fiber cut or carrier core issue can knock out data backhaul and phone paths at once. Wi-Fi problems are another major risk. In an emergency, everyone competes for bandwidth at the same time, and controller failures or saturation can make wireless communications unreliable right when they are needed most.

Power loss is equally important. Network gear that is not protected by UPS or generator support can disappear during a partial outage, even if the broader building remains occupied. Then there are the design blind spots that quietly create single points of failure long before an incident happens. Michael calls out examples such as single VLANs carrying both tenant traffic and paging, or mass notification systems that require cloud authentication. These design choices may seem efficient during normal operations, but they can turn a manageable event into a communications collapse.

• Carrier loss can take out both data and phone paths.
• Wi-Fi saturation and controller failures are common during high-stress events.
• Power protection matters for network gear, paging, and communications infrastructure.
• Single shared paths and cloud-dependent tools can become hidden failure points.

How to get resilience without overspending

One of the most useful parts of the conversation is the distinction between expensive redundancy and practical middle-ground resilience. Alex raises the concern many building teams have: redundancy sounds good, but it also sounds expensive. Michael agrees that top-tier redundancy, such as duplicate uplinks, multiple carriers, and full failover, is effective but costly.

His recommendation is to think in tiers. The highest-value middle tier is made up of low-maintenance, low-cost controls that reduce confusion when an outage occurs. He specifically points to battery-backed paging amplifiers, a small cache of preconfigured two-way radios, and laminated templates for lobby staff. None of these tools eliminates risk entirely. What they do is preserve basic coordination and clear messaging when more sophisticated systems are degraded.

That point matters because confusion is often the cost multiplier in an incident. When tenants receive mixed directions, when security and facilities cannot coordinate, or when staff are unsure who should say what, a technical issue becomes an operational failure. Inexpensive redundancies can stop that spiral.

• Full failover is valuable but not always necessary as a first step.
• Low-cost controls can dramatically improve coordination during partial outages.
• Reducing confusion is often the fastest path to reducing outage impact.

Balancing coverage and control across communication tools

The episode also offers a useful way to compare communication tools without turning the discussion into a product debate. Michael frames the decision as coverage versus control. Mass notification platforms provide broad reach and useful logging, but they depend on third-party networks, carriers, and cloud services. That means they are valuable, but not sufficient on their own.

Local paging systems offer a different benefit. If they are supported by independent power, they remain under building control and can continue working even when internet or carrier services are unavailable. Two-way radios are described as especially valuable for staff coordination because they require no cloud, no carrier, and no delay. They provide immediate communication between the people who actually have to manage the building in real time. Visual alerts such as strobes or local signage players add another layer, especially for occupants who may not hear an announcement.

The practical takeaway is not to choose one perfect system. It is to combine channels so one outage does not kill every path at once.

• Mass notification offers reach and logging but depends on outside networks.
• Local paging improves control inside the building.
• Two-way radios support fast staff coordination during degraded conditions.
• Visual alerts expand accessibility and redundancy.

Governance matters as much as equipment

Another strong theme in the episode is that resilience is not only about hardware. It is about ownership, message discipline, and testing. Michael pushes back on the idea that radios are too burdensome for most properties. In his view, the governance is light when handled correctly: one owner, monthly battery checks, channel discipline, a small pre-programmed cache, and spare units kept in the security office.

The same governance principle applies to messaging. Michael recommends limiting senders to a small trained group, typically a security manager, facilities director, and operations lead. He also recommends tiered templates: a one-line immediate instruction and a short follow-up status update. Escalation should be defined in advance. If the primary sender cannot be reached within a set number of minutes, a backup takes over. Those simple rules prevent duplicate alerts, contradictory instructions, and tenant confusion.

• Name a small trained group of authorized senders.
• Use short templates for immediate instruction and follow-up updates.
• Define escalation clearly so ownership does not stall during an incident.
• Treat radios and paging as governed assets, not ad hoc tools.

The testing cadence teams can actually sustain

Testing is where many plans either become credible or fall apart. Alex raises the concern of alarm fatigue, and Michael answers with a rhythm that is simple enough to remember and realistic enough to sustain. He recommends quarterly tabletop reviews with the core team, monthly quick checks for physical items such as batteries and radios, and one limited live test of key systems each year.

He emphasizes that live tests should stay focused and be announced to tenants as tests. The goal is not to create noise. The goal is to confirm whether key systems actually work, capture what failed, and document it with a short log that includes date, initials, and status. Small repeatable checks, rather than elaborate exercises, are what keep the plan honest over time.

• Quarterly tabletop reviews keep decision-makers aligned.
• Monthly physical checks catch battery, radio, and equipment readiness issues.
• Annual live tests validate key systems without causing fatigue.
• Short logs make follow-through easier and more consistent.

A real example and the checklist to start this week

To ground the advice, Michael shares a real-world example from a downtown office during renovations. A contractor cut a fiber feed, dropping internet and backhaul. The property did not have an elaborate system, but it did have two important basics: laminated announcement scripts at the front desk and two handheld radios for security and facilities. Staff used the scripts over the lobby speakers and coordinated over radios. The result was clear tenant direction, better ingress coordination, and an orderly response instead of confusion.

The closing checklist is intentionally straightforward:

• Map dependencies and flag single points tied to internet, carrier backhaul, and local power.
• Create or update two templates: an immediate instruction and a one-hour status update.
• Stock one low-tech redundancy such as two radios or a battery-backed paging amp.
• Assign an owner and schedule a quick test within 30 days.

Michael adds that the one-page procedure should name senders, include templates, define escalation, and set the testing cadence. His final point is the one that ties the episode together: do not let perfect be the enemy of good. A basic tested plan with clear ownership and a couple of inexpensive redundancies will outperform a complex fragile system every time.

When normal communications fail, building operations fail with them

Many buildings invest heavily in power, connectivity, and tenant amenities, yet one of the most overlooked parts of resilience is internal emergency communication. When an incident unfolds inside a property, the problem is rarely just that phones stop working. The real issue is that people lose the ability to coordinate, instruct occupants, and maintain control at the exact moment clarity matters most.

In this episode of Built, Wired, and Secured, Alex Morgan speaks with Michael Harrington about pragmatic ways to make in-building emergency communications more resilient without turning the solution into an expensive engineering exercise. Their conversation stays grounded in the realities property teams face: partial outages, tenant confusion, bandwidth saturation, unclear ownership, and the need for tools that still work when cloud services, carrier paths, or Wi-Fi become unreliable.

The core message is simple. A resilient communications plan does not have to be elaborate. It has to be clear, layered, owned, and tested.

Why communications failures spread so quickly in a building

One of the most important observations from the discussion is how fast a localized outage becomes an operations problem. Michael points out that when phones and backhaul fail, the impact moves beyond missed calls. Elevators, access control, vendor alerting, and tenant help desk workflows can all begin to break down. In other words, communications sit in the middle of many systems that building teams depend on to keep occupants informed and operations moving.

That is why the first step is not choosing a product. It is asking a more strategic question: what breaks if this goes down? If a building cannot answer that clearly, then it cannot prioritize the right redundancies. Dependency mapping becomes the starting point for better resilience. Teams need to know which systems rely on internet access, which rely on carrier backhaul, which rely on local power, and which contain hidden single points of failure.

This is where many buildings discover that their emergency communication posture is far more fragile than expected. A platform may appear robust on paper, but if it depends on cloud authentication or shares the same path as general tenant traffic, it may fail right alongside the problem it was supposed to help manage.

The failure modes worth planning around first

Michael highlights several predictable failure modes that building operators should evaluate immediately.

First is carrier loss. A fiber cut or a carrier core issue can take down key data and phone paths simultaneously. Second is Wi-Fi saturation or controller failure. During an incident, everyone reaches for bandwidth at once, and infrastructure that handles normal daily load may struggle under concentrated demand. Third is power loss. Network gear that lacks UPS or generator support can disappear during a partial outage, even if parts of the building remain active. Fourth are design blind spots, such as running both paging and tenant traffic across the same VLAN or depending too heavily on cloud-native tools for critical messaging.

These are not edge cases. They are practical, recurring risks. The value of naming them is that it shifts planning from vague “business continuity” talk into specific action. If teams understand the likely ways communication fails, they can put sensible countermeasures in place without overspending.

The business case for low-cost redundancies

Resilience conversations often stall because teams assume the only meaningful answer is full technical redundancy. Alex brings up that concern directly, and Michael offers a more workable framing. Think in tiers.

At the top tier are duplicate uplinks, multiple carriers, and comprehensive failover designs. Those investments may be justified for some properties, but they are not the only path to better outcomes. The middle tier, which Michael clearly favors as a starting point, includes low-maintenance, low-cost tools that preserve clarity and coordination during degraded conditions.

His examples are refreshingly practical:

• Battery-backed paging amplifiers
• A small cache of preconfigured two-way radios
• Laminated scripts for lobby and front desk staff

These are not glamorous purchases, but that is exactly the point. They are affordable, simple to govern, and highly useful when more sophisticated systems are unavailable. Their value is not that they eliminate all risk. Their value is that they reduce confusion.

That is a major business outcome. During an outage, tenant frustration, staff hesitation, and conflicting messages can drive escalation far more quickly than the underlying technical failure. When people receive clear instructions and staff can coordinate calmly, the building protects trust, reduces friction, and limits avoidable disruption.

Coverage versus control: why one channel is never enough

Another strong takeaway from the episode is the way Michael frames communication design as a balance between coverage and control.

Mass notification platforms offer broad reach and useful logging. They can be valuable for contacting people off-site and maintaining audit trails. But they depend on third-party networks, carriers, and cloud services. That means they are helpful channels, not complete strategies.

Local paging systems offer something different: direct building-level control. If they are supported by independent power, they can keep operating when internet and carrier connectivity are degraded. Two-way radios fill another critical role by giving staff immediate coordination without needing cloud services or cellular capacity. Visual alerts, including strobes or local signage players, extend the plan to occupants who may not hear an audio announcement.

The strategic lesson is that resilience comes from layering. If every communication method relies on the same external dependency, then one failure can silence the whole building. If channels are mixed intentionally, a single outage is less likely to take everything down at once.

Why governance matters more than people think

Technology alone does not solve emergency communication problems. Governance does. Michael makes this point repeatedly, especially when the conversation turns to radios and messaging ownership.

Some teams dismiss radios as outdated or too hard to manage. Michael’s counterpoint is practical: the governance burden is actually light when handled properly. One owner. Monthly battery checks. Clear channel discipline. A small pre-programmed cache with spares stored in the security office. That is not an overwhelming operational load, and the payoff is significant when mobile networks are saturated or unavailable.

The same disciplined thinking applies to message authority. Michael recommends limiting senders to a small trained group, such as the security manager, facilities director, and an operations lead. He also recommends tiered templates: a one-line immediate instruction followed by a short status update. Escalation should be explicitly defined so that if the primary sender cannot be reached in a set amount of time, a backup takes over.

These rules sound simple, but they address one of the most damaging problems during incidents: message proliferation. When too many people can communicate without a framework, tenants receive conflicting instructions and confidence drops. Clear ownership protects both safety and credibility.

The testing rhythm teams can actually maintain

Plans become useful only when they are tested. At the same time, over-testing can create fatigue and reduce trust. The cadence Michael recommends strikes a realistic balance.

• Quarterly tabletop reviews with the core team
• Monthly quick checks for physical items like batteries and radios
• One limited live test of key systems each year

That cadence works because it keeps the plan active without becoming disruptive. Tabletop reviews help decision-makers walk through escalation, roles, and likely failure modes. Monthly physical checks catch the practical issues that often undermine readiness, such as dead batteries or missing equipment. Annual live testing validates whether key systems function in the real world while staying focused enough to avoid alarm fatigue.

Michael’s additional advice is equally useful: keep the log short. Date, initials, and status. The simpler the tracking process, the more likely it will actually be maintained.

A real-world example of low-effort resilience

The episode includes a concrete example that captures the value of modest preparation. During renovations at a downtown office, a contractor cut a fiber feed. Internet and backhaul dropped. The property did not rely on a complex backup architecture. Instead, it had two simple controls in place: laminated announcement scripts at the front desk and two handheld radios for security and facilities.

That was enough to make the response orderly. Staff used the scripts over lobby speakers, coordinated over radios, directed tenants clearly, and managed ingress more effectively. The cost of those measures was small compared with the disruption they prevented.

This example is especially important for commercial real estate teams because it reframes resilience. The goal is not to build the most complicated system. The goal is to preserve operational control during the kinds of incidents buildings actually experience.

The checklist to act on this week

Michael closes the episode with a practical three-step list that building teams can start immediately:

• Map dependencies and identify single points tied to internet, carrier backhaul, and local power.
• Create or update two templates: one immediate instruction and one one-hour status update.
• Stock one low-tech redundancy, such as two radios or a battery-backed paging amplifier.

He adds that each property should assign an owner and schedule a quick test within 30 days. The supporting one-page procedure should name authorized senders, include message templates, define escalation, and document the testing cadence.

That advice fits a broader operational truth. In emergency communications, disciplined basics outperform fragile complexity. Clear ownership, short message templates, a simple backup channel, and repeatable testing can improve safety and business continuity far more than a plan that looks impressive but depends on too many things working perfectly.

Final takeaway

If there is one question every building team should take from this episode, it is this: what breaks if this goes down? Once that question is answered honestly, practical improvements become much easier to identify.

A basic tested plan with named owners and a few inexpensive redundancies can keep staff aligned, tenants informed, and operations steadier during partial outages. For commercial real estate leaders and facilities teams, that is not just a technical improvement. It is a business resilience advantage.

Listen to the full episode for the complete discussion and use it as a prompt to review whether your building can still communicate when the usual lines fail. https://builtwiredsecured.com/episodes/when-the-lines-go-down-resilient-in-building-emergency-communications