Dispatch measuredin seconds.
A connected digital mobility platform that transforms a traditional taxi operating model into real-time dispatch across passengers, drivers and operators in the Greater Toronto Area.
Where the story starts.
A taxi operator in the Greater Toronto Area set out to move from a traditional operating model to a connected digital mobility platform. Taxi operations depend on seconds: a dispatch platform must understand passenger location, available vehicles, driver status, geographic zones, scheduled bookings, journey status, communications and ETAs at once. For the passenger the promise is simple — a car arrives. Underneath, every element has to agree in real time.
Traditional operations leaned on manual dispatching. Every zone, booking and driver was tracked by hand.
Conventional taxi operations involved significant dispatcher intervention — manual dispatching, geographic zone complexity, scheduled bookings, driver assignment and disconnected phone systems. Tracking was inconsistent, passenger visibility was limited and driver availability had to be managed by hand. Moving to real-time operations meant modelling location, zones, driver status, booking type and ETA as one connected system rather than a set of separate phone calls.
How the platform is wired.
The path a single request travels — each step an engineering decision.
The applications behind it.
Passenger application
Pickup location, destination, immediate and scheduled bookings, ETA, trip status, driver info, notifications and booking history.
Driver application
For dedicated driver devices and tablets: authentication, availability, job assignments and acceptance, pickup, journey progression, zone awareness, navigation support and driver status.
Dispatcher platform
The operational heart: fleet visibility, booking queues, geographic views, driver availability, scheduled trips, assignment controls and operational interventions.
Administration platform
Drivers, vehicles, geographic zones, users, permissions, trip data, operational configuration and reporting.
Real-time and maps layer
Event-driven updates, location services, mapping and push notifications keeping passengers, drivers and dispatchers in sync.
The hard problems we solved.
Not screens — the difficult, load-bearing engineering underneath.
Geographic dispatch
The GTA contains operational zones influencing driver assignment; identifying a vehicle accounts for location, zone, driver availability, booking type and ETA together.
Real-time state
Managing location update frequency, latency and live state so fleet, bookings and journeys stay accurate second by second.
Mobile field constraints
Treating battery consumption, failed connectivity and location update behaviour on driver devices as core product problems.
Scheduled versus immediate
Reconciling immediate bookings with scheduled trips, dispatcher overrides and geographic rules within one assignment model.
Intelligent dispatch direction
Creating a pathway toward AI-supported dispatch that can evaluate demand, driver location, historical trip patterns, ETA, scheduled demand and zone coverage to recommend optimal assignments.
Architecture, not a logo wall.
What became possible.
A connected platform uniting passengers, drivers and dispatchers
A shift from manual dispatch toward data-driven mobility operations
Real-time fleet visibility and geographic, zone-aware assignment
An architecture ready for AI-supported intelligent dispatch
The services this drew on.
What this demonstrates — CodeFacts can build operationally critical platforms where real-time data, maps, mobile applications, workflow and optimisation must work together.