Emergency Services
Cutting Response Times: What Dispatch Software Can and Can't Fix
Routing algorithms get the attention, but most minutes are lost before a vehicle ever moves. A look at where dispatch time actually goes.
Every ambulance service we have worked with wants the same number to come down: the interval between a call landing and a crew arriving. The instinct is to reach for better routing. In practice, routing is rarely where the minutes are hiding.
Where the minutes actually go
Break the interval into its parts and it usually reads: call intake, triage, unit selection, crew acknowledgement, travel. Travel is the only segment a map optimises, and on urban roads a better route saves seconds. The larger losses sit in the handoffs — a dispatcher retyping an address, a crew waiting on a radio confirmation, a supervisor unsure which unit is genuinely free.
One call record, three applications
That is why our dispatch product is three applications against one call record rather than a single map. When a dispatcher assigns a unit, the crew's device already has the address, the patient details and the destination. Nothing is re-entered, and nothing waits on a voice channel to be confirmed.
The connectivity problem nobody plans for
The other unglamorous factor is connectivity. Crews lose signal in basements, stairwells and underground car parks — exactly where they are when the status matters most. A dispatch app that cannot write offline will silently drop a status change and leave the board showing a unit that is no longer where it says it is. Queue the change locally, sync on reconnect, and the control room keeps an honest picture.
Software cannot make a vehicle move faster. It can stop the vehicle waiting on information it should already have.
Set expectations accordingly. Dispatch software earns its place by removing the pauses between people, not by outsmarting traffic. Measure the handoffs, fix those first, and the total comes down on its own.
