

25 Years Of Know-How

Features
When the Fire Protocol was first rolled out in 2001, it wasn’t uncommon for fire chiefs to walk out of presentations, claiming it would never work for them. Comfortable in their own routines, they questioned why they should retrain their staff to do things someone else’s way.
But even in those early days, dedicated International Academies of Emergency Dispatch® (IAED™) Fire Protocol experts Mike Thompson and Gary Galasso could identify exactly why: The industry needed (and continues to need) standardization, prioritization of response, and a structured approach to life and property preservation driven by proven instructions for callers.
Paving the way with evidence-based protocols, the IAED has incorporated user feedback, research, and fire service industry evolution into the Fire Priority Dispatch System™ (FPDS®) we know today. Under the oversight of the IAED’s College of Fellows, Council of Standards, and International Cultural Committees, the FPDS has undergone eight major version releases and is now regarded globally as the leading standardized fire and life safety dispatch protocol system.
That growth didn’t happen by accident. It came from listening to professionals in the fire industry. Most notably, a period of significant evolution occurred when the user pool grew from 300–500+ agencies. The Proposals For Change (PFC) likewise accelerated with user input, advancing the protocol to become THE industry standard. Today, there are 668 FPDS users throughout the world.
“I often hear people say, ‘The Fire Service doesn’t change,’” Thompson said. “I used to say the same thing at one time myself, but I was wrong, and they’re wrong. They’re just not paying close attention. Today, we keep our finger on the pulse of the fire service industry so we’re prepared to address evolving elements like bigger and hotter wildland fires, fire suppression in varying building/structure types, electric vehicle fires1 and problems, fires involving solar panels, and lithium-ion batteries to name just a few.”
The National Fire Protection Agency provides a snapshot of the effect of fire across the United States, according to data from 20242:
• Local fire departments responded to an estimated 1.38 million fires in the United States.
• These fires caused an estimated 3,920 civilian fire deaths and 11,780 reported civilian fire injuries.
• The property damage caused by these fires was estimated at $19 billion.
• On average, a fire department responded to a fire somewhere in the U.S. every 23 seconds.
“Fire kills more people in the United States than weather-related events or natural disasters,” said Priority Dispatch Corp.™ (PDC™) Senior Implementations Manager Jay Dornseif. “Telling people how to get out of a burning building or helping them realize they are not in a safe location has become more important now than ever.”

Life and property preservation: Pre-Arrival Instructions
Of all the benefits provided by a unified protocol, one of the most crucial components is what happens on the line between callers asking for help and receiving that help. If an Emergency Fire Dispatcher (EFD) can provide instructions to keep a caller safe, that’s one fewer rescue situation for the fire department to address when they arrive.
“I tell people all the time, ‘If you don’t have this system, one thing you’re missing the most is the instructions we have,’” Thompson said. “We’ve got instructions for virtually every incident type you can encounter in our Fire Protocol—even more so than medical and police. We’ve done the research, seen the evidence, and incorporated the science into the actions people can take right now to improve their own situation before responders even arrive.”
Some agencies would say they have no need for these perceived “one-off” events. In an average multidiscipline comm. center where fire calls only represent about 10% of their call volume, they may feel prepared to handle these incidents well enough on their own. Maybe because they haven’t had one yet.
But centers lose their confidence in “well enough” when an inexperienced dispatcher without a proven protocol freezes as the caller asks what to do while stuck in her car on the railroad tracks. You can hear the frantic seconds pass and the train horn sounding, but “well enough” does little to make up for the sound of scraping metal in that dispatcher’s ears (a real, recent call).
“These protocol instructions are not just a want or a should, they’re a MUST,” Galasso said. “Get these dispatchers out of that untenable position of having to come up with something on the fly—because they don’t have a unified protocol—while fearing what could happen otherwise. The FPDS is there to help EFDs provide the best care in all situations, especially the challenging and uncommon ones.”
These high-risk, low-frequency events not only create a liability exposure for centers, but they instill an underlying fear in their dispatchers who are not properly equipped with a protocol to handle what may happen tomorrow: the disabled neighbor alone with smoke filling their home, the young mother and children trapped in a sinking vehicle, or the worker who can barely choke out the words that a building has collapsed on top of him. What will you tell them while they wait for help? When does it become too late?
“Unfortunately, people in these emergencies can’t always rely on common sense because these scenarios aren’t common,” Thompson said. “And it’s not only callers who get stuck mentally; it can happen to the dispatcher they rely on.”
There is an old phrase that sums this up nicely, but somewhat ominously, which Dr. Jeff Clawson, protocol founder, has taught over the years called “paralysis by (personal) analysis.” Unprotocolized dispatchers don’t usually “gap” in these situations, but start to unnecessarily repeat unimportant things, give off-the-wall advice, and even mimic the caller, “Okay, you said ….” Meanwhile something’s still burning, or someone’s still trapped.
Freelancing advice is also dangerous, and you don’t have to look far to see it play out. When wildfires wreak havoc on entire communities, simply instructing residents to “evacuate” doesn’t ensure they’re moving in the right direction. Ragtag, spontaneous instructions aren’t going to account for every eventuality, nor do they help the caller gain situational awareness. As Dr. Clawson has said for all three systems, “The protocol never has a ‘bad hair day’—and never forgets.”
“One of the things that I believe led us to look into the Fire Priority Dispatch System was some of our larger brush fires that we have in Ventura,” said Training Supervisor Jordan Roberts from Fire Communication Center Ventura County Fire Department (Camarillo, California, USA). “We needed some type of tool to handle large incidents like that, as well as the more routine, day-to-day incidents—fire alarms, structure fires— to have a more standardized response.”3
It’s often the situations beyond the standard where the FPDS becomes a lifeline.
“Our Pre-Arrival Instructions for ‘Sinking Vehicle,’ ‘Person in Vehicle on Fire,’ and ‘Trapped in Wildland Fire’ exist nowhere else in the world,” Thompson said. “And yet these incidents happen virtually every day in the U.S. and abroad.”⁴

