A group of eight comes off the Interislander at Picton at 1.15pm. Four need to be at Marlborough Airport outside Blenheim for a late-afternoon departure. The other four are going on to Nelson and have a site visit the next morning. Book that day the way the market is organised and you will use three different operators, and search for a company shuttle Picton option to tie it together and you will find that nobody sells the day as one job.
That is the structural problem at the top of the South Island. Picton, Blenheim and Nelson are one operating area for the businesses that work there, and three separate markets for the people who move them. The questions buyers actually ask confirm it: is there a shuttle from Nelson to Picton, is there a shuttle service from Blenheim to Nelson, what does a Blenheim to Picton run cost. Every one of those is a connection question, and connections are precisely what a per-leg booking chain handles worst.
The triangle, with the distances that make it one problem
Take the geography on its own terms, approximately.
Picton is the Cook Strait gateway. Interislander and Bluebridge both land here, which makes it the entry point for freight, crews and any North Island team travelling with vehicles or heavy kit. Waikawa sits immediately adjacent and generates its own marine traffic.
Blenheim and Marlborough Airport are roughly 30 km south of Picton, about 25 to 30 minutes down the road. That is the region's air gateway, and Marlborough Airport publishes an indicative taxi figure of around $35 one way for the short airport-to-Blenheim leg at 15 to 20 minutes, which gives you a sense of the local rate base.
Nelson is roughly 110 km west of Picton over the Whangamoa and Rai saddles, about two hours of real driving, and a similar run from Blenheim. It is not a motorway run. It is a saddle road with weather exposure, and the drive time is the drive time regardless of how the schedule looks on paper.
So the three points sit within about two and a half hours of each other, and the employers who generate the demand, Marlborough wine, aquaculture and the aviation sector, routinely need two or three of those legs on the same day. A company shuttle Picton booking that only covers Picton solves a third of the problem.
Where the chain breaks: the handoff
Here is the part no ranking page covers. When each leg is a different operator, nobody owns the connection.
The ferry is late by 50 minutes. Your Picton operator has delivered its passengers and gone. The Blenheim operator holding the airport leg has a 2.40pm pickup that is now a 3.30pm pickup, and it has another job at 3.15. The Nelson leg is booked for a departure time that has become meaningless. Three operators, three contracts, three sets of terms, and not one of them is responsible for the outcome you actually bought, which was eight people arriving where they needed to be.
The same thing happens in reverse. A late inbound at Marlborough Airport breaks the Nelson leg. A cancelled sailing breaks everything. In each case every individual operator has performed to its own contract and the day has still failed, and the person holding the consequence is the travel coordinator who assembled the chain.
This is not a reflection on the incumbents. Picton Shuttles is long established and does Picton and Waikawa work properly. Marlborough Shuttles is correctly focused on Blenheim Airport. Wine Country handles Sounds transfers. Each is sized for the leg it sells, and Picton's shuttle supply in particular is sized for ferry foot passengers arriving in volume at fixed times, not for a corporate group whose timings move.
A company shuttle Picton contract that holds all three legs
The alternative is to treat the triangle as one operating area under one operator, which is how Legacy runs it.
One dispatch sees the whole day. If the sailing is late, the Blenheim pickup and the Nelson departure are both re-timed by the same controller, in the same system, without anybody having to ring three companies and renegotiate. Real-time flight monitoring covers the Marlborough Airport leg the same way, so a late arrival into Blenheim moves the onward Nelson run before the passengers have cleared the terminal.
Drivers are Legacy employees, uniformed, not contractors sourced per job, which is why a vehicle can be held or reassigned by instruction. The fleet is owned and European, from sedans through vans to coaches, so a group of eight splitting into a four and a four does not require two subcontracted vans from two different suppliers. And because Legacy operates nationwide as a single operator across more than fifteen New Zealand locations, a Wellington leg before the ferry and a Christchurch leg after Blenheim sit on the same account with the same billing.
That is the real difference, and it is a difference in who carries the risk rather than in the quality of any individual drive.
What to settle before you split a run across operators
If you are quoting a multi-leg Marlborough day, get four things answered.
Who is responsible when leg one is late and leg two is missed. If the answer is nobody, you have bought three services rather than one day.
Whether the operator monitors the ferry and the flight, or waits to be told.
Whether the same account covers Picton, Blenheim and Nelson, or whether you will reconcile three invoices against one trip.
Whether there is a cover vehicle, and in which of the three towns it actually sits.
Our Nelson coverage looks at the western end of this corridor in its own right, and the Locations page sets out where Legacy holds vehicles and drivers across the country.
The top of the South rewards operators who understand that Picton is a gateway rather than a destination. If your people move between the ferry, the airport and Nelson in the same week, a company shuttle Picton arrangement should cover the whole triangle on one contract. Talk to Legacy EPT about running it that way.
Michael Graves, Legacy EPT