Travel and transport administration
Event shuttle departure schedule
Delegates ask what time the shuttle leaves, and the answer depends on a vehicle that is also needed at a second pickup point.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A shuttle departure schedule lists each pickup point, a departure window rather than a single minute, the vehicle assigned and the seats it offers. It is built from the supplier's confirmed vehicles and the cycle times the supplier states, not from your own guess at the road.
Publish windows and the instruction for what delegates do if they miss one. Use the shuttle seat planner to check that each wave fits the seats and that no vehicle is scheduled at two points at once.
What the schedule must settle before it is published
- Which pickup points exist, and which are confirmed in writing with the property or venue.
- How many vehicles are confirmed and how many seats each has, as stated by the supplier.
- The cycle time the supplier states for a round trip, entered as the supplier's figure with the date it was given.
- What happens to delegates who miss their window, and who tells them.
- Who has authority to add, cancel or swap a departure on the day.
Reading the schedule as a constraint, not a timetable
A vehicle cannot depart from the hotel and be at the venue at once. If one vehicle serves two points, the schedule has to show the gap the supplier needs between its two departures.
Where the constraint does not hold, the usual fixes are a later window for the second point, another vehicle, or a smaller second wave. Decide which with the supplier before delegates see anything.
Schedule table
| Wave | Pickup point | Departure window | Vehicle | Seats offered | Supplier-stated cycle (date given) | Notes |
|---|---|---|---|---|---|---|
| A | Main hotel lobby entrance | Opening window of the morning | Vehicle 1 | As confirmed | Supplier figure | Wave A fills first |
| B | Second hotel entrance | Window after A, with the supplier's gap | Vehicle 1 | As confirmed | Same vehicle: gap applies | Check conflict with A |
| C | Venue return point | After the closing session | Vehicle 2 | As confirmed | Supplier figure | Return waves need a named marshal |
Publishing and changing it
- Collect passenger numbers per wave as aggregates, not named lists, unless the supplier needs names.
- Send the draft to the supplier and ask for written confirmation of vehicles, seats, pickup points and cycle times.
- Publish windows to delegates through the travel information pack, with a version date.
- Name one person who may change departures, and send every change to the supplier and the pack owner together.
- Review demand after the first wave and add or merge a departure only through that named person.
- Record unused seats per wave for the post-event review.
Common failures
- A single departure minute is published, then late delegates assume the vehicle will wait.
- The same vehicle appears in two waves with no gap.
- Seats are counted as the vehicle's maximum when the supplier confirmed fewer for luggage.
- Return waves have no marshal and no stated rule for late sessions.
- Changes are sent to delegates but not to the supplier.
Worked example · Fictional example
A shuttle between hotel and venue for a one-day forum
Fictional organisation and figures, for illustration only.
A fictional logistics forum expects 60 delegates staying at one hotel and 30 at another. The supplier confirms two vehicles with 22 seats each and states a round-trip cycle time in writing.
With 44 seats per cycle and 90 delegates, the secretariat plans three waves, the first two from hotel one and the third from hotel two, so that no vehicle is needed at two points at the same time. It publishes windows, not exact minutes, and names a marshal at the venue for the return.
Use this yourself
Shuttle departure schedule checklist
Tick each line before the schedule leaves the secretariat.
- Pickup points confirmed in writing by each property or venue.
- Vehicles and seat counts confirmed in writing by the supplier, with date.
- Cycle time entered as the supplier's stated figure, with date given.
- Each wave fits the seats offered, and unused seats are recorded.
- No vehicle scheduled at two points at once.
- Departure windows published, not single minutes.
- Rule for missed shuttles and late sessions written down.
- One named person approves changes; supplier and pack owner copied.
- Version date on every published copy.
Handle it in-house, or bring in help?
Your team can usually handle this when
- One vehicle, one route, one hotel and a single venue.
- Supplier is already confirmed in writing and the committee can answer delegate queries.
Outside planning help earns its fee when
- Several vehicles, several pickup points and waves that overlap.
- Delegates are split across hotels or arrive at different times.
- Nobody is free to stay with the schedule on the day and change it with the supplier.
Need the schedule built and checked?
A conference project lead can gather passenger numbers by wave, test them against the supplier's confirmed seats and cycle times, and produce the schedule and the change rule for you to approve. The project lead coordinates with the supplier; the supplier remains responsible for vehicles, drivers and timings it confirms. Send delegate counts per hotel and the supplier's written confirmation if you have it.
Questions organisers ask
Should we publish exact departure times?
Publish windows and say that vehicles depart when loaded within the window, if the supplier agrees. An exact minute becomes a promise that road conditions can break.
How do we know how long a trip takes?
Ask the supplier for its stated cycle time in writing, and treat it as the supplier's figure. Do not put your own journey time in the schedule.
What if more delegates turn up than seats?
Agree in advance whether to add a departure, and who approves it. Record the extra demand for the next day.
Who tells delegates about changes?
The named change owner, using the same channel as the pack, with a new version date.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.