Register the passenger request
Record requested pickup window, supplied location, destination description, contact route and access note.
Workflow blueprint
Taxi dispatch records should separate a request, an offer and a reported trip event
A dispatch handoff ribbon, not vehicle tracking, driver clearance, regulated pricing, emergency response or trip-completion proof.
Preserve the passenger-supplied request, each driver offer, expiry, acceptance, revised instruction, reported milestone, exception and fare question.
TL;DR — Preserve the passenger-supplied request, each driver offer, expiry, acceptance, revised instruction, reported milestone, exception and fare question.
Offer the trip with an expiry
Keep recipient, vehicle claim, issue time, response and dispatcher decision for every offer.
Attribute each reported milestone
Separate arrival, passenger contact, start, wait, drop-off and no-show reports by source.
Hand exceptions to authorised owners
Bundle changed locations, disputes, lost-property notes and fare questions without deciding them.
Page-specific decision aid
A trip request, offer, driver response, reported milestone, exception and fare handoff ribbon
The ribbon follows an airport transfer through two declined offers, one acceptance, a revised terminal, a driver-reported arrival and a fare question. Requested, offered, accepted and reported states keep their own clocks so messages cannot masquerade as physical events.
- ✓A driver acceptance is not vehicle arrival.
- ✓A location message is not GPS evidence.
- ✓An estimate is not an authorised fare.
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Declined and expired offers remain in the ribbon
- ✓Driver reports never become GPS evidence
- ✓Estimated amounts stay outside regulated fare authority
- ✓Licensing screening vehicle status route safety payment and completion proof excluded
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow