Live map
The fleet as it is right now: trips drawn as lines, drivers as markers that move, and alerts as they happen.
The live map is the fleet as it is right now. Every trip in progress is drawn as a line with its stops, every driver is a marker that moves, and an alert list fills in as things go wrong. You will find it under Live Fleet in the sidebar.
It is a watching surface rather than an editing one: nothing on this page changes a trip. What it does is tell you which trip to go and open.
Who can do this
- Role
- Administrators
The map itself needs no feature flag. driver_live_presence — together with the tenant’s own opt-in under Customization → Live Tracking — gates only the layer that shows clocked-in drivers who are not on a trip. Without it the map still shows every driver who is on a trip.
Behind the driver_live_presence feature flag. Ask support to enable it for your organisation.
What is on the map
For each active trip, Cooriroo draws the route plan’s path, a marker for each stop, and a marker for the driver at their last reported position. Clicking any of them opens the trip in the right-hand panel with its progress, next stop and estimated arrival.
Across the top, a row of counters summarises the same data: how many drivers are moving, how many are stopped, how many have lost signal, how many are clocked in but not on a trip, and how many stops are done out of the day’s total.
| On trip | Clocked in | Offline | |
|---|---|---|---|
| What it means | Driving a trip right now | Clocked in, between trips | Clocked in, but no recent position |
| Where the position comes from | Trip GPS, high frequency | Off-trip presence pings | The last presence ping received |
| Needs the presence layer | No | Yes | Yes |
| Clicking it opens | The trip panel | The driver panel | The driver panel |
How the map stays live
A WebSocket carries position updates, trip progress and alerts as they happen; the Live indicator in the top right reflects that connection, and drops to Offline when it is lost. Reconnection is automatic, with a growing delay between attempts.
The socket only updates trips that are already on screen — it has no "a trip just started" event — so a periodic reload runs alongside it. While connected that reload is a slow safety net, roughly every five minutes. While disconnected it speeds up to every thirty seconds, because it is then the only source of fresh positions. The refresh control reloads on demand at any time.
Rosters, search and filters
The left rail holds two rosters behind a pair of tabs — one for trips, one for drivers — with a count on each. Both stay loaded when you switch, so search text and filter choices survive moving between them.
- Filtering trips changes the map. A trip filtered out of the roster is removed from the map as well, which is how you isolate one round on a busy morning. Filters cover status and priority, and search covers the trip and its driver.
- Picking a driver follows them. The map centres on their last position. A driver on a trip opens the richer trip panel; an idle one opens a driver panel with their last-seen time and shortcuts to locate, message or notify them.
Alerts
Alerts arrive over the same connection and stack in the right-hand panel. A failed trip and a vehicle breakdown are treated as critical; a route deviation, a signal loss and a failed stop as warnings. You can dismiss one or clear them all.
This list is a live feed, not a record. It is per session — reloading the page starts it empty, and an alert you dismiss is not filed anywhere. The underlying events live on the trip itself, where they can be reviewed properly.
Turn on the presence layer
Tracking a driver who is not on a trip is a privacy decision, so it is off until two separate switches say otherwise.
- 1
Check the entitlement
The controls below are locked, not merely off, when your plan does not include live presence. No tenant setting will unlock them.
- 2
Switch on live presence tracking
Customization → Live Tracking → PresenceThis is the tenant’s opt-in. With it off, the server does not accept off-trip positions at all, so there is nothing to show and nothing stored.
- 3
Set the ping interval
How often a clocked-in driver’s device reports while off-trip. It defaults to ten minutes and can be set between one minute and one hour. Off-trip reporting is deliberately far less frequent than the on-trip cadence, and cannot be configured to match it — the point is a rough "where is everyone", not a second trail.
- 4
Set the staleness threshold
How long without a fresh position before a driver reads as Offline. It defaults to twice the ping interval and is never allowed below one full interval, so a driver reporting exactly on schedule cannot flicker offline between pings.
- 5
Choose how long off-trip history is kept
Off-trip positions are deleted automatically after this window, which defaults to 30 days. On-trip history is a separate record and is not governed by it.
When something looks wrong
The clocked-in driver layer never appears
One of the two presence gates is off, or no driver has reported an off-trip position yet.
Check Customization → Live Tracking. A locked toggle means the entitlement is missing from the plan. If both gates are on, give it one ping interval — the layer populates as devices report.
A trip is running but no line is drawn for it
The trip has no route plan, or the plan was invalidated by a recent edit.
The map draws the stored path, so a trip without one shows only its driver and stops. Open the trip and calculate a route; see Route optimization for when this happens on its own.
A driver shows as Signal Lost
No GPS has arrived from their trip for longer than the signal-loss threshold.
The default is two minutes, and it is configurable per tenant. It usually means coverage, a phone in a pocket, or a device that has gone to sleep — it does not by itself mean the trip has stopped.
A trip I just started is not on the map
The live connection has no "trip started" event, so new trips arrive on the next reload.
Use the refresh control rather than waiting. The same applies in reverse: a trip that has just finished drops off at the next reload, not the instant it completes.
Terminology
Your organisation can rename these. If your screens say something else, this is what they mean here.
- Trip
- One journey with an ordered list of stops. Some tenants call these routes, runs or jobs.Rename it in Settings → Terminology
- Driver
- The person carrying out a trip. Some tenants call these operators, couriers or crew.Rename it in Settings → Terminology
- Stop
- One place a trip calls at. Some tenants call these drops, calls or visits.Rename it in Settings → Terminology
- Driver status is derivedWhy on trip, clocked in and offline are computed rather than set by hand.
- Route optimizationWhere the path on the map comes from, and why it sometimes disappears briefly.
- The driver appWhat the driver’s device reports, and when it reports it.
- Trips and dispatch problemsSymptoms and fixes for trips that will not start, route or progress.