Build a hotel programme on the same record as the rest of the trip

This guide is written by the team behind GTOS, the Global Travel Operating System from Voraal, and is built on operating experience across 100,000+ trips. Product context sits on the hotel desk, in-policy hotels and, more conservatively, hotel content sources. Meetings and events covers group stays and blocks. We do not name hotel chains, aggregators, or certified content connectors.

1. Split everyday stays from desk-handled stays, not the file

In-policy search in My Mobility is the right path for a standard overnight. Preferred rates, negotiated houses, sold-out dates, and group blocks belong with the hotel desk, working in Control Tower. Both paths must write the same trip record. If the desk confirms a stay in a side email, the traveller will not know which voucher to present, and finance will not know which cost to match.

2. Write programme rules into policy

A preferred house only works if travellers are offered it first, or if a departure from it is flagged. Travel policy can hold those rules by destination, designation and department, including caps where you use them. Approvers then see cost and the policy check together. A handbook list of hotels that never appears in search will not be followed for long.

3. Measure use, not only contracted availability

Spend reporting should show hotel spend by destination, supplier and department, and should make programme use visible rather than leaving it as an anecdote. USD is the main currency on this site. GTOS can record spend in more than one currency. Software pricing is in USD and available on request. We do not publish hotel rates or claim a most-favoured-rate guarantee.

A rate that is never booked is not a saving. A stay booked off the record cannot be counted as programme compliance. The record is what makes both statements checkable.

4. Load sources honestly

How preferred houses, rates and wider hotel content are loaded is a demo and implementation conversation. The hotel-content page does not publish a source catalogue, and this guide will not invent one. Avunzo is designed to connect travel content and booking flows to your own channels and is not yet live on production; early access is available on request. It is not a claim that a particular hotel source is already live inside GTOS.

Each company sees only its own data. Access is by role. We do not claim certifications we do not hold. A useful demo includes an everyday in-policy stay and a desk-handled preferred or block stay, then shows both on the same record, with the spend view finance would use. Bring your current preferred list, even if it is still a spreadsheet. The walkthrough is more useful when it starts from what you already have.