Tachograph data: hosting, analysis and integration

Digital tachograph data reaches an analysis platform by one of three routes: remote download over the telematics unit, manual download to a card reader or key, or a file transfer from whoever currently hosts your data. Remote download is the only one that scales, and it is the one that determines whether tachograph compliance is a weekly task or a background process.

This guide is about the plumbing: how the data moves, who holds it, and what to check in a hosting contract. If what you need is a list of which tachograph tools connect to fleet software, that is a different question and we cover it separately, linked at the end.

The three integration routes

Remote download via telematics. The telematics unit reads the vehicle unit and driver card data over the CAN connection and transmits it. No depot visit, no missed downloads, and the statutory download intervals are met without anyone remembering. This requires a telematics unit with tachograph remote download capability and the correct company card arrangement in place.

Manual download. A card reader or download key, taken to the vehicle, with files transferred afterwards. Reliable in the sense that it works, unreliable in the sense that it depends on someone doing it on schedule, and vehicles that are away from base at the wrong moment generate gaps.

Provider to provider transfer. Where a tachograph analysis bureau already holds your data, you need it exported in a usable format to move or to combine it with anything else. Check this before you sign anything, because the practical ability to leave depends on it.

What to check before choosing a hosting or analysis provider

• Remote download support for your telematics. Not every combination of telematics unit and tachograph platform works, so confirm the specific pairing rather than accepting a general assurance.
• Raw file retention and export. You should be able to get the original driver card and vehicle unit files out, not just reports. Reports are the provider's interpretation. The files are the record.
• Retention period against your statutory obligation. Confirm the platform retains data for at least as long as you are required to hold it.
• Infringement rules transparency. Two platforms can report different infringement counts on the same data depending on how rules are applied. You want to know how yours are configured.
• API access. If the data cannot leave the platform programmatically, it cannot be combined with fuel, cost or route data, and it stays a compliance silo.
• Missing mileage and gap reporting. Unaccounted distance is both a compliance issue and a genuine operational signal, and not every platform surfaces it clearly.

What tachograph data is worth beyond compliance

Once the data is accessible rather than locked in an infringement report, three uses are worth having:

Driver identification for cost attribution. Tachograph card data tells you who was driving which vehicle, when. That is exactly what fuel exception investigation and fine liability need, and it is more reliable than a rota.

Duty cycle characterisation. Driving time against working time against rest, per route, is what tells you whether a duty cycle is genuinely severe or just long. That distinction matters for maintenance budgeting and for electrification feasibility.

Unaccounted mileage as a data quality signal. Distance recorded by the vehicle unit that is not attributed to a driver card is worth investigating, and it frequently correlates with other attribution gaps.

The integration that is usually missing

Most fleets have tachograph analysis and telematics and a fuel card, and no connection between the three. The result is that they cannot answer who was driving when a given fuel transaction happened, from systems that collectively contain the answer. Joining tachograph driver identity to telematics position and fuel transactions is a small piece of integration with a disproportionate effect on what the rest of the data can tell you.

Frequently asked questions

How does remote tachograph download work?

A telematics unit with tachograph download capability reads the vehicle unit and driver card data over the vehicle's data connection and transmits it to the analysis platform, using an authorised company card arrangement, so no depot visit is needed.

Who should own tachograph data hosting, the telematics provider or a specialist?

The telematics provider usually supplies the download path, and a specialist platform usually does the analysis, because infringement rule sets are a regulatory speciality. What matters is that the specialist can export raw files and offers API access, so the data is not trapped.

What should be in a tachograph hosting contract?

Raw driver card and vehicle unit file export, a retention period at least as long as your statutory obligation, transparency about how infringement rules are configured, API access, and a defined exit process that returns your data in a usable format.

Can tachograph data be combined with fuel and cost data?

Yes, and it is worth doing, because tachograph data supplies reliable driver identity per vehicle per period. That is the missing key for attributing fuel exceptions and fines to a person rather than to a rota entry.

What is unaccounted mileage?

Distance recorded by the vehicle unit that is not attributed to any driver card, usually meaning the vehicle moved without a card inserted. It is both a compliance matter and a useful signal that something in your attribution is incomplete.

Do I need a separate tachograph platform if I have telematics?

Usually yes, because tachograph analysis involves specific regulatory rule sets that general telematics reporting does not implement. The telematics unit often provides the download path, and the analysis sits elsewhere.

Where Fleevo fits

Fleevo does not replace tachograph analysis. It consumes the driver identity and activity data alongside telematics, fuel and maintenance records, which is what allows a fuel exception or a fine to be attributed to the person who was actually driving. Fleevo is an official partner of Samsara, Geotab and Verizon Connect, and integrates with Webfleet and other providers, including the tachograph download paths those units support.

Related reading

• Which digital tachograph tools integrate with fleet software — the specific tools and pairings, if you are choosing a platform
• Drivers' hours and tachograph rules — the compliance rules the data is assessed against
• Combining telematics and tachograph data
• Fleet fuel reconciliation — why driver identity is the join that makes fuel exceptions actionable