Brief travellers on policy in words, and again in the booking path

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. It sits next to the guide on how to write a corporate travel policy and the product pages for travel policy, policy search and out-of-policy controls.

1. Say what the programme is for

A briefing that starts with cabin tables and ends with a threat will be tuned out. Start with the reason: the company wants travellers to have a usable journey, a current confirmation, and a way to change a plan, while keeping cost and duty of care in view. Policy is the set of rules that makes that possible, not a list of punishments.

Then be specific. How a request is made in My Mobility, including on a phone as a mobile web experience. Who approves it, and on what basis. What happens if an option is outside the rules. How to reach the desk when a plan changes. Where documents will be found afterwards.

2. Put the same rules in search, not only in a handbook

If the booking path offers options the handbook forbids, the handbook will lose. Policy-checked search should show what is in bounds, and should flag what is not, so the traveller can see the consequence before they request it. Approvers should see the same check, with cost, on the request. A briefing can then point at the path rather than trying to memorise every route and cap.

3. Brief exceptions as a path, not as a rumour

Every programme has exceptions: a client requirement, a medical need, a leadership movement, a sold-out cabin. If the unofficial advice is “just call someone,” travellers will do exactly that, and finance will meet the booking later. Tell people how an exception is requested, who decides, and that the trip still sits on the record. Out-of-policy is a controlled route, not a back door.

4. Repeat the briefing when policy or tools change

A single induction conversation goes stale when destinations, caps, or the booking path change. Short, current notes at the point of request are more useful than a long annual presentation. When you do hold a briefing, use a real trip as the example: an in-policy hop, an exception, and a late change.

USD is the main currency on this site. Pricing is in USD and available on request. We do not invent compliance rates or traveller-satisfaction scores. Each company sees only its own data. Access is by role. We do not claim certifications we do not hold. A demo can walk through the traveller view and the approver view of the same request, which is often the most convincing briefing a travel manager can later reuse.