A cancelled Cook Strait sailing is not an emergency in Marlborough. It is a normal weather outcome that happens several times a season, and any serious conference transport Picton plan is written on that assumption rather than around it. The question is not whether a sailing will be disrupted during your programme. It is what your operator does in the four hours after the notification lands, while a hundred delegates sit in Wellington and your vehicles sit on the Picton foreshore doing nothing.
What actually happens when a sailing is pulled
The notification arrives before the delegates understand what it means. From the operator's side three things change at once.
The arrival wave shifts. A cancelled morning sailing usually pushes people to an afternoon departure, which moves your entire arrival window by four to six hours. If the strait stays closed, it moves to the next day, and the group splits across two sailings because the recovery sailings are already sold.
The committed resource does not shift. Vehicles and drivers were rostered against the original timetable. They are in Picton, they are paid, and they are idle. Releasing them looks like the obvious saving and is usually the wrong call, because the recovery sailing will land and the vehicles will need to be back, and a coach recalled from Blenheim or Nelson at two hours' notice is neither guaranteed nor cheap.
The programme has to absorb the gap. A missing half-day is an organiser problem, not a transport one, but the transport plan determines which recovery options are still open by the time the decision is made.
Why holding a vehicle usually beats releasing it
The instinct when a sailing is cancelled is to stand vehicles down and re-book for the new arrival. In Marlborough that instinct is expensive. The regional fleet is finite, and the same cancellation that stranded your group has also disrupted every other movement in the district that day, so the vehicle you released has been picked up by someone else.
Holding costs vehicle hours. Re-sourcing costs the movement. Legacy's default on a disrupted Cook Strait day is to hold capacity and re-time it, and to make that call early with the organiser rather than at the point where nothing is available. Because Legacy runs an owned fleet with employed drivers across more than fifteen locations, the holding decision is internal, and a vehicle can be brought up the coast from another base if the recovery wave is larger than the original.
Two pressure valves every conference transport Picton plan needs
Marlborough has two genuine release valves, and both need to be identified in the planning phase rather than discovered on the day.
The first is air. Marlborough Airport (BHE) at Woodbourne, just west of Blenheim, sits roughly 30 minutes south of Picton by road. When the strait closes, a portion of a delegation can be redirected onto flights into BHE and collected there instead. That only works if the transport plan already contemplates a second arrival point, with vehicles positioned accordingly.
The second is accommodation. Blenheim has substantially more room stock than Picton, so an overflow or a forced overnight is far easier to place there. The trade-off is a 25 to 30 minute transfer each way added to the programme, which changes the morning shuttle from a walk to a scheduled movement. That is manageable when planned and chaotic when improvised.
The public alternatives are not contingencies
Organisers looking at Picton often find two visible services and assume they provide a fallback. Neither does.
The Marlborough District Council operates a Blenheim to Picton bus route that its own published information describes as off-peak only, running between 9am and 3pm on Tuesdays, Thursdays and Saturdays. A conference does not arrive on that pattern. InterCity coaches meet ferries outside the Interislander terminal, which is useful for individual travellers but is a scheduled line-haul service with fixed capacity and no obligation to your group.
Both were timetabled long before your programme existed. Neither flexes when the strait closes, which is precisely when you need flex. Any conference transport Picton plan that quietly relies on them has no contingency at all.
Queen Charlotte Drive dictates vehicle size
Contingency planning in the Sounds runs into a physical constraint that has nothing to do with the ferry. Queen Charlotte Drive is narrow and winding in long sections, with limited passing and turning space, so the road decides the vehicle rather than the headcount.
If your dinner venue or lodge is out along the Sounds, the answer is more smaller vehicles running more trips, not one large coach. That has a direct contingency consequence: a delayed arrival wave compresses the window for a shuttle that was always going to take three runs. Build the Sounds legs with a realistic turnaround time and they survive a late sailing. Build them on a single coach assumption and they do not.
Writing the recovery plan before you need it
A workable contingency for a Picton programme is a short document, agreed in advance, that names four things: who is notified and in what order when a sailing changes, whether vehicles hold or stand down and who authorises it, what the BHE and Blenheim fallbacks look like with vehicles attached, and which programme elements are cut first if the group lands late.
Legacy EPT writes that plan as part of the quote rather than as an extra, because on this corridor it is the part of the job that earns its fee. Real-time flight monitoring covers the BHE leg, digital dispatch covers the re-timing, and account management means one person is making the calls rather than an organiser chasing three suppliers.
The corridor either side
Picton is rarely the whole itinerary. Nelson is roughly two hours west by road, Christchurch around four and a half hours south, and Wellington is across the strait. Running the South Island legs and the North Island legs through one operator removes the handover risk at exactly the point where disruption is most likely.
Our full coverage is on the Locations page and further operational write-ups sit on the Blog. If you are building a conference transport Picton brief, send Legacy the sailing you are planning around and we will write the recovery plan alongside the movement plan.
Written by Michael Graves, Legacy EPT. Michael leads national operations and corridor planning across the Legacy network.