When people talk about a VOSA Tachograph check, they usually mean an inspection of driver hours records and Tachograph compliance by the UK enforcement authorities. The name VOSA is still widely used in transport, even though VOSA became part of DVSA some years ago. In practice, operators still use the old term to describe roadside stops, depot visits and operator compliance checks where Tachograph records, downloads and management controls are examined.

For day to day fleet compliance, these checks matter because they do not just look at whether a driver has the right card in the unit on the day. They look at whether we, as the operator, have a working system for collecting data, spotting issues, following up infringements and keeping complete records across the fleet. If that system is weak, problems usually show up quickly.

What people mean by VOSA tachograph checks

In UK transport operations, a VOSA Tachograph check can mean two slightly different things.

The first is a roadside enforcement check. A vehicle may be stopped and the driver asked to produce evidence relating to driver hours and Tachograph use. That can include the driver card, printouts, manual entries and any records needed to cover the current day and the previous 28 calendar days. For analogue records, that means charts. For digital records, it means the driver card data and any supporting printouts or written explanations where needed.

The second is an operator compliance check. This is broader and more important from a management point of view. DVSA officers can review whether we are downloading and retaining Tachograph data at the right intervals, whether infringements are being analysed, whether missing mileage or unknown driving is being investigated, and whether we have effective control over driver hours across the business.

The old VOSA name survives because many operators have used it for years, and people still refer to a VOSA Tachograph inspection in everyday conversation. What matters operationally is understanding what UK enforcement expects now.

For UK operators, that means being ready for both vehicle level checks and system level checks. Inspectors are not only interested in one isolated infringement. They want to see whether our transport operation is being actively managed. If we run HGV vehicles under EU drivers' hours rules, that includes proper use of the Tachograph, timely downloads, record retention and evidence that infringements are reviewed and acted on. If we run mixed fleets, we also need clarity on which vehicles and journeys fall under EU rules, which fall under GB domestic rules, and how we record that difference.

That distinction matters because the UK still applies retained drivers' hours and Tachograph requirements for in-scope operations, but there can be differences from EU member state practice in enforcement approach and domestic exemptions. Drivers moving between UK domestic work and EU rules work need clear instructions, because confusion around scope is a common source of avoidable errors.

What inspectors look for in Tachograph records

During a compliance review, inspectors usually want to see both the raw records and the way we manage them.

At the record level, that starts with driver card data. Inspectors may check whether the card has been downloaded within the required interval, whether activity is complete, whether there are unexplained gaps, and whether manual entries have been used correctly. Driver hours evidence must tell a coherent story. If a driver has had other work, rest, ferry movements, periods away from the vehicle or days without driving, the records need to account for that properly.

Vehicle unit data is equally important. The vehicle unit download shows driving without a card, unidentified activity, overspeed events, calibration details and vehicle movement history. If vehicle data is not being downloaded on time, we lose visibility of issues that may not appear on a driver card alone. In the UK, operators are expected to download driver cards at least every 28 days and vehicle units at least every 90 days. Many fleets choose to do this more often, because waiting until the limit leaves very little margin for missed vehicles, absent drivers or technical failures.

Inspectors also look at retention. Digital Tachograph data should be stored securely and remain accessible for at least 12 months. In practice, many operators keep it longer to support investigations, audits and employment matters. What matters most is that records can be produced when requested, in a usable format, and linked clearly to the vehicle and driver concerned.

Then there are the management controls. This is where many checks are won or lost. Enforcement officers often want to see:

  • a download schedule for driver cards and vehicle units
  • evidence that missed downloads are chased
  • infringement reports and review notes
  • records of driver debriefs or follow up action
  • processes for card expiry, replacement and renewal
  • procedures for agency drivers, subcontractors and hire vehicles
  • evidence that missing records are investigated, not ignored

If we rely on spreadsheets and manual diary reminders, it is easy for one late download or one absent driver to create a gap. That is why operators increasingly use remote Tachograph downloads across the fleet, especially where vehicles are away from base for long periods.

