Remote tachograph data download: how it works and which checks matter
Remote download transfers compatible vehicle-unit and driver-card data without waiting for the vehicle to return. Regulation (EU) No 581/2010 sets maximum periods of 90 and 28 days; automation reduces manual work, but the undertaking must still verify outcomes, periods, completeness, retention and responsibilities.
- Published
- Updated
What should you know before automating downloads?
Frequency is only one part of the process: a reliable archive needs compatibility, authorisation, outcome checks and a documented policy.
Maximum periods
- 28 days for relevant driver-card data, counting days with recorded activity
- 90 days for relevant vehicle-unit data, not a generic calendar-month interval
Outcome checks
Every job should be checked by vehicle, driver, interval and file continuity.
Undertaking responsibility
Automation does not transfer organisational duties and decisions to the software.
Which data is downloaded, and where does it come from?
The driver card and vehicle unit are separate sources. Complete coverage requires both to enter the process where applicable.
Driver card
It records activity associated with the person and follows the driver between vehicles. Downloading the card does not replace downloading the vehicle unit.
Vehicle unit
It records data relating to the vehicle and its use. Downloading the unit does not replace downloading the cards used by drivers.
Files and integrity
Files must remain attributable to their source and period, readable and unaltered. DDD is a common label, but extensions and conventions can depend on the tools used; validation cannot stop at the file name.
How often should driver-card and vehicle-unit data be downloaded?
Regulation (EU) No 581/2010 defines maximum periods, not a recommended frequency that fits every organisation.
Maximum periods
| Source | Maximum period | Operational check |
|---|---|---|
| Driver card | 28 days | Check every card and the days with recorded activity |
| Vehicle unit | 90 days | Check every applicable vehicle and continuity across the period |
What maximum means
An undertaking may schedule more frequent downloads to reduce operational risk. The regulation also says that data must be downloaded without loss and that only days with recorded activity count when determining the periods.
Why the Italian decree of 31 March 2006 is no longer a current source
Italy's 31 March 2006 decree was repealed by a decree of 19 October 2021. For maximum periods, this guide therefore relies on Regulation (EU) No 581/2010, which is directly applicable and listed by EUR-Lex as in force.
How does a remote tachograph download work?
The workflow connects a compatible tachograph, device, connectivity, company authorisation, schedule and archive; one missing component can interrupt the chain.
1. Compatibility check
The tachograph model, vehicle, device, connection and required signals are checked. Availability should not be inferred from the vehicle year alone.
2. Undertaking authorisation
The workflow uses company credentials and the company card according to the configured architecture. Storage, renewal and authorisation status need a named owner.
3. Request and transfer
The system schedules the request; when the vehicle, device and network allow it, the file is transferred to the archive without a manual action on board.
4. Outcome and exception management
The job must produce a verifiable outcome. An error needs a recovery queue, a responsible person and another request before the maximum period is exceeded.
How do you check errors, empty files and missing periods?
An archive is not complete merely because it contains files. Each outcome must be connected to the vehicle, driver, requested interval and expected activity.
Control matrix
| Symptom | Initial check | Prudent action |
|---|---|---|
| Failed job | Connectivity, device, compatibility, company card | Record the error and reschedule before the deadline |
| Empty or very small file | Requested period, recorded activity, authorisation | Do not assume the cause; compare tachograph, logs and interval |
| Missing driver card | Assignment, last download, days with activity | Open a driver-specific exception and check the card |
| Discontinuous period | Start and end date of previous files | Reconstruct the gap and document the recovery outcome |
The check that prevents false certainty
Do not automatically attribute an empty file to a company lock or an error to connectivity. The same outcome can have different causes; diagnosis and recovery depend on the tachograph, device and configuration.
What remains the undertaking's responsibility after a download?
Remote download automates a transfer; by itself, it does not certify compliance, completeness or the correctness of a retention policy.
Checks and training
Article 33 of Regulation (EU) No 165/2014 assigns transport undertakings responsibilities for driver training, instructions and regular checks on correct tachograph use.
Availability and copies
The same article covers retention of record sheets and printouts and giving drivers copies of data downloaded from their cards when requested. Data and records must also be produced to competent authorities under the applicable rules.
File retention
Country, data type and purpose can affect applicable periods. The policy should state duration, access, integrity, copies, deletion and request handling; it requires legal review before being presented as a universal rule.
Penalties
Offences and amounts depend on national law and can change. This guide does not quantify them: an up-to-date assessment should come from a qualified adviser or the competent authority.
When does remote download make sense compared with manual download?
Remote download becomes useful when the cost and risk of manual coordination outweigh the technical process that must be managed.
Operational comparison
| Condition | Manual | Remote |
|---|---|---|
| Few vehicles at one depot | Can remain workable with clear ownership | Adds continuity but should be justified |
| Vehicles away for several days | Requires coordination and a physical return | Reduces dependence on vehicle return |
| Several depots or many drivers | Reminders and exceptions increase | Centralises schedules and outcomes |
| Recurring errors | Diagnosis is often distributed | Can expose logs and queues where supported |
Primary sources and limits of this guide
Sources are institutional and regulatory. Last reviewed: 24 August 2026. The page explains the process but does not provide legal advice.
Maximum download periods
Regulation (EU) No 581/2010, Article 1: 90 days for the vehicle unit and 28 days for the driver card; EUR-Lex lists the regulation as in force.
Undertaking responsibilities and records
Regulation (EU) No 165/2014, particularly Articles 33 and 36 in the consolidated text.
Correction to the former Italian source
A decree of 19 October 2021 repealed Italy's decree of 31 March 2006. The previous version of this guide incorrectly cited it as a current source; that reference was removed on 24 August 2026.
Questions about remote tachograph download
Concise answers about intervals, company cards, files, errors, retention and choosing a method.
How often must tachograph data be downloaded?
Regulation (EU) No 581/2010 sets maximum periods of 28 days for driver-card data and 90 days for vehicle-unit data. It also states that only days with recorded activity count and that downloading must prevent data loss. National rules or company procedures may call for more frequent checks.
What is remote tachograph download?
It is a process that requests and transfers available tachograph data through a compatible connection between the vehicle unit, telematics device, connectivity and archive. It reduces manual work, but every download still needs to be checked for outcome, period and completeness.
Is remote tachograph download mandatory?
No. The cited EU regulations set duties, maximum periods and data responsibilities, but do not require the transfer to be remote. Remote download is an organisational choice when vehicles, depots or shifts make the manual process fragile.
What does the company card do in a remote download workflow?
In compatible workflows, the company card is used to authenticate the undertaking and authorise access to the data it is entitled to retrieve. Storage, authentication, company locks and error recovery depend on the tachograph, device and configured workflow and must be checked before activation.
What are tachograph DDD files?
DDD is a common label for files exported from digital tachographs and driver cards. Extensions and conventions can vary between tools and markets: file integrity, covered period, origin and readability matter more than the extension name alone.
Why can a remote download fail or be incomplete?
Possible causes include tachograph or device compatibility, connectivity, company-card authentication, configuration, the requested interval or no recorded activity. A technically successful status is not enough: the team should check vehicle, driver, period, file size and archive continuity.
How long must tachograph data be retained?
Regulation (EU) No 165/2014 covers undertaking responsibilities, records, printouts and data availability, while Regulation No 581/2010 covers maximum download periods. The retention period for downloaded files must be checked against the country, data type and specific duty; this page does not replace legal review of a retention policy.
Check compatibility, process and exceptions before automating.
Bring tachograph models, vehicles, depots, cards and the current workflow to a demo: Zenit can delimit what is technically available without replacing regulatory review.