Even communities that prepare well can often encounter complications. From these situations new improvements are developed and shared.
“When we were hit by Hurricane Harvey [in 2017], we had no good way to triage the incoming calls related to the weather, flooding, stranded in vehicles in floodwater, stranded in homes with rising water,” said Angela Burrer, PDC Implementations Project Manager, formerly District Chief–Communications, Cy-Fair Fire Department, Houston, Texas (USA).
Emergency Dispatchers rallied around, relying on the Service Call Protocol without dropping or missing emergency calls, but Burrer later asked the Fire Council of Standards if they had a better system for prioritizing responses during natural disasters.
“We didn’t need the Weather Protocol until we needed it,” she said.
It just so happened that such a protocol was already being utilized in a cultural version of the FPDS in Germany. After a few polishing iterations, Protocol 83: Weather and Disaster Situations was released internationally for all languages. Though it often stays in the back pocket, it came in handy for Burrer’s center during the Great Texas Freeze (widely known as Winter Storm Uri) in 2021, enabling better prioritization. Though only 1,050 cases have been handled on Protocol 83 according to the IAED Data Center, the beauty of a unified protocol system is that one agency’s experience can initiate and enhance the development of a tool available for every user throughout the world, so you’re never caught unprepared.

Prioritization of response
Unfortunately, the barriers to adopting a proven protocol are often based on emotion, not evidence. Specifically, fear of unknown outcomes and effects on call-processing times keeps some agencies from utilizing the Fire Protocol’s prioritization. In a world where “fast” is valued above “right,” the door is often shut before you can explain how to have both.
“I hear worries that using the FPDS is going to take too long,” Thompson said. “People think gathering critical information will slow them down, so they rely on a homegrown method of asking for little to no information to determine when, how, or what type of apparatus and manpower is sent. The results can be frustrating, sometimes delaying the right resources, which is unfortunately discovered after arriving on scene.”
This quick-send approach leaves a wide margin for error and waste. Agencies fail to determine what are truly nonemergent or lower-acuity calls for service that can utilize lower-priority responses and instead default to a mentality of “throwing everything we’ve got” hot and fast—at a significant cost—in equipment, personnel, and their safety. Likewise, they sometimes fail to determine what are emergent, high-acuity events that will benefit from a high-priority quick response.
“There’s no need to send multiple million-dollar apparatuses out for burned food,” Burrer said. “The FPDS’ prioritization allows you to configure the exact response you need for each incident, doing more, correctly, with less.”
Matching appropriate resources to the needs at the scene is particularly important in a season where both responders and equipment are in high demand. Currently, ordering replacement fire trucks may involve a three- or four-year delay due to manufacturing schedules, which means many agencies are trying to stretch their apparatus to last longer than originally planned.

