What an out-of-policy travel booking is

This definition is written by the team behind GTOS, the Global Travel Operating System from Voraal, and is built on operating experience across 100,000+ trips. A practical guide is in how to reduce out-of-policy bookings. We do not invent compliance rates.

Three different cases

The first case is a booking the official path should not allow to complete without a decision. Policy at search and out-of-policy controls exist for this: the option is flagged or blocked, and if the trip still has a business case it is sent through an approval chain with a reason. The second case is an approved exception. Once a named approver has allowed it, the booking is still out of the standing rule, but it is no longer unofficial. The trail has to live on the trip, or finance will later treat it as leakage. The third case is travel booked outside the tool entirely. That is the case a policy document cannot reach, and it is the case travel analytics will under-count if the only source is the official path.

Keeping those three distinct is the core of policy compliance. A single “out of policy” percentage that mixes approved exceptions with unofficial leakage is not a management number. It is a blur.

Why people leave the rule set

Sometimes the rule is wrong: a cap that does not fit a corridor, a class rule that cannot survive a long-haul overnight, a window that sales travel cannot meet. People then leave the official online booking tool because the official path cannot finish the trip. Sometimes the path is awkward and a consumer site is faster. Sometimes nobody has explained the rule, or the exception path is slower than just paying and claiming. The response is not only tighter blocking. The response is to fix rules that cannot be followed, to make in-policy options easy to choose, and to make the exception path official rather than informal.

Cost is the usual reason leadership asks about this. Duty of care is the other: unofficial travel is travel the organisation may not be able to see when plans change.

How to measure it

Measure from the trip record, as set out in measuring policy compliance. Count in-policy bookings, approved exceptions, blocked attempts where those are visible, and, as far as finance data allows, leakage off the path. Do not treat an approved exception as a failure of the programme; treat an undocumented one as a failure of the trail. Over time, the useful questions are: are rules being applied at search, are exceptions going through the chain, and is unofficial volume falling because the official path is usable?

What software can do

Software can apply the rule at search, route the exception, keep the trail, and report the cuts. It cannot force a booking that happened on a personal card onto the record unless some other feed or process brings it in, and this glossary does not invent such a feed. Honesty about what the record can see is part of a serious control. GTOS is designed so that when people do use the official path, out-of-policy behaviour is controlled and reportable on the same file as the booking itself.