Policy that follows designation, department and destination

GTOS lets rules be set by designation, department and destination, and matched to your written policy. Those rules run in policy-checked search, so travellers see in- or out-of-policy options before they select. The same determination is what approvers and finance later see. The source for who someone is — their designation, department and manager — is the organisation chart in the Client Portal. GTOS is the Global Travel Operating System from Voraal, built on operating experience across 100,000+ trips.

Why the chart and the policy have to be the same programme

A designation rule is only as accurate as the person's current role. If someone has been promoted and the chart still shows the old designation, they will be shown the wrong options, or they will request an exception they should not need. Keeping employees and roles current is therefore part of policy operations, not a separate HR courtesy.

Approval chains can also follow role and amount. A policy that is generous for one designation may still require a higher approval when the amount crosses a limit. The two designs should not contradict each other.

Writing a policy the system can apply

A document full of narrative and a system full of unenforceable clauses will drift apart. The guide to writing a corporate travel policy is about keeping those two aligned. This page is the product outcome: different people in the same company can be shown different in-policy options, for a reason the company can explain.

Policy compliance then reports whether those rules were followed, including the exceptions you chose to allow.

USD is the main currency on this site. Pricing is in USD and available on request. How employee data might sync from an HR system is scoped during implementation; we do not publish named HRIS connectors. See HRIS employee sync.

Each company sees only its own data. Access is by role. We do not claim certifications we do not hold. A demo can load two designations and show how search and approval differ, which is the most direct way to test this use case. If your written policy already names different rules by grade or department, bring that language so it can be compared with what the booking path actually applies. A written rule that search cannot express will become an exception pattern, and the designation matrix will exist only on paper. The booking path has to carry the rule for the policy to be real.