How to Coordinate Transportation Between Multiple Office Buildings

Most companies that operate out of more than one building did not plan it that way. A headquarters absorbs a satellite office after an acquisition. A lease on a second building gets signed because the first one ran out of desks. A campus grows into three or four structures separated by a parking lot, a shuttle ride, or in some cases several miles of city traffic. Nobody sat down and designed the commute between Building A and Building C. It just accumulated.

The result, according to CBRE’s 2026 workplace research, is that the average office portfolio now runs at roughly 53% utilization even as more companies enforce in-office policies of three or more days a week. Buildings are fuller on paper than they are in practice, and a growing share of that in-office time is spent moving between sites rather than sitting at one desk. Cross-campus meetings, shared amenities like a single cafeteria or training room, department reorganizations that split teams across buildings, all of it adds foot and vehicle traffic to a route that was never engineered to carry it.

If your organization is feeling that friction, the problem usually is not that people cannot physically get from one building to another. It is that nobody owns the decision of how they should. This guide walks through the three coordination models companies actually use, how to pick the right one for your specific layout, and the operational details (scheduling, vendor selection, and cost control) that determine whether the system works or quietly falls apart after the first month.

Why “Just Let People Walk or Drive” Stops Working

Every multi-building coordination problem starts the same way: informally. Someone walks. Someone drives their own car and expenses the mileage. Someone books a rideshare because they are running fifteen minutes behind for a meeting in the other building. For a while, this works fine, especially if the buildings are genuinely close together and the number of cross-building trips is small.

It stops working at a fairly predictable inflection point, and it is worth being honest about where your organization sits relative to it:

Distance. Anything under a five-minute walk on a connected campus rarely needs a formal transportation solution. Once buildings are separated by a distance that requires crossing a public street, a highway, a rail line, or more than about a quarter mile of exposed walking, walking stops being a reasonable default for all-weather, all-day use.

Volume. A handful of cross-building trips a day is a non-issue. Dozens of trips a day, especially concentrated around meeting start times (the top and bottom of every hour, typically), creates real parking lot congestion, rideshare surge pricing at predictable times, and productivity loss as people build in 20 minutes of buffer for what should be a five-minute trip.

Liability and equity. When employees drive their own vehicles between work sites during the workday, most organizations are exposed to some level of liability if an accident occurs, and mileage reimbursement policies vary widely in how consistently they are applied. Employees without a personal vehicle, whether by choice or circumstance, are effectively locked out of meetings and amenities at the other site, which is a quieter but real equity problem.

Time cost, aggregated. Fifteen minutes lost per cross-building trip does not sound like much until you multiply it by trip frequency and headcount. A mid-size company moving 40 people a day between two buildings, with 15 minutes of friction per trip, is burning the equivalent of a full-time employee’s weekly hours in pure transit inefficiency, every week.

None of these problems require a shuttle bus on day one. But they are the signal that it is time to stop treating inter-building movement as something each employee solves individually and start treating it as a piece of company infrastructure, the same way you’d treat internet connectivity or badge access.

The Three Coordination Models

Once a company decides to formalize inter-building transportation, the decision usually comes down to one of three structural models. They are not mutually exclusive, larger campuses sometimes run a hybrid, but almost every workable system is a variation on one of these three.

Model 1: The Fixed Loop

A fixed loop runs a vehicle (or several, depending on volume) on a continuous circuit connecting every building on a set schedule, typically every 10 to 20 minutes during business hours. Think of it as a private bus line serving only your campus.

This model works best when:

• You have three or more buildings arranged in a pattern that supports a logical circuit rather than a straight line
• Trip volume is high and relatively evenly distributed across the day
• Buildings are far enough apart that walking is impractical, but close enough together that a loop of 15 to 25 minutes can realistically connect all of them

