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.
- Pilgrimage / Religious Tourism
- Features
- Trip Execution
Trip Execution
Compare planned and actual journey times at each ordered stop.
OverviewTrip Stop Log×
Pilgrimage / Religious Tourism · Trip Execution
New
Trip Stop Log
Trip stops
| Trip | Sequence | Location | Planned arrival | Actual arrival | Departed at | |
|---|---|---|---|---|---|---|
| TRP-2697 | 40 | E-7 | 09 Oct | 15 Oct | 21 Oct | |
| TRP-2498 | 80 | N-7 | 03 Oct | 10 Oct | 18 Oct | |
| TRP-5746 | 20 | B-17 | 14 Oct | 23 Oct | 31 Oct | |
| TRP-4563 | 40 | E-16 | 09 Oct | 11 Oct | 13 Oct | |
| TRP-5967 | 50 | U-10 | 11 Oct | 20 Oct | 22 Oct |
6 of 6 records
E-7Trip stops · TS-97627
TripTRP-2697
Sequence40
Planned arrival09 Oct
Actual arrival15 Oct
Departed at21 Oct
What you can do
Follow the journey after departure
The planned trip retains its origin, destination, start and end. When the driver departs, the actual start marks the journey in progress. Each ordered stop has a sequence, location and planned arrival, followed by actual arrival and departure as the movement takes place. At the end of the route, the actual trip end gives Operations Manager a complete journey timeline to review.
Use the stop sequence to keep the itinerary readable. A late arrival at an early stop may change the rest of the route, so Dispatcher and Driver should inspect the planned and actual times side by side. The stop log is the place to review the route history; the trip board shows the broader status of the journey. Both are useful during a call from the group leader asking where the vehicle is.
How the work is organized
- Trip timeline. The trip retains planned and actual start and end dates.
- Ordered stops. Trip stops keeps sequence, location and planned arrival on each stop.
- Actual movement. Driver records arrival and departure at the stops as the route proceeds.
For a journey with a pickup point and a pilgrimage site, Dispatcher enters each stop in travel order. The driver reads the assignment before departure, records the actual start, then adds actual arrival and departure as each stop is reached. Operations Manager can compare the planned arrival with the actual arrival and review a delay in the context of the whole trip.
What to agree during setup
Decide when the driver records the actual start, each stop arrival and each departure. Agree how late or corrected timestamps should be handled by the operations team. Confirm who updates the route when a stop changes during travel and how Dispatcher communicates that change to the driver. A trip that ends without a completed stop log may still need investigation before the delivery handoff is accepted.
Define what the team means by a completed trip. The arrival at the destination and a recipient confirmation are related but different entries. Delivery evidence records the recipient, proof and delivery time. Trip stops records the route movement. Keeping both records tied to the same trip lets a reviewer reconcile the final location with the handoff.
Check the handoff on an actual case
Rehearse one scheduled journey with ordered stops. Have Driver record actual departure and a stop arrival, then compare the planned and actual dates in the stop log. Continue through the last stop and capture departure there. Ask Operations Manager to check whether the final route history agrees with the delivery record before the trip is treated as complete. This case exposes unclear timestamp ownership before the team handles a busy travel day.
What your team sees
- Trip Stop Log — Compare planned arrival with actual arrival and departure in stop order.
- My trips — Let the assigned driver see the journey dates and status.
- Trip Dispatch Board — Give dispatch a status view of active movements.
Follow the work through
Read journey execution and delivery and charges. Use the reports page for timing questions.
What it keeps track of
Data model- Trips
- Planned and dispatched journeys carrying pilgrim groups between origin and destination.
- Trip stops
- Ordered itinerary stops for a trip with planned and actual arrival and departure times.
- Delivery evidence
- Proof of delivery recorded at the end of a trip with recipient and confirmation status.
Who uses it
Permissions- Driver
- , Dispatcher, Operations Manager and Admin follow the movement and review its handoff.
Set up Pilgrimage / Religious Tourism your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.