Every comm center has at least one procedure that nobody can explain the origin of. Someone, at some point, decided it was the right approach. It got written into the SOP or absorbed into the oral tradition. And now it's part of the operational DNA of the center, defended not on its merits but on its tenure.
"We've always done it this way" isn't just a cliche in emergency communications. It's an operational philosophy that preserves procedures past their expiration date, insulates bad habits from scrutiny, and punishes the people who ask "why?" by treating the question as disrespect rather than professional curiosity.
How procedures outlive their purpose
A procedure gets created for a reason. Maybe the reason was a specific incident. Maybe it was a technology limitation. Maybe it was a supervisor's preference that got codified into policy. The reason was valid at the time.
Then the technology changes. The staffing model changes. The CAD upgrades. The radio system migrates. The procedure remains, because updating it requires someone to notice it's outdated, have the authority to change it, navigate the approval process, retrain the staff, and accept responsibility for the new version. Leaving it alone requires nothing. Inertia wins by default.
The result is centers running 2026 incidents on procedures designed for 2008 technology and 2012 staffing models. Nobody is doing this intentionally. It happens because updating procedures is nobody's primary job, so it becomes nobody's job at all.
The culture that protects the status quo
In many centers, questioning an established procedure is received as questioning the people who established it. If the day-shift supervisor with 20 years of experience built this workflow, and the night-shift dispatcher with 18 months suggests it could be better, the 18-month dispatcher is going to lose that conversation regardless of who's right.
This isn't unique to dispatch - every organization with a strong operational culture develops defensive patterns around established practices. But in dispatch, the stakes are different. An outdated procedure in most workplaces produces inefficiency. An outdated procedure in a comm center can produce a delayed notification, a missed resource, or a coordination failure during an incident where seconds matter.
The same culture that says "we've always done it this way" is the culture that misses the new hire's good idea, dismisses the lateral transfer's observation about how their last center did it better, and treats innovation as a threat to institutional identity rather than a contribution to operational quality.
The annual procedure audit nobody does
Once a year, take your SOP manual and ask three questions about every procedure in it. First: does this procedure still match the technology we're using? If it references a system we've replaced, it needs to be updated or deleted. Second: does this procedure still match our staffing model? If it assumes a position configuration we no longer run, it's creating a gap between what the policy says and what the floor does. Third: when was the last time someone used this procedure during a live incident, and did it work?
That third question is the important one. Procedures that haven't been tested against real incidents accumulate invisible assumptions. They assume conditions that may no longer exist, capabilities that may no longer be available, or coordination patterns that haven't been exercised.
The audit isn't exciting work. But it's the difference between a center that runs on current reality and a center that runs on institutional memory - and institutional memory doesn't update itself.