The advantage of a fixed loop is predictability. Employees learn the schedule the way they’d learn a subway timetable, and they build their day around it without needing to request anything. The disadvantage is that it is the least flexible model. If someone misses the loop by two minutes, they wait for the next one, and off-peak hours can mean running near-empty vehicles on a schedule, which is where cost efficiency suffers.

Model 2: Point-to-Point Scheduled Service

Point-to-point service runs a vehicle directly between two specific buildings at scheduled times, often synced to meeting blocks (for example, departures at :45 past each hour, timed to arrive five minutes before the top of the hour). This is the right model when you have two primary buildings with heavy traffic between them, and secondary buildings that see much lighter volume.

Point-to-point service is more efficient per trip than a fixed loop because every run has a clear purpose, but it does not scale well past two or three building pairs without starting to resemble a fixed loop anyway. Many companies that start here migrate to a loop model as they add locations.

Model 3: On-Demand / Reservation-Based

For lower-volume situations, an on-demand model makes a vehicle available to be booked for specific trips, similar to how a company might book an internal conference room. This works well for campuses where cross-building travel is driven by scheduled events (a training session, an all-hands, a client visit) rather than constant day-to-day flow, and it is often the most cost-effective option when overall trip volume does not justify a vehicle running fixed hours.

The tradeoff is coordination overhead. Someone, usually an office manager or executive assistant, needs to own the booking process, and utilization can be unpredictable, which makes vehicle sizing harder to plan.

Choosing Between Them

Situation	Best-fit model
3+ buildings, high and steady trip volume across the day	Fixed loop
2 primary buildings with heavy traffic, others lighter	Point-to-point scheduled
Trips driven mainly by scheduled events, not constant flow	On-demand / reservation-based
Campus growing quickly, model likely to change within a year	Point-to-point or on-demand (lower commitment, easier to convert to a loop later)

If you are not sure which category you fall into, a two-week trip log, having employees or building security note or badge-scan cross-building trips for ten business days, will usually make the pattern obvious. Most facilities and HR teams are surprised by how concentrated the demand turns out to be around a handful of predictable windows.

Building the Schedule: The Details That Actually Matter

Once you have picked a model, the schedule itself is where most coordination breakdowns happen. A few principles that hold regardless of which model you choose:

Anchor to meeting patterns, not round numbers. It is tempting to schedule a loop or point-to-point run every 15 or 30 minutes because those are clean numbers. But if most meetings start on the hour and half hour, a shuttle that also departs on the hour and half hour means everyone arrives exactly when the meeting is starting, not before it. Offset departures by 5 to 10 minutes ahead of common meeting start times instead.

Build in a buffer for the first and last run of the day. The 8:00 a.m. run and the 5:30 p.m. run tend to carry the highest and most schedule-sensitive volume of the day. Consider running these more frequently, or with a slightly larger vehicle, than the mid-day schedule.

Plan for lunch-hour spikes separately. If your buildings share a single cafeteria, gym, or other amenity, the 11:30 a.m. to 1:30 p.m. window often needs its own mini-schedule, since it behaves nothing like the rest of the day.

Publish the schedule somewhere employees actually check. A schedule that lives only on a printed sign in the lobby will not survive contact with a hybrid workforce. Put it in the same internal tool employees already use for room booking or the company directory, and if headcount and budget support it, a simple live-tracking link (many charter and shuttle providers now offer GPS-based passenger apps) removes most of the “is it running late” uncertainty that erodes trust in a new system fastest.

Choosing the Right Vehicle and Provider

Multi-building coordination does not require a full-size motorcoach in most cases. Vehicle sizing should follow your actual trip data, not a guess:

• Under 15 passengers per run: a minibus or sprinter-style vehicle is usually the right fit and is meaningfully cheaper to operate on a recurring schedule than a full-size coach.
• 15 to 35 passengers per run: a mid-size charter bus balances capacity with the ability to navigate tighter campus roads and drop-off areas that a full-size coach may struggle with.
• 35+ passengers, or combined with special events like an all-hands or a training day: a full-size charter bus becomes more cost-effective per rider, particularly if it is also being used for other corporate transportation needs on the same day.

