How to Build a Travel and Expense Policy That Travelers Actually Follow

Two-thirds of travelers still book outside your travel and expense policy. The problem isn't that the policy is poorly written or hidden. It's that the policy lives in a document while booking decisions happen in a workflow, and nothing connects the two. When finance asks why the travel budget is over, that disconnect is what you're trying to explain.

This article covers four structural shifts, from document design to OBT enforcement to executive exception handling to compliance measurement, that close the gap between what travelers know and how they actually book.

Why Travel and Expense Policy Awareness Doesn't Produce Compliance

The assumption behind most corporate travel policy rollouts is straightforward: if travelers read the rules, they'll follow them. The data says otherwise.

The disconnect starts with enforcement. Across 3,200+ US companies, 62.9% have zero enforcement of their travel and expense policy, with another 27.5% at only low enforcement in the enforcement benchmark. That means roughly 90% of corporate travel programs operate without meaningful consequences for non-compliance.

The policy document makes it worse. 51% of travel policies exceed 10 pages, and 24% run longer than 20 pages in the policy benchmark. Only 14% of travel managers report shorter policies over the past three years, so policies keep getting longer while the gap between what's written and what's practical at booking time keeps widening.

Then there's the language problem. Forty-six percent of companies instruct employees to book "reasonably priced" hotels instead of setting explicit rate caps. "Reasonably priced" means something different to every traveler, and nothing useful when finance audits the expense report.

Design Your Travel and Expense Policy to Drive Compliance

A travel and expense policy that drives compliance needs two layers: a concise traveler-facing reference that shapes daily behavior, and a detailed back-end document that powers enforcement.

The Traveler-Facing Policy Summary

The first document is a visual one-page summary. It improves compliance by answering the only question travelers actually have at the point of booking: what am I allowed to do? This one-page policy covers the booking channel requirement, cabin class rules, hotel rate caps by city tier, and where to go for exceptions.

The detailed back-end document handles everything else: the expense system logic, the enforcement escalation ladder, regulatory compliance language, and the full scope of who the policy covers. That scope matters.

The policy should apply to anyone traveling on the company's expense, including consultants, job candidates, customers, and non-employee traveler groups. Both documents also require a CEO or CFO statement of scope and purpose to signal that the rules carry real authority.

Rate Caps Over Vague Policy Language

The traveler-facing summary works only if it replaces vague language with specific numbers. Only some companies set explicit rate caps. The rest rely on subjective phrasing that creates gray zones at every booking.

Structured rate targets signal what an acceptable price looks like inside the booking flow, steering behavior without the traveler friction of hard caps that drive bookings off-platform entirely. City-based thresholds work even better when they reflect current per diem data.

Benefit-Framing Over Policy Mandates

The traveler-facing summary should lead with what travelers gain, not what they're prohibited from doing. Replace "you must book through the approved channel" with language that shows travelers what they get: negotiated travel rates and travel alerts. When travelers see personal benefit, compliance feels less like enforcement.

Lead traveler-facing communications with duty of care rationale, not cost-savings messaging. "We need to know where you are if something goes wrong" resonates more than "we need to save money on your flights."

Build Policy Enforcement Into the Booking Flow

A well-written policy document still sits outside the booking experience. The highest-leverage move is putting enforcement into the channels where travelers actually make decisions. This is the same problem many teams face with the OBT guide and compliance guide: the rule exists, but the workflow doesn't reinforce it.

Traditional OBT configuration offers two enforcement mechanisms, but both carry trade-offs:

• Hard blocks prevent non-compliant bookings from completing. The option is hidden, grayed out, or the flow terminates. Maximum compliance effect, but highest risk of pushing travelers off-platform entirely, which means losing visibility altogether.
• Soft blocks allow the booking but require a mandatory reason code before confirmation. Lower friction, and the reason codes feed compliance reporting data for finance. But they still depend on travelers choosing the OBT over faster alternatives.

The balance between hard and soft blocks is a policy-level decision, not a global setting. Configure dynamically by destination so hotel rate caps adjust automatically based on local per-diem rates, which prevents a single national cap from generating excessive exceptions in high-cost cities. The core limitation remains the same: these controls only work when travelers use the managed channel in the first place.

Beyond OBT configuration, centralized payment is the fastest path to near-complete compliance. Airlines, hotels, and car rental companies can all be paid through centralized payment systems, and those categories make up the majority of a typical T&E budget. When employees don't front their own money, they're less likely to seek workarounds.

The biggest policy decision is whether the company will reimburse travelers who book outside the mandated channel. State this explicitly. Ambiguity here is where leakage starts.

