Dispatch liability comes down to one question: when a 911 call goes wrong, who answers for it, and on what grounds? In most states, dispatchers and the agencies that employ them are protected from ordinary negligence claims. That protection has limits. It varies by state, and it depends heavily on whether your center followed its own written procedures. Immunity is not a plan. Documented protocols, training and quality assurance are.
This guide is for municipal leaders, communications center directors, EMS and fire chiefs, and the attorneys who advise them. It explains how liability works in practice and where we see agencies exposed. It also covers what you can do now, before anyone files a claim. It is general information, not legal advice. Your county or city attorney should apply your state’s law to your center.
TL;DR
- Most states shield 911 dispatchers and public safety answering points (PSAPs) from ordinary negligence claims, but gross negligence, willful or wanton conduct and intentional acts generally remove that shield.
- The rules are set by state statute and state court rulings, so your exposure depends on where you operate.
- Courts and expert witnesses increasingly measure performance against recognized industry standards, including the APCO/NENA QA/QI standard released in 2025.
- Written policies that nobody audits can hurt you. A working QA/QI program is your best evidence that the center does what it says it does.
- NG9-1-1, video, sensor data and AI add new liability questions that your policies need to address now.
Table of Contents
- Why immunity is not the whole story
- How state law shapes your exposure
- Design versus implementation: where protocols decide cases
- The standard of care for emergency dispatch
- QA/QI: the best evidence you have
- When a bad call becomes a case
- New technology, new exposure
- A practical plan for the next 90 days
- Our perspective
- How we can help
- FAQ
- Sources
Why immunity is not the whole story
The common view is simple: dispatchers are public employees, public employees are immune, so there is nothing to worry about. The first half of that is mostly right, and the conclusion is wrong.
Findlaw’s overview of dispatcher suits explains the baseline. In general, people do not owe each other a duty to help in an emergency, and that includes 911 call centers. In most states, dispatchers are immune from civil liability for negligence. A plaintiff who can show gross negligence, willful or wanton conduct, or intentional harm may get past that protection, depending on the state.
There are three reasons leaders should not stop reading there.
- The exceptions are where lawsuits are built. Plaintiffs’ attorneys do not plead ordinary mistakes. They plead a pattern: a call-taker who skipped a required question, a supervisor who never reviewed calls, a policy that was written and ignored.
- Immunity varies by statute. Some states protect the PSAP and its employees by one statute. Others route emergency medical calls through a different law. Courts sometimes have to decide which applies.
- Defending a claim costs money even when you win. Discovery, depositions, expert reports and staff time come out of the same budget that pays for your call-takers.
How state law shapes your exposure
There is no single national rule. Two examples show how much the wording matters.
North Carolina’s statute on limitation of liability opens with a broad protection for PSAPs and their employees, directors, officers, vendors and agents, and then carves out cases of gross negligence or wanton or willful misconduct. Read the full text of your own state’s equivalent. Note who is covered, including vendors, and note what is excluded.
In April 2025, the New Mexico Supreme Court addressed which statute governs dispatcher liability for emergency medical calls. According to the court’s release, the justices unanimously concluded that the Emergency Medical Services Act governed the question and that the Enhanced 911 Act had no relevance to a dispatcher’s handling of those calls. The practical lesson reaches beyond New Mexico. A center can believe it is covered by one law and discover in litigation that a different one controls.
We recommend a short exercise for every agency attorney and center director:
- Identify every statute that could apply to your PSAP, including 911 funding and surcharge statutes, EMS acts and general tort claims acts.
- Note what each says about negligence, gross negligence and willful misconduct.
- Note whether it covers your contracted vendors, your medical director and your private partners.
- Ask your attorney how recent appellate decisions in your state have read those statutes.
Design versus implementation: where protocols decide cases
Legal commentators often describe a distinction that matters to every dispatch leader. Decisions about how to design an emergency system, such as how many call-takers to fund or which protocol suite to adopt, tend to receive broader discretionary protection. Decisions about how the system is carried out on a given call are more exposed. That is where a dispatcher has a duty to follow the process the agency chose.
That is why a protocol matters twice. If your call-takers follow a written, medically approved protocol and you can prove it, you have a strong account of what happened. If they deviate and nobody noticed, the protocol becomes the yardstick the plaintiff uses against you.
The pattern we see in assessments is consistent. Courts and experts look at whether the center operated according to its own stated procedures, not only at the outcome. A center with a thick policy manual and no audit trail is in a worse position than a center with a leaner manual that it demonstrably enforces. A policy you do not audit or enforce can become a liability trap instead of a protection.
The standard of care for emergency dispatch
If a case does get past immunity, the question becomes what a reasonable dispatch center should have done. The Academy of Emergency Dispatch’s research journal argues that a standard of care for dispatch exists. In its words, it developed over time and through litigation into a reflection of society’s expectations of an emergency dispatch system. Ignorance of the standard is no defense.
In practice, expert witnesses draw that standard from sources like these:
- ANSI-approved standards from APCO and NENA, many of which are indexed on the NENA standards page.
- The medical, fire or police protocol suite the agency adopted, and the agency’s own written directives.
- State training and certification requirements, where they exist.
- Documented QA/QI results for the specific call-taker and the specific type of call.
No single federal mandate governs how every 911 dispatcher is trained. Training is decentralized across states and localities. National guidance still sets a professional baseline. APCO’s Public Safety Telecommunicator 1 course, now in its 8th edition, is a 40-contact-hour course that covers foundational topics including liability, call processing and emerging technologies. Because each agency builds its own program, each agency also carries the burden of showing that the program is sound.
QA/QI: the best evidence you have
In November 2025, NENA announced the availability of the ANSI-approved APCO/NENA standard for establishing a QA/QI program in emergency communications centers. The announcement describes recommended best practices for implementing a program that evaluates the performance of public safety communications personnel. Leaders should read it, and so should their attorneys. A published national standard gives experts on both sides a common reference.
Many agencies treat QA/QI as a chore, a monthly sample of calls that someone has to score. Think of it differently. A QA/QI program is the record that shows your center finds its own problems and fixes them. The National 911 Program has noted that measuring a center only by whether calls are answered and incidents are dispatched within time-defined standards will not be enough to measure processing efficiency going forward, and that PSAPs will need to adapt their quality programs.
What a defensible program looks like
This checklist reflects what we look for when we assess a center. It is not a legal standard.
| Element | What good looks like | The question a plaintiff’s expert asks |
|---|---|---|
| Written directives | Current, reviewed on a schedule, signed off by medical or operational leadership | When was this last updated, and who approved it? |
| Call review | A defined sample, scored against the protocol, with feedback to the call-taker | How many calls were reviewed for this employee? |
| Corrective action | Documented coaching, retraining and follow-up | What happened after the deviation was found? |
| Training records | Initial and continuing education tied to job tasks | Was this call-taker trained on this protocol? |
| Data and trends | Compliance scores, trends and gaps reported to leadership | Did leadership know about the problem before this incident? |
| Technology review | Policies updated when new tools, data feeds or automation are added | Did the center assess the risk of this tool before using it? |
The last column is the one to take seriously. If the honest answer to several of these is that you do not know, the gap is worth closing before an incident forces the question.
When a bad call becomes a case
Most dispatch claims follow familiar patterns. Public discussion of dispatcher errors has long centered on wrong directions given to responding crews, call-handling failures and breaches of caller privacy. Our own commentary on a public case involving a 911 reply and a fatal outcome shows how quickly a single call can become a question about the whole system.
When we look at these situations, the questions that matter are rarely about one person. They are about how the center is run.
- Was the dispatcher given the tools, staffing and time to follow the protocol?
- Did the protocol fit the type of call?
- Had earlier deviations been identified and corrected?
- Was the dispatcher trained and certified for the discipline involved, such as emergency medical, fire or police dispatch? The National 911 Program notes that many 911 professionals hold those certifications.
A dispatcher who made an error inside a well-run system is in a very different position from a dispatcher who made the same error in a center with no QA, short staffing and outdated directives. Fairness to employees and protection for the municipality point the same way: build a system that sets people up to succeed.
New technology, new exposure
Next Generation 9-1-1 changes what a call-taker receives and what the agency is expected to do with it. Text, video, sensor data and automated alerts all arrive in the center. The National 911 Program’s toolkit on the integration of technology describes how information must be analyzed, interpreted and organized before it is entered into a computer-aided dispatch system. More data does not remove that human step. It makes it harder.
Three questions belong on every leadership agenda:
- Who is responsible for data that arrives but is not seen? If a video feed was available and no one watched it, what does your policy say?
- How is automation supervised? If software suggests a priority or a response, the call-taker needs to know when to trust it and when to override it, and the override needs to be documented.
- Do your QA/QI reviews cover the new inputs? A program built for voice-only calls will miss risks in the rest.
We cover this ground in more detail in our guides on AI in public safety and on how to optimize public safety communication systems.
A practical plan for the next 90 days
You do not need to fix everything at once. Here is a sequence that works for most municipal centers.
- Days 1 to 15: Map your legal ground. Ask your attorney to summarize the immunity statutes, exceptions and recent appellate decisions that apply to your PSAP and its vendors.
- Days 15 to 30: Inventory your directives. List every protocol and written directive, its last review date and its owner. Retire what is out of date. Fix what contradicts actual practice.
- Days 30 to 60: Audit the audit. Pull your last six months of QA/QI records. Check that reviews happened, scores were shared and corrective action was documented. Compare your program against the 2025 APCO/NENA standard.
- Days 60 to 75: Check training alignment. Confirm that each call-taker’s training and certification records match the disciplines they handle.
- Days 75 to 90: Review technology risk. Document how each new data source and automated tool is supervised, and update your policies and QA scoring accordingly.
For a deeper look at how to evaluate a center, see our guide on how to assess emergency communications centers. If you are planning new construction or a redesign, our piece on designing a high-performance 911 dispatch center covers the operational side. For the broader context of dispatch inside the EMS system, read The Role of Dispatch in EMS.
Our perspective
We have spent more than 32 years working with public safety agencies, and one pattern holds up. The agencies that fare best when scrutiny arrives did not rely on a legal shield. They could show their work.
Immunity is a legal question, and your attorney owns it. Everything else is operational. Do your call-takers have the training and support to follow the protocol? Does your leadership see the data? Do you fix what you find? Those questions decide whether a bad day becomes a crisis, and they decide something more important: whether the next caller gets the help they need.
We also want to be fair to the people on the headset. They make decisions in seconds, with partial information, often for someone on the worst day of their life. A good liability program is not built to blame them. It is built to give them clear protocols, enough staff, honest feedback and leaders who read the numbers. That serves the public, it serves the employee, and it serves the municipality.
If you take one step this quarter, make it an honest review of your QA/QI program. Most centers find gaps. Finding them yourself is far better than having someone else find them for you.
— Mike
How we can help
The Public Safety Consulting Group (PSCG) works alongside municipal leaders, EMS agencies, fire departments, emergency managers and attorneys. We help identify operational gaps in communications and EMS systems, and we support the work from the first assessment through deployment. Our Operational Risk Reduction service is built for this kind of review. Our 911 communications consulting work covers dispatch and communication center evaluation. Attorneys who need an experienced EMS expert witness can find that service and our full list of offerings at thepscgroup.net.
FAQ
Can 911 dispatchers be sued?
Yes, but it is difficult. In most states, dispatchers and their employers are immune from civil liability for ordinary negligence. That immunity generally does not cover gross negligence, willful or wanton conduct or intentional harm. The details depend on your state’s statutes and court decisions, so ask a local attorney.
Does immunity protect a dispatch center that ignores its own protocols?
Do not count on it. Courts and experts often look at whether the center followed its own written procedures. Deviation from a specific protocol is a common focus of challenges. Your attorney can tell you how courts in your state treat that issue.
Is there a national training standard for 911 dispatchers?
No single federal standard applies to every dispatcher. Training and certification are set largely by state and local governance. National organizations offer baselines, such as the APCO PST 1 course, which is 40 contact hours. Agencies build programs that fit their local requirements.
What is a QA/QI program and why does it matter for liability?
QA/QI is the structured review of call handling to measure performance and correct problems. The 2025 APCO/NENA standard sets out recommended components. A documented program shows that your center identifies and corrects gaps, which is the evidence leaders want if a call is questioned.
Do we need an expert witness after a dispatch incident?
Often, yes. Whether a dispatcher’s actions met the standard of care in a high-stress call usually takes specialized knowledge of protocols and industry standards. Attorneys on either side commonly retain someone with direct EMS and communications experience. Reach us at thepscgroup.net if you need that support.
Sources
- Can I Sue a 911 Dispatcher? (FindLaw)
- G.S. 143B-1413, Limitation of liability (North Carolina General Assembly)
- New Mexico Supreme Court release on 911 dispatcher civil liability, April 21, 2025
- Is There a Standard of Care and Practice for Emergency Dispatch? (AEDR Journal)
- NENA Standards
- APCO/NENA Standard for the Establishment of a QA/QI Program for ECCs (NENA)
- APCO Public Safety Telecommunicator courses
- Workforce Optimization: A Smarter Approach (911.gov)
- Telecommunicators and Training (911.gov)
- The Operational Integration of Technology and Tools (911.gov)
