What an in-house travel team should keep, and what a platform should hold

GTOS is the Global Travel Operating System from Voraal, built on operating experience across 100,000+ trips. Travel managers work in the Client Portal. The desk works in Control Tower. Travellers book in My Mobility. This page compares an in-house operating model with a platform model, and then describes how they can share one record rather than compete.

What in-house teams already do well

They know the company: who may fly in which cabin, which routes are sensitive, which cost centres are under pressure, and when a leadership trip needs a different path. They can brief a traveller, make a judgement on an exception, and hold a relationship with a preferred hotel or a specialist desk. None of that disappears because software arrives. See travel managers.

Where in-house work strains is the file itself. Requests arrive by message. Approvals sit in a thread. Tickets are forwarded as attachments. Changes are logged in a workbook. Month-end becomes a reconstruction. The companion page versus spreadsheets covers that failure mode. A team can be highly skilled and still be operating without a shared record.

What a platform should take, and what it should not

The platform should take search, policy checks, approval chains, ticketing paths, documents, spend, and a live view of who is on the road. It should offer a handoff to an expert desk or a managed-travel model when a trip needs a specialist, without creating a second itinerary. Managed travel is that wider option, including when an agency or TMC works the same record.

The platform should not pretend that policy writes itself, or that a travel manager is optional once auto-issue is switched on. Approved, in-policy bookings can be issued automatically so the team is not a queue for routine trips. Judgement remains a human job. The test of a good platform is whether that judgement is applied on the live file.

USD is the main currency on this site. GTOS can record spend in more than one currency. Pricing is in USD and available on request. We do not invent time-saved figures, headcount reductions, or customer stories on this page. Each company sees only its own data. Access is by role. We do not claim certifications we do not hold.

How to use a comparison conversation

Bring a week of real requests: a routine in-policy hop, an exception, a leadership movement, and a late change. Ask where each one lives today, and where it would live in GTOS. If the in-house team would still need a side mailbox for any of those, that is the gap to examine in a demo, not a reason to abandon either the team or the platform.