The Coordination Problem
A team of eight arriving at the same airporto on six different volos within a 90-minute window sounds manageable. In practice, it involves six different orario di arrivos, potentially terminal multipli, varying baggage volumes, and at least one volo that will almost certainly be delayed. Without a coordination plan, the team self-organizes at arrivi in an airporto they may not know — everyone calling each other, waiting for stragglers, and arriving at the destination in an unplanned sequence.
The solution is to make all decisions ahead of time and communicate them clearly before anyone travels. This is a central aspect of how group reservations for events work at scale — the same logic applies to a team traveling to an offsite or a multi-person delegazione.
Building the Arrival Matrix
Start with a simple table covering every person, their volo, estimated orario di arrivo, terminal, and numero di bagagli. This is the working document for all transfer decisions.
| Name | volo | orario di arrivo | terminal | bagagli | Transfer Group |
|---|---|---|---|---|---|
| Person A | LH 4422 | 14:10 | T1 | 1 bag | Group 1 |
| Person B | BA 2134 | 14:25 | T1 | 1 bag | Group 1 |
| Person C | AF 1876 | 14:40 | T2 | 2 bags | Group 2 |
| Person D | IB 3301 | 15:05 | T2 | 1 bag | Group 2 |
Once the arrival matrix is complete, grouping decisions become straightforward: people arriving within 30 minutes from the same terminal can share a veicolo. People arriving from different terminals or with long delays should be on separate prenotaziones.
How to Group arrivi Efficiently
A 30-minute window is meaningless if the volos arrive at different terminals. Grouping must account for terminal location — mixing terminals creates long waits at the veicolo.
Three to four people per Monovolume is comfortable. Five with bagagli is tight. Don't over-fill veicolos to reduce veicolo count — it creates discomfort and risks if a bag doesn't fit.
Group cost-efficiency doesn't apply to the most senior traveler or any client who is joining the team. They should have a dedicated veicolo regardless of the grouping logic.
Everyone needs to know: who they're sharing with, which veicolo to look for at arrivi, and what to do if they can't find the veicolo or their group member is very late.
When a volo Is Delayed
A delay of 45 minutes or more should automatically trigger a reassignment decision: does the delayed person wait (with a new veicolo prenotazione), or does the rest of the group proceed without them? This decision rule should be established before travel — not negotiated by phone from a crowded area arrivi.
Define your threshold in anticipo. A common rule: if one traveler is delayed more than 45 minutes, the group proceeds and the delayed person gets an individual veicolo. The prenotazione system needs to reflect this — which means someone needs to monitor volo status and make the reprenotazione call as soon as the delay is confirmed, not when it's already happened.
Communication Before and During Arrival
Send every team member their transfer details 48 hours before partenza: which veicolo group they're in, the autista name or prelievo identifier, the exact luogo di prelievo inside the terminal, and an emergency contact number. This eliminates the calls that happen when people arrive and don't know where to go.
The broader framework for airporto prelievo operations details exactly what autistas need to know and what escalation steps are in place if something doesn't go as planned — making sure every arrival, whether on-time or delayed, results in a successful handoff.
To explore Transferhood directly, you can visit the main platform.