Henrico & White Oak Data Center Transportation

Plan a White Oak or Henrico Data-Center Visit

White Oak and Henrico data-center transportation may be requested for a technical delegation, investor, vendor, executive or infrastructure-site visit. State whether the traveler is going to a public office, a host-approved visitor area or a controlled campus, and provide the building and passenger entrance.

The facility sponsor controls authorization, escort and any device or photography restrictions. Chauffeured service delivers the passenger to the approved handoff; it does not grant campus access or enter operational areas.

White Oak, Eastern Henrico and Richmond Connections

Trips may connect White Oak Technology Park, eastern Henrico, downtown Richmond, RIC, IAD and Washington-area destinations. Identify the actual visitor building and host contact at each stop. A campus, office park or project name can have separate employee, freight and visitor entrances.

If the day includes a controlled site and a hotel, airport or public meeting, list the order and expected release time for each stop. Dispatch should not infer which entrance to use from a map pin.

Airport and Private-Aviation Coordination

Commercial airport reservations should include the operating airline and flight number, passenger mobile, baggage, meeting method and onward destination. Airport arrivals include a 30-minute grace period, except at FBOs. Flight monitoring supports dispatch, but cancellations, diversions, rebookings and changed flight numbers must be reported directly. Meet-and-greet is available only when requested and confirmed.

Private-aviation and FBO service is planned separately. Provide the airport, current FBO, aircraft reference, tail number when appropriate, lead passenger, handling or release contact, luggage and authorized meeting point. FBO waiting terms are confirmed separately; no grace period applies to FBO pickups.

Sedan, SUV, Sprinter, Minibus or Motorcoach

Choose equipment for who is traveling together to the White Oak or Henrico visit. An individual executive may need a sedan or SUV; a technical delegation may share a Sprinter only after the site sponsor confirms vehicle access, passenger count and ordinary luggage.

For a White Oak or Henrico campus visit, list each executive, companion, personal bag and presentation case, with the approved site entrance and meeting time. The nominal seat count does not establish fit for every item. Provide the full inventory so reservations can confirm the vehicle model, passenger space and usable storage.

Keep the Visitor Sponsor and Travel Booker Aligned

The executive assistant or travel desk controls the passenger itinerary, while the site sponsor confirms visitor access and the approved vehicle meeting point. Name both contacts and who can authorize a changed stop or delayed departure.

For a delegation, assign each person to a vehicle and identify whether the team separates after the site visit. Keep operational diagrams, access codes, facility security details and confidential project information out of routine trip notes.

Coordinate Controlled-Campus and Office Stops

A White Oak day may combine an office briefing, an escorted campus visit and a hotel or airport transfer. Confirm the host and vehicle access at each point before the schedule is accepted. If the site release is uncertain, protect the next fixed meeting and decide who can remove an optional stop.

For an itinerary spanning several days, provide dates, service windows, daily destinations and the person authorized to approve changes. Any retained time or return pickup must be confirmed in writing.

White Oak Site-Visit Booking Details

Send the date and local time zone, passenger and coordinator mobiles, complete addresses, approved visitor entrance, sponsor, flight when relevant, passenger and luggage count, equipment, stop order, required arrival, expected site release and return plan.

Confirm whether a host or escort will meet the traveler and whether the vehicle may wait at the approved location. Do not share facility access codes or sensitive operational data in the reservation.

Delegations and Campus-Visit Load Planning

A technical delegation may include employees, vendors and visitors with separate sponsors or access windows. Provide a passenger list and identify who may travel together. Confirm whether the vehicle should wait in a designated visitor area or return at a specified time.

If the campus visit includes presentation equipment, count cases and describe dimensions before assignment. A larger party may require more than one vehicle even when the total seat count appears sufficient.

Visitor Release and Vehicle Return

Before the visit, agree whether the chauffeur waits, returns later or moves to another assignment. The site contact should message the named coordinator when the traveler is released; the driver should not enter a controlled area to locate a visitor.

Controlled Campus and Public-Office Handoffs

White Oak and Henrico trips may pair a controlled technology site with a public office, hotel or airport. Confirm which stop requires a sponsor and whether its passenger entrance differs from employee or freight access. The customer arranges approval and escort.

For a two-site day, ask each host for a check-in and release contact. If a final airport departure is fixed, the coordinator should identify a flexible meeting that can be removed rather than compressing the final transfer.

Frequently Asked Questions