Most corporate travel policies devote several pages to air fares and hotel caps, then dispose of ground transport in a single line about choosing the most economical option available. That line is the reason travel managers spend so much of the week adjudicating individual cases. Cars are where policy meets judgement, and a document offering no framework for judgement simply hands the decision to whoever happens to be under the most pressure.
A workable ground transport policy does three things. It tells travellers what they may arrange without asking, it gives approvers a test for everything else, and it tells finance what evidence to expect against each journey. What follows is a way of drafting each of those, together with the clauses that turn out to matter once real journeys start running against them.
Start with the decisions, not the rules
Policies fail when they are written as prohibitions. A traveller reading a list of things that are not permitted has no way to work out what to do about a seven o'clock start ninety miles from home, so they either book something defensible and unsuitable or they come to you. Write the document around the handful of decisions a traveller genuinely faces, and the rules fall out of those decisions rather than being imposed on top of them.
There are only four such decisions. Is a car warranted at all, or does rail do the job perfectly well? If a car is warranted, should it be chauffeured, a taxi, a hire car or a private vehicle with mileage claimed? Who signs it off, and does that happen before or after the journey? And which channel is used to arrange it? Answer those clearly and most of what currently reaches your inbox resolves itself.
When a car is the right answer
The most useful clause in a ground transport policy describes circumstances rather than listing job titles. Circumstances give travellers a test they can apply themselves, give approvers something concrete to point at, and remove the awkwardness of a document that appears to rank colleagues by grade alone. They also age considerably better, because roles are reorganised far more often than the underlying reasons people need a car.
Draft those circumstances from journeys your organisation actually makes rather than from a borrowed template, which will describe situations that never arise while missing the ones that do. Ask three or four assistants what they book most often and what they had to seek permission for last quarter. The list tends to write itself in an afternoon, and it will look something like the following.
- Early starts or late finishes outside the reasonable operating hours of public transport
- Journeys where confidential material or a confidential conversation travels with the passenger
- Multi-stop days where one held vehicle removes the need for repeated separate bookings
- Destinations poorly served by rail, or where the final leg of the trip is unreliable
- Client-facing collections where the arrival itself forms part of the impression
- Any traveller with a mobility, health or accessibility requirement, without further justification
- Group movements where a single vehicle replaces several individual journeys
- Return legs from evening events, particularly where alcohol has been served
Eligibility without a status hierarchy
Grade-based entitlement is easy to administer and quietly corrosive. It produces a document in which the same overnight journey is appropriate for one colleague and extravagant for another, which is difficult to defend and unpleasant to enforce. It also fails at the edges, because the people who most often need a car at an unreasonable hour are rarely the most senior ones in the building.
A better construction sets a default for everyone, then names the circumstances that lift it. Seniority can still appear, but as one circumstance among several rather than as the organising principle. Where a traveller has an accessibility or health requirement, the policy should say plainly that no case needs to be argued and no explanation recorded on a claim form, which spares people from disclosing more than they wish to.
Approval that survives Friday afternoon
Approval processes are designed on quiet Tuesdays and tested at five o'clock on a Friday when the approver is on a flight. If the only route is a named individual, the policy will be broken routinely and nobody will tell you. Build the escape route into the document rather than leaving people to invent one, and you keep visibility of the exceptions instead of losing them.
The design principles are unglamorous but they hold. Keep the number of approvals low, make deputies explicit, allow retrospective sign-off for genuinely urgent travel with a short written reason, and set a threshold in terms of journey type rather than value so nobody is doing arithmetic at the kerb. A few structural choices prevent most of the friction.
- A named deputy for every approver, published rather than assumed
- A defined category of journeys that need no approval at all
- A retrospective route for genuine urgency, with a one-line written reason
- A single owner for disputes, so nothing circulates between departments
- A stated response time, after which the traveller may proceed and notify
- An annual list of standing approvals for recurring or scheduled journeys
Booking channels and named suppliers
A policy that permits a car without saying how to arrange one produces a long tail of personal accounts, ad hoc apps and receipts that nobody can reconcile. Name the channel. If assistants book directly with a chauffeur supplier, say so and say who holds the relationship. If everything routes through a travel team or an online tool, make the exceptions explicit rather than leaving people to guess when the tool will not do.
Be specific about who may instruct a change once a journey is running, because that is where most confusion originates. If a traveller can redirect a car directly from the back seat, the policy should permit it and require that the booker is copied. If it must come through a central point, the supplier needs to be told that too, otherwise a well-meaning chauffeur will follow the instruction in front of him.
It is worth stating what the organisation expects of a supplier as well as what it expects of travellers. Written quotations before confirmation, a clear position on waiting and schedule changes, and a single point of contact are reasonable things to require, and they give you something to hold a supplier to when a journey goes badly.
Testing the policy against real journeys
Before publication, run the draft against a dozen journeys from the past quarter and see what it produces. Pick awkward ones deliberately: the site visit that needed three vehicles, the overnight return from a regional office, the client collection that ran two hours late. If the policy gives an obviously wrong answer, or no answer, the fault is in the drafting rather than in the traveller who ignored it.
Then diarise a review. Ground transport patterns shift with office footprints, hybrid working and where clients happen to be based, and a policy written for one arrangement of offices reads oddly against another. An annual pass, informed by what assistants actually escalated during the year, keeps the document connected to how people travel rather than to how they travelled when it was written.
