Resgrid Blog
Resgrid.com Blog | Open Source Dispatch
At some point, every public safety director gets the same rude lesson. A big incident doesn't fail because responders stop working. It fails because coordination breaks before effort does. A wildfire jumps a county line. A flood knocks out roads in two jurisdictions at once. Dispatch starts fielding requests for barricades, buses, engines, shelter support, …
At 2:13 a.m., the call volume jumps, someone is trying to update a paper contact list from memory, one supervisor is on the radio asking for unit status, and another is texting a group thread that half the team muted months ago. The incident itself may be manageable. The information flow is what starts to …
Grant season hits, and the station office turns into an evidence locker. Paper sign-in sheets are stuffed in binders. Training attendance lives in a text thread. Community event hours sit in somebody's email. Response time from standby crews was never written down at all. Then a funder asks one simple question: how many volunteer hours …
You're probably dealing with this right now. A neighborhood keeps calling about slow response times. Crews swear they're getting out the door fast. Dispatch says traffic is the problem. City leadership wants an explanation, and all anyone has are scattered incident notes, radio memories, and a few screenshots from last month. That's how agencies stay …
When a major incident hits, nobody wants to be standing in the doorway of the command post asking a basic question that should already be answered: who on this shift is fully cleared to respond? In public safety, that question isn't clerical. It's operational. If one EMT, dispatcher, rescue tech, or driver is out of …
Your phone rings before dawn. A neighboring jurisdiction has a warehouse fire, your own crews are already committed, and dispatch is trying to figure out who can send people, what equipment can cross the line, who pays for overtime, and whether incoming personnel can legally operate under your command. If those answers live in old …
For first responders, CAD stands for Computer-Aided Dispatch, the system used to create calls, track unit status, and manage dispatch operations across tools like SMS, WhatsApp, or Slack. In other fields, CAD can also mean Computer-Aided Design or Coronary Artery Disease, which is why dispatch teams need to be clear about the context fast. If …
You're probably dealing with some version of this right now. A call starts small, then stretches. More units arrive. Mutual aid checks in. Someone asks for traffic control, someone else asks for medical, and two supervisors start giving different directions to the same crews. That's the moment when incident command responsibilities stop being a training …
The call comes in. A storm has knocked out a feeder line, your dispatch board is half updated, one team is texting in a group thread, another is on radio, and the supervisor is working from a printed continuity plan that was last revised months ago. Nobody is sure which generator site was already checked, …
The tones drop, three callers report the same highway pileup, and your dispatch floor shifts from routine to overload in seconds. One person is trying to confirm location details, another is calling mutual aid, someone else is checking unit availability, and the radio traffic starts stepping on itself. The team is experienced, but the process …