What a travel operating system covers

This guide defines the coverage of that category and shows how GTOS, the Global Travel Operating System from Voraal, is built. A companion page, how a travel operating system works, walks through the flow from search to invoice. Definitions also sit in the glossary. The product is built on operating experience across 100,000+ trips.

The record is the product

Everything a travel operating system covers hangs on a single idea: one booking, one live status. The traveller, the approver, finance and the desk should not hold different versions of the trip. If they do, you do not have an operating system yet. You have a stack.

In GTOS that record is shared across three portals. My Mobility is for travellers. The Client Portal is for admins, approvers, finance and leadership. Control Tower is for the travel team behind the account. See the platform overview.

Policy and approvals

Coverage starts before a fare is chosen. The system should apply rules by designation, department and destination, and show whether an option is in policy. It should route exceptions on a chain taken from the organisation chart, and keep an audit trail. Without that, booking is still informal, even if it happens in a polished screen.

Booking and issuance

A travel operating system includes the booking layer: flights (one-way, return and multi-city), hotels and related services such as transfers, car rental, eSIM, lounges and meet and greet. It also includes what happens after approval. Approved, in-policy bookings can be issued automatically. Complex trips go to a specialist desk. Coverage that stops at the request is an OBT, not an operating system.

Spend, budgets and invoices

Finance should see cost on the same record, including spend by department, traveller, supplier and policy compliance, plus budgets, commitments, receipts and invoices. USD is the main currency on this site; a complete operating system should also be able to record spend in more than one currency. A later export into a spreadsheet is not the same coverage.

Duty of care and documents

Coverage includes a live view of where travellers are, passport and visa readiness, documents on the trip, and a way to reach people when plans change. Visa decisions rest with the authorities. 24/7 operations belong on this record, not in a disconnected inbox. If duty of care is a separate product that travellers must remember to use, the operating system is incomplete.

The desk, agencies and the edges of coverage

A travel operating system should give a desk an operations view on the same file: changes, groups, meetings, visas and response times. That is how managed travel works without two truths.

There are also edges. A travel operating system is not, by itself, a full reservations platform for an agency's retail sales, and it is not by itself a full accounting suite for a travel company. Voraal addresses those jobs with Rezencia and Folio6. Avunzo is designed to connect travel content and booking flows to a business's own channels; it is not yet live on production, and early access is available on request. Naming those edges is part of honest coverage.

GTOS is built to scale to 1,000+ employees per client. Each company sees only its own data, with access by role and two-step sign-in on the app. We do not claim certifications we do not hold. Pricing is in USD and available on request. For a view of all modules, see features. For the corporate programme shape, see corporate travel management.