Corporate Travel Policy Template: What to Include in Each Section

Your travel policy exists. It went out in onboarding and lives in a shared drive. Yet booking outside required channels remains the single largest booking compliance issue for corporate travel programs, because most travel policy documents go vague right when a traveler is deciding what to book.

When the policy doesn't answer the question in front of the traveler, they answer it themselves. A formal business travel policy controls cost, meets duty of care obligations, and creates the audit trail finance can defend at year-end.

This template walks through ten sections that close the gaps generic policies leave open. You get specific rule language for each section, structured to work as a corporate travel policy PDF, so you close leakage at the booking moment instead of cleaning it up in audit.

Policy Scope and Purpose

Start by defining who the corporate travel policy PDF covers. This is the section most templates treat as boilerplate, and it's where your first compliance gap shows up. The policy should apply to anyone traveling on the company's dime, including non-employee travelers like contractors, candidates, and board members. If your scope section is silent on that category, that spend has no rules attached.

Next, define where the policy applies. Decide between a single national policy or location-specific rules, and pick deliberately. Don't leave it ambiguous.

The policy scope should also name who enforces the policy, which trip types it covers, and how divisions may apply stricter rules without weakening the company standard. Skip soft words like "encouraged" and "logical." A policy that reads as a suggestion gets treated as one.

Booking Channels and Online Booking Tool (OBT) Mandate

Name the approved channel explicitly. Either a designated Travel Management Company (TMC) or a specific OBT, and state that it is the sole channel for standard travel. The mandate has to cover air and hotel at minimum, with ground transportation under the same rule. A policy that mandates the OBT for flights but goes silent on hotels leaks badly, because travelers book hotels direct and the spend never shows up in your managed data. Hotel leakage grew or held steady over the past year for 81% of travel managers, while 67% said the same for air.

If the policy permits direct booking in any category, it needs guardrails: price comparisons against the OBT, pre-approved budget limits, and explicit rules for fares that show up outside the standard OBT, including how bundled fare families map to your cabin class rules. For mid-market programs with an established TMC, an AI layer like Otto the Agent sits alongside the TMC and surfaces within-policy and out-of-policy indicators on every option, so policy visibility lives inside the booking step instead of getting reconstructed at audit. Smaller companies without a TMC get the same policy-aware booking experience through Otto directly.

Drop-in clause language: "All air, hotel, ground transportation, and rail bookings for company business must be made through [Approved TMC/OBT Name]. Direct bookings are permitted only when the approved tool does not return a fare or rate within 10% of a publicly available alternative, and require submission of a price comparison with the expense report."

Once the channel is locked in, the next gap is fare and cabin specificity.

Air Travel Rules

Air rules need enough specificity to cut exception requests and policy disputes. Spell out the following so travelers can stay in policy without flooding your inbox with edge cases.

Cabin class by trip type and duration

Most policies say "economy class" and stop. That leaves longer domestic and international flights ambiguous. Set cabin class by flight duration. A common threshold for business class is a single leg of 8 hours or more, with some programs starting at 6 hours for international travel. The cost difference is big enough that vague rules invite disputes, so put the threshold in the policy itself.

Drop-in clause language: "Economy class is required for all flights with a single leg of less than 8 hours. Business class is permitted for single legs of 8 hours or more and for any international flight with a same-day arrival meeting. Premium economy is permitted at the manager's discretion for legs of 6 hours or more."

Advance booking requirements

Set a minimum booking window and state what happens when travelers book inside it. A common benchmark is 14+ days domestic and 21+ days international, which gives you a defensible standard for exception review. Last-minute bookings drive the highest fares, so attach a manager-approval trigger to any booking inside the window.

Preferred carriers and fare class rules

If the program has preferred airline agreements, list them and define "lowest logical fare" precisely, typically within a two-hour travel window. Tackle fare class friction head-on. Loyalty status, bundled fares, basic economy restrictions, and preferred-carrier commitments all spark disputes when the policy doesn't say which rule wins.

Ground Transportation

Ground transportation is the section most policies leave to expense-report cleanup, which turns rental class disputes and rideshare receipts into recurring noise. Cover four areas explicitly.

