Nelson conferences are rarely contained by Nelson. The plenary is in the CBD, a third of the delegates are accommodated out at Richmond, the partner programme heads for Kaiteriteri, and the closing dinner is somewhere on the Moutere. That spread is why a conference shuttle Nelson plan has to be written for a region rather than a city, and why the vehicle you assumed you would book often cannot go where the programme wants it to.
Nelson Airport (NSN) is the easy part. It sits roughly 5 to 7 km from the CBD, about ten to fifteen minutes by road, which is one of the shortest airport runs in the country. Everything after that transfer is where the planning effort belongs.
A conference shuttle Nelson plan covers a whole region
Accommodation capacity in the region does not sit in one block. Richmond is roughly 15 km southwest of the CBD, about twenty minutes outside commuter periods and longer when Whakatu Drive is busy. Mapua is roughly thirty minutes out. Once a meaningful share of your delegates is housed beyond the CBD, ad hoc transfers stop working and you need a scheduled loop with a fixed headway, published in the delegate pack, running to and from the venue at set times.
The Rutherford Hotel and the Trafalgar Centre are the CBD anchors most programmes are built around, and both sit on city streets where kerbside loading time is limited. Staged loading in waves, with a marshal on the footpath and vehicles cycling through rather than queueing, moves a large group far faster than parking four coaches nose to tail and hoping.
Vehicle sizing for Moutere, Mapua and the Abel Tasman roads
This is the decision that defines a conference shuttle Nelson plan. Kaiteriteri and Marahau are roughly an hour from the city, and the final approach roads narrow considerably, with limited turning and parking space at the Marahau end where the water taxis leave. The Moutere wine trail runs on narrow rural roads with gravel cellar-door entrances and tight turning circles. Neither route rewards a full-size coach.
In practice the right answer for a partner day is usually a set of vans running in convoy rather than a single large vehicle, which also solves the second problem: an Abel Tasman day almost never returns as one group. Walkers, kayakers and cruise passengers finish at different points and different times, and a convoy can peel off to collect them while a coach cannot. Legacy operates an owned European fleet from sedans through vans to coaches, so the sizing question is answered by the road and the itinerary rather than by whatever a subcontractor has available that morning.
Build the return around the water taxi schedule, not the other way round. The boat leaves on its own timetable, and a delegate group that misses the last departure has a long problem.
NSN fog is a planning assumption, not an exception
Morning fog and low cloud regularly delay arrivals into Nelson, and the delay usually lands on exactly the flights that matter, the early ones carrying speakers and organisers. Because those aircraft then run late for the rest of the day, a single morning of low cloud can push the whole inbound bank into the afternoon.
Plan for it rather than reacting to it. Put speakers on the previous evening's flight wherever the budget allows. Keep the first session of day one flexible, or open with something that does not depend on a specific person being in the room. Hold the airport vehicle rather than releasing the driver after the scheduled landing time, and make sure someone is watching the actual aircraft. Legacy uses real-time flight monitoring and digital dispatch, so a delayed or diverted NSN inbound updates the run sheet before the organiser's phone starts ringing.
One operator across the region
Nelson programmes generate a lot of small movements: an airport run, a Richmond loop, a Mapua dinner transfer, a Marahau partner day, a late-night return from a Moutere winery. Split across several suppliers, each one is fine and the seams between them are where delegates get stranded. Run them through a single operator with one dispatch board and the seams disappear.
Legacy provides account-managed corporate service across more than fifteen New Zealand locations with employed, uniformed drivers rather than a contractor pool, which matters most on the movements nobody photographs, such as the eleven o'clock return from a winery in the rain. Coverage detail is at wearelegacy.co.nz.
The Picton corridor
A good number of Nelson conferences arrive or leave via Marlborough. Picton is roughly two to two and a half hours away, most directly over the Rai Valley on State Highway 6, and delegates crossing Cook Strait on the ferry will use that road in both directions. Treat it as one scheduled movement with a driver who knows the road, rather than as a handover between two regional operators, and the luggage arrives when the delegates do.
What to put in the brief
Name the accommodation split between the CBD, Richmond and anywhere further out. Name the partner-day destination and let the operator size the vehicles for the road. State your NSN contingency and who owns the decision to move a session. State the last water taxi or last winery departure time as a hard constraint. A conference shuttle Nelson brief written that way can be executed by any competent operator, and it will expose immediately anyone quoting a coach for a road that will not take one.
Further operational write-ups sit on the Legacy blog, and Legacy EPT will review a regional run sheet against the roads before you commit to it.
Written by Catherine McDougall, Legacy EPT.