Before the Call — Surfside Condo Collapse, Miami

The first minutes of the Surfside collapse are a case study in the dispatch problem of ambiguous, escalating information from multiple callers describing the same event in completely different terms. None of them are wrong. None of them have the full picture. And the pattern doesn't become clear until you're looking at several calls at once.

• Multiple calls from the same location are a signal, not just volume. When your center begins receiving multiple 911 calls from the same address or block with dramatically different descriptions — explosion, fire alarm, half the building gone — that divergence is itself information. Something significant happened and different callers are seeing different pieces of it. Escalate based on the worst credible description, not the average one.
• Run to the worst possibility when the information is ambiguous. A structural collapse is worse than an explosion, which is worse than a fire alarm. With three different reports and no definitive answer, you dispatch to the worst credible interpretation and let first responders downgrade if the scene is less severe. You don't wait for consensus on what happened.
• The scene size is unknown — that itself is a dispatch decision. Structural collapse of a high-rise building is a mass casualty incident until proven otherwise. That determination should trigger USAR protocols, multi-agency notification, and hospital pre-notification — even before you know exactly how many people are affected. "Unknown MCI, possible structural collapse, 12-story residential building, call volume escalating" is enough to trigger those protocols.
• Ask every caller the same rapid orientation questions. "Where are you right now relative to the building? Are you inside, outside, across the street?" Mapping caller positions against each other builds a picture of the incident perimeter even before first responders arrive.

The Surfside dispatch challenge was not a shortage of information — it was a surplus of incomplete, perspective-dependent information arriving simultaneously. Callers from inside the building had high urgency and low visibility. Callers from outside had more visual information but no knowledge of who was inside. Family members had emotional urgency and almost no actionable information. All of these calls are real and all of them need to be handled.

• Triage caller type and information type simultaneously. A trapped resident calling from inside the building is a rescue call — they need to be kept calm and their location documented precisely. A neighbor watching from across the street is a scene intelligence call — what are they seeing that first responders should know? A family member calling from out of state is an information request — they need to be told what you can tell them and directed to a family reunification point.
• Trapped caller protocol applies to Surfside as much as to an elevator or a vehicle. The caller in the un-collapsed portion of the building who is afraid and calling 911 needs the same basic call-taking: stay on the line, tell me exactly where you are in the building, are you injured, what do you see around you. That call will inform where rescue resources go first.
• Scene intel calls are valuable — document specifically. A hotel guest watching from across the street who says "there are people on balconies on the north side, maybe the 5th and 6th floors" is giving actionable rescue intelligence. That needs to be documented with their vantage point and passed to rescue command immediately.
• Out-of-state family members cannot be processed like rescue calls. They cannot help and they are taking dispatcher time that is needed elsewhere. Your center should have a protocol for directing family callers to a non-emergency line or information hotline during a MCI. If your center doesn't have that protocol established, this is the time to build it.

When a mass casualty incident attracts resources from multiple agencies — including non-traditional resources like faith-based emergency services and international teams — dispatch's role shifts from resource deployment to coordination infrastructure. You are the communications backbone for an operation that has more moving parts than any single commander can track.

• Staging location management becomes critical. Eighty-plus units cannot all be on-scene simultaneously. Staging areas, resource check-in processes, and assignment to sector commanders require dispatch to maintain an accurate picture of what is staged, what is on-scene, and what is en route. In large USAR events, that picture degrades rapidly if it's not actively maintained.
• Interoperability starts at dispatch. Miami-Dade units, Broward County units, and Hatzalah may not share radio infrastructure. International teams will not. Dispatch needs to know which agencies are operating on which channels and ensure that information flows across those channel gaps, especially for safety-critical communications like evacuation signals during secondary collapse risk.
• Family notification and search coordination are dispatch functions during SAR. Families calling to report a specific unit number where their relative lived — "they're in 8C, is anyone looking at 8C?" — are giving search prioritization information. There needs to be a documented channel for that information to reach USAR sector commanders. Dispatch is often the intake point.
• Know when to hand off. Once an incident reaches a certain scale, the incident command structure absorbs the coordination function. Dispatch's role transitions from primary coordination to communications support for ICS. That transition needs to be explicit — dispatchers should know when ICS has taken over what functions, and what their residual responsibilities are during an extended operation.