• Rental car class and insurance. Cap the standard class at intermediate or standard size, and name approved rental partners. State whether collision damage waiver (CDW) is reimbursable, since most corporate cards already include coverage.
• Rideshare and taxi. Permit Uber, Lyft, and licensed taxi for airport transfers and intracity business travel. Cap or prohibit premium tiers like Uber Black or XL when not required for group size.
• Personal vehicle mileage. Reimburse at the IRS standard mileage rate for business use, and require origin, destination, and business purpose on every claim.
• Parking and tolls. Cover airport parking at long-term or economy lots, hotel self-parking when no alternative exists, and tolls with documentation. Set a per-trip cap on valet.

Drop-in clause language: "Rental vehicles are limited to intermediate class or smaller; full-size is permitted for three or more travelers sharing the vehicle. Collision damage waiver is not reimbursable when booked on a corporate card that includes rental coverage. Rideshare is reimbursable at standard tier (UberX, Lyft Standard); premium tiers (Uber Black, Lyft Lux) are not reimbursable without prior manager approval."

Hotel Policy

Use the hotel section to turn leakage data into specific controls travelers can apply: city caps, preferred properties, payment rules, personal nights, and incidentals. Each element below needs explicit language.

• Set destination-based rate caps by city tier. A flat national number guarantees either overspending in expensive markets or impossible caps in cheap ones. Tier your caps and calibrate against IRS high-low benchmarks of $233/night lodging for high-cost localities and $151/night lodging for all other CONUS localities under Notice 2025-54.
• A preferred hotel list and mandated booking channel. Name the preferred chains and require approved channels. Without this, your program loses the room-night volume it needs to protect contracted rates.
• Pay-now versus pay-later eligibility. Push travelers toward flexible rates when an itinerary might shift, since prepaid bargain rates are non-refundable. Silence here means change fees you didn't budget for.
• Bleisure and personal night rules. Spell out how personal nights separate from business nights, who covers any difference in room rate during personal nights, and whether the traveler's hotel stay or flight return date can shift to accommodate leisure time.
• Reimbursable versus non-reimbursable incidentals. State whether parking and resort fees are covered, and list non-allowable items like personal entertainment, spa services, and family member travel. Vague incidental rules drive most post-trip disputes.

Drop-in clause language: "Lodging rates are capped at $233/night in high-cost markets (NYC, SF, Boston, DC, LA, Seattle, Chicago) and $151/night in all other domestic markets, exclusive of taxes and fees. Travelers must book through [Approved TMC/OBT Name] and select a preferred property ([Marriott / Hilton / Hyatt / IHG]) when one is available within the rate cap. Rates above the cap require pre-approval and a written justification on the expense report."

Hotel incidentals tie directly into how you handle meals and per diems, so the expense framework picks up next.

Expense Reimbursement and Per Diems

Travelers hit reimbursement rules directly, and vague requirements create post-trip disputes. Set destination per diem rates by referencing GSA CONUS rates so you're not maintaining a custom table that drifts out of date. For FY2025 and FY2026, the standard CONUS rate is $110/night lodging and $68/day for meals and incidentals. Build in the rules that trip people up: travelers get only 75% of the M&IE rate on the first and last day of a trip.

Drop-in clause language: "Lodging and meals are reimbursed at the GSA CONUS rate for the travel destination as of the trip start date. Travelers receive 75% of the M&IE rate on the first and last calendar day of travel. Lodging receipts are required regardless of amount; M&IE is paid as a flat per diem without receipts."

Next, set receipt requirements by dollar threshold and a submission deadline. The $75 receipt threshold applies to most categories, and the IRS safe harbor expects reports within 60 days of return for accountable plan treatment.

Validate rates every year. The FY2025 jump in the standard M&IE rate from $59 to $68, the first revision since FY2022, instantly put any policy still citing the old number below benchmark and pushed travelers over the cap.

International Travel Addendum

International trips break enough policy assumptions that they need a separate section instead of scattered references inside the main rules. Cover the following:

• Passport and visa responsibility. State who initiates visa applications, who pays expedited fees, and the minimum passport validity required before departure (typically six months).
• Currency conversion. Reimburse foreign-currency expenses at the corporate card's settled exchange rate, or at the trip-date rate from a named source for cash expenses.
• International per diems. Reference the State Department's DSSR rates for destinations outside CONUS instead of building a custom international table.
• Country risk and traveler tracking. Require traveler check-in within 24 hours of arrival, name the country-risk advisory source you follow, and define a pre-trip approval trigger for any destination on a State Department Level 3 or 4 advisory.

