Before the Call — Boston Marathon Bombing

The Boston Marathon's medical infrastructure had been refined over decades of running a world-class event through a major metropolitan area. It wasn't a document — it was a practiced system with assigned roles, tested protocols, and relationships built over years. The communications layer of that system is what this exercise focuses on.

• WebEOC as the shared situational platform. WebEOC — Boston's emergency operations coordination tool — was activated within one minute of the first blast because there was a pre-established protocol for activating it, and the people who needed to activate it knew exactly what to do. The shared situational picture it provided was available to every participating agency within minutes. At Route 91, no equivalent shared platform existed for the event.
• Pre-negotiated hospital patient distribution. Every receiving hospital in the Boston area had been included in pre-event planning. They knew the patient distribution protocol, they had pre-positioned surge capacity, and they had direct communication channels to EMS coordination. The result was that 30 red-tag patients were distributed across multiple facilities with no single hospital overwhelmed. This protocol was not improvised — it was executed.
• Staged medical resources as first-response infrastructure. Boston EMS had teams, equipment, and a Medical Director staged at the marathon before the race started. When the blast occurred, medical care began within seconds — not minutes after dispatch — because the resources were already there. The dispatch role in the first minutes was coordination and mutual aid activation, not primary resource mobilization.
• Mutual aid network pre-activated by protocol. 73 ambulances committed within 6 minutes. That number is only possible if the mutual aid network is pre-established, the staging areas are pre-designated, and the activation protocol is known to all participating agencies before the event. Dispatch activated a network that already existed — it didn't build one under fire.
• Annual rehearsal is the mechanism that makes plans functional. A plan that exists on paper and has never been practiced is not an operational plan — it is a document. The Boston Marathon medical plan was rehearsed annually. Every participating dispatcher, medical coordinator, and hospital administrator knew their role because they had played it before. Rehearsal is the investment that converts planning into performance.

The second device hold at Boston is one of the most studied single decisions in American mass casualty response. It was the right call — there was a second device. It was made in under 60 seconds, under extraordinary pressure, with incomplete information. And it was made because Dr. Serino had a protocol for it and the authority to execute it.

• Dispatch must be a participant in second device protocol, not just a recipient of it. When a second device hold is issued, dispatch has immediate responsibilities: broadcasting the hold to all responding units, halting the movement of additional resources into the scene perimeter, coordinating with law enforcement for device sweep, and maintaining communication with the Medical Director on hold status. These are not improvised — they are protocol steps that must be pre-assigned.
• The hold creates a second communications challenge: managing the perimeter. When patient movement is halted, there are patients on the scene, medical personnel staged at the perimeter, and additional resources converging. Dispatch must manage that perimeter — preventing additional exposure while maintaining the resources needed for the moment the hold lifts. This requires active channel management, not passive monitoring.
• The hold lifts on authority, not on assumption. At Boston, the hold was lifted when law enforcement confirmed that the immediate perimeter was clear. Dispatch should not assume a hold has lifted because time has passed or because field units resume movement. The lifting of a second device hold should be an explicit communication from the designated authority — and dispatch should confirm it before resuming normal patient movement.
• Pre-incident briefing on second device protocol for all agencies. The second device hold only works if every agency responding to the scene understands it, respects it, and knows who has the authority to lift it. A fire crew that doesn't know the hold is in effect, moving patients toward the perimeter, creates exactly the exposure the hold was designed to prevent. Pre-incident briefing is how every responding agency enters the scene with the same protocol.

The JFK Library fire is the secondary incident management test that Boston passed quietly. In the chaos of an active mass casualty scene, a simultaneous report of a third explosion at a separate location is exactly the kind of information that can degrade a response — if dispatch allows it to. Boston didn't.

• Secondary incident triage is a dispatch skill. When a report of a possible third device arrived at 2:56 PM, dispatch had to make an immediate assessment: is this confirmed, is it connected, does it require diversion of resources from the primary scene? The correct answer — treat as a secondary incident, dispatch a separate resource, maintain primary allocation — required both situational awareness and the discipline not to over-react to unconfirmed information.
• Unconfirmed secondary incidents do not automatically escalate. The JFK Library fire was not confirmed as an explosion. It was reported as one. The distinction matters operationally: an unconfirmed report warrants investigation and a designated response, not a wholesale redirection of primary scene resources. Dispatch must hold that distinction clearly, communicate it clearly to incident command, and resist pressure to treat unconfirmed reports as confirmed facts.
• Communication clarity prevents secondary degradation. If Incident Command at the finish line believed a third device had detonated at the JFK Library, their decision calculus changes — resource requests, perimeter management, patient movement. Dispatch's role is to communicate the accurate status: possible secondary incident under investigation, separate resources dispatched, primary scene resources not diverted. That clarity is a specific communications function, not incidental.
• The false alarm as a training opportunity. The JFK Library fire turned out to be a mechanical failure unrelated to the bombing. That outcome isn't knowable in real time. The training lesson is not "it was fine because it wasn't real" — it's "the process was correct." Treat as secondary, investigate with dedicated resources, protect primary allocation, communicate status accurately. That process is correct regardless of what the investigation finds.

The Hennebury call is the end of a four-day communications story that began at Boylston Street. For four days, the Boston-area communications infrastructure had been managing an event of unprecedented scale — a mass casualty scene, a citywide manhunt, the killing of an MIT police officer, a firefight in a residential neighborhood, and a metropolitan shelter-in-place. The resolution came from a single civilian noticing something wrong and calling 911.

• The high-stakes civilian caller requires a specific handling approach. David Hennebury was calling about the most wanted person in America, from a backyard in a city that had just emerged from shelter-in-place after four days of crisis. The dispatcher receiving that call had to simultaneously: assess the caller's safety, confirm the location, understand what he was describing, and immediately escalate without alarming the caller or causing him to take action that could be dangerous. That is a high-skill call under extraordinary circumstances.
• Precision at the point of resolution matters enormously. The address, the access point, the exact location of the boat in the yard — these details, extracted accurately from Hennebury in the first minutes of the call, are what allowed 20,000 law enforcement personnel to converge on a specific point rather than a general neighborhood. Dispatch accuracy at the resolution point of a manhunt is as operationally significant as dispatch accuracy at the initiation.
• Caller safety management in an active threat context. Hennebury had already seen blood and a body under the tarp. He was in proximity to a wounded, dangerous suspect. Dispatch managing his safety — keeping him calm, moving him away from the boat, keeping him on the line without creating urgency that might cause him to act — was a direct life-safety function. The handling of his location and movement in the first minutes of that call required active, deliberate management.
• The civilian caller as a sensor network. Over four days, thousands of Boston-area residents were the eyes and ears of the investigation. Tips, observations, and reports flowed through 911 and other channels continuously. Hennebury's call was the decisive one — but it came after thousands of others that had been triaged, assessed, and followed up. The communications infrastructure that handled four days of sustained high-volume investigative support is itself a training subject.