Travel request form

A trip request with itinerary details and purpose that triggers the approval flow. It captures the basic information an approver needs — dates, destination, estimated cost and business reason — before a booking is made. Once approved, the details on the form typically carry through into the actual booking.

A travel request usually includes the traveller's name, destination, dates, purpose of the trip, the project or cost centre, estimated costs for transport, accommodation and daily expenses, and any special requirements. In some companies, the request is submitted before any options are selected; in others, the traveller chooses specific flights and hotels and submits them for approval as part of the request, so the approver sees the exact cost.

The traditional approach — a paper or email form followed by separate booking — has several drawbacks. Information is entered twice, prices may change between approval and booking, and the link between the request and the final costs is easily lost. Modern platforms combine the request and booking steps: the traveller builds the trip, the system checks it against the policy and the approver confirms the actual itinerary and price.

In Tumodo, the trip itself acts as the travel request. The traveller or coordinator selects flights, hotels, rail tickets and transfers within the policy, and the trip is sent for approval in one click. The approver sees exactly what has been chosen and at what cost, and once approved, services are issued without re-entering any details. A single trip overview with all key details, tickets and vouchers can then be shared with the employee.