“You Have 30 Minutes”

The Atlanta transcript shows the gap between receiving the call and dispatching to the threat location rather than the pay phone. The first instinct was to find the caller rather than to move on the threat. That decision cost time the dispatcher did not have.

Most centers have a bomb threat protocol that includes: notifying the supervisor, contacting the threat location, initiating law enforcement response, and contacting the bomb squad. The question is the sequence and who owns each step. In Atlanta, the confusion about whether the dispatcher or a field unit was responsible for notifying state police — and the absence of confirmation that it happened — is the single most correctable failure in the transcript.

For your center: pull your bomb threat protocol. Does it specify who notifies the venue directly? Who calls the bomb squad? Who confirms state or federal partner notification? Are those steps checked off by the dispatcher, or does the protocol assume someone else is handling it?

This is not primarily a technology failure — it is a training failure. The dispatcher and operator did not know how Centennial Olympic Park was stored in their system. For a venue that had been the centerpiece of the Atlanta Olympics for two weeks and that was drawing 15,000 people a night, that gap is a pre-incident planning failure.

CAD address matching for major venues, event locations, and non-standard sites is something that should be validated before events begin. How is your county fairground stored? Your sports stadium? Your downtown concert venue? If a caller says “the park by the river” or the name of a new development that was just built, does your dispatcher know how to find it?

The practical fix: before any major planned event in your jurisdiction, verify with your CAD administrator how the venue is addressable in your system. Dispatch it. Confirm it resolves. That exercise takes five minutes and could matter enormously. Atlanta had the Olympics in their city and did not do it.

The Centennial Park bombing produced a partial evacuation because a private security guard acted correctly without knowing about the 911 call, while a 911 call was being processed without any direct link to the security team on the ground at the park. Two parallel warning systems that were not connected to each other.

At large pre-planned events, best practice is to establish a unified command structure that integrates private event security with local law enforcement, and to have a direct radio or phone link between the event’s security command and the 911 comm center. If Jewell had been able to call a direct line to the officer in charge at the park rather than flagging down a GBI agent he happened to find, and if that officer had been in contact with the comm center, the evacuation might have started faster.

For your jurisdiction: what is your pre-planned event protocol? Does your comm center have a direct contact at the event security command post? Do they have a way to reach you other than 911? Is there a designated liaison between the event and law enforcement before the event starts?

This is a mass notification question. Verbal instructions from officers moving through a crowd of 15,000 people at a concert are the slowest possible evacuation method. The most effective tool available was the concert sound system — if it had been commandeered to announce a clear evacuation order, it would have reached all 15,000 people simultaneously rather than requiring officers to personally direct each cluster of attendees.

From the comm center perspective: who has the authority to order a venue to use its public address system? Is that call made by the dispatcher, the supervisor, the incident commander on scene, or nobody? Does your center have contact information for the event sound production operator? In 1996, this was not standard. In 2024, it still varies by jurisdiction.

Additionally: given that only 10 of the 22 minutes between the 911 call and detonation were actually available for evacuation after the delay, the practical window for moving 15,000 people was never realistic without immediate, large-scale notification tools. That math matters for how you plan large event response.

Centennial Olympic Park had no metal detectors, no bag checks, and no formal perimeter screening for a park that was open to the public 24 hours a day during the Games. The security investment went to the ticketed venues, the athlete compounds, and the official event sites. The public gathering space — described as the “spiritual heart” of the Games — was open access.

Rudolph walked in carrying a backpack full of pipe bombs. He set it down. He walked away. He called 911 from a pay phone. The “massive security effort” did not prevent any of that. What stopped the death toll from being far higher was one alert private security guard.

For dispatchers and training coordinators: visible security presence is not the same as effective threat detection. The lesson for comm centers is that the first notification of an actual threat often comes from someone who has no formal role in security — a vendor, a passerby, a security guard from an adjacent property. Your protocols should be as ready to receive and act on those calls as they are to receive calls from law enforcement.

This question sits at the edge of dispatch operations but is worth raising: the information environment after a major incident is shaped by what law enforcement communicates, and the comm center is often the first repository of information about who made what call, who was at a scene, and what was reported. Dispatch recordings, CAD notes, and call logs become investigative materials. They can also become leak material.

Jewell’s wrongful public accusation destroyed three months of his life and is now studied as a case study in media irresponsibility and law enforcement information leakage. The anonymous source who identified him to the Atlanta Journal-Constitution was never publicly named. The FBI later acknowledged it had no direct evidence implicating him.

For comm centers: your records are sensitive. Your personnel have access to information that, if disclosed without authorization, can cause real harm to real people. Post-incident information security — who can discuss a call, to whom, in what context — is a protocol question that belongs in your training alongside call handling and dispatch procedures.

This is an actionable pre-event checklist item. Before the event opens, someone should test-dispatch a call to the venue in your CAD and confirm it resolves correctly. If it does not, work with your CAD administrator to add or correct the address before the event begins. This takes minutes and is directly traceable to one of the most documented dispatch failures in modern American history.

Also worth confirming: does your center have a direct contact number for the event’s security command post, separate from 911? Is that number in your CAD notes or on a printed reference at the console?

The Atlanta transcript shows a field unit being told to notify state police rather than the dispatcher making that call directly. There is no documented confirmation in the transcript that state police were actually reached. In a protocol with multiple parallel notification requirements, the weakest link is always the one that depends on someone else to make the call without verification.

Best practice: bomb threat protocols should assign specific notification responsibilities by name or role, not by “advise the appropriate agencies.” And each notification should be confirmed back to the dispatcher and documented in the CAD record, not assumed to have happened because someone was told to do it.