Roadshows are the most demanding thing a chauffeur does, and also the most rewarding to get right. A team moves through eight or ten meetings in a day, sometimes across two cities, carrying materials and running to a schedule that was built by someone optimistic. The car is not transport in that context; it is the only fixed point in the entire day.
Because of that, roadshow travel is bought differently. Nobody books ten transfers. You book the car and the chauffeur for the duration and let the schedule move within it. What that costs depends on the density of the meetings, how many cities are involved, how many people are travelling and how the days are stitched together, and each of those is worth understanding before the itinerary is fixed.
A roadshow is a schedule, not a trip
The defining feature is that the plan will change. A meeting is added at nine the night before, another runs twenty minutes over, a third moves across town, and the order of the afternoon is rewritten in a taxi rank. An arrangement built on individually booked journeys collapses under that. One built on held hours simply absorbs it.
This is why the sensible unit is the day, or the block of days, rather than the leg. It also explains why roadshow quotations look different from ordinary transfer quotations: they describe a period of exclusive availability, a chauffeur briefed on the whole itinerary, and a vehicle that stays with the team rather than being released and re-summoned.
The practical benefit is enormous and slightly hard to see on paper. Materials stay in the car. Coats stay in the car. Nobody has to find a vehicle in the rain between the fourth and fifth meeting. The team arrives at each address composed rather than harried, which is the entire point of the exercise.
Cars are held, not journeys sold
In a dense city schedule, the driving is a small fraction of the day. Most of the hours are spent standing near an office waiting for a meeting to finish, which means the cost is dominated by availability rather than by mileage. That is the honest position, and it is why comparing a roadshow to a series of point-to-point fares is not a useful exercise.
It also means the schedule's shape matters more than its geography. Six meetings clustered in one district is a comfortable day. The same six spread between two financial centres involves real driving between each, longer margins, and a much greater chance that one overrun rewrites the afternoon. Where the meeting order can be arranged geographically, it usually should be.
- The number of meetings and how tightly they are spaced
- Whether appointments cluster in one district or spread across a city
- Standing and parking arrangements near each address
- How much material or equipment travels with the team
- The earliest start and the latest finish across each day
- Any evening dinner or event at the end of the schedule
City density and standing time
London, Edinburgh, Manchester and the other financial centres share a common difficulty: there is nowhere legal to stand outside most offices. A chauffeur therefore circles, uses a nearby car park, or finds a legal spot and walks the team to the door. Each of those consumes time and, in the case of parking, charges that attach to the day.
Congestion charging and emissions requirements apply on top, and the exact combination depends on the city and the hours worked. None of this is dramatic in isolation, but across a week of meetings it is a real component of the arrangement, and a quotation that does not mention it at all is worth a second look.
Multi-city legs and repositioning
The moment a roadshow crosses cities, two new questions appear: how the team travels between them, and what happens to the car. Sometimes the answer is that the same car and chauffeur drive the leg, which suits a team that wants to keep working and to arrive with their materials intact. Sometimes it is a train or a flight, with a separate car meeting the team at the far end.
Both are perfectly good arrangements and they cost quite differently, so it is worth deciding deliberately rather than by default. If the car does travel, remember that it has to get back at some point, and building that into the plan is better than leaving it as an unpriced assumption. Where flights are involved, giving us the flight numbers lets each collection be planned around the published schedule.
Where roadshow budgets leak
The commonest leak is booking two vehicles when one would do, usually because the team grew by one person after the arrangement was made. A luxury MPV carries a team of four or five with their materials comfortably and keeps everybody together, which is worth more on a roadshow than the marginal comfort of separate saloons.
The second is holding cars beyond the point at which they are needed, because nobody wanted to make the call. A short message releasing the vehicle at the end of the day costs nothing and is genuinely useful. The third is late confirmation of a schedule that was largely known a week earlier, which pushes the whole arrangement into whatever availability remains.
Send us the draft itinerary as early as you have one, even in rough form, with the cities, the dates, the team size and any known fixed points. Roadshows are quoted individually and in writing, with the held hours, the vehicle and the terms set out, and we would far rather revise a plan twice than build one from a half-finished schedule.
- Two cars booked where one larger vehicle would carry the whole team
- Vehicles held after the last meeting because nobody confirmed the finish
- Late schedule confirmation for dates that were known well in advance
- Cross-city legs left unplanned until the morning they happen
- Airport collections without flight numbers, forcing wider margins
