Travel policy exceptions

Approved deviations from policy in justified cases. Even a well-designed travel policy needs a process for legitimate exceptions — for example, a medical need for a higher class of travel. Tracking exceptions separately helps travel managers see whether they're rare edge cases or a sign the policy itself needs revisiting.

Common reasons for exceptions include medical needs, security concerns, the unavailability of compliant options, last-minute changes caused by the business, travel with a client or senior executive, and events where the only reasonable hotel is above the usual limit. A good exception process asks for a short justification, routes the request to the right approver quickly and records the decision so it can be reviewed later.

Exceptions are not necessarily a problem — they are a sign that the policy recognises real-world situations. However, if the same exception is requested repeatedly, the policy may need adjusting. For example, frequent exceptions for hotel prices in one city suggest the limit for that city is too low. Analysing exceptions by type, department and destination turns them into a valuable source of information for improving the policy.

In Tumodo, exceptions are handled within the booking flow. When a traveller selects an option outside the policy, the platform shows which criterion is not met, and the booking can proceed with approval according to the company's approval scheme. Approval flows can be simple or multi-level, with a backup approver when decision-makers are unavailable, so exceptions are processed quickly and every decision is recorded in the trip.