Most transport briefs for a Marlborough conference start with the venue and work outwards. That is the wrong order. If your delegates are crossing Cook Strait, a conference shuttle Picton plan is a ferry timetable problem first and a road problem second, and every road decision you make downstream is subordinate to a sailing you do not control.
The Interislander and Bluebridge crossings run roughly three and a half hours between Wellington and Picton. That figure is the easy part. The part that shapes the run sheet is what happens when a sailing is delayed by weather in the strait, by a berthing queue, or by a loading problem at the Wellington end. A delayed sailing does not inconvenience one delegate. It moves an entire arrival wave, often by hours, and it does so while those delegates are at sea and largely out of contact.
Why a conference shuttle Picton brief is built on sailing times
Air arrivals fail individually. Ferry arrivals fail collectively. If a flight is late, one or two delegates are affected and the rest of the programme proceeds. If the 2.30pm sailing runs two hours behind, everyone who booked it arrives together and late, and whatever was scheduled for that afternoon has to move as a block.
That changes how the day is planned. A ferry-fed conference should not put a hard commitment, a welcome function or an opening session immediately behind an arrival wave. It should leave a deliberate buffer, and the transport plan should assume the buffer will be used rather than treat it as spare.
The second consequence is vehicle holding. A fleet staged for a 2.30pm arrival that becomes a 4.30pm arrival is either standing idle at the terminal or has to be released and recalled. Legacy EPT runs digital dispatch and an account-managed desk so that decision is made once, by a named person watching the sailing status, rather than by five drivers making individual calls.
Meeting a delayed sailing properly
The terminal at Picton is compact and it empties quickly. Foot passengers come off in a rush, and a group of 60 or 80 delegates carrying bags will disperse into the town within a few minutes if there is nothing obvious to walk towards.
The operational answer is a marshalled meeting point with a uniformed driver standing at it, vehicles staged close but not blocking the terminal approach, and a clear boarding sequence communicated to delegates before they sail. Legacy's drivers are employed rather than contracted, which means they can be briefed on the specific meeting point, the group name and the wave structure, and they stay with the group rather than treating the pickup as a discrete job.
When a sailing slips, the delegates need to hear it from the organiser, not discover it. Build a message into the plan that goes out while people are still on board, confirming that transport is holding and where to go on arrival.
The Blenheim (BHE) alternative, roughly 30 km south
Not every delegate will cross the strait. Some will fly, and some will fly because a sailing has been cancelled. Blenheim's Woodbourne airport, BHE, sits roughly 30 km south of Picton, around 25 to 30 minutes by road on State Highway 1 in ordinary conditions.
That proximity makes a split feed realistic. A conference based in Picton can take a ferry wave and a BHE air wave on the same afternoon and land them into the same welcome function, provided the timetable is written as two feeds rather than one. Legacy EPT applies real-time flight monitoring to the BHE arrivals and sailing status to the ferry wave, and the account manager reconciles both against the programme.
BHE also functions as the recovery route. If a crossing is cancelled outright, rebooked delegates frequently arrive by air the following morning, and the transport plan should already know who is meeting them.
Marlborough Sounds venues and what the road allows
The reason Marlborough conferences are worth the logistical effort is the venues. Sounds lodges and Marlborough wineries deliver something a city convention centre cannot, and delegates remember them. They also sit at the end of roads that were not built for conference traffic.
Queen Charlotte Drive is the clearest example. It is a narrow, winding coastal road between Picton and Havelock with tight corners, limited passing opportunities and very little room to turn a large vehicle at the far end. A full-size coach is often the wrong answer on that road even when the delegate count suggests otherwise, and some lodge driveways will not take one at all.
The practical planning rule is to size vehicles to the road and the venue's turning space, then work out how many you need, rather than sizing to headcount and hoping. Legacy EPT runs an owned European fleet from sedans through vans to coaches, so a group can travel by coach on the State Highway 1 legs and transfer to a set of vans for the Sounds leg without changing operator.
Winery venues closer to Blenheim are generally easier on access but introduce the same evening problem any wine-region programme has: alcohol is served, so the return movement has to be professionally driven and staged. Legacy's employed drivers work to a zero-alcohol standard on duty.
Writing the brief
- Your booked sailings, by operator and departure time, for every delegate wave
- The buffer you have deliberately left behind each arrival wave
- Which delegates are flying into BHE and when
- Every venue on the programme, with its access road and turning space
- Who owns the decision to hold, release or recall vehicles when a sailing slips
Get those five things written down and the rest of the plan follows. Legacy EPT will build the run sheet against your sailing bookings rather than a generic timetable. Start at wearelegacy.co.nz, check the regional footprint on the Locations page, and if your programme continues over the hill to Nelson, the Nelson contingency planning write-up on the Legacy blog covers the road recovery side of that corridor.
Michael Graves writes on corporate and conference movement for Legacy EPT.