If you plan events for a living, you already know a hotel transfer is deceptively simple to book and surprisingly easy to get wrong. This isn't an introduction — it's the operational detail that separates a transfer your guests never think about from one that becomes the story of the night. Written for planners who've stood in a lobby watching a bus that isn't coming.
Multi-drop runs live or die on sequencing
A single pickup is easy. Three hotels, a venue and a staggered return is where it gets real. The order of stops, the time budget between them, and whether the coach can physically access each hotel's frontage all need to be worked out before the day, not improvised by the driver. Give your operator the full picture — every hotel, every window — and let them build the run backwards from the fixed point, usually the event start.
Timing precision is the whole job
Guests will forgive almost anything except waiting. Build realistic buffers for Melbourne traffic and CBD loading zones, confirm the return timing (especially after a dinner or wedding, when "one more drink" is guaranteed), and agree what happens if the event runs long. A professional operator plans for the run going over, because it usually does.
What to brief your driver on
- The exact stop order, addresses and access points for every hotel and the venue.
- Your on-the-ground contact's mobile — and who the driver calls if a group is late.
- Guest count per stop, and whether anyone needs accessible boarding.
- The hard deadline (ceremony, keynote, dinner service) the run is built around.
- Return plan and last-run time, so no guest is stranded.
Guest experience is part of your brand
The transfer is the first and last impression of your event. A clean coach, a driver who greets people, and a run that simply works reflect on you and your client. It's a small part of the budget carrying a large part of the impression.
Skylight handles hotel and venue transfers for conferences, corporate events and weddings across Melbourne — multi-drop runs, precise timing, and one contact who owns the plan. Send through the run and we'll map it properly.
