Resgrid Blog
Resgrid.com Blog | Open Source Dispatch
A crew can do everything right on a call and still get burned by equipment that was never ready. The airway bag looks stocked until a seal is broken and a key item is missing. The reserve unit shows as available until the battery charger fails its check. A rescue tool is assigned on paper, …
You're probably dealing with this already. A unit is en route, another is staging, dispatch is fielding updates from three directions, and someone important is still relying on a phone call chain or a consumer chat thread to push operational information. That works right up until the moment it doesn't. In routine operations, bad communication …
The call comes in, the crew rolls, and someone reaches for a critical item that should have been there. The seal is broken. The box is empty. Or worse, the item is there but expired. That kind of miss doesn't feel like an inventory problem in the moment. It feels like a readiness failure. In …
You're probably dealing with some version of this right now. Calls come in from different places. One supervisor gets a text. Dispatch gets a phone update. Someone in the field radios that conditions changed, but that update never makes it to the person assigning units. Later, everyone agrees the response felt messy, yet nobody can …
At 2:17 a.m., the storm hits, alarms start coming in, and the room changes fast. One dispatcher is juggling radio traffic. Another is writing addresses on a legal pad because the whiteboard is already full. A supervisor is trying to figure out which crew is currently available, not just which unit was supposed to clear …
A city festival starts well enough. Traffic posts are staffed. Medical has a treatment tent. Security has a radio channel. Then the crowd shifts after a weather alert, one volunteer team loses contact, and three different supervisors start updating three different spreadsheets. Dispatch knows units are moving, but operations doesn't have a clean view of …
You usually notice the compliance problem after the incident is over. A reimbursement packet is due. An internal review has started. A grant file needs backup. Someone asks for the timeline, the personnel roster, the unit activity log, the patient handling record, and the reason one status change never made it into the final report. …
A call drops, units are moving, and then someone says the reserve ambulance has a charging issue and the frontline rig is already down for a repair nobody documented clearly. That's how many agencies discover their maintenance process isn't really a process. It's a mix of memory, sticky notes, paper check sheets, and a spreadsheet …
You probably already know the problem. Your people completed ICS courses, passed the quizzes, and walked away with binders or PDFs. Then six months later a real incident hits, the radio traffic gets messy, resources start moving without clear assignments, and the person in command has to think, talk, track, and prioritize all at once. …
It's the end of the shift. The rigs are back in service, the station has finally gone quiet, and someone still has to finish the incident report. That's usually the moment NFIRS becomes everybody's least favorite task. Most departments treat nfirs fire reporting like a compliance chore. Fill the boxes, pick the codes, send it …