Corporate & Employee Shuttles

Transportation built around Northwest workplaces.

Start with the people you need to move, the places they need to reach and the times that matter. A recurring shuttle, a temporary project and a single company event call for different plans. Our team will review the route, vehicle, driver schedule and service requirements with your organizer.

• Portland, Hillsboro and the Willamette Valley: discuss employee pickups, office-campus connections, remote parking and hotel-to-worksite transfers. Include shift start times, approved loading points and any access restrictions.
• Tacoma, Seattle and the Puget Sound area: plan group movements between meeting points, workplaces, hotels and events. Separate campus transfers from longer commute or intercity movements so each route has a useful purpose.
• Bend, Redmond and Central Oregon: coordinate staff travel, construction-project movements, training days and corporate retreats. Include seasonal road considerations when the itinerary crosses the Cascades.
• Eugene, Salem, Southern Oregon and regional project sites: request workforce or meeting transportation with the full operating area and dates. For remote sites or longer assignments, provide the site address, lodging plan and required arrival windows.

These are examples of transportation requests we can review, subject to availability and confirmation. For local trip planning, explore our Portland, Eugene and Tacoma-area pages.

Employee commute and campus shuttle programs

A useful employee route connects a clear origin with a real workday need. That may be an approved central pickup, a remote parking area, a hotel used by visiting staff or a transfer between buildings. Send expected riders by shift and pickup point, along with the arrival deadline at the workplace.

For campus transfers, map the buildings, boarding locations and busiest time windows. For commute service, identify the workdays, shift-change pattern, travel distance and return departures. A proposal should distinguish a fixed scheduled route, repeated transfers and a vehicle requested for a defined operating window.

A Portland-area employer might request a remote-parking connection during a busy period. A Tacoma organization might need a hotel-to-training-site transfer for visiting staff. A Central Oregon company might combine an employee meeting with a team activity. These examples help frame a request; route feasibility and availability are reviewed for the actual program.

Data center and construction workforce transportation

Large projects can involve changing crew counts, early starts, multiple contractors and controlled site access. Transportation planning should account for those details from the beginning. We welcome inquiries from project owners, general contractors, facilities teams and staffing coordinators.

• Shift-based movements: give the reporting time, expected boarding demand, shift overlap and return release windows. Explain whether the crew count changes during the project.
• Remote parking and staging: identify approved lots, passenger loading areas, coach turning space and where vehicles can wait between movements.
• Controlled access: share badging, escort, screening, vehicle inspection and site-orientation requirements. Confirm the site representative responsible for permissions and arrival instructions.
• Project phases: include mobilization, peak staffing, weekend work and anticipated changes. A short initial assignment and an extended program need different scheduling review.
• Crew belongings and accessibility: describe bags, tools or other equipment and any assistance needs so vehicle requirements can be discussed.

For a data-center or industrial-site request, send the actual site location and access process rather than relying on the project name. Dedicated service, standby periods, reporting and additional vehicles should be specified in the proposal.

Union events, strike transportation and labor disruptions

Unions and labor organizations can request transportation for conventions, training, member meetings, rallies and travel to approved picket or assembly locations. Employers can also submit transportation requests during strikes or other labor disruptions. Each request is reviewed individually before any service is confirmed.

A transportation plan for these situations needs a clear description of who will travel, the trip’s purpose, the pickup and destination, the operating dates and the responsible organizer. Describe any expected changes in site access, street access, pedestrian activity or loading arrangements so the team can review the route and operating requirements.

• Union-organized travel: identify the union hall, meeting venue, training site or approved assembly location, with passenger counts and the planned return.
• Employer requests during disruption: explain the passenger group, worksite, shift windows, requested movements and site contact. The scope and operating conditions must be reviewed before a commitment.
• Access and coordination: provide authorized loading points, property permissions and a reachable on-site contact. Transportation arrangements must account for current access conditions and instructions.
• Changes on the day: agree on who can approve revised stops or times and how passengers receive updated instructions.

Availability, site conditions, driver scheduling and the proposed scope determine whether a request can be accepted. Time-sensitive inquiries should include the full details and a direct callback number.

Corporate meetings, retreats and special events

A company transportation program may include airport arrivals, hotel transfers, an all-hands meeting, a site visit or an employee celebration. Share the whole agenda so the travel plan covers the beginning and end of the day, including the return after an evening function.

For a multi-day meeting or hotel loop, see conference transportation. For a group activity, explore concert and venue charters, ski trips or wine and brewery transportation. Activities and venue reservations should be coordinated separately from transportation unless included in the written arrangements.

What procurement and operations teams should send

• Scope: program purpose, start and end dates, days of operation, pickup and destination addresses, and anticipated contract period.
• Demand: passenger estimates by route, shift or event movement; peak periods; luggage or equipment; and accessibility requirements.
• Schedule: first required arrival, return windows, breaks, standby periods and any overnight travel.
• Site requirements: approved loading, parking and staging areas; access contacts; vendor onboarding; requested documentation; and any required site procedures.
• Commercial details: proposal deadline, billing contact, purchase-order process, approval steps and how the organization expects changes to be handled.

Ask the team to identify what the quote includes, the assigned service assumptions and any items that require further confirmation. Requested vehicle features, insurance documentation, reporting arrangements and vendor qualifications should be reviewed directly with the charter team.

Agree on a launch plan and a way to measure it.

For a recurring program, start with the route map and demand estimate. Review pickup access and the daily operating window, then agree on the final scope before communicating service to riders. If an initial trial period is useful, request it as part of the proposal rather than assuming it is included.

Decide with your transportation contact how ridership, boarding delays, schedule adherence and approved changes will be recorded and reviewed. Define a missed pickup, a late arrival and the passenger-count process in advance. Any technology, live tracking or customized reporting should be confirmed in the proposal.

A named operations contact, current pickup instructions and a clear change-approval process help a shuttle remain useful as the workplace changes. Share revised shift patterns and passenger demand promptly so the service plan can be reviewed.