home home

Attendee and Guest Movement

Event Transportation

Coordinate attendee groups, hotels, airports, venues, pickup windows, repeated runs, accessibility requests, organizer communication, and return movement as one event transportation plan.

Movement brief

  • Passenger groups
  • Pickup windows and route
  • Release and return plan

Organizer view

Event movement begins before the doors open

An event may bring together hotel guests, employees, speakers, attendees, staff, performers, sponsors, or separate invitation groups.

Transportation works best when the organizer identifies who needs to move, where each group starts, when they must arrive, and how the return or departure will be released. Metro reviews requests for events and organized groups. Final route, operating company, availability, price, and terms are confirmed through the quote and reservation documents.

Movement patterns

Common event transportation patterns

Hotel groups

Hotel-to-destination movement

Coordinate one or several hotels, passenger groups, pickup windows, arrival times, and return departures.

Arrivals

Airport arrivals and departures

Connect attendees or guests with hotels, meetings, or event locations. Include flight details and luggage when known.

Waves

Repeated attendee runs

Describe the route, passenger volume, operating window, pickup frequency, organizer release process, and final return.

Multiple locations

Sequenced event movement

List locations in order, timing between them, passenger groups, waiting needs, and the responsible contact at each stop.

Separate schedules

Staff, speaker, or organizer movement

Identify groups with schedules different from general attendees and any separate pickup or return plan.

Five decisions

Build the event movement in five decisions

01

Passenger groups

Describe each group and expected count for each hotel, airport, meeting point, or event window.

02

Pickup windows

Provide earliest and latest pickup times, required arrival, and schedule dependencies.

03

Route and stop sequence

List every hotel, airport, destination, meal, meeting, or return stop in the correct order.

04

Communication and release

Identify the organizer who can release each group, communicate changes, and confirm final passenger counts.

05

Return and closeout

Explain whether transportation waits, returns later, operates repeated departures, serves several hotels, or finishes at an airport or another destination.

Service boundaries

Event transportation versus related services

Broad event movement

Event Transportation

Use for attendee, guest, staff, hotel, airport, and destination movement around an organized event.

Wedding day

Wedding Transportation

Use for guest movement between hotels, ceremony, reception, and related wedding-day locations.

Athletic itinerary

Sports Team Transportation

Use for athletes, coaches, staff, equipment, games, tournaments, hotels, airports, and team schedules.

Business itinerary

Corporate Transportation

Use for meetings, clients, guests, teams, business events, and other itinerary-led movement.

Stakeholder framework

Group Transportation Planning

Use when several people are shaping the complete itinerary.

Coordinator checklist

What the event coordinator should prepare

  • Event date and schedule
  • Locations, hotels, and airports
  • Passenger groups and expected counts
  • Pickup windows and repeated-run needs
  • Luggage or equipment
  • Accessibility requests
  • Organizer and backup contact
  • Parking, loading, or waiting considerations
  • Return and departure plan

Do not submit attendee medical data, government identification numbers, payment-card information, or unrelated sensitive information.

Current operating details

Airport, hotel, and destination planning

For airport arrivals, include flight or terminal details when known, luggage, meeting instructions, hotel, event schedule, and organizer contact. For hotel groups, list the property, expected passengers, pickup window, destination, and return schedule.

Confirm current loading, parking, and access instructions with the destination or appropriate official source close to the event. Metro does not imply affiliation with any destination, hotel, airport, league, or event.

Metro Quick Quote

Start an event transportation request

Share the event schedule, hotels, airports, destinations, attendee groups, pickup windows, repeated runs, coordinator details, and return plan.

Required fields are marked with an asterisk. Share only the trip and contact details needed for your request.

Questions planners ask

Service planning FAQs

What event details should be included?

Provide the event date, venue or locations, hotels, airports, pickup windows, attendee groups, expected passenger counts, accessibility requests, organizer contacts, repeated runs, and return plan.

Can one plan include several hotels or pickup locations?

Yes. List each hotel or meeting point, the expected passenger group, the pickup window, destination, and the order in which the movement should occur.

Can transportation run in repeated waves?

A request can describe repeated arrival or departure windows. Include expected passenger volume, timing, route points, communication plan, and how the organizer will release each group.

How is event transportation different from wedding transportation?

Event Transportation covers broader attendee and organizer movement for many event types. Wedding Transportation focuses on guest movement between hotels, ceremony, reception, and related wedding-day locations.

Can an event plan include airports and hotels?

Yes. Include flight or airport details when known, hotel groups, venue schedule, luggage, arrival windows, and return or departure requirements.

When is event transportation confirmed?

Final availability, operating company, route, price, payment terms, and service conditions are confirmed in the quote and reservation documents.

Turn attendee groups and event timing into one movement plan

A clear hotel, airport, destination, communication, and return sequence helps Metro review the event as one coordinated request.