Managing fleet compliance across multiple depots

A driver or vehicle that moves between depots — covering an absence elsewhere, or as part of normal fleet flexibility — creates a real risk if each depot is tracking compliance independently: a licence check due at one site, or a CPC renewal tracked in another depot's spreadsheet, can fall through the gap between the two.

The same applies to vehicle maintenance history — a daily check record or an outstanding defect logged at one depot needs to be visible if that vehicle turns up at another, rather than the receiving depot having no visibility into the vehicle's recent condition.

A single, organisation-wide record — covering every driver and vehicle regardless of which depot they're currently based at — closes this gap. It's the same principle that matters across most fleet compliance risk: visibility that's siloed by location creates blind spots that a shared record simply doesn't have.

Where responsibility for a shared vehicle or driver actually sits

A less obvious problem with multi-depot operation is ownership — when a vehicle or driver is temporarily at a second depot, it needs to be clear whose responsibility it is to make sure the daily check happens, or that a scheduled licence review isn't missed while they're away from their usual site. Without an explicit answer, the natural (and risky) default is that neither depot fully owns it: the home depot assumes the receiving depot is handling day-to-day checks, and the receiving depot assumes the home depot is still tracking the underlying compliance calendar. That gap is exactly where things get missed, and it's worth resolving with an explicit rule — ownership travels with the asset, or ownership stays with the home depot regardless of location — rather than left ambiguous.

Standardising checks and records across sites

Multi-depot fleets often grow that way gradually — a second site added as the business expanded, sometimes through acquisition of an existing operation with its own established (and different) way of doing things. That history means it's fairly common to find each depot running its own version of a daily check sheet, its own local spreadsheet for licence renewals, and its own informal process for flagging defects. None of those individual processes need to be badly designed for the overall picture to be weak — the problem is that they don't talk to each other, and a transport manager trying to get a fleet-wide view has to manually reconcile several different systems that were never built to be compared.

What good multi-depot visibility looks like

In practice, a fleet that's got this right can answer a handful of basic questions without anyone having to ring around the depots first: which drivers, across the whole fleet, have a CPC or licence check due in the next month; which vehicles have an outstanding defect right now, wherever they happen to be parked; and where a specific driver or vehicle currently is, if it's moved recently. If those questions require phoning two or three depot managers and waiting for replies, the fleet doesn't yet have organisation-wide visibility — it has several separate, locally-good systems that happen to sit under one Operator's Licence.

Consistent driver treatment across depots

Beyond records and paperwork, multi-depot fleets should be alert to inconsistent standards of driver treatment between sites — one depot enforcing a stricter points policy than another, or one site's transport manager being noticeably more diligent about licence checks than a counterpart elsewhere. Drivers talk to each other, including across depots, and a fleet with visibly inconsistent standards risks both a genuine compliance gap at the more lax site and a fairness perception problem among drivers who notice the difference.

One transport manager versus one per depot

Multi-depot operators have a real choice between a single nominated transport manager overseeing the whole fleet, or a transport manager (or delegated responsible person) at each site with a more localised view. There's no universally correct answer — a single transport manager gives one consistent standard applied everywhere but can become a bottleneck as the fleet grows, while per-depot management scales more easily but risks exactly the inconsistency described above unless the depots are working from genuinely shared standards and records. Whichever structure is chosen, it's worth being explicit about which compliance decisions sit with the transport manager centrally and which can be handled locally, rather than leaving that boundary implicit and discovering the gaps only when something's missed.

Bringing an acquired depot up to a shared standard

Where a second depot joins the fleet through acquisition rather than organic expansion, it usually arrives with its own established habits, some of which may be genuinely good practice worth adopting fleet-wide, and some of which may simply reflect how that business happened to do things before. Assuming the acquired depot needs to instantly conform to the existing depot's exact processes, without first understanding what's actually working well there, can lose useful practice along with the parts genuinely worth changing. A short structured review of how each depot currently handles checks, licence tracking and defect reporting, before deciding on a single shared standard, tends to produce a better combined process than simply imposing one depot's existing system on the other.

• –A vehicle temporarily rebased to cover another depot's absence has an outstanding defect that the receiving depot never sees
• –A driver's CPC renewal is tracked on a spreadsheet at their home depot and missed entirely while they're on loan elsewhere
• –Two depots, added to the fleet at different times, each run a different daily check sheet with no shared format
• –A transport manager can't answer "which vehicles have open defects right now" without calling every depot individually