Fleet tracking · Cambridge

Fleet tracking for taxi fleets in Cambridge

Live driver pins, geofences, and replay — accurate to 200ms. Configured for Cambridge City Council Hackney + PHV Licensing.

Fleet tracking in Cambridge is the live driver pins, geofences, and replay — accurate to 200ms, configured against Cambridge City Council Hackney + PHV Licensing and the operating reality of a 0.6k-vehicle market. TaxiCloud Fleet Tracking ships live driver-pin tracking, geofenced coverage zones, route replay for incident review, and aggregate fleet-utilisation analytics. Driver GPS pings stream over WebSocket at 200ms latency. For Cambridge specifically, the feature reads from regulator-aware booking, dispatch, and reporting surfaces — no bolt-on integration, no separate console.

Fleet tracking in Cambridge — the operating reality

Fleet tracking ships against the Cambridgeshire operating geography as a structural object. Fleet tracking is the foundation that makes live dispatch, customer-app live tracking, and dispute resolution all work. TaxiCloud's tracking layer is engineered around 200ms ping latency — driver GPS streams to the WebSocket gateway, fans out to dispatch board, customer app, and supervisor view, and updates pins in lockstep. The result is a tracking experience that matches Uber and Bolt on responsiveness rather than the polling-refresh feel that legacy dispatch platforms ship with. In Cambridge, the feature posts cleanly against Cambridge City Council Hackney + PHV Licensing quarterly returns, vehicle inspection cycles, and the 580-vehicle scale that defines the market. STN airport flows integrate natively where applicable.

How TaxiCloud delivers fleet tracking in Cambridge

Operators in Cambridge typically run fleet tracking on TaxiCloud after a 6-10 day migration off iCabbi, Autocab, Cordic, or TaxiCaller. Geofences are first-class objects. Coverage zones (your operating area), airports (terminal pickup zones), restricted areas (Old Town in Edinburgh, congestion zones in London), and corporate-account boundaries all configure as geofences with entry / exit events. The dispatch board flags geofence events in real time; AI Copilot uses geofence state to rank reassignment suggestions; the customer app surfaces geofence-triggered information (e.g. "Your driver has entered the airport pickup zone"). The dispatcher impact is highest in the Cambridge operating tempo because Cambridge City Council Hackney + PHV Licensing compliance overlays the standard PHV regulatory posture, and fleet tracking surfaces the resulting reports through the same dispatch flow rather than as a separate finance task.

FAQ

Fleet tracking in Cambridge — questions answered.

How does Fleet tracking work in Cambridge?
Fleet tracking in Cambridge reads from the live dispatch board, the customer-facing booking widget, and the Cambridge City Council Hackney + PHV Licensing compliance reporting layer in a single tenant. Driver app streams GPS pings over WebSocket at 200ms intervals. The Cambridge configuration is preset for the city's 580-vehicle market and the Cambridgeshire operating geography.
Is Fleet tracking compliant with Cambridge City Council Hackney + PHV Licensing?
Yes. Fleet tracking is calibrated for Cambridge City Council Hackney + PHV Licensing reporting, audit, and renewal cycles. Vehicle inspection deadlines, driver-licence audits, and the local quarterly return format ship pre-configured. Format updates land in-sprint when the regulator changes requirements.
What does Fleet tracking cost for a Cambridge fleet?
Fleet tracking ships on every TaxiCloud plan — Starter through Pro Ultra. Prezzi trasparenti £49-£349/mese. Most Cambridge fleets run Pro (£149/€55/$59/A$89 month) or Pro Max (£349/€395/$449/A$629 month). No setup fee on Starter or Pro; month-to-month contracts; fleet tracking configuration in Cambridge is included.

Share this article

Pronti quando lo sei tu

Dispatch in modalità autopilota.

Prova gratuita di 14 giorni. Cancel anytime.

47 flotte iscritte questo mese · Parla con il commerciale
Fleet tracking in Cambridge — TaxiCloud · TaxiCloud