Measure policy compliance from the bookings you already have, and the ones you are missing
Travel policy compliance reporting is only as true as the bookings in the file, and as honest as the definition you use. A rate that counts only tickets issued in the official tool, and ignores personal-card travel, will look healthy while the programme leaks. A rate that treats every approved exception as a failure will punish a policy that was designed to allow some exceptions. This guide is about measuring compliance in a way a travel lead and a finance lead can both defend.
It is written by the team behind GTOS, the Global Travel Operating System from Voraal, and is built on operating experience across 100,000+ trips. In GTOS, compliance views are cuts of the same trip record as spend reporting. The policy compliance programme page describes the operating model. We do not invent target percentages or industry benchmarks. Your organisation should set the standard; the measurement should be true.
1. Define the states before you report the rate
At least four states usually matter: in-policy bookings, out-of-policy bookings that were approved as exceptions, out-of-policy bookings that should not have been issued, and trips that never entered the official path. If you collapse those into one number, you will not know whether the problem is the rule, the path, or the unofficial channel. The guide to cutting out-of-policy bookings is about the operating fixes; this guide is about seeing the states clearly.
2. Build the report from the trip, including the trail
Each booking should already carry the policy check and the approval. A later compliance report should not need a mailbox search to explain an exception. Cuts by department, designation, destination, supplier and traveller are how you find where the rule is failing, or where the rule itself is unworkable. Amounts should sit next to counts. A small number of high-cost exceptions can matter more than a large number of minor ones.
3. Watch leakage, not only the official denominator
If volume is leaving the tool, the official compliance rate will improve for the wrong reason. Track whether people are using the path, especially on short-notice and domestic trips. A usable in-policy flow is part of measurement, because it is what keeps the denominator honest.
4. Review the rule when the report repeats the same exception
If one designation or one market produces the same exception every month, the policy may be wrong, not the travellers. Measuring compliance is also a way to improve the document. USD is the main currency on this site. Pricing for GTOS is in USD and available on request. A demo can show the same trip in a compliance cut and in an audit-style record, which is the standard this guide argues for, and the one finance can defend.
Each company sees only its own data. We do not claim certifications we do not hold.
Frequently asked questions
Should approved exceptions count as non-compliant?
They should be visible as approved exceptions, not hidden inside a single failure rate. Whether you treat them as a breach is a policy choice you should make explicitly.
Do you publish a benchmark compliance percentage?
No. We do not invent industry targets. The report should be true for your programme, including unofficial leakage.
Can we cut compliance by department or destination?
Yes, if the trip record holds those attributes. In GTOS, spend and compliance can be cut that way from the same bookings.
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