Build approval chains that match the way your organisation actually decides

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. You can apply it in any system that can read a chart, a role and a limit. Where the idea maps to GTOS, the feature pages are linked: approval chains, approvals and organisation roles.

1. Start with the chart, not with a list of names

Names change. Roles and reporting lines are what should drive a chain. If your chart is not current, fix that first, or the best-designed limits will still route badly. In GTOS the chart in the Client Portal is the source for who can approve and who can see what. An HR connection, if you want one, is scoped during implementation; we do not publish named HRIS connectors.

Write down, for each common trip type, who should decide. A team leader may cover a regional ticket up to a set amount. A higher amount, a different cabin, or an out-of-policy hotel may need the next role. Amount and role should work together. Role alone misses cost. Amount alone misses who is actually accountable.

2. Keep in-policy paths short

If four people must sign a standard domestic ticket, the path will be bypassed. Approved, in-policy bookings should be able to move quickly, including auto-issue once the right person has agreed. Exceptions and high amounts should take a longer path, and they should be flagged as such. Faster approvals is the outcome; the design choice is not to make every trip instant, but to stop routine work inheriting exceptional delay.

Approvers should see the itinerary, the estimated cost and the policy check in one view, including on a phone. If they have to reconstruct a fare from a forwarded screenshot, the chain is already broken even if the names are right.

3. Record the decision

Later reviews will ask who agreed to an exception, and at what amount. If the answer lives only in email, the chain has no memory. The decision should be written to the trip record, with reminders when a request is waiting, so silence is not the same as approval.

4. Review the chain when the organisation changes

Promotions, departures and reorganisations should trigger a chart review. A leftover approver is both a delay and an access problem. A demo can load your actual roles and walk a routine request next to an exception, which is the fastest way to see whether the chain is short enough to use and complete enough to review.

USD is the main currency on this site. Pricing for GTOS is in USD and available on request. Each company sees only its own data. We do not invent average approval-time metrics, and we do not claim certifications we do not hold.