Trip status lived in phone calls between hubs. Detentions surfaced after the invoice dispute, not during the trip. Enterprise customers demanded API-level visibility as a condition of contract renewals.
A control-tower platform ingesting GPS, hub scans, and driver-app events into one live trip timeline; exception engines that alert on deviation, delay, and detention as they begin; and customer-facing tracking with SLA analytics.
Exceptions first
Ops teams do not need another map with 3,000 dots on it. They need the eleven trips that are about to go wrong. The control tower leads with exceptions — deviation, delay, detention — and lets everything healthy stay quiet, which is the only arrangement in which a live view of a national fleet is still readable at nine in the morning.
One timeline from three sources
GPS pings, hub scans and driver-app events each describe part of a trip and none of them describes all of it. They arrive late, out of order, and sometimes not at all. Reconciling them into a single ordered timeline — including the stretches where a vehicle simply goes quiet, which are the interesting ones — is the work that everything above it depends on.
Detention is a data problem before it is a billing dispute
A detention charge argued after the invoice is a negotiation nobody wins. The same detention flagged as it begins is an operational decision somebody can still act on: call the consignee, reroute the next trip, stop the clock. Moving detection to the moment it starts is where the 41% reduction came from.
Visibility became a contract term
Enterprise customers had made API-level tracking a condition of renewal, which turns a reporting feature into a commercial requirement with a deadline attached. Six integrations later, those customers read shipment status from inside their own systems instead of telephoning a hub to ask.