2026-10-14 · Multi-Site Coordination

How Do You Coordinate Vehicle Use Across Multiple Company Sites in Shanghai? Shuttle Routes, Inter-Site Runs and Stop Connections

Head office in the city, plant on the outskirts, warehouse beyond the outer ring, staff living in every direction: as soon as a company stretches beyond one address, transport stops being a matter of booking a vehicle and becomes a matter of running a network. Several commuting flows leave at the same morning peak, business travel between sites runs through them, and changing one route disturbs the timetables of another. Ten questions and answers set out a workable method: mapping the four sets of facts first; consolidating shuttle routes; a two-layer structure of scheduled and booked inter-site runs; how timetables connect and where transfer points belong; handling swings in headcount; managing stops and boarding order; four review measures; cost allocation and settlement through the company account; how to handle relocation, new sites and one-off events; and the four things that keep it running. General framework and method only; your own policy and agreement terms govern the specifics.

1. Mapping the Facts: Where Multi-Site Transport Gets Difficult

Q1: Why is vehicle use across several sites harder than a single site, and what should you map out first?

The difficulty across several sites is usually not a shortage of vehicles but demand that is scattered and timetables that collide. A single site runs one commuting flow; a multi-site company runs three or four at once with business travel between the sites threaded through them, so changing one route disturbs another. Before designing anything, put four sets of information on one sheet: the location, resident headcount and working pattern of each site, including start and finish times, whether shifts rotate and whether production runs at weekends; the journeys that must happen between sites every day - who travels, for what, and by when they must arrive; the vehicles and drivers available, how many passengers each carries and the hours they can work; and the physical conditions at each site, including how many vehicles can park at the gate and where staff wait. Without those four, route and timetable design becomes guesswork. The commonest disorder in practice is each site booking its own vehicles, so that two depart the same direction at the same morning peak, one full and the other half empty.

Q2: How do you consolidate shuttle routes across several sites?

The logic is to draw the sectors by where people live first, then assign them to sites. Group staff addresses into residential clusters along districts and metro lines - by address, not by department, since where someone lives has nothing to do with which department they sit in. Then look at the distance and travel time from each cluster to each site and judge which clusters can share a trunk route. Then match trunk routes to sites: where one cluster serves two sites, a trunk-and-feeder structure usually works best, with the trunk running to a split point and midibuses covering the last legs, which costs less and runs faster than two half-empty vehicles. Two limits should hold. Journey time should not run too long - beyond about sixty to seventy-five minutes, splitting the route deserves consideration, or staff experience suffers and turnover follows. And each route should carry a defensible load factor; below roughly half full on a sustained basis, merging routes or changing vehicle size is the honest answer rather than running the service anyway.

2. Inter-Site Runs and Timetable Connections

Q3: How should inter-site runs for business travel be arranged?

Inter-site travel is a different job from commuting and should not be merged with it. It carries few people, runs often and follows the business clock: a coach is wasteful, while dedicating vehicles to it ties up capacity. A practical structure has two layers, scheduled and booked. The scheduled layer covers fixed departures each day - say two in the morning and two in the afternoon - from the main site to the others, with staff presenting themselves at the timetable. The booked layer covers ad hoc and uncertain journeys, registered by departments in advance with time, number of passengers and destination, and consolidated by the dispatcher the previous evening, combining adjacent requests into one run where possible. Between them, predictable demand goes on the timetable and unpredictable demand is absorbed by combining bookings, which avoids running a vehicle empty several times a day. Agree one rule at the same time: ad hoc journeys must be registered in advance, and verbal same-hour requests are not accepted, because otherwise nothing can be combined and the cost cannot be held down.

Q4: How do shuttle and inter-site timetables connect, and where should transfer points sit?

Connection depends on building in a buffer rather than aiming to arrive exactly on time. Work out three intervals first: how long the trunk route actually takes to reach the transfer point, allowing for morning peak variation; the waiting and departure interval on the feeder; and the walking time from the drop-off point to the workstation. The sum of the three is the real arrival time for that route. Transfer points are best chosen in this order: inside the same car park or plot, so nobody crosses a road; close to a slip road or main road entrance, to cut detours; and with shelter from wind and rain. The worst choice is a busy junction, where staff have to cross traffic and vehicles have to turn around, which is poor on both safety and time. Allow five to ten minutes of buffer in the timetable: it is better for the vehicle to wait a few minutes for staff than to design to the minute, when a single hold-up at the morning peak can cause every connection on the line to be missed.

3. Headcount Swings and Order at Stops

Q5: How do you handle swings in headcount from shift patterns, overtime and leave?