Where fleets usually run into problems

Most compliance failures are not caused by a lack of awareness of the rules. They come from broken routines.

A common issue is missed downloads. A driver card reaches the 28 day point, but the driver is on holiday, working nights, away on tramping work or using a different vehicle than expected. A vehicle unit reaches the 90 day point while the vehicle is off site, at a customer location or on hire. One missed event becomes a pattern, and by the time anyone notices, several records are overdue.

Another regular problem is incomplete records. Drivers forget manual entries. They remove the card and do not take a printout when needed. They use the wrong mode, fail to account for other work, or leave gaps between shifts. Agency drivers are especially risky if onboarding is rushed and nobody checks whether they understand the company process for Tachograph use.

Driving without a card is another trigger for scrutiny. There may be a genuine reason, such as a lost, stolen or malfunctioning card, but if the exception process is not followed properly, the vehicle unit will still show unidentified driving. Inspectors will expect us to explain what happened and what action we took.

Unreviewed infringements are also a major weakness. Downloading data is not enough on its own. If a system produces reports showing reduced daily rest, excess driving time, missed breaks or unknown activity, and nobody reviews them, then the operator cannot argue that it had effective control. A backlog of unexamined reports is often worse than having fewer reports, because it shows the process exists on paper but not in practice.

Poor driver processes sit behind many of these issues. Drivers need clear instructions on card insertion, manual entries, printouts, mode selection and what to do when the unit or card fails. They also need to know what happens after an infringement. If debriefs are inconsistent, one depot may challenge issues properly while another lets them pass.

Card expiry is another avoidable problem. A digital Tachograph card expiring mid operation can create immediate disruption, especially for drivers who work away from base. We see operators reduce that risk by keeping card expiry dates visible and planning renewals early, rather than relying on the driver to remember. Our guide to renewing a digital Tachograph card without disruption covers the practical steps.

How to keep Tachograph data ready for inspection

The most reliable way to stay inspection ready is to treat Tachograph compliance as a routine workflow, not an occasional admin task.

For most fleets, that workflow has four parts. Download, store, review and act.

First, download. We need a clear schedule for both driver cards and vehicle units. At minimum, that means the legal download intervals are never exceeded. In practice, we recommend tighter internal targets, because they give us time to recover from missed events. Remote collection is particularly useful for HGV fleets with vehicles on the road for days at a time, and for mixed fleets where some units return to base less often than others.

Second, store. Data needs to be retained in an organised way, with files correctly associated to the right driver and vehicle. If records are scattered across local PCs, USB sticks and inboxes, producing a complete audit trail becomes slow and risky. Secure central storage also makes it easier to review fleet history and respond quickly if enforcement asks for records.

Third, review. Downloads only become compliance management when someone checks the data. That means looking for infringements, missing mileage, unknown driving, overdue downloads and patterns by driver, vehicle or depot. It also means checking for exceptions that need explanation, such as card faults, manual entry errors or unusual work patterns. Our article on Tachograph analysis that cuts compliance guesswork explains how operators can move from raw files to usable oversight.

Fourth, act. If a report identifies a problem, there should be a visible response. That may be a driver debrief, extra training, a note on the file, a correction to the rota, or a technical check on the vehicle unit. If infringements repeat, the record should show escalation. Inspectors are looking not only for data, but for evidence that management is in control.

For mixed fleets, the workflow needs a little more structure. Not every van is in scope for Tachograph rules, and not every journey falls under the same regime. We need a consistent way to identify which vehicles and duties require Tachograph records, and which are covered by domestic rules or exemptions. That is where central fleet visibility helps, because compliance teams can see the asset, the route pattern and the driver activity in one place rather than piecing it together afterwards.