If your company already contracts for other group transportation (an employee shuttle service for daily commuting, or charter buses for company events), it is worth asking that same provider to quote inter-building coordination as an add-on. Consolidating under one contract usually simplifies billing and gives you a single point of accountability for driver reliability, insurance, and scheduling, rather than managing a separate relationship for what is fundamentally the same kind of service at a smaller scale.

When evaluating a provider specifically for this use case, a few questions matter more than they would for a one-time event rental:

1. Can they commit to a recurring schedule with driver consistency? A different driver every week means a different learning curve for campus-specific quirks (a low-clearance drop-off area, a security gate code, a preferred idling spot).
2. What is their standby or delay policy? Inter-building coordination fails fast if a single mechanical issue takes the whole schedule offline for the day with no backup vehicle.
3. Are they insured and compliant for the specific routing? If any part of the route touches public roads (as opposed to private campus roads), confirm the provider carries appropriate commercial insurance and that drivers meet DOT hours-of-service rules, the same standard that applies to any charter bus operating on public roadways.
4. What does the contract say about schedule changes? Campuses evolve. Confirm how much notice is required to adjust stop locations or run times before you’re locked into a full annual term. The details in a typical charter bus rental contract are worth reviewing closely for recurring service, since the terms differ from a one-off event booking.

Communicating the Change to Employees

A well-designed schedule with poor internal communication will still fail. A few things that reliably improve adoption:

Explain the why, not just the what. Employees are more likely to use a new system, and less likely to default back to driving or walking, if they understand it is solving a real problem (parking constraints, safety, equity of access) rather than being an arbitrary new rule.

Run a two-week pilot before finalizing the schedule. Treat the first schedule as a draft. Actual usage patterns almost always reveal a gap (a run that’s consistently over capacity, a time slot nobody uses) that is worth adjusting before you commit to a longer contract term.

Designate a point of contact for schedule issues. Someone in facilities or HR should own this system the way they’d own any other piece of workplace infrastructure, with a clear channel for employees to flag problems.

Accommodate accessibility needs explicitly. Confirm your chosen vehicle and provider support ADA-accessible boarding, and make sure the accommodation process is easy to find and use, not something an employee has to ask around about.

When Coordination Extends Beyond the Daily Schedule

Regular inter-building transportation is only part of the picture. Multi-site companies also periodically need to move larger groups for one-off reasons: an all-hands meeting held at the building with the biggest auditorium, a department relocating equipment and staff between sites, a joint training session that pulls people from every location to one central spot. These events usually justify a dedicated charter bus rental for the specific occasion rather than trying to stretch your daily inter-building schedule to cover a much larger, one-time spike in demand.

It’s worth building this into your planning from the start: a facilities or HR team that already has a relationship with a transportation provider for daily inter-building service can typically add an event-day charter with far less lead time and negotiation than starting from scratch, since the provider already understands your campus layout, your drop-off points, and your security or badge-access requirements.

Measuring Whether the System Is Working

Once a coordination system is live, a few simple metrics tell you whether it’s actually solving the problem:

• Ridership relative to headcount. If a large share of employees who need to move between buildings are still driving or walking instead of using the scheduled service, something about the schedule, stop locations, or communication isn’t matching real demand.
• On-time performance. Late runs erode trust quickly. If a provider is consistently missing scheduled times, that’s worth raising immediately rather than waiting for a contract renewal conversation.
• Complaints or requests routed to your point of contact. A spike in “the shuttle didn’t show” or “I didn’t know this existed” messages usually points to a specific, fixable gap rather than a fundamental design flaw.
• Cost per trip, tracked over a full quarter. Seasonal variation (weather, headcount changes, a new building coming online) can shift utilization enough that a schedule built for August doesn’t hold up in January.

