What a travel management company (TMC) is

This page is written by the team behind GTOS, the Global Travel Operating System from Voraal, and is built on operating experience across 100,000+ trips. Where GTOS is the platform a TMC can work in, the relevant pages are linked. We do not name invented clients or claim a certified league table of TMCs.

What a TMC actually does

A TMC takes a brief — policy, preferred hotels and airlines where they exist, service hours, and the shape of the programme — and turns day-to-day travel into bookings that can be defended. Advisers handle trips that will not stay on a self-serve path: complex multi-city itineraries, group movements, tight connections, and changes while someone is already away. Account teams report spend and compliance to the client. A serious TMC also holds a duty-of-care posture: when plans change, the current itinerary has to be findable.

That work can be done well or badly on almost any mix of tools. Email and spreadsheets still run a surprising number of accounts. The cost of that mix is familiar: the client sees a different version of the trip from the desk, invoices arrive without a clean booking to match, and unofficial bookings leak around the programme. A TMC platform is the software response to that problem, not a replacement for the company.

The platform is not the company

Buyers often blur the two. An online booking tool is a path travellers use. A travel operating system is the record and workflow. A TMC is the organisation that staffs the desk, owns the client relationship and, in managed travel, applies policy and preferred supply on the client’s behalf. One company may use several tools. One platform may be used by a corporate travel team with no TMC at all, or by a TMC running many corporate accounts.

GTOS is software, not a TMC. It is built so a travel management company can run accounts on one booking record, with a client portal the account team and the client both see, and Control Tower for the desk. The working pattern is described in how TMCs use software and in the TMC solution page. Agency and corporate tool roles are compared in agency vs corporate tool.

What to ask a TMC about its system

Ask how a booking, an exception and a mid-trip change sit on one file, and whether the client can open that file without waiting for a spreadsheet. Ask how unofficial spend is visible, and how invoices are matched to the trip. Ask what happens after hours, and whether the night desk works the same record. Those questions test the operating model. They also test whether the TMC has a platform or a pile of inboxes.

A TMC that cannot show the current trip to the client will struggle to defend the programme when finance asks for a clean close, or when a traveller’s plans change and someone has to act. The company can still be experienced and well staffed. The gap is the record.

Boundaries worth stating

A TMC may also be a licensed travel agency, and many agencies run corporate accounts without using the TMC label. The label matters less than the operating promise: managed travel on a shared record, with a desk that can take work the booking path cannot finish. Reservations content may arrive through a GDS or an NDC path; whether a given connection is in place is a conversation for a demo, not a claim made here. Accounting and ticketing products at the edge of the file should be named only when they are actually in use.