Moving one executive to an airport is a booking. Moving fourteen colleagues to the same airport for the same conference is a project, and the difference is not simply one of scale. A group has internal structure: people leaving from different addresses, arriving on different flights, carrying wildly different amounts of luggage, and holding strong private views about how early they wish to arrive.
Handled as fourteen separate bookings it becomes unmanageable and expensive in coordination alone. Handled as one movement with a manifest behind it, it becomes straightforward. This sets out how to build that manifest, how to divide the group sensibly, and which parts of a team transfer reliably cause trouble.
A group is not one big booking
The common mistake is to treat a team movement as a single large vehicle problem, when it is really a sequencing problem with several vehicles in it. Colleagues live in different places, and a coach that collects everyone from the office at once forces half the group to travel to the office first, often at an hour that makes the whole exercise longer than travelling independently would have been.
Start instead from where people actually are. Some will be collected from home, some from a shared point, some are already staying near the airport and need nothing. Once the origins are laid out, the vehicle plan follows naturally, and it usually involves fewer vehicles than people fear and more than a single coach.
Build a manifest first
Nothing about a team transfer can be arranged sensibly until the manifest exists, and it is worth building it as a single shared document rather than assembling it from replies to an email. People change their flights, add a night, or decide to make their own way, and a document that is updated in place stays accurate where a thread does not.
Ask for the following from each traveller. Collecting it once, properly, is what turns the exercise from a fortnight of correspondence into an afternoon's work.
- Name, and the mobile number they will actually answer on the day
- Flight number, terminal and scheduled departure or arrival time
- Origin address, or the shared collection point they intend to use
- Number of hold bags and cabin bags, counted rather than estimated
- Whether they are travelling on the return leg or extending the trip
- Any mobility, accessibility or seating requirement
- Whether they would rather travel alone or with colleagues
- Who to contact if they cannot be reached on the morning
Splitting the group across vehicles
Once you have the manifest, group people by geography first and by flight second. Colleagues living within a reasonable radius of each other share a vehicle; those who do not travel separately. Resist the temptation to group by seniority or by team, which produces vehicles that criss-cross the county to collect people who could have walked to each other.
Be realistic about how many people belong in one vehicle once luggage is counted. A vehicle rated for a certain number of passengers will not carry that number with a hold bag each, and this is where team transfers most often fail at the kerb. If in doubt, plan for the luggage and let the seating be comfortable rather than exact.
Staggered flights and shared meeting points
Teams rarely fly together. Two colleagues are on an earlier service, three are connecting from a regional airport, one is coming back a day later. A movement plan that assumes a single departure and a single return will be wrong for a third of the group before it is even circulated.
Where flights are spread across a morning, group travellers into departure bands rather than trying to accommodate each individually. Where a shared collection point makes sense, name it precisely, state the time the vehicle leaves rather than the time it arrives, and be clear that it will not wait beyond a stated point. Groups run late in a way individuals do not, and a stated departure time is the only thing that prevents one person delaying eleven others.
Luggage volume is the usual failure
Ask any assistant who has organised a team movement and this is the story they tell: the vehicle arrived, the seats were sufficient, and the boot was not. Groups travelling to conferences and offsites carry stand materials, promotional items and equipment on top of personal luggage, and none of that appears in a passenger count.
Count items rather than people, ask specifically about anything that is not a suitcase, and consider sending bulky materials ahead separately. Where equipment must travel with the group, say so when booking and specify a vehicle chosen for load space. A vehicle with generous boot capacity and one empty seat is a considerably better outcome than a full one with cases on laps.
The return leg and late changes
Return legs change more than outbound ones. People extend, leave early, switch flights after a client meeting runs over, or decide to travel back with a colleague. Build the return with that expectation rather than treating it as the outbound reversed, and name a single person authorised to make changes so the supplier is not receiving conflicting instructions from four travellers.
A short discipline around the return keeps it manageable, and it takes very little effort if it is agreed before departure rather than negotiated over messages from a foreign airport.
- One named coordinator authorised to change the return arrangements
- A stated cut-off for changes, communicated before the group departs
- Confirmation of the return manifest the day before travelling back
- A meeting point at the arrival airport, given to travellers in writing
- A plan for anyone whose inbound flight is delayed past the group's departure
- Additional luggage capacity assumed, because groups return with more
