Cut out-of-policy bookings by making the rule visible before the ticket exists
Out-of-policy travel booking is often treated as a behaviour problem. Sometimes it is. More often it is a design problem: the rule is not visible at search, the in-policy option is hard to complete, or the official path is slower than a personal card. Cutting out-of-policy bookings starts before the ticket exists, and it continues in how exceptions are routed and later measured.
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. You can apply it without being a GTOS customer. In GTOS, policy-checked search marks options before a selection is made, and out-of-policy controls route the exception, with the decision on the trip record.
1. Put the rule in the path, not only in a document
A policy people cannot see at the moment of choice will be remembered late, or not at all. Each option should show whether it is in policy for that person's designation, department and destination. The approver should see the same determination. If search uses one rule and approval uses another, no one will trust the system, and unofficial booking will continue.
Write the policy so the system can apply it. The guide to writing a corporate travel policy is about that alignment. A narrative rule that cannot be expressed in search will become an exception pattern.
2. Decide what "out of policy" means in your programme
Some programmes prevent a class of choice. Others show it and route it to a higher approval. Both can be valid. What does not work is a silent out-of-policy booking that finance discovers at month-end. Flag the choice, route it, and record who agreed. That is control. Blocking everything, or blocking nothing, are both usually too blunt.
Also ask whether the rule itself is followable. A sales team that must travel same-week will ignore a two-week advance window. Fix the rule for the real pattern, then apply it firmly. A tighter rule that people use is better than a perfect rule that they go around.
3. Make the official path as fast as the unofficial one for in-policy trips
If an in-policy booking is slow, people will leave. Short approval chains and auto-issue for approved in-policy trips are compliance tools, not only convenience tools. They remove the excuse that the programme could not move at the speed of the meeting.
4. Measure from the record, and include the unofficial gap
Measuring policy compliance only works if the bookings are on the file. A compliance rate that ignores personal-card travel is a comforting fiction. Spend reporting should be cut by policy status, and the programme should also watch volume that never entered the path. We do not invent target compliance percentages. Your board or finance lead should set the standard; the system should make the number true.
USD is the main currency on this site. Pricing for GTOS is in USD and available on request. A demo can load your policy and show an in-policy option next to a flagged exception, with both ending on the spend and compliance view.
Frequently asked questions
Should we block every out-of-policy option?
Not necessarily. Some programmes flag and route exceptions; others prevent a class of choice. Silent out-of-policy booking is the failure to avoid.
Why would a tighter policy increase unofficial travel?
If the official path cannot be followed for real work, people will leave it. Write a rule for the pattern you have, then apply it in search.
Do you publish a benchmark compliance rate?
No. We do not invent target percentages. The report should be built from the trip record, including whether exceptions were approved.
Related
See GTOS in a demo
We are now taking early-access requests. Demo accounts are available now.
- A walkthrough of the Client Portal, My Mobility and Control Tower
- Your travel policy, set up in a demo account
- USD pricing discussed on request, with PKR quotes available
Prefer email or WhatsApp? insights@goglobal.pk · +92 320 4111222