Neither size the fleet for a full load nor take the average and add a little. Three steps work better. First, work out the theoretical peak from each site’s working pattern - the greatest number starting or finishing at the same time. Second, discount it with the last three months of actual attendance data, removing those on long leave, working flexibly or driving themselves, to arrive at a realistic peak. Third, keep one movable vehicle in reserve rather than filling every route. Rotating shifts are the special case: where a site runs three shifts, shuttles follow the handover rather than running twice a day, so fewer routes with more departures are the pattern, and rostering must protect the rest of drivers on night duties. Overtime and leave run through two channels. Departments with regular overtime report numbers a day ahead, and late additions are submitted by the department head before a cut-off on the morning itself. The dispatcher then decides whether to merge, add a departure or bring in a vehicle. Once the rules are set, they should hold, or someone will add a name at the last minute every day and the shuttles will never run on time.

Q6: How should stops and boarding order be managed?

Three things matter at stops: position, capacity and order. On position, a stop should be within about ten minutes’ walk for most staff in the cluster it serves; if it is not, the stop should move rather than staff being asked to adapt. On capacity, estimate by the number waiting at the same time at the peak, since an undersized waiting area spills into the traffic lane and needs agreeing with the estate or park operator. On order, three simple measures work: a fixed boarding bay, a fixed departure time and clear signage on the vehicle head showing route number and stops, so staff know which vehicle to board without asking the driver. Safety at the stop need not rest on the driver alone - guidance at the peak for a short period, by the administration team or the provider for the first week or two, lets habits form. Once a stop is fixed, changes should be notified in writing, so that staff are not left looking for a vehicle that moved five metres today and ten metres tomorrow.

4. Review Measures and Cost Settlement

Q7: How should multi-site transport be reviewed, and against which measures?

Four measures cover punctuality, efficiency, connection and experience. First, on-time performance: departures and arrivals against the timetable, reported route by route, because in a multi-site operation one congested route will flatten the aggregate figure and hide the real problem. Second, load factor: passengers carried against seats, by route and departure, used to decide whether to merge routes, change vehicle size or adjust departures; higher is not automatically better, since sustained loadings above ninety per cent mean it is time to add a departure. Third, connection success: the proportion of transferring staff who make their second leg as planned, a measure specific to multi-site operations and usually where complaints cluster. Fourth, feedback closure: the number, type and resolution time of complaints and suggestions. Review monthly, reassess quarterly, feed the results back to the provider and link them to quarterly assessment; collecting data without feeding it back means an extra spreadsheet each quarter and nothing more.

Q8: How should the cost be allocated and settled?

Start by separating shared from dedicated. Shared items - a trunk shuttle, the dispatch function, the reserve vehicle - benefit every site and can be allocated by passenger numbers or resident headcount. Dedicated items - an inter-site run used by one site, or overtime departures for a single site - are charged to that site or department. The advantage of splitting this way is that the rule can be explained: a site manager can see how their figure arises and is far less likely to overturn the whole arrangement at the next budget round. On settlement, a single company-account arrangement works best: one master agreement, one settlement cycle, usually monthly, and one consolidated statement with the trip detail attached, rather than a small contract and a separate payment run for every site. A statement should reconcile three things at minimum: the trip record with date, route or purpose and vehicle; confirmation of use, signed by whoever travelled or authorised it; and the cost build-up covering departures, waiting time and ad hoc additions. Anything that does not reconcile should be raised before settlement, not after payment.

5. Handling Change and Making It Run

Q9: What happens when a site relocates, a new site opens or an event needs transport?

Treat all three as route changes and run them through one process. Assess first: where staff are around the new address, how journey times change, and whether vehicles are added or released. Trial next: a new route is best run for a week at low load or empty to measure actual times rather than adopting the theoretical figure from a map. Then finalise: publish the timetable only after the trial data has corrected it, and give staff time to adjust. Relocation deserves particular care during the overlap, when the old site still has people closing it down and the new one is already running, which is when demand is most complex; start measuring against the new address two weeks ahead and hold some flexible capacity back. Events such as training days, annual meetings or visits are one-off trips: raise a separate request and confirm vehicles and drivers separately. Do not borrow the commuting shuttle - borrow it once and everyone on that route is late.

Q10: How do you keep this running day to day?

Four things. One set of figures, so routes, departures, stops, passenger numbers and complaints are all recorded in the same place rather than administration, sites and finance each keeping their own. Layered contacts, with one overall coordinator on the company side, one site contact at each location, and a single counterpart at the provider, so instructions come from one channel on each side. A fixed rhythm: daily attention to dispatch and exceptions, monthly review of measures and the statement, quarterly reassessment of routes and load factors, and an annual look at fleet and capacity structure, covering whether to merge routes, change vehicle size or adjust reserve capacity. And changes on the record, with stop adjustments, timetable revisions and ad hoc departures notified and logged in writing. With those four in place, multi-site transport moves from firefighting to running on a schedule. General framework and method only; your own policy and agreement terms govern the specifics.