Running Fleets Across Multiple Sites Without Losing Your Mind

Managing a fleet at a single site is hard enough. Scale it to three sites, then five, then a dozen, and every problem you had before doesn't scale linearly -- it scales exponentially. The reporting complexity, the vehicle allocation decisions, the maintenance coordination, the cost visibility. We've seen fleet managers who are genuinely excellent operators at one site become reactive and overwhelmed the moment the organisation expands.

The four problems that show up at scale

In our work with multi-site fleet operators, the same four operational problems appear consistently, regardless of fleet size or sector. Getting ahead of them before they compound is the difference between managed growth and controlled chaos.

Problem 1: Metric drift. Each site develops its own definition of shared metrics. "Vehicle availability" at Site A means vehicles not booked for maintenance. At Site B it means vehicles with no scheduled assignment. At Site C the depot manager eyeballs it. The numbers are meaningless as comparators.

Problem 2: Vehicle visibility gaps. Vehicles move between sites, are temporarily assigned, or are held at third-party workshops. The fleet management system at the home depot loses sight of them. Nobody at the receiving site formally logs them. The vehicle falls into a grey zone where it's not generating cost data, not appearing in availability figures, and nobody quite knows where the responsibility lies.

Problem 3: Maintenance coordination failure. Each site has a preferred maintenance provider. Maintenance schedules are managed locally. A vehicle transferred between sites may miss a scheduled service because neither site's system knows it was due. Alternatively, it may be serviced twice in three weeks because both sites' systems trigger reminders independently.

Problem 4: Resource misallocation. Without a cross-site view, the fleet director has no reliable basis for knowing whether Site C's underperformance is a capacity problem (not enough vehicles) or a utilisation problem (enough vehicles, poorly deployed). These require completely different interventions, and choosing the wrong one wastes money while the real problem persists.

The vehicle master record: why it matters more than you think

Every multi-site fleet management problem traces back, eventually, to the quality of the vehicle master record. A vehicle master record is the single, authoritative source of truth for a vehicle's identity, specification, location, ownership, and operational status.

In single-site operations, this can be maintained in a spreadsheet and kept reasonably accurate with modest discipline. At multi-site scale, a spreadsheet-based master record fails within months. Vehicles move, data gets updated in one place but not another, and the record diverges from reality.

A vehicle master data hub -- which is the term we use at ExoFleets -- is a managed master record that all site-level systems pull from and contribute to, with defined rules about what data any given system can update and what requires a controlled change process. It sounds bureaucratic. In practice, it's what lets a 500-vehicle, 8-site fleet produce a consolidated performance report that everyone agrees is accurate.

"At four sites, a spreadsheet just about works. At seven, it doesn't. The inflection point is sharper than people expect." — ExoFleets Team

Practical steps for multi-site control

Getting multi-site fleet management under control doesn't require a single large programme. The most effective approach we've seen is incremental, starting with the data foundation and building operational capability on top of it.

1. Establish a central vehicle registry. Every vehicle has a single record with a unique identifier that follows it across all sites. Location, status, and home depot are attributes of the vehicle, not of the site system.
2. Agree metric definitions centrally. Write down what "utilisation", "availability", "cost per mile", and "maintenance compliance" mean for your organisation. These definitions apply at every site, no exceptions.
3. Create cross-site maintenance rules. When a vehicle moves, its maintenance schedule moves with it. The receiving site's system picks up the maintenance record on arrival. No vehicle falls out of the maintenance loop during transfers.
4. Build a consolidated reporting view. A weekly or fortnightly multi-site performance report that uses consistent metrics and is generated automatically from live data, not manually assembled from site manager emails.

The cultural dimension

There's a reality that technology can't fully solve: depot managers often resist central oversight. The data reveals things that were previously invisible, and not everything revealed is comfortable. A depot that's been reporting strong performance on its own metrics may look different when those metrics are standardised against a cross-site definition.

This is why multi-site fleet consolidation projects that are positioned as "visibility programmes" tend to fail, and ones positioned as "resource allocation tools" tend to succeed. Depot managers respond better to "this helps you make the case for more vehicles" than to "this shows us how your depot is performing." Both are true. Framing matters.