Conference & Convention Transportation

Build around the places your attendees need to be.

A strong conference plan accounts for the whole attendee journey: arrival day, opening sessions, peak departures, evening functions and the trip home. Share your agenda and hotel list so we can review the movements that need dedicated group transportation.

• Portland: plan hotel-to-event transfers for programs at the Oregon Convention Center or other meeting venues. Identify the exact building entrance and approved passenger loading area.
• Tacoma and Seattle: discuss hotel loops for the Greater Tacoma Convention Center or Seattle Convention Center. For Seattle events, specify the correct Arch or Summit building rather than only the event name.
• Bend and Redmond: coordinate resort meetings, association gatherings and company retreats with hotel pickups and Redmond-area arrival plans. Include meeting sessions and evening activities in the same itinerary.
• Eugene, Salem and Southern Oregon: request group travel to regional conferences, university events and professional meetings. An itinerary can combine the main venue with a reception or hosted dinner, subject to route and schedule review.

Venue references illustrate possible itineraries and do not imply a venue partnership. Loading access and transportation availability are confirmed for each event.

Translate the agenda into passenger movements.

• Map each movement: record pickup, destination, first arrival, last departure and the passengers expected in each time window. A total registration count alone will not show the busiest shuttle periods.
• Separate peak demand: the first session, a large lunch break and the final reception can move most attendees at once. Share those periods so vehicle requirements can be reviewed.
• Review hotel loops: too many stops can make a loop difficult to predict. Group nearby hotels when practical and identify approved loading space at every property.
• Plan airport transfers: provide flight arrival windows, terminals, luggage counts and a trip contact. Charter airport movements are separate from our published scheduled-route services.
• Make information easy to use: distribute pickup instructions, route names, departure windows and the event organizer’s contact details before guests travel.

Request a written scope for operating hours, vehicle count, routing and any standby periods. Frequency depends on the actual route, loading time and traffic; confirm the proposed service pattern before publishing it to attendees.

A conference day can involve several kinds of travel.

For example, an association gathering in Portland may need a morning hotel transfer, a midday off-site visit and a final return after dinner. A Tacoma trade event may need a focused arrival period followed by a longer afternoon departure window. A Bend retreat may combine a meeting, team activity and restaurant transfer. These are planning examples, not fixed packages or guaranteed schedules.

Tell us whether you are moving attendees, speakers, exhibitors, staff or a mix of groups. Different arrival deadlines and equipment needs can call for separate movements. Provide accessibility requirements and assistance needs early so the appropriate arrangements can be discussed.

For an ongoing employee program, explore corporate and employee shuttles. For an evening group activity, see concert transportation or wine and brewery tour transportation.

What helps us prepare a useful proposal?

Send the event dates, draft agenda, hotel addresses, venue contacts, passenger estimates by movement and any known luggage or equipment. Include the earliest required arrival and latest planned return, along with requested amenities and accessibility arrangements.

Ask the team to explain what the quote includes and how changes are handled. Vehicle availability, extended operating time, extra stops, parking, overnight travel and revised demand can affect the final transportation plan. One organizer should approve itinerary changes and keep the passenger information current.