Event shuttle stop coordinator checklist and boarding log

Set the stop role and decision boundary

Name an organizer lead, an onsite stop coordinator, the transport operator’s dispatch contact and the venue contact for each active stop. Write who confirms a vehicle’s identity and trip, who records boarding, who approves a changed departure or pickup point, and who tells attendees. The same person can cover two roles at a small event, but the approval and message path must still be explicit. The coordinator should observe and relay a problem, not improvise a new vehicle route or curb arrangement.

The US Federal Transit Administration advises agencies and major-event organizers to coordinate service demand, hours and accessibility. UK HSE guidance separately treats arrivals, onsite movement and departures as distinct event phases and calls for transport-provider coordination where relevant. Use those as prompts for a local handoff, not as universal operating rules. The approved venue and operator plan remains the source for traffic, boarding position, vehicle suitability and any specialist access decision.[1][2]

Receive the approved plan before the first pickup

Download the editable shuttle stop and boarding log (Markdown, English)

Ask for the current service version: route and trip IDs, planned pickup windows, exact stop names, passenger instructions, operator dispatch contact, onsite venue contact and the channel that will carry changes. Match the stop label on the event page, map, sign and driver instruction. If two sources disagree, mark the discrepancy and ask the designated owner to issue one confirmed version before briefing people at the stop.

Agree what information the operator actually needs to recognize riders. A named passenger list is not automatically necessary for every shuttle; some services use reservations, some count boardings, and some have open seating. If names or contact details are required by the approved service, keep that record in its restricted system. Use an aggregate trip log for ordinary staff handoffs, and do not put access needs or personal explanations in a broadly shared sheet.

Prepare the stop card and test the contact path

Put the current stop location, route name, first and last scheduled trips, operator dispatch number, organizer escalation contact and next update channel on a one-page run card. Include the approved accessible boarding contact and the specific place to direct a rider who needs help, without promising a vehicle or route that has not been confirmed. Check whether the chosen phone, radio or messaging channel works at the actual stop and agree a backup contact path.

Walk the public instruction from the venue entrance to the approved stop with the venue representative. The representative decides whether the route and waiting area remain suitable under its site plan. Keep signs and staff instructions consistent, including the return direction. A volunteer should know whom to call if the waiting area, queue or road situation changes; this article is not a design for traffic or crowd controls.

Before the first public pickup, make a short confirmation loop: the stop coordinator reads the route and next trip ID to dispatch; dispatch confirms the assigned run or says it is not yet assigned; the venue contact confirms the approved waiting location; and the organizer verifies which message is public. Write the result and time on the run card. If one input is missing, mark that part conditional and give staff a specific person to call. Repeat this check after a shift change or a changed stop, because a correct morning briefing can become outdated. It is a coordination check, not a departure clearance or a guarantee that the vehicle will arrive.

Record a small set of facts for every trip

Start a new row when the operator confirms a vehicle is serving a named trip. Record the planned time and stop, vehicle or run identifier supplied by the operator, actual arrival, boarding start, aggregate people boarded, actual departure and the person who confirmed those details. If a vehicle does not appear, record “not confirmed” rather than a guessed arrival. Distinguish “people waiting” from “people boarded”; neither is the same as ticket sales or venue check-in.

Compare the observed boarding count with the operator’s agreed count or reservation record only when those numbers are available and comparable. A discrepancy can arise from another stop, a changed trip, a no-show or a counting error; do not silently overwrite either figure. Note the difference, owner, time of follow-up and resolution reference. The operator controls vehicle capacity and any decision to board more passengers. Ask before announcing space on a later trip.

Turn an exception into a verified attendee update

For a delay, missing vehicle, changed stop or missed connection, first record what dispatch or the venue has confirmed. Route any proposed departure hold, substitute vehicle or stop change to the owner named in the approved plan. The stop coordinator can relay the confirmed decision and record when it reached the organizer, other stops and onsite staff. Never describe an unapproved alternative as available.

Use a short message: affected route and stop, verified current status, next update time with time zone, and a staffed contact or confirmed alternative if there is one. Repeat the same version on the channels attendees actually use, including staff at the stop. If no reliable ETA exists, say that it is being checked. Keep the earlier message in the log so the next shift can see what attendees were told.

Hand over open trips and close the service record

At a shift change, the outgoing coordinator reads the active trip and unresolved exceptions aloud to the incoming coordinator. Both compare the latest operator update, planned next departure, current waiting estimate, message version and contact numbers. Record who accepted the handoff and when. Do not treat an unanswered message as a completed transfer.

After the final operator-confirmed trip, reconcile scheduled versus observed trips, aggregate boardings where recorded, unresolved rider questions and any attendee updates that need a follow-up. Send the log to the organizer’s designated owner through the approved channel. Preserve personal manifests, if any, under the event’s restricted process rather than attaching them to a general debrief. This closes the stop-coordination record; it does not certify transport, traffic or venue safety.