Approval Workflows and Exceptions

Start with approver tiers by trip cost. For most programs, that means manager pre-approval for all travel and director-level sign-off above a threshold like $1,500. International travel routes through an additional risk and budget check.

Once tiers are set, keep the chain short. Two approvers, typically a direct manager and the travel manager, is enough for most trips. Set an approval response time, like 24 hours, so delays don't push travelers into higher fares.

Finally, tie approval to the booking flow. That's where booking tool enforcement happens and project codes attach before the trip instead of getting reconstructed after it.

Drop-in clause language: "All travel requires direct manager pre-approval before booking. Trips with a total estimated cost above $1,500, and all international travel, require additional director-level approval. Approvers must respond within 24 business hours of request; requests not actioned within that window auto-escalate to the next tier to prevent fare expiration."

Workflows that skip this structure fail in predictable ways:

• Email-based chains with no audit trail. Hard to track, easy to delay, and impossible to reconstruct for audit.
• Siloed systems. A manager approving a request can't see whether the cost falls within budget and ends up approving on estimates that break policy.
• Vague exception criteria. If pre-authorization only kicks in above a high threshold, too much travel bypasses budget review entirely.

Duty of Care Coverage

Mid-market programs often have a duty of care section that reads like compliance language instead of operational guidance. To make it functional, start with an emergency contact protocol travelers actually know about. The section should name the 24/7 emergency hotline, the mass notification method, and the process for confirming traveler location during a disruption. Around-the-clock support isn't optional, because emergencies don't follow business hours.

Duty of care runs on itinerary data, so every off-channel booking is a traveler the TMC may not be able to locate during a disruption. Tighten the channel mandate and your duty of care coverage tightens with it.

Policy Rollout and Communication

A travel policy document travelers haven't read is a policy that won't hold at the booking moment. Build rollout into the document itself.

• Acknowledgment tracking. Require an annual signed acknowledgment from every covered traveler and from new hires within 30 days of start. Track in HRIS so finance can pull the list for audit.
• Training cadence. Run a short walkthrough at onboarding and a refresher whenever a major rule changes, including per diem updates, a new TMC, or new approval thresholds.
• Annual review. Set a quarterly cadence for spot-checks and an October review aligned to the GSA fiscal-year rate reset.
• Change communication. Email the change, summarize what's different in three bullets, and re-export the corporate travel policy PDF with a new effective date in the filename.

A Policy That Works Is One Travelers Can Follow at the Moment of Booking

Written policy controls work when the rule is specific enough to apply before spend leaves the managed program. But policy language still has to show up where booking decisions happen.

Otto is an AI layer that sits on top of your existing TMC for mid-market programs, or handles booking directly for smaller companies without a TMC. It ingests your corporate travel policy, including budgets, cabin rules, and vendor rules, and shows within-policy and out-of-policy indicators with explanations on every flight and hotel option before the traveler confirms. That ties policy visibility to the booking decision, not the expense report.

Set up Otto to bring policy signals into booking and reduce policy leakage at the moment of decision.

FAQ

How often should a corporate travel policy PDF be updated?

Review the policy annually at minimum, and re-export the corporate travel policy PDF you distribute each time. GSA per diem rates reset every fiscal year on October 1, so a cap that was accurate in September can be invalid the next day. Treat any TMC change or supplier renegotiation as an additional trigger for a full rule review.

What are the most common policy failure reasons?

Most failures start where the policy stops being operational: hotel caps, cabin thresholds, channel rules, and exception triggers. Those are the sections travelers touch during booking, so specificity there cuts avoidable disputes and exceptions.

Should a travel policy cover hotel bookings as strictly as flights?

Yes. Hotel policy needs the same channel mandate and exception language as air, plus city caps, payment timing, personal nights, and incidentals. Those extra details prevent disputes that flight policies usually don't create.

How do I handle policy leakage?

Start with the leakage source, not the punishment. Hotel and air need clear channel rules, exception triggers, and budget limits before enforcement can move spend back into managed data.

How can I make it easier for travelers to book within policy?

Put policy status inside the booking path instead of waiting for audit. Otto ingests your travel policy and shows within-policy and out-of-policy indicators on each option during booking, which keeps more spend visible before it becomes compliance cleanup. For companies building a managed travel program, the same principle applies: show the rule where the booking decision happens.