The One-Page Travel Policy Your Team Will Actually Follow
Most small company travel policies are twelve pages nobody has read. They were adapted from a template, approved by someone who does not travel, and stored in a shared drive where they are opened exactly twice: when a new hire is onboarded and when an expense report is disputed. Meanwhile employees book whatever seems reasonable, finance reconciles it after the fact, and both sides are mildly annoyed.
Policies fail for a specific reason
A long policy fails because it answers questions nobody asked while leaving the actual questions ambiguous. An employee standing in an airport at six in the morning wants to know three things: can I book this, how much can I spend, and who do I call. If the document does not answer those in under a minute, it will not be consulted, and the employee will make a reasonable guess. Reasonable guesses are not the problem. Inconsistent reasonable guesses are, and they are the pattern Wilton Vida is usually called in to fix.
The second failure is enforcement by exception. A policy that is technically strict but routinely waived teaches everyone that the real rule is who you ask. That is worse than a permissive policy applied evenly, because it creates the perception of favoritism and it produces spend data that means nothing.
What belongs on the one page
Start with booking channel. One sentence naming where travel is booked and what happens if it is booked elsewhere. This is the single highest-leverage line in the document, because a company that does not know where its people are cannot support them when something goes wrong, and cannot negotiate anything with suppliers.
Then class of service, stated by flight duration rather than by seniority. A rule that reads "economy under six hours, premium economy or business above six hours" is understood instantly and applied consistently. A rule that reads "at the discretion of the department head" is not a rule.
Then lodging, expressed as a per-night cap by city tier rather than a single national number, because a cap that works in Tampa is meaningless in New York. Then meals, as a simple daily figure rather than an itemized schedule, which reduces receipt volume and the administrative cost of processing it. Then ground transport, naming what is reimbursable and what is not. Then the approval threshold: one number above which a trip needs sign-off, and who gives it.
Finally, a personal travel clause, which most small company policies omit entirely. Employees extend trips. Saying so explicitly, and stating that personal days are permitted at the employee's own cost with the business portion booked separately, prevents the most common expense report dispute there is.
What does not belong on it
Airline and hotel brand preferences do not belong in the policy document. They change, and every change requires reissuing the policy. Put them in a separate booking guide that can be updated without ceremony. Detailed receipt requirements belong in the expense system, where they can be enforced automatically rather than read. Safety and emergency procedures deserve their own short document, because burying them on page nine of a spend policy guarantees nobody finds them under pressure.
The part most companies skip
Duty of care is the obligation to know where your travelers are and to be able to reach them. For a company of fifteen this sounds like an enterprise concern. It is not. It is the reason a founder should be able to answer, within ten minutes, whether anyone from the company is currently in a city where something has just happened.
That capability comes almost entirely from consolidating bookings through a single channel. It is the practical argument for the booking channel line at the top of the page, and it is more persuasive to most owners than the savings argument, because the savings are abstract and a stranded employee is not.
Make it real in ninety days
Write the page. Have the two or three most frequent travelers read it and mark anything they would guess wrong. Fix those lines. Circulate it once with a short note from an owner explaining why it exists, which is usually a combination of predictable costs and being able to help people when a trip breaks. Then apply it evenly for a quarter and revisit. A policy that survives one quarter unchanged is a policy that fits the company.
Resist the urge to add to it. Every addition after the first page is a deduction from the odds it gets read.
Where we come in
Wilton Vida builds travel programs for companies that are too small to staff a travel manager and too busy to keep improvising. That means drafting the one-page policy against how your team actually travels, standing up the booking channel behind it, and serving as the number employees call when something goes wrong at an inconvenient hour.
Through Travel Leaders Network we bring negotiated fares, hotel programs, and partner amenities that a fifteen-person company cannot access on its own, which is frequently where the program pays for itself. But the more durable benefit is simpler. Everyone books the same way, finance knows what a trip costs before it happens, and somebody who is not the founder is awake when a flight cancels.
Preparamos la política y damos soporte a su equipo en español y en inglés.
If your travel policy is twelve pages or zero pages, both are fixable this quarter. Reach our team at wiltonvida.com or connect on WhatsApp at https://wa.me/message/YUIL7UEHTZDAM1.