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
- Data model
The tables behind Taxi / Ride-hailing Platform
Taxi / Ride-hailing Platform ships with 20 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 20
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Ride bookings
Bookings owns the ride interval, organization, staff owner and revision. Ride requests.Parent links rider and address details to that booking.
Driver dispatch
Booking resources.Parent references Bookings, while Driver and Vehicle reference Drivers and Vehicles. Resources holds fleet and partner identities; Bookings.Counterparty references Resources. Routes describes service corridors within an organization.
Trip tracking and completion
Trip tracking events.Booking references Bookings. Trip completion evidence references both Bookings and ride requests. Record attachments retains a related record text reference and the file or URL used as supporting evidence.
Fare and payment evidence
Payment evidence.Parent references Bookings. Provider event ID identifies the provider evidence; Type, amount USD, Currency and Status describe the component being examined.
Fleet upkeep
Vehicle defects, vehicle inspections, vehicle maintenance plans and fuel transactions reference Vehicles. Vehicle defects.Owner references team members.
Review and operations
Review decisions stores source table, source record and source revision as the decision context. Operation receipts stores Action, result state and external reference. Organizations, team members and Users establish the operating organization and staff links.
Every table, by feature
- Ride bookings5
- Driver dispatch6
- Trip tracking and completion7
- Fare and payment evidence5
- Fleet upkeep6
- Review and operations7
- Shared and settings2
- Bookings
Ride bookings with their lifecycle, quoted fare, assigned resource and revision.
Linked to Organizations, Team members, Resources - Ride requests
Domain-specific ride requests supporting confirm an accepted driver match.
Linked to Bookings - Organizations
Operating organizations that own taxi bookings, resources and team members.
- Team members
Internal staff who prepare, review and execute ride-hailing operations.
Linked to Users, Organizations - Resources
Bookable ride resources: vehicles, drivers and partner fleets available for taxi bookings.
Linked to Organizations
- Booking resources
Resource lines attached to a booking, with capacity and confirmation.
Linked to Bookings, Drivers, Vehicles - Bookings
Ride bookings with their lifecycle, quoted fare, assigned resource and revision.
Linked to Organizations, Team members, Resources - Drivers
Drivers eligible to accept ride requests.
Linked to Organizations - Vehicles
Vehicles available for taxi and ride-hailing service.
Linked to Organizations - Resources
Bookable ride resources: vehicles, drivers and partner fleets available for taxi bookings.
Linked to Organizations - Review decisions
Independent review decisions recorded against a booking revision.
Linked to Organizations, Team members
- Ride requests
Domain-specific ride requests supporting confirm an accepted driver match.
Linked to Bookings - Trip tracking events
Location and status events recorded during a taxi trip.
Linked to Bookings - Trip completion evidence
Evidence captured when a ride-hailing trip completes.
Linked to Bookings, Ride requests - Booking resources
Resource lines attached to a booking, with capacity and confirmation.
Linked to Bookings, Drivers, Vehicles - Bookings
Ride bookings with their lifecycle, quoted fare, assigned resource and revision.
Linked to Organizations, Team members, Resources - Record attachments
Evidence files attached to bookings and ride operations.
Linked to Organizations - Operation receipts
Stable operation receipts proving each executed ride-hailing action.
Linked to Organizations, Team members
- Payment evidence
Provider payment evidence for a booking: authorization, capture, refund or void.
Linked to Bookings - Bookings
Ride bookings with their lifecycle, quoted fare, assigned resource and revision.
Linked to Organizations, Team members, Resources - Trip completion evidence
Evidence captured when a ride-hailing trip completes.
Linked to Bookings, Ride requests - Record attachments
Evidence files attached to bookings and ride operations.
Linked to Organizations - Operation receipts
Stable operation receipts proving each executed ride-hailing action.
Linked to Organizations, Team members
- Vehicles
Vehicles available for taxi and ride-hailing service.
Linked to Organizations - Drivers
Drivers eligible to accept ride requests.
Linked to Organizations - Vehicle defects
Defects reported against vehicles.
Linked to Team members, Vehicles - Vehicle inspections
Inspection results recorded against a taxi vehicle.
Linked to Vehicles - Vehicle maintenance plans
Planned maintenance for vehicles in the taxi fleet.
Linked to Vehicles - Fuel transactions
Fuel and charging transactions recorded against vehicles.
Linked to Vehicles
- Review decisions
Independent review decisions recorded against a booking revision.
Linked to Organizations, Team members - Operation receipts
Stable operation receipts proving each executed ride-hailing action.
Linked to Organizations, Team members - Record attachments
Evidence files attached to bookings and ride operations.
Linked to Organizations - Bookings
Ride bookings with their lifecycle, quoted fare, assigned resource and revision.
Linked to Organizations, Team members, Resources - Trip completion evidence
Evidence captured when a ride-hailing trip completes.
Linked to Bookings, Ride requests - Organizations
Operating organizations that own taxi bookings, resources and team members.
- Team members
Internal staff who prepare, review and execute ride-hailing operations.
Linked to Users, Organizations
Keys and references
Keep Bookings.record number, ride requests.request number and booking resources.line number stable during import. Driver ID and vehicle ID identify the operational resources; use the actual reference targets when linking an assignment. Team members.User connects the staff record to Users, which is needed when configuring the current-user booking view.
Source record, source table, related record and external reference are text fields. Agree their format and validate their targets during setup. They do not become reference columns merely because they contain a record identifier. Review decisions.source revision should identify the Bookings.Revision the reviewer examined.
Payment evidence.amount USD and Currency need an explicit import convention before amounts are totaled. Fuel transactions.odometer miles and Volume also need consistent units. Preserve existing timestamps and distinguish observed trip time from import time.
Migration order
- Organizations and accounts. Prepare Organizations and Users, then connect team members to their organization and user identity.
- Operating resources. Load Resources, Drivers, Vehicles and Routes with stable source identities and current activity states.
- Fleet evidence. Link vehicle inspections, vehicle defects, vehicle maintenance plans and fuel transactions to the correct Vehicles.
- Open rides. Import Bookings, then ride requests and booking resources using their parent and resource references.
- Trip and payment evidence. Attach trip tracking events, trip completion evidence and payment evidence to existing booking identities.
- Reviews and action history. Retain review decisions, operation receipts and record attachments with source references that resolve to the imported work. Reconcile the retained history before enabling new operating actions.
Set up Taxi / Ride-hailing Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.