Most Marlborough conference programmes are written as though Picton were the destination. It is not. Picton is where delegates land, and almost everything else — the accommodation, the airport, the function venues — sits roughly 25 to 30 minutes south in Blenheim. That gap is the whole operation. Planning conference transport Picton without planning the Blenheim corridor produces a programme that looks tidy on paper and fails on the first morning, because the thing you have actually committed to is a shuttle service across state highway, not a set of local transfers.
Picton arrives, Blenheim hosts
Picton is a port town of a few thousand people built around a ferry terminal. It has hotels, but not the volume a conference of any size needs, and it does not hold the region's conference infrastructure. The accommodation block, the ASB Theatre Marlborough, the Marlborough wine-country function venues and Marlborough Airport (BHE) are all Blenheim-side. The practical consequence is that a Marlborough conference typically has two geographic anchors and a single road between them: State Highway 1 through the Tuamarina valley, roughly 28 kilometres, around 25 to 30 minutes in normal conditions.
The corridor is not difficult driving: a two-lane highway in good condition with no real congestion by national standards. What makes it an operational problem is volume and timing. Every delegate crosses it at least twice, most cross it four or more times across a three-day programme, and the crossings cluster — sailing arrivals, the morning run in, the evening function, the departure wave. A corridor with no traffic problem can still have a capacity problem if 120 people need to traverse it inside the same 40 minutes.
The public bus will not carry your delegates
This is where most planning assumptions quietly break. There is a public bus between the two towns — Marlborough District Council Route 3, Blenheim to Picton — and organisers reasonably assume delegates can use it for some legs. They cannot.
The council timetable is explicit: the Picton to Blenheim service runs off-peak only, roughly 9:00am to 3:00pm, on Tuesdays, Thursdays and Saturdays. Read that against a normal conference programme. There is no service on Monday, Wednesday, Friday or Sunday at all. On the three days it does run, it does not operate before roughly 9:00am, which excludes every morning arrival into the first session, and it stops around 3:00pm, which excludes every evening function and every late return. A delegate who checks the timetable and plans around it will arrive after your opening address or not at all.
Scheduled transport in Marlborough is a resident service, built for residents making mid-week, mid-day trips. It is not a delegate transport option and it should not appear in your delegate pack as one. A scheduled InterCity coach may connect the towns on some days, but a public timetable with public stops and no obligation to your programme is a different thing from transport you control. Every Picton to Blenheim movement in a conference programme is a chartered movement, and conference transport Picton should be budgeted on that basis from the outset.
Running conference transport Picton as a corridor, not a transfer
Once the corridor is accepted as the core of the job, the planning changes shape. You are not buying airport transfers. You are buying scheduled shuttle capacity across a fixed route, and the questions become the ones a transport operator asks rather than the ones a hotel asks.
How many delegates arrive on each sailing, and how many sailings are involved? A vehicle meeting one arrival can run back loaded; a vehicle meeting three staggered arrivals either waits in Picton for an hour or does three round trips of roughly an hour each. How many crossings does the programme genuinely require, and can any be removed? Holding a welcome function in Picton on arrival evening, rather than running everyone to Blenheim and back for dinner, removes two full crossings for the entire delegation. Where do vehicles dwell between legs? Positioning a coach empty across the corridor is a 25 to 30 minute cost nobody sees in the programme but someone pays for.
Legacy plans Marlborough work this way deliberately, as a corridor operation with a published internal schedule, because the alternative is a series of ad hoc bookings that each look reasonable and collectively cost far more. Legacy's owned fleet runs from sedans through vans to coaches across 15-plus New Zealand locations, so a corridor schedule can mix vehicle sizes against actual load rather than sending a coach to move eleven people.
Arrivals by sea and by air
Picton receives the Interislander and Bluebridge sailings from Wellington, and those sailings are the defining arrival pattern for most Marlborough conferences. Berthing is subject to Cook Strait conditions, which we have covered separately as a contingency subject. For corridor planning the point is narrower: sailing times set the start of your shuttle schedule, and a late berthing compresses everything downstream.
The air alternative is BHE, roughly 10 minutes from central Blenheim and on the far side of the corridor from Picton. Mixed arrival modes are common — speakers and sponsors fly into BHE, the bulk of delegates sail into Picton — and that mix is precisely where single-operator coverage earns its place. Legacy EPT runs real-time flight monitoring on the BHE arrivals and the same digital dispatch handles the Picton sailing meets, so both streams sit in one plan under one account manager instead of two suppliers each solving half the day.
Evening functions in the wine country
Marlborough's function venues are vineyard venues, scattered through the Wairau plains west and south of Blenheim, typically 10 to 20 minutes from Blenheim accommodation. For a Blenheim-based delegation this is straightforward. For delegates accommodated in Picton — which happens when the Blenheim block fills — a vineyard dinner means a corridor crossing each way on top of the venue transfer, putting the last delegate back after midnight on a rural road.
That is a strong argument for consolidating accommodation in Blenheim even when Picton rooms are cheaper. The room saving is usually smaller than the vehicle and driver-hour cost of the crossings it creates.
Settle these before you contract
Decide your accommodation base before anything else, and assume it is Blenheim. Count the crossings the programme requires and cut any that exist only out of habit. Get sailing manifests and flight numbers to your operator early. And put nothing in the delegate pack about scheduled buses. Handled in that order, conference transport Picton becomes a fixed schedule rather than a daily negotiation. For a sense of how the same corridor logic applies further west, the Nelson corridor legs piece is a useful companion, and other regional guides sit on the Legacy blog.
Written by Michael Graves, Legacy EPT