Travel policy in 2026 — what's worth tightening
Class of service, advance-purchase windows, hotel caps, ground transport rules and the exceptions worth keeping in your corporate travel policy.
By Tulla Operations Desk

Most travel policies were written before fares moved the way they move now. The ones that perform in 2026 share three traits: they are short, they are enforced through the booking workflow rather than at expense reporting, and they trust travellers to make sensible exceptions when the rules genuinely fail.
If your current policy is more than 12 pages, longer than your code of conduct, or relies on a finance team to police compliance after the fact, it is structurally out of date. Travellers will not read it, approvers will not enforce it, and savings will continue to leak through routes the policy never anticipated.
Tighten advance-purchase windows
Domestic and regional flights booked inside 7 days now cost 35–60% more than the same fare booked at 21 days. International long-haul booked inside 14 days routinely costs double. A simple advance-purchase rule — 14 days regional, 21 days international, exceptions logged — is the single highest-leverage policy change most organisations can make this year.
Class of service: anchor on flight time, not seniority
Anchor business-class eligibility to flight duration (e.g. 6+ hours) rather than role. It is fairer, easier to administer, removes the awkward conversations and aligns the cost with the productivity benefit. Keep a documented exception for medical and accessibility reasons, and a separate principal-level exception for board members and C-suite where the organisation has chosen to make that call.
Hotel caps: per city, refreshed twice a year
A flat per-night cap collapses in cities like Geneva, Singapore, London and Doha. Maintain a per-city cap list, refresh it every six months against actual market data, and let your TMC enforce it at booking — not at expense reporting. A booking-time enforcement saves more than any post-trip audit.
Ground transport: vetted operators, not ride-hailing for executives
Ride-hailing apps work for individual travellers in low-risk cities. They do not work for executive movement, late-night arrivals, group transfers or any city where vehicle vetting matters. Your policy should name the cities where ride-hailing is acceptable and require pre-vetted ground operators everywhere else. The cost difference is small; the risk reduction is significant.
Exceptions worth keeping
- Same-day urgent travel for client-facing roles, with a 24-hour approval SLA
- Redirect to a closer airport for late-night returns over a defined hour
- Premium economy on red-eyes for travellers over a defined seniority
- Co-located hotel even if 10–15% above cap, for groups of 4+
- Hotel upgrade where the booked room is unavailable on arrival, with no second approval needed
Compliance through workflow, not policing
The most compliant programmes we see do not have stricter rules; they have better booking workflows. Travellers see policy-compliant options first. Out-of-policy options require a one-click justification. Approvers see exceptions, not every booking. Compliance climbs into the high 90s without anyone needing to chase.
Frequently asked
Should our travel policy be the same for all staff? Different rules for different traveller groups (executives, project staff, consultants on client projects) are fine and often necessary. What matters is that the rules are written down, applied consistently within each group, and enforced through the booking workflow.


