Before the Call — Pulse Nightclub, Orlando

The Pulse shooting is the defining modern example of an incident type transition during a MCI. Active shooter protocol says move resources fast, limit command and control delay, push for rapid neutralization. Hostage negotiation protocol says slow everything down, buy time, keep the subject talking. These are contradictory postures applied to the same incident within the same hour.

• Incident type transitions must be declared, not assumed. At some point during the Pulse response, someone had to make a command decision that this was no longer a straight active shooter call and that negotiation protocol was in effect. That decision determines how dispatch positions resources, manages information flow, and coordinates agencies. If it's never declared clearly, dispatch is trying to run two protocols simultaneously with different agencies pulling in different directions.
• Your job in a type transition is information management. You are the node connecting law enforcement command, fire/EMS staging, negotiators, and incoming 911 calls. When the incident type changes, the information you're surfacing and routing changes. Know what questions the new incident type requires: for a hostage situation, that includes number of hostages, their location, any reported weapons beyond the confirmed shooter, and any communications from inside.
• The shooter calling 911 is a protocol event. What does your center's protocol say about a subject-of-an-incident calling 911 during an active event? Who does that call go to — the floor dispatcher, a supervisor, directly to negotiators? Has your center ever trained on that scenario?
• Brief incoming units on type changes in real time. Units staged outside Pulse during the first hour were briefed on an active shooter situation. As the incident transitioned to a hostage standoff, that briefing had to be updated. Dispatchers carrying the radio traffic for staged units need to push type-change information proactively, not wait to be asked.

This is a scenario that falls outside most standard dispatch training, but it has happened at Pulse, at other barricaded subject incidents, and it will happen again. The subject of the call — the threat — is also a 911 caller. Your center is now a communication channel to someone who has killed people and is holding others hostage.

• The call is a resource, not a distraction. Every time the subject calls or is reached, that is an opportunity for negotiators to gather information: number of hostages, any demands, the subject's mental state, any movement or intent. Dispatchers patching those calls are part of the negotiation infrastructure. Understanding that your role in those moments is to facilitate communication — not to respond emotionally or argue — is training, not instinct.
• Document every contact with the subject. Time of call, duration, what was said, what the subject's demeanor was. This documentation feeds incident command's picture of the situation and becomes part of the after-action record.
• Coordinate call-back attempts with negotiators, not unilaterally. At Pulse, negotiators were tracking that the subject answered approximately every 10th call. That cadence was information that informed strategy. If dispatch is making independent call-back attempts without coordinating with negotiators, it can disrupt a pattern that the negotiation team is using.
• Be prepared for the calls to be disturbing. A subject who has killed dozens of people is calling your center. He may say things that are threatening, ideologically charged, or designed to manipulate. Your job is to stay neutral, document accurately, and route the call appropriately — not to process those statements emotionally on an active console. There will be time for that later. Not now.

False reports in a mass casualty event are not rare — they are nearly predictable. Hundreds of people in a high-panic state are calling 911 with incomplete, second-hand, or actively incorrect information. Some reports are honest misperceptions. Some are miscommunications. Occasionally, some are deliberate. Your job is not to evaluate them as true or false in the moment — your job is to document, route, and flag confidence levels.

• Distinguish confirmed from unconfirmed when you relay information. "Caller reports a second shooter at ORMC — unconfirmed" is a different piece of information than "second shooter at ORMC." Both are information. Only one has a verified source. That distinction needs to survive the relay chain from dispatch to command to responding units.
• Source and time-stamp every significant report. When information is wrong, the after-action investigation will trace it back to where the incorrect information entered the dispatch chain. Your documentation is your record that you relayed what was told to you, with accurate attribution. Don't editorialize, but do document the source.
• When multiple callers report the same thing, it does not confirm it. Panic is contagious and calls from the same scene often share the same incorrect information. "Multiple callers reporting" does not mean independently verified — it may mean one person told others what they believed and those others all called 911.
• Have a protocol for conflicting information. If you receive a call that directly contradicts information already in the command channel — "I'm inside, there is no second shooter, that's wrong" — that conflict needs to reach incident command immediately, flagged as conflicting, with both sources documented. Don't resolve the conflict yourself. Surface it.