These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Taxi / Ride-hailing Platform
- Features
- Driver dispatch
Driver dispatch
Connect an accepted match to the correct booking, driver and vehicle.
OverviewMy ride bookings×
Taxi / Ride-hailing Platform · Driver dispatch
New
My ride bookings
Bookings
| Record number | Subject | Starts at | Ends at | Status | Revision | |
|---|---|---|---|---|---|---|
| BKN-66325 | Draft bkn-630 | 10 Oct | 19 Oct | Draft | 940 | |
| BKN-21458 | Review bkn-396 | 20 Oct | 26 Oct | Review | 620 | |
| BKN-87649 | Approved bkn-300 | 11 Oct | 15 Oct | Approved | 260 | |
| BKN-12028 | Executed bkn-946 | 03 Oct | 08 Oct | Executed | 290 | |
| BKN-48832 | Rejected bkn-412 | 10 Oct | 12 Oct | Draft | 100 |
6 of 6 records
Draft bkn-630Bookings · BKN-66325
DraftStarts at10 Oct
Ends at19 Oct
Revision940
What you can do
Confirm the people and vehicle for the ride
An accepted driver match needs an operational record that the dispatch desk can inspect. Dispatcher checks the driver and vehicle, then connects them to the booking through its resource line. The line carries a confirmation time, a capacity note and a revision so colleagues can understand what was assigned and when it was confirmed.
Driver availability and vehicle availability answer different questions. A driver may be Available while the intended vehicle is in Maintenance. A vehicle may be Available while the driver’s record is Inactive. Check both records before confirming the match, together with the booking interval and any competing assignment the desk is already managing.
How the work is organized
- Review the proposed match. Dispatcher opens the booking resource and checks the linked driver and vehicle. Read the capacity note against the requested work and verify the current record identities.
- Confirm the assignment. Record the accepted match and its confirmation time. Assigned identifies the resource selected for the booking; Active identifies an assignment being used during the trip.
- Escalate an unresolved match. If no eligible match can be confirmed, give Operations Reviewer a clear reason and source booking. Keep the unresolved request visible for dispatch follow-up.
What to agree during setup
Agree the availability checks for each service zone. Fleet Coordinator maintains driver activity, license class and expiry, while vehicle records identify class and service status. Decide which license and vehicle-class combinations your operating policy allows. Those decisions need local operating review before staff rely on them for assignment.
Define how dispatchers check overlapping intervals and how an accepted match from a driver channel reaches the booking resource. A driver channel is a connection to configure. Establish what staff should do when a match arrives after a cancellation or when a driver changes vehicles before pickup. The confirmation must still refer to the intended booking revision.
Check the handoff on an actual case
A van is chosen for a station transfer. Before confirmation, Fleet Coordinator moves it to Maintenance after a reported defect. Dispatcher checks the current vehicle status, stops that match and looks for another suitable vehicle. The same driver’s availability cannot make the original van ready for service.
When a replacement is accepted, Dispatcher confirms the correct vehicle on the booking resource and checks the ride interval again. Operations Reviewer examines any escalation raised during the change. Trip Coordinator should then see the resource actually used, with a confirmation time that explains the handoff. Rehearse this case while the original resource line is still visible so staff do not mistake an earlier proposal for the current assignment.
What your team sees
- Driver match queue — Proposed and Assigned resource lines that connect a booking to its driver and vehicle.
- Available drivers — Drivers marked Available, with activity and license details for the dispatch check.
- Available vehicles — Vehicles marked Available, with class and plate details for confirmation.
Follow the work through
Rehearse booking to assignment and the resource release in cancellation and correction. Review fleet upkeep when eligibility changes during a shift.
What it keeps track of
Data model- Booking resources
- Resource lines attached to a booking, with capacity and confirmation.
- Bookings
- Ride bookings with their lifecycle, quoted fare, assigned resource and revision.
- Drivers
- Drivers eligible to accept ride requests.
- Vehicles
- Vehicles available for taxi and ride-hailing service.
- Resources
- Bookable ride resources: vehicles, drivers and partner fleets available for taxi bookings.
- Review decisions
- Independent review decisions recorded against a booking revision.
Who uses it
Permissions- Dispatcher
- , Fleet Coordinator, Operations Reviewer.
- Dispatcher
- Confirms the match.
- Fleet Coordinator
- Keeps the driver and vehicle records current.
- Operations Reviewer
- Handles the decision when a match needs escalation.
Set up Taxi / Ride-hailing Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.