Picton gets treated as a doorway rather than a destination, and that assumption is what wrecks the Marlborough excursion day. The programme says wine country at 10am and ferry at 2.30pm, somebody books one vehicle for both, and by lunchtime the organiser is standing in a cellar door car park doing sums. A conference shuttle Picton plan has to decide early whether it is serving the excursion or serving the departure, because on a wine-country day it cannot credibly do both with the same bus.
The Picton to Blenheim leg is longer than the map suggests
Picton to Blenheim is roughly thirty kilometres down State Highway 1 through the Dashwood side of the valley, around twenty-five to thirty minutes in normal conditions. That is the easy part of the day. The cellar doors are not in Blenheim. The Rapaura Road and Renwick wine country sits a further ten to twenty minutes west and northwest of the town, so a Picton base to a working cellar door is realistically a forty-five minute leg each way before anybody tastes anything.
Add the Queen Charlotte Drive option and the numbers change again. The run west toward Havelock is about thirty-five kilometres but it is narrow, winding and slow, and forty-five minutes is a fair estimate rather than a cautious one. It is a beautiful road and a poor choice for a tight schedule. We will take delegates along it when the day has room, and we will say so when it does not.
Vehicle sizing is set by the cellar door, not the headcount
This is the single most common error in Marlborough excursion planning. The organiser books by delegate number, a 50-seat coach turns up, and the cellar door approach cannot take it. Many of the smaller and more interesting properties sit behind a gated vineyard entrance with a gravel apron and no turning circle. A full-size coach either cannot enter or cannot leave without a reverse manoeuvre nobody wants to watch.
The vehicle that handles a conference shuttle Picton airport run comfortably is not always the vehicle that can get up a vineyard driveway. The honest answer is that a Marlborough cellar-door circuit is a van job more often than a coach job. Legacy runs an owned European fleet from sedans through vans to coaches, which means we can put three vans on a vineyard circuit and still bring a coach for the straight-line airport leg later. The fleet decision follows the driveway, and we check the driveway before quoting rather than after arriving.
Two vans also give you something a coach cannot: the ability to split the group across two cellar doors simultaneously and swap them, which turns a four-stop day into a two-stop day without losing anything the delegates came for.
A conference shuttle Picton day cannot also be the departure run
Here is the collision. The afternoon ferry sailing out of the Picton terminal needs delegates checked in and in the terminal well ahead of the published departure, and foot passengers are processed separately from vehicles. Blenheim Airport, BHE, sits roughly eight kilometres from Blenheim town and about thirty-five to forty minutes from Picton, and its departure bank is concentrated rather than spread across the day. Both of those deadlines are external. Neither will wait for a group that is enjoying a tasting.
If one vehicle is doing the cellar-door circuit and the departure run, the excursion gets cut short to protect the deadline, every time. The delegates notice. The better structure is two movements. One vehicle stays with the excursion and brings the non-departing delegates back to Picton on its own timing. A second vehicle collects the departing group from the last cellar door, or from the Blenheim side of the circuit, and goes straight to BHE or back to the ferry terminal. The second vehicle costs a few hours of vehicle time and buys the whole day its integrity.
It also solves the luggage problem. Delegates departing the same afternoon are carrying bags, and bags on a cellar-door circuit are a nuisance for everyone. A separate departure vehicle can collect luggage from accommodation while the group is out.
Sequencing the day backwards
We build a conference shuttle Picton day from the departure deadline inward, in this order.
Start with the hard stop. That is the BHE flight bank or the ferry check-in close, whichever the departing delegates are using. Work back the leg time with a buffer sized for the route, not a flat twenty minutes, because the Renwick approaches and the SH1 run through Spring Creek behave differently in the wet.
Then set the last cellar door to finish before that, and only then decide how many stops fit in front of it. Most organisers arrive with four cellar doors on the list and leave with three. Three stops done properly reads better in the delegate feedback than four stops done at a jog.
Picton, Blenheim and the Nelson corridor
A reasonable share of Marlborough conference groups arrive through Picton and leave through Nelson, or the reverse. Picton to Nelson is roughly 110 kilometres on State Highway 6 and about two hours in good conditions, over the Rai Saddle and through Havelock. It is a corridor, not a transfer, and it needs a vehicle committed to it for most of the morning.
Legacy covers both ends of that route as a single operator across more than fifteen New Zealand locations, so the same account, the same dispatch and the same driver standard apply on the Nelson leg as on the Picton leg. There is no handoff to a local subcontractor at a regional boundary, which is where most multi-region programmes lose visibility. Other regional notes of this kind sit on the Legacy blog, and the operating detail is at wearelegacy.co.nz.
What a conference shuttle Picton brief needs
Send the delegate count, the accommodation in Picton or Blenheim, the cellar doors you have shortlisted, and the departure deadline for anyone leaving that afternoon with their ferry sailing or BHE flight number. We will come back with a vehicle plan, a view on which of those cellar doors can take the vehicle you need, and a quote built on vehicle hours rather than a per-head figure that hides the second vehicle you are going to need anyway.
Legacy drivers are employed staff, not contractors, and they are uniformed and briefed on the specific programme. Flights are monitored in real time, dispatch is digital, and the whole movement is account-managed on one invoice. More at wearelegacy.co.nz.
Michael Graves, Legacy EPT