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
- Trip completion and documents
Trip completion and documents
Stops, completion evidence and trip paperwork.
OverviewEvidence reviewer queue×
Tour Operator Software · Trip completion and documents
New
Evidence reviewer queue
Approval conditions
| Id | Trip | Delivered at | Recipient name | Proof | |
|---|---|---|---|---|---|
| IDD-290 | TRP-9365 | 18 Oct | Recipient 247 | PRF-679 | |
| IDD-223 | TRP-3379 | 08 Oct | Recipient 233 | PRF-473 | |
| IDD-622 | TRP-4717 | 08 Oct | Recipient 204 | PRF-421 | |
| IDD-256 | TRP-5776 | 16 Oct | Recipient 693 | PRF-966 | |
| IDD-300 | TRP-8512 | 23 Oct | Recipient 462 | PRF-171 |
6 of 6 records
IDD-290Delivery evidence · DE-11221
TripTRP-9365
Delivered at18 Oct
Recipient nameRecipient 247
ProofPRF-679
What you can do
Close each trip with proof
When a trip ends, the driver records completion evidence: when the group was handed over, who received them and proof such as a signed sheet or photo. The evidence starts as pending. A reviewer confirms it or disputes it. Confirmation completes the trip with the observed time and approves its draft charges for invoicing. A dispute keeps the charges in draft until it is settled.
Only the stop arrivals and departures that were actually observed are added; planned times stay as planned. Trip paperwork such as manifests, permits and inspection records is attached to the trip as transport documents, each verified by a named person, so the file for any trip shows what was carried and checked.
How the work is organized
Drivers record evidence; the evidence reviewer decides; the operations manager keeps documents in order.
- Observed, not assumed. Only real stop times are recorded.
- Reviewed completion. A trip completes when its evidence is confirmed.
- Documents verified. Each transport document names who verified it.
What to agree during setup
Agree what counts as proof of completion for each kind of trip, who reviews evidence and how fast. Agree which documents each trip needs (passenger manifest, permits, vehicle inspection) and who verifies them. Prepare examples of a confirmed completion, a disputed one, a trip with a missing permit and a trip whose last stop was skipped.
Check the handoff on an actual case
A coach returns a group to their hotel at 18:40. The driver records the hand-over with the hotel’s duty manager as recipient and a photo of the signed manifest. The reviewer confirms it the next morning; the trip completes at 18:40 and its charges move to approved. On another trip the customer complains about a missed stop; the reviewer disputes the evidence and the charges stay in draft while it is sorted out.
What your team sees
- Evidence reviewer queue — Pending completion evidence for the reviewer.
- Trip stops — Planned and actual stop times.
Follow the work through
- Completion and charges: From evidence to invoiced charges.
What it keeps track of
Data model- Delivery evidence
- Proof of delivery captured at the end of a trip.
- Trip stops
- Ordered stops on a trip with planned and actual arrival times.
- Transport documents
- Trip paperwork such as manifests, permits and inspection records.
- Trips
- Planned and executed transport trips with customer, vehicle and driver.
Who uses it
PermissionsSet up Tour Operator Software your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.