Responder Match

Blue-light ETAs for every available unit, learned from real emergency driving, so you send the one that gets there first.

From the call to the unit to send.

You send

Incident location Where the call is.
Units available And where they are, from your CAD.
Vehicle profile Car, fire appliance, etc.

You get

Units ranked by blue-light ETA

1 B – 8 min Fastest
2 A – 15 min Nearest
3 C – 17 min

Here the nearest, A, is across the river and has to go round by a bridge, so B gets there first.

Nearest isn’t always fastest.

Built on Blue Light Routing, powered by data from real emergency driving, so we know what an emergency vehicle can and can’t do.

Blue-light road speeds

How fast emergency vehicles really drive each road under blue lights, at different times of day, learned from real runs. Every ETA is built from those speeds.

Exemptions

Bus lanes, bus gates, contraflow, restricted turns and pedestrianised zones. A unit further away can be quicker through them.

The vehicle

A width limit a car fits through can send a fire appliance the long way round.

Through your CAD, or from the API directly.

Through your CAD

Ranked units in the system your dispatchers already use, if your CAD supplier offers it.

Direct API

Call it from your own systems.

For developers

Send the call and the units. Get them back ranked.

Here’s the idea behind Responder Match in a few lines of JSON.

Match request

{  "incident": [51.75, -1.26],  "vehicle": "fire_appliance",  "units": {    "A": [51.76, -1.26],    "B": [51.74, -1.28],    "C": [51.77, -1.23]  }}

Match response · ranked by blue-light ETA

{  "ranked": [    { "unit": "B", "eta_s": 360 },    { "unit": "A", "eta_s": 540 },    { "unit": "C", "eta_s": 660 }  ]}

Tell us what you need to know.

Which unit to send, or where cover is thin. We’ll tell you straight whether Responder Insights can answer it, including when it can’t.

Talk to us

UK-based · Hosted only in UK and EU datacentres