Academic conferences move people differently from corporate ones, and Dunedin is where that difference shows up most clearly. Planning conference transport Dunedin programmes around a single venue address, the way you would in a convention centre city, produces a run sheet that does not survive contact with the actual week. The venue is not a building. It is an estate, and the delegates arrive on routings no corporate traveller would accept.
Two features of the city drive almost every operational decision. The first is the airport. The second is the campus.
DUD is genuinely far out, and it changes your schedule
Dunedin Airport sits roughly 27 to 30 km south of the city, around 30 to 40 minutes by road depending on traffic and conditions. That is not a hop you can absorb late in a day that has already slipped. It is a scheduled operation that has to be planned against session times.
The practical consequences are specific. A delegate landing at 4pm is not making a 4:30 session, and publishing a programme that implies otherwise generates complaints you cannot fix. A speaker on a tight connection needs a dedicated vehicle rather than a shared run, because a shared run waits for the slowest bag. And a departure day with a mid-afternoon flight means people leave the final session early whether you plan for it or not, so it is better to build the departure shuttle into the programme than to pretend the last paper will hold the room.
Academic delegates compound this. Institutional travel budgets push people onto cheaper indirect routings, which means arrivals land at hours that a corporate manifest would never produce: late evening, very early morning, spread across three days rather than clustered into one afternoon. A single met-arrival window does not cover that pattern. What covers it is a rolling arrangement with real-time flight monitoring against actual landings, so vehicles are allocated to the aircraft that arrived rather than the one that was scheduled. That is how Legacy EPT handles academic arrival profiles, and it is a different service shape from a conference with a single inbound peak.
The campus is an estate, not a venue
A University of Otago conference distributes across buildings. Registration in one place, plenary in another, parallel sessions in a third and fourth, a poster session somewhere else again, and frequently the Dunedin Centre and Town Hall in the Octagon in the mix for the larger plenary or the conference dinner.
That turns the movement pattern inside out. Instead of one morning run and one evening run, you get repeated short intra-city legs with tight turnarounds, often on a fifteen or twenty minute cycle between sessions. The vehicles are not covering distance, they are covering a schedule, and the constraint is dwell time rather than drive time.
Three things follow from that. Drop points matter more than addresses, because a drop 300 metres from the right entrance costs delegates five minutes they do not have between sessions, and in Dunedin weather that five minutes is remembered. Turnaround discipline matters more than vehicle size, since a shuttle that leaves two minutes late compounds across a whole afternoon of cycles. And driver familiarity with the estate genuinely matters, which is one practical argument for employed drivers who can be briefed and rostered on the same programme across several days rather than a rotating pool of contractors seeing the campus for the first time each morning.
The Otago Peninsula, where the road picks the vehicle
Most Dunedin programmes include a peninsula excursion, and this is the one leg where vehicle size is not a commercial decision. Sections of the harbourside road are narrow, and the road dictates what can sensibly run on it. The right answer is often several smaller vehicles rather than one large one, which costs more in drivers and requires more coordination, and is still the correct call.
The planning error we see most often is selecting a coach on headcount alone and discovering the constraint at the itinerary stage, when the excursion is already published. Legacy runs an owned European fleet from sedans through vans to coaches, so the sizing conversation can start from the road rather than from what happens to be available.
What a workable Dunedin brief contains
A good brief has four elements. A rolling airport arrangement for DUD that covers the spread of academic arrival times rather than one peak window. A campus shuttle cycle with named drop points tied to specific buildings, not street addresses. A dedicated allocation for speakers and anyone with an accessibility requirement, kept separate from the general cycle so it cannot be delayed by it. And a peninsula excursion sized from the road.
Get those four right and the week runs quietly. Legacy provides account-managed corporate service with a single point of contact across all of them, working from one digital dispatch, which matters most on the days when a session overruns and the whole shuttle cycle needs resetting in ten minutes.
If your programme extends up the corridor, a Dunedin conference frequently pairs with Queenstown for pre- or post-conference travel, and that continuity is worth holding with one operator. Our Locations page shows the nationwide coverage, and there is further operational writing on the Legacy Blog. For an Otago programme with a campus shape to it, bring the session timetable to Legacy EPT rather than the delegate count, because the timetable is what the vehicles are actually working to.
Written by Liz Geenty Park, Legacy EPT. Liz manages academic, incentive and alpine delegate movement across Otago and the lower South Island.