Keep out-of-policy bookings visible and controlled

GTOS, the Global Travel Operating System from Voraal, treats out-of-policy controls as part of the booking path. Policy rules run while the traveller searches. Options are marked in or out of policy before a selection is made. When a traveller still needs an exception, the request is routed to the right approver with the cost and the policy check in view. The decision stays on the same trip record. The product is built on operating experience across 100,000+ trips.

What out-of-policy means in a live programme

A written policy can define fare caps, cabin class, hotel bands, advance-purchase windows and preferred suppliers. In practice, travellers meet those rules at the moment of search. Out-of-policy controls are the layer that makes a breach visible instead of silent.

In GTOS, each option can show whether it sits inside the rule set for that person's designation, department and destination. The traveller is not asked to interpret a document mid-search. The approver is not asked to reconstruct the comparison later. Finance can still see, in spend reporting and CFO reports, which trips stayed inside policy and which ones were approved as exceptions.

Out-of-policy is not the same as blocked. Some programmes forbid certain choices. Others allow them with a higher approval. GTOS is designed so you can set the rule and the route, rather than forcing every exception through the same inbox.

How a flagged booking is routed

When a traveller selects an out-of-policy option, the request does not disappear into a generic queue. Approval chains follow role and amount, taken from the organisation chart. The approver sees the itinerary, the estimated cost and the policy check, then approves or declines. Reminders follow if a request is waiting.

The full path is recorded. Who requested the trip, who approved an exception, and what changed after that decision, belongs in the audit trail. That is what makes later reviews possible without a hunt through mailboxes.

Approved, in-policy bookings can still be issued automatically. Exception paths and complex trips can go to a specialist desk. Out-of-policy control is not meant to slow every booking. It is meant to make the unusual path explicit.

Why this belongs next to policy, not after the trip

Most leakage happens after a ticket is in place, when finance is matching a card line to a booking that was never reviewed. Policy-checked search and the travel policy engine exist so the check happens first. Out-of-policy controls are the companion: they decide what happens when the traveller still has a reason to go outside the rule.

The same record then carries receipts, invoices and budget commitments. USD is the main currency on this site. GTOS can record spend in more than one currency. Public prices are not listed; request pricing for a USD quote.

Each company sees only its own data. Access after sign-in is by role. We do not claim certifications we do not hold. Read Security.