Quality assurance in most comm centers works like this: pull a random sample of calls, score them against a checklist, document the results, deliver feedback. The checklist measures whether the dispatcher asked the right questions in the right order, verified the address, provided pre-arrival instructions, and met time benchmarks.
All of that is measurable. All of it is documentable. And almost none of it captures the thing that actually determines whether the call went well.
The judgment gap in dispatch QA
The most consequential decision a dispatcher makes on a critical call is usually not on the QA checklist. It's the moment they recognized that a routine-sounding call wasn't routine. It's the decision to upgrade before the caller asked them to. It's the choice to dispatch additional resources based on a gut read of the caller's voice, the time of day, the location, or the combination of all three.
That decision doesn't have a checkbox. It doesn't have a time benchmark. It often doesn't even appear in the CAD notes because it happened in the dispatcher's head before they typed anything. But it's the decision that put the right resources on scene before the incident escalated.
Your dispatch QA program can't measure it. So your QA program ignores it. And because your QA program ignores it, your training program doesn't develop it.
Compliance is the floor, not the ceiling
Protocol compliance keeps you out of liability trouble. It ensures minimum standards are met. It creates a defensible record. These are real, important functions of any 911 quality assurance program and I'm not arguing against them.
But compliance is the floor. The difference between a competent dispatcher and an excellent one lives above the floor, in the judgment space where the protocol runs out and the dispatcher has to think. QA programs that only measure the floor never see the ceiling.
What better quality assurance looks like
Pull your critical incidents - the calls where the outcome was either unusually good or unusually bad. Don't score them against the checklist. Instead, reconstruct the dispatcher's decision chain. What did they know, when did they know it, what did they do with it, and what was the result?
Some of those decisions will align perfectly with protocol. Others won't appear in any protocol at all. The second category is where the real learning lives - both for the dispatcher and for the center's training program.
The best dispatch QA isn't a compliance check. It's a decision audit. And it feeds directly into the training program, because every consequential decision that gets surfaced becomes a teaching scenario for the rest of the team.