What managed corporate travel is

This definition is written by the team behind GTOS, the Global Travel Operating System from Voraal, and is built on operating experience across 100,000+ trips. The comparison with a pure self-serve posture is in managed vs self-serve. We do not invent “managed programme” savings figures.

What has to be in place

A policy document without an official path is not managed travel. An online booking tool without a desk is a self-serve path, and it may be the right path for many trips, but it is not yet a managed programme. A desk without a shared record is a service agency working from inboxes. Managed travel is the combination, described on the managed travel solution page: rules that apply at search, approvals that leave a trail, issue or handoff on the same file, spend that can be reported, and duty of care that can see the current itinerary.

A travel management company is often the firm that operates this model on a client’s behalf. A corporate travel team can also operate it directly on a travel operating system. The model is not owned by either party. The software is not the model either, though a platform that cannot hold the record will make the model much harder to run.

Managed is not “everything goes through a person”

A well-run managed programme uses self-serve for clean, in-policy bookings, including auto-issue where the file is ready, and uses the desk where judgement is required. The opposite of managed is not self-serve. The opposite is unmanaged: unofficial bookings, no trail, no current view of who is away, and a close built from cards. Self-serve inside a managed programme is a feature of the model, not a rival to it. That is why a buying conversation that frames “managed or self-serve” as a strict fork is usually asking the wrong question. The question is which trips should be self-serve, which should go to a desk, and whether both still sit on one file.

What a managed-travel platform should show

It should show policy in the booking path, an approval chain where required, a control tower or equivalent desk view, spend and compliance cuts from the record, and a way to work a change after hours without starting a new file. GTOS is built as that kind of platform: My Mobility for the traveller, a client portal for the account, and Control Tower for the desk. A TMC can run client programmes on it; a corporate team can run its own.

How to tell if you already have one

If unofficial volume is high, if invoices do not match itineraries, or if a mid-trip change starts with “forward me the confirmation,” the programme is not yet managed in the sense this glossary uses, even if a TMC is appointed and a tool is in place. If a traveller can book in policy, an approver can decide on the file, a desk can change the same file, and finance can open the cost, the model is in operation — and the remaining work is to tighten rules, supply and coverage, not to invent a new layer of tools.