Choosing one system for compliance across several depots

If you run vehicles from more than one operating centre, the hard part is rarely collecting data. It is keeping the right evidence in one place without stripping depot teams of the responsibility they need to manage vehicles, trailers and drivers day to day. A good multi depot fleet compliance system should let head office see risk across the whole licence, while each depot still owns inspections, defects, licence checks and follow-up.

That matters in the UK because operator-licence compliance is judged on evidence as much as intent. When DVSA visits, or when a Traffic Commissioner file is being prepared, you need to show what was due, what was done, what was missed, who knew about it, and what happened next. If that information sits across spreadsheets, workshop diaries, email chains and separate tachograph portals, the problem is not only admin. It is control.

What a multi-depot system must control in one place

For several depots, one system should hold the full operator-licence record at vehicle, trailer, driver and depot level. That means more than a list of assets and expiry dates. It means a live compliance file that reflects how your fleet actually runs.

Start with the core asset register. Every vehicle and trailer should have a single record with registration or fleet number, depot allocation, operating centre, tax class where relevant, MOT or annual-test due date, plating details for trailers, PMI or safety inspection schedule, odometer history, ownership status, and document storage. If a unit moves from one depot to another, the history should remain intact. You should be able to see where it is now, where it was before, and which inspections or defects sit against it.

Drivers need the same treatment. A proper record should include licence categories, licence expiry, right to work evidence where you hold it, Driver CPC deadlines, DQC expiry, medical dates where applicable, induction records, agency status, depot allocation and licence check history. For passenger fleets and some private hire operations, local authority records may matter too, but the core UK operator-licence position stays the same. You need the driver file to show current entitlement and a clear review history.

Inspections and maintenance planning must also sit centrally. For UK goods and PSV operators, the system should schedule safety inspections in line with your declared maintenance regime and the DVSA Guide to Maintaining Roadworthiness. That means setting inspection intervals by vehicle or fleet group, planning by calendar date and mileage where needed, and keeping a record of completed inspections, brake tests, repairs, technician sign-off and any missed or deferred events. If your workshop works to an ISO week plan, the system should support that cleanly so depot teams can see what is due in week 32, week 33 and so on, without building their own parallel planner.

Tachograph evidence is another area where separate tools often create risk. It is not enough to have analysis somewhere else and hope someone logs in. A joined-up system should hold driver and vehicle tachograph records, infringements, missing mileage or unaccounted periods, and confirmation that follow-up happened. Operators should be able to connect the tachograph picture to the driver file and the depot responsible, rather than treating it as a standalone compliance island. If you are comparing options, our guide to tachograph analysis for smaller fleets is useful because the same workflow issues apply at larger scale.

For fleets that include vans, the legal framework is not identical to HGV and PSV operation, but the management need is similar. Vans may not sit under the same annual-test and tachograph requirements in every case, yet operators still need one record of inspections, defects, licence checks and document control. That is why many mixed operators look for compliance software for van fleets that can sit alongside heavier vehicles in one system rather than splitting the fleet by vehicle type.

How to compare central control with depot-level responsibility

The best systems do not force a choice between head-office control and depot accountability. They separate visibility from permission.

When you compare systems, look first at user permissions. A transport manager at one depot may need to add defects, complete inspection records, assign drivers and mark a vehicle VOR, but not edit records for another depot or change global settings. Head office may need group-wide reporting, audit access and escalation rights, but not to interfere with local workshop notes. If every user sees everything and can edit everything, you do not have control. If only one central user can update records, depot teams will revert to side systems and email.

Depot views matter just as much. A planner in Birmingham should be able to open a dashboard that shows only Birmingham vehicles, trailers and drivers, with overdue items, upcoming MOT or annual-test dates, open defects, licence checks due and tachograph exceptions needing action. Group management should then be able to roll that up across all depots to identify patterns, such as one site repeatedly missing PMI completion or one traffic office falling behind on Driver CPC follow-up.

Escalation is where many systems become superficial. It is easy to generate reminders. It is harder to prove what happened when a reminder was ignored. A useful compliance system should let you define what happens if an inspection is not booked, if a defect remains open, if a DQC is close to expiry, or if a licence check has not been completed. The audit trail should show the date due, the alert issued, who received it, whether it was acknowledged, and who escalated it. That is the difference between admin software and a compliance control system.

VOR handling deserves special attention. In practice, VOR is not only a workshop status. It is an operational control. When a serious defect is reported, the system should allow the vehicle or trailer to be marked VOR immediately, prevent casual closure, record the reason, record who applied the status, and show the release decision with date, time and sign-off. If a depot can remove VOR status without evidence of repair or authorisation, the process is weak. If head office can see VOR events but depot teams can still act quickly, you have a better balance.

Transport managers also need local accountability preserved. Under the UK regime, nominated transport managers carry real responsibility for continuous and effective management. A central system should support that, not blur it. The right question is not whether head office can see everything. It is whether each transport manager can demonstrate control over their own vehicles, drivers and maintenance arrangements while the operator retains oversight across the licence.

Which records matter most when DVSA asks for evidence

When DVSA asks for evidence, speed matters, but structure matters more. You need to produce records that are complete, legible, dated and attributable to a person.

The first priority is the preventive maintenance record. For each vehicle and trailer, you should be able to produce the inspection planner, completed inspection sheets, repair records, brake testing evidence where held, odometer readings, and any record of missed inspections or interval changes. If an inspection was late, the file should show why, who approved the deviation, and what was done to manage the risk. A blank gap is far worse than a documented exception.