Research on the FPDS shows that call and event type distribution data allows fire services to drive more effective training and make informed decisions on purchasing new equipment (e.g., prioritizing the purchase of a brush truck when learning that outside fire calls are even more common than structure fire calls).⁵
“In the ever-growing system of smaller budgets, longer lead time on replacement apparatus, and a reduction in personnel, the question becomes how you can afford not to prioritize your calls for assistance,” Burrer said.
The FPDS recognizes both sides of the coin, prioritizing responses while still sending early in the call.
“I’ve heard ‘It takes too long,’ or ‘There are too many questions,’ and really that’s not true,” said Nancy Lockhart, former Fire Operations Chief from St. Joseph County 9-1-1 (Mishawaka, Indiana, USA). “So if someone is thinking about making that change, go to a center that’s actually using it. Have them show you the data. Because what we perceive to be the problem or what we perceive to be a longer call-processing time and what is actually happening in the protocol are two totally different things. I can pull a report today that shows from opening a case to sending out an ECHO response is 30 seconds or less 90% of the time.”6
In fact, anyone can view the IAED’s Data Center dashboard, which provides aggregated, de-identified data from approximately 200 FPDS agencies, totaling more than 2.3 million calls. All ECHO calls are sent within 32 seconds—well below the 60-second benchmark established by the national standard for processing the highest-priority emergency events.
Dornseif knows these standards well, as he serves as the current chair of the NFPA 1225 committee. The 2022 edition of NFPA 1225, Section 15.4.4, states: “Emergency event processing for the highest prioritization level emergency events [explosions and structure fires] shall be completed within 60 seconds, 90 percent of the time.”7
FPDS studies have shown that in over 200,000 studied cases, median call prioritization time for all cases was 52 seconds, 96.2 percent of all cases had a time of 120 seconds or less, and 99.2 percent of all cases had a time of 180 seconds or less. ECHO-level calls had the shortest median prioritization time of 18 seconds, while BRAVO-level calls had the longest at 55 seconds.8 An additional study demonstrated that 90 percent of structure fire calls handled with the FPDS were prioritized within 90 seconds.9 However, it’s clear that time alone is not the only indicator of effective dispatch, as quality and type of information are also necessary to ensure the safest, most appropriate response.
“That’s the beauty of it,” Dornseif said. “The FPDS is built to send as quickly as is reasonably possible, but we go the extra mile and make sure we’re not wasting resources or causing additional delays by sending out the wrong resources.”

Standardization
Beyond better resource allocation, the FPDS provides a standardized foundation to EFDs, responders, and the public they serve. Though fire departments may assign their own unique responses and customize their response assignments, each citizen can expect the same thorough and professional interaction on the line, regardless of where or when they call.
Whatever the EFD’s background or level of experience (or lack thereof), complying with a standardized protocol ensures a level of service that never has a bad day, casts judgment, forgets, or misinforms.
“Without a standardized protocol to follow, dispatchers are only as good as the person who trained them,” Dornseif said. “With a higher turnover rate today, the next generation of dispatchers don’t always have access to the legacy person to give them experience anymore.”
Former IAED College of Fellows member Fred Hurtado, on a national television show, once said of one of the largest fire departments in the world, that their unprotocolized and informal dispatch training of sitting with more experienced dispatchers, “Just taught them to make the same mistakes as their predecessors.”
Relying on protocol, the EFD can avoid feelings of confusion, lack of confidence, and decision fatigue associated with undefined processes. The questions asked and instructions provided are the same for every caller in the same circumstances, setting the industry standard and meeting the public’s expectation.
“Our center [Parkland County Emergency Communication Centre (Canada)] has been an Accredited Center of Excellence in FPDS for 15 years, and it has brought both consistency and confidence to our call processing,” said Team Lead Coordinator Chelsea Davis. “Prior to the FPDS, calltaking often relied heavily on the individual calltaker's experience and judgment to determine what questions to ask and what instructions to provide. Rather than slowing us down, the FPDS has helped us gather critical information quickly and accurately while identifying potential scene safety concerns and providing responders with the information they need to prepare before arriving on scene.”
As Dr. Clawson taught in the early 1980s, “The trained and protocolized Emergency Dispatcher is actually the scene commander—at least until another professional gets to the scene!”
In cases of multidiscipline comm. centers, a standardized protocol enables Emergency Dispatchers to train efficiently, switch between disciplines seamlessly, and engage with responders more effectively. This interoperability eases the use of mutual aid during large incidents such as wildfires, serious traffic collisions, natural disasters, and mass-casualty events. Confidence in a standardized protocol puts the Emergency Dispatcher in the front seat to drive, coordinating elements remotely from the console.
“For us, the FPDS was the bridge between simply ‘taking a call’ and truly managing an incident,” said Michael Bronner, Assistant Chief of Operations at Springdale Fire Department (Arkansas, USA). “The real game-changer has been the FPDS components, which allow our dispatchers to stop being passive observers and start actively managing the scene during calltaking.”
The results extend beyond the comm. center. Sending the right resources, providing life-critical instructions to the caller, and gathering scene information means responders don’t have to establish control upon arrival, but merely transfer into it.
“By providing critical, structured instructions to the caller, our EFDs effectively mitigate hazards and size-up the scene before our units even arrive,” Bronner said. “This doesn't just improve our data collection; it empowers our EFDs to be the ‘true’ first, first responders on the scene, ensuring that the right resources are requested and the most vital information is in the hands of our crews en route."
Finally, a standardized protocol allows comm. centers to measure their performance with established Performance Standards as part of a quality assurance program. For many centers, this one element is a game-changer: conducting case review, identifying potential compliance errors, and improving performance collectively and individually.
Additionally, the IAED not only has systems for comm. centers to collect and review their own data (call prioritization times, distributions, trends, and other specialty reports), but they can also compare with the IAED’s Data Center, which currently shares aggregate data on over two million cases handled with the FPDS—the entire time and action sequences produced by ProQA®.
“Having a standardized approach supports all staff, regardless of their level of experience,” Davis said. “At the same time, [the FPDS] is flexible enough to allow us to work with our local administration to tailor response plans and ensure our processes are timely and align with the unique operational needs of our responding departments.”

