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.
- Tour Operator Software
- Features
- Trips and dispatch
Trips and dispatch
Planned trips approved, scheduled and run.
OverviewMy trips×
Tour Operator Software · Trips and dispatch
New
My trips
Trips
| Name | Origin | Destination | Planned start | Vehicle | Status | |
|---|---|---|---|---|---|---|
| Trip 539 | ORG-812 | DST-833 | 10 Oct | VHC-73283 | Requested | |
| Trip 374 | ORG-797 | DST-242 | 21 Oct | VHC-36966 | Approved | |
| Trip 769 | ORG-881 | DST-216 | 16 Oct | VHC-61614 | Scheduled | |
| Trip 646 | ORG-382 | DST-218 | 09 Oct | VHC-59154 | In progress | |
| Trip 109 | ORG-420 | DST-779 | 15 Oct | VHC-81509 | Completed |
6 of 6 records
Trip 539Trips · TRP-65640
RequestedOriginORG-812
DestinationDST-833
Planned start10 Oct
VehicleVHC-73283
What you can do
Approve the trip before the bus leaves
A trip is one run of the operation: origin and destination, planned start and end, the vehicle, the driver and the customer. It is requested, approved by the dispatcher, scheduled and then run, and it ends completed or cancelled. Actual start and end times are recorded beside the planned ones, so delays are visible rather than overwritten.
The dispatcher approves each requested trip after checking the vehicle and driver assignment. Approval moves the trip to scheduled, and departure moves it to in progress. Each trip’s stops are recorded in sequence with their location, planned arrival, actual arrival and departure time.
How the work is organized
The dispatcher approves and schedules; drivers run the trips.
- Approved before scheduled. A trip is not scheduled until the dispatcher approves its assignment.
- Planned and actual side by side. Actual times never overwrite planned ones.
- Stops in order. Each stop has its sequence and times.
What to agree during setup
Agree who can request trips and who approves them. Agree what the dispatcher checks before approval: vehicle capacity against travellers, driver hours, documents. Prepare examples of a normal trip, a trip with a vehicle swap, a delayed departure and a cancelled trip.
Check the handoff on an actual case
A coastal tour trip is requested for Saturday with the 20-seat coach and a named driver. The dispatcher checks the coach is available, approves the trip and it is scheduled. On the day the coach leaves 25 minutes late; the actual start is recorded next to the planned one. Each stop’s actual arrival is added as the trip runs, so the operations manager can see where the time was lost.
If the coach had broken down, the dispatcher would have swapped the vehicle on the trip before departure, and the change would show on the trip record for anyone checking later.
What your team sees
- Dispatch board — Trips by requested, approved, scheduled and in progress.
- Trips awaiting approval — Requested trips for the dispatcher.
- Fleet schedule — Approved and running trips with planned start and end.
Follow the work through
- Trip dispatch and run: From a requested trip to a completed run.
Check permissions for dispatchers.
What it keeps track of
Data model- Trips
- Planned and executed transport trips with customer, vehicle and driver.
- Trip stops
- Ordered stops on a trip with planned and actual arrival times.
- Vehicles
- Fleet vehicles available for tour and transfer operations.
- People
- Staff and drivers who operate tours and transport for the operator.
Who uses it
Permissions- Dispatcher
- , Driver.
- The dispatcher approves and schedules; drivers run trips and record stops.
Set up Tour Operator Software your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.