Ground transport fragments quietly. An office opens, somebody needs a car for a visiting director, a local firm is found and does the job well, and eight years later that firm is embedded in a way nobody ever decided. Repeat across six locations and an organisation ends up with six relationships, six sets of expectations and no ability to answer a straightforward question about how its people travel by road.
Consolidation is worth doing for reasons that have very little to do with negotiating leverage. It gives you one standard, one assurance file, one escalation route and a single view of activity. This sets out how to audit what happens now, decide the shape of the arrangement, and bring offices across without provoking a defence of the status quo.
How fragmentation happens
Nobody chooses fragmentation. It accumulates through a series of individually sensible decisions made under time pressure by people solving an immediate problem. The local arrangement usually works well for the local office, which is precisely why it persists and why an attempt to replace it is received as an accusation rather than as an improvement.
Recognising that shapes how you approach the exercise. The office with its own arrangement is not being obstructive; it has something that functions and is being asked to swap it for something unproven. Any consolidation that does not offer the local team something they visibly gain will be complied with on paper and circumvented in practice, which is worse than leaving things alone.
Mapping what each office does now
Before proposing anything, find out what actually happens. This is harder than it sounds, because much of the activity sits outside any central system: personal accounts, local suppliers invoiced directly to a site budget, taxi accounts held by a receptionist, and occasional bookings made by assistants who never thought of them as travel. The picture is usually broader than the reporting suggests.
Ask the people who book rather than reading the ledger, and ask them about behaviour rather than volume. A short conversation per site will produce the following, and the exercise itself often surfaces the strongest advocates for a change.
- Which suppliers each office uses and how the relationship began
- Who books, and whether they book for one traveller or many
- How bookings are paid for and which budget they land against
- What the office believes it gets locally that it could not get centrally
- Which journey types recur, and which arise only occasionally
- What has gone wrong in the past year and how it was resolved
- Whether any local arrangement involves a personal account or card
One supplier or several
The instinctive answer is one supplier everywhere, and it is usually right, but only where that supplier has genuine reach rather than a map with pins in it. What matters is whether the standard holds in your smallest location as reliably as in your largest, which comes down to how the supplier selects and briefs the professional operators it works with beyond its own cars.
A defensible alternative is a principal supplier for the majority of activity with a named local arrangement retained where geography or a specialist requirement justifies it. That is not a failure of consolidation. What you are eliminating is the unmanaged long tail, not every exception, and a policy that acknowledges two or three deliberate exceptions is far more durable than one that pretends there are none.
Writing the standard everyone books to
Consolidation delivers value through consistency of specification, not merely consistency of supplier. Write down what a booking looks like: the information captured, the vehicle expectations, how waiting and overruns are handled, what a confirmation contains and how a journey is coded. Offices then have something concrete to book against, and the supplier has one brief rather than six local interpretations.
Keep the standard short and give it to the people who book rather than filing it with policy. A single page that an assistant can follow beats a governance document that nobody opens, and it makes the eventual comparison between locations meaningful because everyone is describing the same thing in the same way.
Bringing offices across without a fight
Sequence matters more than persuasion. Start with the location that has the weakest existing arrangement and the most to gain, run it properly for a quarter, then let that office describe the experience to the next one. Internal testimony from a peer does more than any amount of central advocacy, and it gives you a real account of what needed adjusting.
Handle the transition with more care than the decision. Local suppliers are often people the office likes, and how the relationship is ended is noticed. A staged approach removes most of the resistance.
- Begin where the current arrangement is weakest, not where volume is highest
- Run a genuine trial in that location before extending the decision
- Let the first office brief the second, in their own words
- Give each site a named contact at the supplier from the first day
- Keep any deliberate local exception explicit rather than tolerated quietly
- Agree how existing local relationships are wound down, and by whom
- Set a review date per office so problems surface early rather than fester
What consolidation does not fix
It will not fix an absent policy. If travellers do not know when a car is appropriate, routing them to one supplier simply centralises the ambiguity. Nor will it fix a booking process that captures no coding, because the information gap persists regardless of who supplies the vehicle. Address those alongside consolidation rather than expecting the supplier change to resolve them.
It also will not eliminate exceptions, and an arrangement designed on the assumption that it will is fragile. Build in a route for the genuinely unusual journey, make it visible rather than hidden, and treat its frequency as a diagnostic. Exceptions that recur are telling you something about the standard rather than about the people using it.