Conclusion
Today’s callers are more dialed in than ever, relying on the voice on the line when seconds matter most. As the fire industry continues to evolve to meet the modern complexity and changing nature of the world around us, so, too, does the FPDS—due to the unique standards processes that continually evolve and improve the Fire Protocols.
By guiding callers with critical instructions, sending prioritized resources, and providing standardized care, our Emergency Fire Dispatchers are leading the response, proving we are, at least, ready for every call—before it even occurs.
Sources
1. Thompson, M. “Case Report: The FPDS and Electrical Vehicle (EV) Fires.” Annals of Emergency Dispatch & Response. 2022; Sept. 19. aedrjournal.org/case-report-the-fpds-and-electrical-vehicle-ev-fires (accessed Sept. 21, 2026).
2. Hall, S. “Fire Loss in the United States During 2024.” National Fire Protection Association. 2025; November. nfpnfpa.org/news-blogs-and-articles/nfpajournal/2026/02/12/us-fire-loss-2024a.org/news-blogs-and-articles/nfpajournal/2026/02/12/us-fire-loss-2024 (accessed Aug. 10, 2026).
3. “The Fire Priority Dispatch System.” International Academies of Emergency Dispatch. emergencydispatch.org/learn/emergency-priority-dispatch-system/fire-protocol (accessed Aug. 18, 2026).
4. Giesbrecht, G. G. “The Evidence Base for a New ‘Vehicle in Water’ Emergency Dispatch Protocol.” Annals of Emergency Dispatch & Response. 2016; March 20. aedrjournal.org/the-evidence-base-for-a-new-vehicle-in-water-emergency-dispatch-protocol (accessed Sept. 21, 2026).
5. Dornseif, J., Johnson, B., VanDyke, A., Robinson, D., Wiggins, T., Daubert, L., Hutchison, M., Crook, S., Sipple, K., Kalmbach, L., Scott, G., Gardett, I., Clawson, J. J., Olola, C. “The Distribution of a Fire Priority Dispatch System’s Call Incident Types and Priority Levels in Selected U.S. Fire Agencies.” Annals of Emergency Dispatch & Response. 2014; Aug. 12. aedrjournal.org/the-distribution-of-a-fire-priority-dispatch-systems-call-incident-types-and-priority-levels-in-selected-u-s-fire-agencies (accessed Sept. 21, 2026).
6. See note 3.
7. “NFPA 1225: Standard for Emergency Services Communications.” National Fire Protection Association. 2022.
8. Dornseif, J., Gardett, I. M., Scott, G., Grassi, R., VanDyke, A., Robinson, D., Wiggins, T., Daubert, L., Hutchison, M., Crook, S., Sipple, K., Kalmbach, L., Clawson, J. J., Olola, C. “Call Prioritization Time in a Fire Priority Dispatch System.” Annals of Emergency Dispatch & Response. 2015; March 22. https://www.aedrjournal.org/call-prioritization-time-in-a-fire-priority-dispatch-system (accessed Sept. 21, 2026).
9. Dornseif, J., Gardett, I. M., Scott, G., Toxopeus, C., Grassi, R., VanDyke, A., Robinson, D., Wiggins, T., Daubert, L., Hutchison, M., Crook, S., Sipple, K., Kalmbach, L., Clawson, J. J., Olola, C. “Call Prioritization Times for Structure Fires in a Fire Priority Dispatch System.” Annals of Emergency Dispatch & Response. 2016; Aug. 1. aedrjournal.org/call-prioritization-times-for-structure-fires-in-afire-priority-dispatch-system (accessed Sept. 21, 2026).
More Articles
Necessary, Not Sufficient
Basic telecommunicator training becomes more defined, but demands discipline-specific training and certification to actually practice on-line




