During WEF week, a delegation that arrives together does not necessarily finish its Davos evening together. Some guests may leave after dinner, while others remain for a discussion or attend another function. The transport plan should reflect those different commitments. Agree the groups and decision points beforehand so an early traveller is not stranded waiting for the last meeting, and a later traveller does not assume the first car will return automatically.
Group passengers by their next destination
Start with where each person needs to go, then add the earliest practical departure time. Several travellers finishing at different venues may still share a later ride, but only if the collection sequence is agreed and acceptable to everyone. Do not combine people solely because they belong to the same organisation. Hotel location, luggage and individual commitments may make separate movements more practical than one complicated circuit.
An evening plan might contain one early hotel return and one later departure from a different venue. Give these movements distinct labels in the organiser’s list. Guests can then identify their own collection without trying to infer it from a shared chat in which the most recent message may concern somebody else.
Distinguish fixed collection from uncertain release
If a guest must leave at a particular time, request a fixed pickup and tell the host about that deadline. For a discussion with an uncertain end, ask dispatch what service arrangement can accommodate the uncertainty. A message saying pickup after the event does not establish a specific time or an unlimited waiting commitment. Record how readiness will be communicated and when the car can be expected after that communication.
Assign a contact to each departing group
Each group needs a lead passenger who has the current instructions and can confirm the whole party is ready. Give dispatch that person’s mobile number. The delegation organiser may be elsewhere by then and should not be the only contact available. If the group changes during the evening, update the names and count so nobody is left waiting for a colleague who has moved to another departure.
Agree what happens when the evening extends
Decide who can approve a changed pickup, extra stop or additional journey. Tell guests that changes require acknowledgement, particularly when a car is already assigned elsewhere after the agreed service. Keep the conversation factual: venue, passengers, requested time and reference. Avoid promising a revised collection to the whole delegation before dispatch has reviewed whether the change is possible and what fare applies.
Close each movement individually
When a group has departed, mark that movement complete in the organiser’s list and leave the remaining journeys visible. A single message saying the delegation is on its way can confuse colleagues whose transport has not yet started. After the final pickup, check that every named guest has a clear destination and confirmed arrangement. This creates a useful record without requiring the organiser to follow private conversations or track travellers beyond the transport task.
Questions about this journey
Can everyone share one return time?
Only if the whole group agrees and the service is confirmed for that time.
Does an early car automatically return for later guests?
No. Request and confirm each movement or an appropriate retained service.
Who should contact dispatch at the end of dinner?
The designated lead passenger for that departure group.