Review the system on a quarterly cadence for the first year, then twice a year once it stabilizes. Campuses change, leases end, teams reorganize, and a transportation plan that isn’t revisited tends to quietly stop matching the buildings it was designed for.

What This Actually Costs

Budget is usually the question that stalls a good plan indefinitely, so it helps to think about inter-building transportation in the same terms you’d use for any other recurring facilities expense, cost per employee per month, rather than as one large annual number that’s harder to justify.

A rough way to frame it for your own numbers: take the quoted monthly or annual rate from a provider, divide by the number of employees who will realistically use the service, and compare that per-employee figure against what you’re already spending informally. Many companies find that once they account for mileage reimbursement, the productivity cost of 15 to 20 minutes of friction per cross-building trip, and the administrative time spent handling ad hoc requests, a scheduled service costs less than the status quo, it just moves the expense from several scattered line items into one visible contract.

A few levers that meaningfully affect the price:

• Vehicle size relative to actual peak demand. Oversizing for a worst-case scenario that happens twice a year, rather than sizing to typical daily volume and handling occasional spikes with an add-on charter, is one of the most common sources of budget overrun.
• Hours of coverage. A schedule that runs from 7:00 a.m. to 7:00 p.m. costs meaningfully more than one that covers core business hours only. Look at your actual badge-swipe or trip-log data before committing to a wider window than you need.
• Contract length and driver consistency. Providers often price a 12-month recurring commitment more favorably than month-to-month service, but only commit to a longer term once your two-week pilot has confirmed the schedule is close to its final shape.

Weather, Security, and Other Site-Specific Factors

A few details are easy to overlook until they cause a problem in month two:

Weather-exposed waiting areas. If a stop location doesn’t have a covered waiting area, ridership drops sharply on rainy or extremely cold days, which is exactly when employees most need an alternative to walking. If a covered shelter isn’t feasible, consider a real-time tracking link so people can time their exit from the building to the vehicle’s actual arrival rather than standing outside waiting.

Badge access and security gates. Any stop or route that crosses a secured perimeter needs to be worked out with your security or facilities team well before the schedule goes live. A driver who doesn’t have a working gate code or badge credential on day one is a fast way to erode confidence in a brand-new system.

Visitor and contractor access. If your inter-building service will also carry visitors, contractors, or interview candidates (a common request once a scheduled system exists), decide in advance whether that’s in scope, since it changes both the badge-access logistics and the liability and insurance picture from an employee-only service.

Frequently Asked Questions

Do we need a formal contract, or can we book charters as needed? For genuinely low, event-driven volume, on-demand booking is often more cost-effective. Once trip volume becomes a daily, predictable pattern, a recurring contract with a fixed schedule almost always outperforms ad hoc booking on both cost and reliability.

What if our buildings are in different cities, not on one campus? That’s a different problem, closer to intercity corporate travel than campus shuttling, and is usually better solved with scheduled charter service tied to specific meeting days rather than a daily loop. The vendor evaluation questions in this guide still apply, but the schedule design section is built around same-day, same-campus movement.

Can one provider handle both our daily employee shuttle and inter-building coordination? In most cases, yes, and it’s usually worth asking. A provider already running a commuter shuttle program for your company already understands your site access requirements and can often extend a smaller vehicle to cover inter-building routes at a lower incremental cost than starting a second vendor relationship.

The Bottom Line

Coordinating transportation between multiple office buildings is rarely about the vehicles themselves. It’s about picking a structural model that matches your actual campus layout and trip volume, building a schedule around real meeting patterns instead of round numbers, and choosing a provider who can commit to the kind of day-in, day-out reliability that a one-time event rental doesn’t require. Get those three things right, and the system tends to disappear into the background the way good infrastructure should, employees stop thinking about how they’ll get from Building A to Building C, and just show up.

If your company is evaluating a recurring inter-building transportation plan, or needs a one-time charter for an all-hands or multi-site event, request a quote and our team can help size the right vehicle and schedule for your specific campus.