Travel, VIPs and Departure: Connect Every Guest Handover

Define support from need, not a label

VIP can describe several different requirements: a senior decision-maker, a speaker with a fixed appearance, a guest needing privacy or someone with a particular assistance request. Do not assume that the label tells the team what to do. Ask the authorised client contact to define the actual arrangements, decision rights and boundaries.

Create a guest-support brief stating the contact owner, confirmed requirements, arrival and departure plan, programme commitments and escalation route. Share only the detail each service owner needs. Personal preferences or itineraries should not be circulated widely as part of a general crew pack.

The client guest owner approves the intended support; the liaison coordinates it; the event lead resolves dependencies with programme, venue and transport. The first gate is a specific brief rather than a general instruction to provide special treatment. For invitation and response ownership, connect this plan to From Invitation to Registration: Plan the Arrival Before the Queue.

Maintain an itinerary register that distinguishes estimates

For guests receiving travel coordination, record the confirmed itinerary, responsible booking contact, arrival status, transfer assignment and next handover. Distinguish scheduled, estimated and confirmed information. An expected arrival time is not a guarantee that a guest is available for a programme cue.

Agree who monitors changes and how the guest contacts support. Do not rely on several people forwarding fragments of travel information to different drivers or hosts. The travel owner maintains the current record, while the transport owner confirms the service arrangement and the programme liaison understands the effect of changes.

Check dependencies such as hotel access, holding arrangements and preparation time before a speaker commitment. Relevant providers and client policies govern booking terms and travel requirements; this guide does not prescribe them. The itinerary gate confirms who owns each leg and what happens if a connection changes. A complete journey includes the return arrangement, not only the impressive arrival.

Make airport transfers a verified handover

A transfer plan needs a meeting instruction, guest contact route, transport contact, assigned service and escalation owner. Explain how the guest identifies the representative and what to do if the meeting does not happen. Confirm the practical pickup arrangement with the responsible transport provider and applicable venue or terminal requirements.

The transport owner should know which itinerary changes affect dispatch, while the guest liaison should know when a transfer is actually under way. Avoid treating an unconfirmed message that a vehicle has arrived as proof that the guest has been met. Use status updates tied to meaningful handovers, such as meeting confirmed and destination handover completed.

Prepare for a missed connection or changed arrival without promising a universal recovery time. The travel owner establishes the facts, the transport owner proposes available options and the authorised client contact approves changes where required. Programme consequences go to the event lead, not directly into an improvised instruction to the stage team.

Coordinate speaker and VIP holding with the programme

A holding space should serve a defined purpose: preparation, briefing, privacy or a short wait before a programme commitment. Confirm who may enter, who hosts the guest and who signals the next movement. The venue must review the actual use and access arrangements. Do not designate a service route or circulation area as holding simply because it is close to the stage.

The liaison confirms readiness with the programme lead before moving the guest. The speaker may need the current introduction, session format, approved content or a brief meeting with the moderator. Those inputs should be scheduled rather than squeezed into the final approach to the stage.

If a guest asks for a programme change, the liaison records the request and routes it to the authorised decision owner. Courtesy does not require making an uncoordinated promise. The holding gate confirms the person, preparation, route and receiving owner. See The Conference and Summit Playbook: Plan the Programme Around the Audience for speaker content and panel preparation.

Scenario: a speaker's flight is delayed

Imagine a speaker reporting a delayed flight before a fixed session. This is hypothetical. The risk is that transfer, preparation and programme assumptions all become uncertain at once. A common failure is to share an optimistic arrival estimate as though it were a confirmed stage-ready time.

The travel owner establishes the best available information and its uncertainty. The transport owner assesses the revised handover. The speaker liaison tells the event lead what preparation is still required after arrival. The programme owner then evaluates approved alternatives, such as moving an available session or changing the discussion format, with affected leads confirming feasibility.

Set a decision checkpoint rather than waiting indefinitely. The client approver accepts the revised programme where necessary, and the programme lead distributes one update. If remote participation is considered, the responsible production team must assess and check it; a phone connection is not automatically a ready hybrid session. The intended outcome is an honest and coordinated decision. The detailed show-recovery response belongs with the operations scenario guide.

Plan valet as a guest and venue interface

Where valet is part of the event arrangement, confirm the scope and operating process with the venue and service provider. Identify the approved arrival and collection points, how guests request their vehicle, how queries are handled and who communicates changes. Do not imply a collection time that the provider has not established for the actual conditions.

Map the relationship between vehicle activity, pedestrians, transfers and other property users with the responsible venue and transport owners. This is a planning interface, not traffic-management design. Required permissions, safety arrangements and operating rules need their appropriate professional owners.

The guest-facing information should be simple and accurate. Hosts need to know where a guest goes for assistance and which provider handles a lost token or collection query. The valet gate is a confirmed service plan and handover, not just a line in a hospitality package. Keep exceptions out of the main guest route where the reviewed arrangement permits it.

Treat dispersal as part of the event

Departure can concentrate demand when a programme ends at one moment. Review who leaves by shared transfer, arranged vehicle, valet or independently, and how those groups receive the right information. The transport and venue owners assess the operating arrangement; the guest lead connects it to the closing programme.

Confirm that the receiving transport arrangement is ready before announcing a movement. If a service is delayed, tell guests the confirmed next step and where support is available. Do not direct everyone outside merely because the stage programme has finished. Any waiting arrangement needs venue review and a named owner.

Reconcile the agreed guest handovers and outstanding assistance requests. A vehicle departing is not proof that every expected guest is aboard unless the relevant process confirms it. The closure gate records unresolved journeys and who is handling them. Use Design the Event Around the Guest Journey to include departure in the full journey map and Dealer Meets and Multi-Day Events: Connect Business, Hospitality and Travel for recurring transfers across several days.

Questions for the travel and guest lead

Does every senior guest need a separate liaison? Decide from actual responsibilities, programme constraints and the ability to perform handovers. This guide does not prescribe a staffing ratio.

Can a delayed speaker join remotely? Only after the programme and relevant technical owners assess the option and confirm the checks needed. Keep an approved programme alternative available.

Who approves travel changes? Name the client decision owner and the provider's operational contact before the event, including the route for time-sensitive changes.

Use the travel-and-handover worksheet to map each journey and exception. For coordinated planning across programme and hospitality, contact hello@threesixzero.live.