At Fleetalyse, we see operators reduce admin pressure when download status, vehicle activity and exception reporting are visible together. Instead of chasing files by email and spreadsheet, they can manage deadlines and follow up from one operational view. For fleets still relying on manual collection, our piece on Tachograph downloads without the spreadsheet chase shows what that change looks like in practice.

How joined-up fleet systems help day to day

Tachograph compliance becomes harder when the data sits in isolation.

If driver hours records are in one system, vehicle locations in another, maintenance schedules in a third and incident evidence somewhere else again, the transport team spends time reconciling information instead of managing the fleet. That is where joined-up systems make a practical difference.

When Tachograph visibility sits alongside live GPS tracking, we can quickly answer everyday operational questions. Is the vehicle back at base for a manual download, or still out on a long run? Did the unidentified driving event happen during a workshop movement, a yard shunt or a live delivery? Is a late card download linked to annual leave, sickness or a route change? Context speeds up compliance decisions.

The same applies to driver management. If a driver hours issue appears in the data, it helps to see the route, the vehicle, the timings and any related operational notes together. A transport manager can identify whether the problem came from poor planning, traffic delay, repeated driver behaviour or a misunderstanding of the rules. That makes follow up more specific and more effective.

For operators using connected cameras, Smart dashcams can add another layer of evidence where events need investigation. They do not replace Tachograph records, but they can support incident review and driver coaching when combined with vehicle activity and route history.

A joined-up platform also helps with oversight across different asset types. Many UK businesses do not run a pure HGV fleet. They may have artics, rigids, vans, trailers and plant moving under one operation. In those environments, separate systems create blind spots. We built Fleetalyse to bring those functions together, with live GPS, remote Tachograph downloads, reporting and hardware options that suit different rollout models.

That can include Fleetalyse-ready trackers for straightforward deployments, unlocked Teltonika devices where a business wants flexibility, and broader fleet setups using IoT SIMs, CAN data and map views based on OpenStreetMap. Day to day, the value is not in the hardware names themselves. It is in giving transport teams one place to work from, through the Customer Portal and Tracker login, instead of jumping between portals and spreadsheets.

The same principle applies to reporting. Good compliance reporting should not sit apart from the rest of Fleet insight. If we can see download status, vehicle utilisation, route activity and exceptions together, we spend less time assembling the picture and more time managing it.

For operators planning a broader rollout, our joined-up fleet management solutions for commercial fleets show how we approach that in practice.

A VOSA Tachograph check is rarely about one file in isolation. It is about whether the records are complete, whether the deadlines are under control, and whether management can show a working compliance process. If we can download on time, store securely, review consistently and act on what the data shows, inspections become far less disruptive and daily fleet compliance becomes easier to maintain.

Fleetalyse supports that with practical tools for UK operators who need Tachograph visibility alongside GPS tracking, reporting and connected fleet workflows. For transport teams trying to reduce admin while tightening control, that joined-up view is often the difference between chasing compliance and managing it.

Does VOSA still carry out tachograph checks?

Many operators still say VOSA, but the checks people mean are now associated with current UK enforcement and compliance bodies. The practical issue is the same: your Tachograph records, driver hours evidence and operator controls must stand up to inspection.

What Tachograph data should an operator keep?

Operators should keep vehicle unit downloads, driver card downloads and supporting records that explain work, rest and any missing data. They also need evidence that records are reviewed and that issues are followed up.

How often should Tachograph data be downloaded?

The exact schedule depends on the applicable rules and your operation, but it must be frequent enough to stay compliant and avoid gaps. Many fleets use remote downloads to reduce the risk of missed deadlines.

What happens if infringements are found?

An infringement does not only concern the individual driver. Inspectors may also look at whether the operator identified the issue, investigated it and took corrective action through training, process changes or management follow-up.

Can small fleets manage Tachograph compliance without extra admin?

Yes, if the process is simple and consistent. A small fleet benefits from clear download schedules, central record storage, regular checks and one place to view vehicle activity, driver information and compliance tasks.