Response by townResponse by vehicle
Click a town to see its vehicles. Click a column heading to sort.
| Town | Vehicles | Call-outs | Average response | Inside 5 min | Over 5 min |
|---|
| Vehicle | Call-outs | Average response | Inside 5 min | Over 5 min |
|---|
Sample data · Built with Claude Dashboards on BigQuery; this copy runs in your browser. The company, vehicles and every figure are invented.
Data to —. “Today” is the latest day in the data.
Slowest town: —, averaging — with — of call-outs inside 5 minutes.
Inside 5 minutes means a recorded response of 300 seconds or less; anything slower counts as over 5 minutes. Changes compare with the same length of time immediately before, cut off at the same time of day.
Click a town to see its vehicles. Click a column heading to sort.
| Town | Vehicles | Call-outs | Average response | Inside 5 min | Over 5 min |
|---|
| Vehicle | Call-outs | Average response | Inside 5 min | Over 5 min |
|---|
Call-outs and average response by the hour the vehicle was dispatched. Shaded hours are night, 22:00 to 06:00.
Failed to load
On days when a vehicle's tracking was offline for 30 minutes or more, — of its call-outs took over 5 minutes, against — on days with under 10 minutes offline.
Night only is on: shift figures cover night shifts (18:00 to 06:00), the shifts that span 22:00 to 06:00.
Vehicles are counted in their home town. Click a town to see its vehicles.
| Town | Vehicles | Shifts | Rostered hours | Overtime hours | Overtime vs rostered | Staff cost |
|---|
| Vehicle | Shifts | Rostered hours | Overtime hours | Overtime vs rostered | Staff cost |
|---|
Night shifts rostered, beside call-outs dispatched between 22:00 and 06:00 and how many of those took over 5 minutes.
| Town | Vehicles | On night roster | Night shifts | Night call-outs | Over 5 min | Share over 5 min |
|---|
| Vehicle | Night shifts | Night call-outs | Over 5 min | Share over 5 min |
|---|
Each dot is a vehicle: minutes its tracking was offline in the period, against the share of its call-outs that took over 5 minutes. Click a dot to open its town.
Failed to load
Share of call-outs over 5 minutes, grouped by how long the responding vehicle's tracking was offline that day. A pattern worth investigating, not proof of cause.
Failed to load
Each call-out brought in — of fees and cost — in staff and fuel.
Revenue is invoiced monthly fees spread evenly over the days of the invoice month. Cost is shift cost plus fuel for vehicles based in the town, for whole days.
Today's call-outs stop at the latest data time, but shift and fuel costs cover the whole day, so today's per call-out figures run high.
Plan filter is on: revenue, clients and call-outs are for that plan. Cost per call-out still uses all of a town's call-outs, because staff and fuel are shared across plans.
Towns with the thinnest margin per call-out first. Click a town to see its vehicles.
Failed to load
| Town | Call-outs | Revenue | Staff cost | Fuel cost | Revenue per call-out | Cost per call-out | Margin per call-out | Clients over plan | Overdue |
|---|
| Vehicle | Call-outs | Staff cost | Fuel cost | Staff + fuel | Cost per call-out | Km driven |
|---|
Call-outs in the last 30 days (—) against the call-outs the plan includes per month. Always 30 days, whatever period is selected, because the allowance is monthly.
| Client | Town | Plan | Included per month | Call-outs, 30 days | Over by |
|---|
Clients with an invoice unpaid past its due date as at the latest data day, longest overdue first. The last column counts every invoice on file that was paid late or is overdue. Not affected by the period.
| Client | Town | Plan | Days overdue | Amount overdue | Invoices overdue | Late or overdue, all invoices |
|---|