Pull up your center's SOP for a pursuit. Read it. Time yourself. Now imagine reading it while a unit is calling out speeds, cross streets are changing every three seconds, the sergeant is asking you a question on the phone, and there are two pending calls on your screen.
If the SOP is more than one page, it fails the operational test. Not because the content is wrong - because the format is unusable at the speed the job requires.
The dual-audience problem
Most standard operating procedures in comm centers are written to serve two audiences simultaneously: the dispatcher who needs to execute the procedure in real time, and the attorney who needs to reference it three years later during litigation. These audiences have opposite design requirements.
The dispatcher needs brevity, clarity, and a decision tree that fits on one screen. Step one leads to step two. Condition A produces Action A, Condition B produces Action B. No preamble. No definitions section. No "purpose and scope" paragraph. Just the operational sequence in the order they'll need it.
The attorney needs comprehensive documentation. Definitions, scope, applicability, authority, exceptions, cross-references to other policies, revision history, approval signatures. Every possible scenario addressed. Every edge case covered. Legal defensibility requires completeness.
When you write one document for both audiences, you get a 14-page policy that's legally excellent and operationally useless. The dispatcher who needs to make a decision in 30 seconds cannot parse a 14-page document. So they don't read it. They learn the procedure from their CTO, who learned it from their CTO, and the SOP sits in the binder gathering authority it never exercises.
The workaround culture
Every comm center has an informal set of procedures that actually govern daily operations. They're not written down. They're transmitted verbally from experienced dispatchers to new ones. They're the operational shortcuts, the practical interpretations, the "here's what the SOP says but here's what we actually do" knowledge that makes the shift work.
This workaround culture exists because the formal procedures don't serve the operator. It's not defiance - it's adaptation. Dispatchers are pragmatists. They'll use whatever tool actually works at operational speed, and if the formal tool doesn't work at operational speed, they'll build their own.
The risk is obvious: the workaround culture is unwritten, inconsistent, and invisible to leadership until something goes wrong and the gap between the SOP and the actual practice gets exposed in a review.
Writing procedures for the person at the console
Separate the legal document from the operational document. The comprehensive policy can exist for the attorneys and the accreditation file. The operational version - the one that lives on the dispatcher's screen or on the wall next to their console - should be a one-page decision tree or a quick-reference card that covers 90% of the situations they'll encounter.
Write the operational version first. If you can't explain the procedure in one page, the procedure is too complex for real-time execution and needs to be simplified - not just reformatted. Then expand it into the legal version. Most centers do this backwards, writing the comprehensive document first and never producing the operational one at all.
Your dispatchers will follow the procedure they can actually use. Make sure the procedure they can actually use is the one you want them following.