Policy & finance
How to Write a Corporate Travel Policy (+ Checklist)
What to include, how to write one people follow, and a free section-by-section checklist.
How to Write a Corporate Travel Policy (+ Checklist)
Most corporate travel policies fail for the same reason: they're written to restrict people, not to be used. The result is a ten-page document nobody reads, out-of-policy bookings that only surface at month-end, and a finance team chasing receipts. A good policy does the opposite, it makes the compliant choice the easy one. This guide covers what to include, how to write one people actually follow, and a section-by-section checklist you can copy. In the rollouts we've seen, the policies that stick are the short ones people can hold in their head; the exhaustive ones get skimmed once and quietly ignored.
It's written for the ops manager, office manager, or finance lead drafting (or fixing) a travel policy for a growing company.
Key Takeaways
• A travel policy's job is to make the right booking the easy booking, not to list rules nobody reads.
• Cover the essentials: booking process, approvals, budgets and caps, preferred vendors, expense rules, and duty of care.
• Keep it short, tie limits to real budgets, and write for the traveller, not the auditor.
• Enforcement happens at the point of booking, not at month-end. That's where most policies quietly break.
What is a corporate travel policy, and why bother?
A corporate travel policy is the agreed set of rules for how your people book, pay for, and expense business travel: flights, hotels, ground transport, and everything around them. At a small company it often lives in someone's head or a Slack thread. That works until it doesn't.
The reason to write it down isn't bureaucracy. It's that an unwritten policy can't be enforced, measured, or scaled, and it quietly costs money through out-of-policy bookings, unused negotiated rates, and reconciliation that eats days each month. A clear policy gives travellers confidence they're doing the right thing and gives finance a baseline to hold spend against.
Think of it as infrastructure, not paperwork.
What should a corporate travel policy include?
Cover six areas, and no more than you need. A policy that tries to legislate every edge case becomes the policy nobody reads. The essentials:
Booking process. Where and how to book (the approved tool or channel), and how far in advance.
Approvals. What needs sign-off, from whom, and above what threshold.
Budgets and caps. Spend limits by trip type or employee grade (flight class, hotel nightly rate, meal per diems).
Preferred vendors and rates. The airlines, hotel chains, and any negotiated rates travellers should use.
Expenses. What's reimbursable, what isn't, receipt rules, and the submission deadline.
Duty of care and safety. How the company tracks travellers, and what to do in a disruption or emergency (the ISO 31030 travel-risk-management guidance is a useful reference).
If a section doesn't change a booking decision, it probably belongs in a separate handbook, not the policy.
How do you write one people actually follow?
Write it for the traveller, and make compliance the path of least resistance. Four principles do most of the work:
Keep it short. One to three pages beats ten. People follow what they can remember.
Tie limits to real budgets, not round numbers. A hotel cap that reflects actual city rates gets respected; an arbitrary one gets ignored or exceptioned.
Make the compliant option the default. If booking in-policy is slower than booking direct, people book direct. The easy path has to be the right one.
Say what happens out of policy. Not as a threat: as clarity. People comply when the consequence is predictable, not when it's punitive.
Then communicate it. A policy launched in a single email and never mentioned again is a policy that will drift within a quarter.
The corporate travel policy checklist
Use this as your section-by-section outline: copy it, fill each line for your company, and you have a first draft.
1. Scope and purpose
Who the policy applies to (employees, contractors, grades)
What it covers (flights, hotels, rail, ground, ancillaries)
2. Booking
Approved booking channel or tool
Advance-booking window (e.g. flights 14+ days ahead where possible)
How to handle exceptions
3. Approvals
What requires pre-trip approval
Approval thresholds and approvers
Turnaround expectation
4. Budgets and class of service
Flight class rules by trip length or grade
Hotel nightly caps (by city tier if useful)
Meal per diems / ground-transport limits
5. Preferred vendors and rates
Preferred airlines / hotel groups
Negotiated or corporate rates and how to apply them
6. Expenses
Reimbursable vs non-reimbursable
Receipt and submission rules + deadline
Payment method (corporate card vs reimbursement)
7. Duty of care
How travellers are tracked / reachable
Emergency contacts and disruption process
Insurance coverage
8. Governance
Policy owner and review cadence
How out-of-policy bookings are handled
A sample policy, in practice
The checklist tells you what to include; here's what filled-in lines look like, for an illustrative 80-person APAC company. Yours will differ: the point is the tone and specificity, not the numbers.
Booking. Book all flights and hotels through [approved channel]. Book flights at least 14 days ahead where the trip is known. Off-channel or last-minute bookings need manager sign-off.
Class of service. Economy for flights under 6 hours; premium economy permitted over 6 hours with manager approval. Hotels: up to S$250/night in Singapore and Tokyo, S$150 in Kuala Lumpur and Bangkok, use the preferred-rate option first.
Approvals. Trips under S$2,000 need no pre-approval if in policy; above that, or any exception, needs manager sign-off before booking.
Expenses. Meals reimbursed to S$60/day; alcohol not reimbursable; submit within 14 days with receipts.
Duty of care. Your itinerary is recorded when you book through the channel. In a disruption, contact [name/number] first.
Notice what this does: every line is a decision a booker can act on without asking, the caps are tiered to real city rates, and exceptions have a clear path rather than a flat "no". That's the difference between a policy that gets used and one that gets worked around. (Figures are illustrative.)
How do you actually enforce a travel policy?
Here's the part most policies get wrong: enforcement has to happen at the point of booking, not at month-end. A rule that's only checked when expenses are reconciled is a rule that's already been broken: the money is spent, the trip is taken, and finance is left chasing an exception after the fact.
The fix is to move the guardrails into the booking moment. That means the caps, the preferred rates, and the approval thresholds are applied when someone books, so an out-of-policy choice is flagged or blocked before it costs anything. We think the policies that actually hold are the ones enforced at the booking screen, not the ones with the most clauses.
Enforcement approach | When rules are checked | Result |
Audit-only (month-end) | After the trip | Breaches caught too late: the money is already spent |
Enforced at booking | At the booking moment | Out-of-policy choices flagged or blocked before they cost anything |
Some companies do this with a travel platform: a system like Accomy, for instance, can apply your price caps and negotiated rates at the point of booking, so the policy enforces itself rather than living in a PDF. However you do it, the principle holds, a policy you can only audit is weaker than one you can apply.
Common mistakes that kill a travel policy
Most failed policies fail the same handful of ways. It's worth checking yours against them:
Too long. A ten-page document is one nobody reads. If it can't be skimmed in two minutes, it won't shape a booking made in two minutes.
Round-number caps. A single global hotel cap ignores that cities price differently. It's either too generous or unbookable, and both breed exceptions. Tier caps to real markets.
No easy compliant path. If the in-policy route is slower than booking direct, the policy loses. Adoption is a user-experience problem before it's a compliance one.
Written for the auditor, not the traveller. Pages of "the Company reserves the right to…" get ignored. Write in plain language, to the person actually booking.
Set and forgotten. Rates, routes, and markets change; a policy nobody reviews slowly stops matching reality and quietly loses authority as people notice it's stale.
All stick, no service. A policy that only restricts, with no help when a trip breaks, feels like a tax. Pair the rules with a way to reach support.
If your current policy is being widely ignored, the cause is almost always somewhere on this list, not a lack of willpower from travellers.
A written policy sets the rules. Enforcing them where the money is spent is what makes it real.
Frequently Asked Questions
What should a corporate travel policy include?
Six essentials: the booking process (where and how to book), approvals (what needs sign-off and from whom), budgets and caps (flight class, hotel rates, per diems), preferred vendors and negotiated rates, expense rules (what's reimbursable, receipts, deadlines), and duty of care (how travellers are tracked and supported in a disruption). Keep anything that doesn't change a booking decision in a separate handbook.
How long should a travel policy be?
As short as it can be while still covering the essentials, typically one to three pages. People follow a policy they can remember. A long document that legislates every edge case tends to go unread, which defeats the point. Put detail in appendices or a handbook, and keep the core policy scannable.
How do you get employees to follow the travel policy?
Make the compliant choice the easy one. Tie caps to real city rates (not arbitrary numbers), ensure the approved booking route is at least as fast as booking direct, state clearly what happens out of policy, and communicate the policy more than once. Enforcement at the point of booking (where caps and rates are applied automatically) beats catching breaches at month-end.
What's the difference between a travel policy and an expense policy?
A travel policy governs how trips are booked and what's allowed (flights, hotels, approvals, caps); an expense policy governs how costs are claimed back and reimbursed. They overlap heavily and are often combined into a single travel-and-expense (T&E) policy, which is usually the cleaner approach for a smaller company.
How often should you review a travel policy?
At least annually, and after any material change: a new office or market, a shift in travel volume, or new negotiated rates. Assign a named owner (usually ops or finance) so the review actually happens. Rates and routes change; a policy that's never revisited slowly stops matching reality.
Quick Takeaways
A policy's job is to make the right booking the easy booking.
Cover six areas: booking, approvals, budgets/caps, preferred rates, expenses, duty of care.
Keep it to 1–3 pages; tie caps to real city rates.
Enforce at the point of booking, not at month-end.
Assign an owner and review it at least once a year.
About Accomy: Accomy is an APAC-first travel operating system for SME and mid-market companies, covering booking, negotiated rates, policy, and payment. More at About Accomy.
Related reading:
How to cut business travel costs (the savings side of the same problem)
Managed vs unmanaged travel (when a policy needs a system behind it)
Duty of care for SME travel programs (traveller safety in practice)
Sources & notes
This is a practical how-to grounded in standard corporate-travel practice; figures (page length, advance-booking windows) are rules of thumb, not cited statistics.
Accomy product capabilities referenced (applying price caps and negotiated rates at booking) are per Accomy's internal product reference; deeper approval-workflow automation is on its roadmap, not described here as live.