A delegate transport manifest is the single spreadsheet that tells the operator who moves, from where, to where, and by when. Build it with one row per movement rather than one row per delegate, and give every row twelve fields: movement ID, delegate name, category, mobile, leg and direction, the fixed time, origin with pick-up point, destination with set-down point, flight details, pax on the row, luggage, and access needs. Everything else is commentary.
One row per movement, not one row per delegate
This is the structural decision, and getting it wrong is why manifests fall apart on day two.
A delegate attending a three-day Sydney conference typically generates four or five movements: airport to hotel on arrival, hotel to venue each morning, venue to the gala dinner, gala dinner back to hotel, hotel to airport on departure. One row per delegate cannot hold that. Organisers who try end up with columns called “Tuesday PM” and “Wednesday AM” that stop making sense the moment one person’s flight changes.
One row per movement means a delegate appears five times, and every row is independently sortable, countable and cancellable. The operator sorts by date and time to build vehicle allocation. You sort by delegate name to answer a question at the registration desk. Same file, two views, no reconciliation.
The cost is a longer spreadsheet. Three hundred delegates with five movements each is 1,500 rows. That is fine. A spreadsheet handles 1,500 rows without complaint, and a transport plan built on any other structure will not survive its first change.
The twelve fields
1. Movement ID
A unique reference for the row, not the delegate. Something like the day number, the leg and a sequence, so a change request can name a row rather than describe it. Every conversation about a change becomes shorter.
2. Delegate name, as it appears on travel documents
Given name and family name in separate columns if you can. Consistency matters more than completeness: the same person spelled two ways becomes two people on a headcount.
3. Delegate category
Delegate, speaker, VIP, sponsor, exhibitor, crew, accompanying person. This field drives vehicle allocation and priority when something goes wrong.
It also separates the movements that need meet and greet from the ones that do not. Crew movements for bump-in and bump-out are usually earlier, smaller and to a different door than the delegate movements, and tagging them here keeps them from being folded into the delegate count.
4. Mobile number in international format
With the country code, including for Australian numbers. Delegates arriving from overseas frequently have a foreign number active on arrival, and a driver cannot call a number written for domestic dialling.
One number per row. Do not put an office landline here. On the day, this field is the difference between a five minute recovery and a missed movement.
5. Direction and leg
Arrival transfer, hotel to venue, venue to offsite, offsite to hotel, departure transfer. Plain words, used identically on every row.
6. Date and the fixed time, with a note on which end is fixed
Every movement has one end that is fixed and one that flexes. An arrival transfer is fixed at the flight; a plenary run is fixed at the venue. Record the time and say which end it belongs to.
Organisers who record only a pick-up time force the operator to guess the deadline, and the guess is what gets tested when traffic is bad.
7. Origin, with the specific pick-up point
Not the hotel name. The hotel name and the door. Large Darling Harbour and Barangaroo hotels frequently have a forecourt, a side street set-down and a porte-cochere a coach cannot enter, and “the hotel” is not an instruction.
8. Destination, with the specific set-down point
Same rule. For ICC Sydney, coach drop-off is at Iron Wharf Place off Darling Drive, with Zollner Circuit as the other approved point. Write the actual point on the row, because a coach cannot simply pull up wherever a taxi would.
9. Flight or vessel details, including terminal
Operating carrier, flight number, port of origin, scheduled arrival time, and terminal. The operating carrier matters because codeshare bookings show one airline on the delegate’s confirmation and land under another.
Terminal is a required field in Sydney, not a nice-to-have. Sydney Airport publishes a meeting point at T1 International on the Arrivals level between exits A and B, and at T2 Domestic on the Arrivals level opposite baggage carousel 6. There is no published T3 meeting point, and T3 uniquely separates Bus Pickup from Coach Pickup. A T3 row therefore needs its meeting point agreed with the operator in advance rather than assumed. Include Western Sydney International as a value option in this field if any delegate is arriving there.
Add a yes or no column for flight monitoring on each arrival row. Flight monitoring is a service to be confirmed rather than assumed, and marking it per row makes the conversation concrete: monitoring 40 arrival rows is a different undertaking from monitoring four VIP rows.
10. Pax on this movement
The number of people travelling on that row, not the size of the delegation. A speaker travelling with a partner is 2 pax on their arrival row and 1 pax on the movement to a speakers’ briefing.
Pax is what the operator adds up to size vehicles. If this column is wrong the vehicle is wrong, and no other field can correct it.
11. Luggage and equipment
Checked cases and cabin bags travelling on that movement, plus anything that is not a bag: pull-up banners, sample cases, exhibition freight, instrument cases, catering.
Record counts and describe anything oversized in plain words. Do not assume the operator will infer luggage from the pax count, because arrival day and mid-conference days are completely different loads for the same people.
12. Access and assistance requirements
Mobility aid and its type, whether a hoist or ramp is required, step-free boarding, assistance animal, or a request for meet and greet inside the terminal.
This field changes which vehicle is assigned, so it has to be captured at registration rather than discovered at the kerb. Wheelchair-equipped vehicles with hoists are available, and a row flagged here needs the vehicle confirmed rather than substituted on the day.
The header block
Above the rows, the file needs five pieces of document control: event name, manifest version number, the date and time it was generated, the name and mobile of the person who owns it, and the name and mobile of the on-site transport contact for the event days.
Version number and timestamp are not bureaucracy. On a live event, three copies of the manifest exist within a day, and the only defence is a version everyone can name.
A copyable header row
Lift this straight into a spreadsheet:
`Movement ID | Family name | Given name | Category | Mobile (international format) | Direction and leg | Date | Fixed time | Which end is fixed | Origin | Pick-up point | Destination | Set-down point | Carrier | Flight number | Port of origin | Scheduled arrival | Terminal | Flight monitoring required | Pax | Checked bags | Cabin bags | Oversized items | Access requirements | Status | Last updated`
The twelve fields expand into these columns once you separate the parts an operator sorts on. Status carries confirmed, provisional or cancelled, and last updated carries a date and time.
Change control, which is the real work
A manifest is not a document. It is a live record, and most of the effort after version one goes into managing change.
Three things keep it stable.
A stated cut-off. Name the time after which changes move to a different channel. Before the cut-off, changes go into the file and a new version is issued. After it, changes are phone calls against named movement IDs.
A single owner. One person issues versions. Anyone can request a change; only one person makes one. Manifests degrade fastest when two people are both helpfully editing.
A day-of channel. Agree in advance how a change reaches the driver on the day, and confirm that the operator has acknowledged it. An unacknowledged change is not a change.
Ask the operator what they need and by when, because their quoting and allocation work runs on the same file. Our written quotes come back within two business hours, and published lead times run two to four weeks for most work and four to eight weeks in peak periods including December, race days, school excursion season and long weekends.
Handling a manifest responsibly
A delegate transport manifest holds personal information. Names, mobile numbers, movement times, and often access or health-related requirements sit together in one file, and the access column in particular deserves care.
Handle it accordingly. Share it only with the people who need it to do the work, send it through a channel your organisation approves rather than a personal account, agree with the operator how long they keep it after the event, and delete the working copies when the event is closed out. If your organisation has a privacy or information handling policy, this file falls under it. Treat that as the governing document rather than anything an operator tells you.
How the manifest becomes a run sheet
The manifest is the source data. The run sheet is what the driver receives, and it is a different document.
Sorting the manifest by date and time, then grouping rows into movements, produces the vehicle allocation: how many vehicles, of what size, at what time, from where. Adding vehicle staging (where each vehicle waits before and between movements) and the wet-weather contingency (the alternative set-down point for each movement, agreed in advance) turns that allocation into a run sheet.
Two Sydney details belong in the staging column. Commercial vehicles must not be left unattended at Sydney Airport terminal frontages, and a bus holding area operates on Ross Smith Avenue, so an arrival movement stages there rather than at the kerb. At ICC Sydney, coach parking is arranged through your dedicated ICC Sydney Event Manager, so venue staging is a conversation with the venue rather than a decision the operator can make alone.
Corporate bus hire in Sydney covers the conference work, group airport transfers in Sydney covers the arrival and departure legs, and accessible bus hire in Sydney covers anything flagged in field twelve.
Frequently asked questions
What data does the operator actually need per delegate?
Per movement rather than per delegate: who, how many, from which specific point, to which specific point, at what fixed time, with what bags and what access needs. Flight details on arrival and departure rows. Everything else is useful context rather than operational input.
How should VIP movements be handled on the manifest?
Tag them in the category field rather than keeping a separate list. A separate VIP list is the thing that gets forgotten when a version is reissued. Category tagging keeps VIP rows inside the same version control while still letting the operator allocate a different vehicle or a meet and greet.
What is flight monitoring and should we ask for it?
Flight monitoring means the operator tracks the actual arrival against the schedule and adjusts the collection. Confirm it explicitly per row rather than assuming it, and be specific about which arrivals need it. Monitoring every arrival on a large conference is a different scope from monitoring a handful of speaker arrivals.
How do we manage changes without breaking the plan?
One owner, numbered versions, a stated cut-off, and a nominated day-of channel with acknowledgement. Reference movement IDs rather than describing changes in prose, and never let two people edit the same file.
What format works best?
A spreadsheet with one row per movement, sent as a file rather than pasted into an email body. Keep column names stable between versions, because operators build their allocation on your column order and a renamed column costs a day.
Does the manifest need to include crew and exhibitor movements?
Yes, on the same file. Bump-in and bump-out crew movements run at different hours to different doors, and keeping them on a separate list is how they end up unresourced. Tag them in the category field and let them sort into place by time.
Next step
Send the manifest, even a partial one, and we will come back with the movement plan behind it: vehicles by movement, staging points, and a written quote naming the vehicles, usually within two business hours.
If the manifest is still being built, call our operations team on 02 9469 6600 and book a shuttle plan review. It is far cheaper to fix the structure now than to rebuild it in version four.
Sources
- Sydney Airport, “Pick-up”, https://www.sydneyairport.com.au/pickup. Accessed 7 September 2026.
- Sydney Airport, “Resources for registered limousines, buses and coaches”, https://www.sydneyairport.com.au/corporate/partner-with-us/commercial-vehicles/resources-for-registered-limousines-buses-and-coaches. Accessed 7 September 2026.
- ICC Sydney, “Getting here”, https://iccsydney.com.au/visitors/getting-here/. Accessed 7 September 2026.