Otto the Agent ingests your corporate travel policy and shows travelers whether each option is within policy or out of policy during the booking flow. Every booking produces an expense-ready receipt in importable PDF format, so the documentation reaching finance is already clean when spend reviews start.

Document Executive Exceptions Before They Undermine Policy Compliance

Executive endorsement gives the policy its authority. When the person whose signature is on the document routinely bypasses it without documentation, credibility erodes for the entire organization. Eliminating exceptions isn't the answer. Documenting them is.

Formalize the Exception Structure

Three structural options exist: differentiated treatment written into the main policy, a separate executive policy not broadly communicated, or a universal policy with no carve-outs. The compliance problem isn't that executives get different treatment. It's that informal accommodations go unrecorded and show up as unexplained spend, creating variances that are difficult to defend when finance reviews the travel budget.

Separate Service Tiers From Policy Tiers

One structural option many programs miss addresses the tension between executive experience and budget control: TMC service-level tiers and policy entitlement tiers are separate structures. An executive can receive dedicated agent access and priority queuing without higher cabin class entitlements or elevated spend limits, which preserves budget controls without sacrificing experience. The same tiered logic applies to road warriors. Frequency-based tiers that loosen restrictions at defined mileage or overnight thresholds help with recruiting and retention, though the known risk is travelers taking unnecessary trips to maintain status.

Turn Exception Patterns Into Program Intelligence

Regardless of tier structure, track exception patterns as improvement signals, not just enforcement data. When travelers consistently decline contracted fares for the same reason, that's a negotiating opportunity or a sign the policy provision needs revision. If exceptions keep turning into unmanaged spend, this policy fixes guide covers the common causes and solutions.

Measure Travel Policy Compliance Gaps Before Finance Finds Them

Policy changes only hold up if you can prove they work. Off-channel booking is the top compliance issue for 35% of travel managers, and hotel leakage has grown or stayed the same at 81% of programs in the leakage study. Without structured reporting, those numbers surface during expense reconciliation instead of in your quarterly review.

Build compliance reporting around three data points:

• Managed channel booking rate: the percentage of bookings flowing through managed channels, which is the first metric finance looks for when travel costs rise faster than headcount
• Reason-code distribution from policy exceptions: this shows where the policy creates genuine friction versus where travelers simply ignore it, which separates enforcement problems from design problems
• The gap between managed-channel spend and expense-system spend: that gap is your leakage number, and it's the clearest signal of how much spend falls outside your program's visibility

When compliance data lives in a standing report instead of a post-hoc audit, you can answer the budget question before it becomes a budget crisis. Many common travel challenges trace back to this same gap between policy design and booking behavior, so the earlier you spot the pattern, the easier the fix.

Give Finance a Travel and Expense Policy That Holds Up

Enforcement in the workflow plus measurement that proves it's working. That combination turns a travel policy from a document finance questions into a program finance trusts.

Otto keeps policy rules visible during the booking flow, not buried in a document travelers check after the fact. Every transaction produces an expense-ready receipt, so the documentation reaching finance is already clean when spend reviews start.

Start with Otto to keep policy visible where booking decisions happen and give finance cleaner receipt documentation at review time.

FAQ

What compliance rate should travel managers target for a mid-market program?

Programs that enforce policy through their OBT and use centralized payment typically see higher in-policy booking rates, but the baseline varies by industry and company size. Programs with recently implemented OBTs often face residual non-compliance even after rollout, so closing that gap should be the first-year priority.

How often should travel managers audit OBT policy rules?

OBT policy rules degrade as rates change and preferred vendor agreements shift. Quarterly audits at minimum keep the tool's actual enforcement behavior aligned with intended policy and prevent rate mapping errors from driving leakage.

Why is hotel compliance harder for travel managers to control than air compliance?

Hotel leakage is harder to control because inventory is more fragmented, personal loyalty programs carry more tangible value, and most companies rely on vague language instead of defined rate caps. Structured rate targets by city tier and preferred-property prioritization in managed booking channels are the most direct levers.

How can travel managers make policy visible at the point of booking without adding friction?

Most booking tools bury policy rules in help documentation or post-booking flags, which means travelers don't see compliance guidance until after they've made a decision. Otto ingests your corporate travel policy and displays within-policy and out-of-policy indicators during the booking flow itself, so travelers see what's compliant before they confirm.

Does policy enforcement improve program outcomes for travel managers?

Firms that balance strategic travel policy controls with flexibility outperform those that do not by up to 30%, and companies with moderate or high enforcement achieve better business outcomes, according to the enforcement benchmark. The takeaway: balanced enforcement outperforms both zero enforcement and rigid controls that choke operational flexibility.