Daily walkaround and defect reporting records are next. Signed checks, whether by app, portal or captured signature, need to show the vehicle, driver, date, time and reported condition. If a defect was found, the system should link the report to the repair or decision taken. If no defect was found, the nil-defect record should still be retrievable. For some operators, especially where depots are dispersed, this is one of the first areas where paper goes missing. A system that can retrieve the last 90 days of checks for a given vehicle in seconds is doing real work.

Driver licence checks and DVLA check history are equally important. You need the current entitlement, previous check dates, results, and any restrictions or endorsements noted. For agency drivers and casual staff, the record should still be tied to the depot and dates worked. If a driver was prevented from allocation because a check was overdue or a licence category was missing, that decision should be visible. The same applies to Driver CPC and DQC records. It is not enough to know an expiry date. You need to show that renewal was monitored and followed up.

Tachograph evidence often decides whether a file looks controlled or fragmented. A strong audit trail will show downloads or imported analysis, infringement review, missing mileage or missing records, driver acknowledgement where used, and management action. If the system cannot connect a tachograph exception to a named driver and a date for review, it leaves too much to explanation after the event.

You should also expect to produce document history quickly. That includes insurance schedules, OCRS-related internal monitoring if you keep it, calibration records where relevant, permit or certificate storage, and correspondence notes. Insurance itself may sit with another team, but many operators still benefit from checking vehicle cover details against askMID, which is the public service backed by the Motor Insurers' Bureau, also known as MIB. That does not replace your own policy records, but it can help spot obvious mismatches.

For operators that need to prepare a file for a Public Inquiry or formal review, the same principle applies. The Traffic Commissioner will not be impressed by a set of screenshots with no chronology. You need a system that can show the sequence of events, the user actions, the exceptions and the corrective action taken.

Comparing tachograph, licence and maintenance workflows

A common buying mistake is to compare modules one by one. Tachograph in one column, licence checking in another, maintenance planner in a third. That approach misses the real test, which is whether the workflows join up.

Take a simple example. A driver incurs repeated tachograph infringements. In a weak system, the analysis sits in one portal, the licence check in another, and the training record in a spreadsheet. In a stronger system, the transport manager can see the infringement pattern on the driver record, confirm the latest DVLA check, review Driver CPC status, add follow-up notes, and schedule a review without leaving the compliance workflow.

The same applies to maintenance. A daily defect should not disappear into a workshop queue with no link back to the original check. You want the chain from reported defect, to triage, to VOR if needed, to repair, to sign-off, to vehicle release. If an inspection is due while the vehicle is off road, the planner should reflect that and the audit trail should explain it. Separate modules can all look capable in a demo, but if they do not share events and statuses, your team ends up doing the joining.

Licence and entitlement checks should also interact with allocation decisions. If a DQC expires, if a DVLA check returns a concern, or if a medical date is overdue, the system should flag that in the same place where the driver is managed. That does not mean every system needs full rostering. It does mean compliance warnings should be visible where operational decisions are made.

Exception handling is often where the better systems pull away. Ask what happens when a vehicle misses an inspection, a trailer changes depot, a driver returns after a long absence, or a tachograph record is missing because the card was lost or damaged. If the answer is "we note it elsewhere", the workflow is incomplete. If the answer is "the exception is logged, assigned, escalated and closed with evidence", you are looking at something more useful.

This is one reason operators compare systems in a practical way rather than by feature checklist alone. Our system comparison page for fleet compliance software is built around that operational view, because compliance failures rarely happen inside a single module.

What to check on setup, data migration and integrations

Implementation is where a good buying decision can still go wrong. The right question is not only how long setup takes. It is how much compliance risk sits in the transition.

Start with data migration. Most operators already have records somewhere, spreadsheets, workshop software, old compliance platforms, shared drives, paper inspection sheets, or separate tachograph tools such as Fleetalyse or Logivo.AI. Before choosing a system, confirm exactly what can be imported. Asset lists are the easy part. The harder questions are whether you can bring in historic inspections, defect history, document expiry dates, driver records, licence check dates, Driver CPC and DQC deadlines, and depot allocations without rebuilding everything by hand.

You should also ask how the system handles inherited gaps. If your existing data is incomplete, the setup process should make those gaps visible so they can be corrected, not hide them in a bulk import. A clean go-live depends on clear ownership of missing registration details, absent inspection dates, duplicate driver records and inconsistent depot naming.

Planning structure matters too. Operators with external maintenance providers, in-house workshops and mixed fleets often work to different cycles. If your planners are built around ISO week scheduling, make sure the system supports that natively. If it only works by fixed monthly intervals, depot teams may end up running a separate wall planner to keep control of actual bookings.

Integrations are worth checking early, not after contract signature. If you already use workshop software, telematics, HR systems or document tools, ask what links are available through a REST API and whether webhooks are supported for status changes and event notifications. A proper integration can remove double entry for new vehicles, driver starters, odometer updates or completed repairs. A poor one can create more exceptions than it solves.

For some operators, links to insurance and verification processes matter too. While askMID is not a substitute for your own records, it can form part of a wider vehicle assurance process. Taxi and private hire fleets often have additional local checks and document requirements, so if you run that kind of operation, our guide to record systems that stand up to checks for taxi drivers covers some of the practical differences.

Finally, check whether the system fits the way your depots already work, or whether it expects everyone to change jobs to suit the software. A good compliance platform should strengthen workshop control, transport office follow-up and management reporting without forcing parallel spreadsheets back into use. At Operator Compliance, built by Fleeta Limited, we have shaped OperatorCompliance around the records and routines operators actually need to produce under the DVSA Guide to Maintaining Roadworthiness, because that is the standard your system has to support when the file is opened and the questions start.