Tachograph Download Deadlines & Compliance

Failing to download tachograph files on time is one of the most common administrative infringements in the transport sector. Even if your drivers perfectly respect driving and rest limits, the absence of a digital record during an audit can result in "Serious" or "Very Serious" penalties under Regulation (EU) 581/2010.

European transport undertakings are legally mandated to extract and securely archive data from both the Vehicle Unit (VU) and the Driver Card. This data must be kept available for inspection for at least 12 months, ensuring a complete, untampered audit trail.

Types of Download Infringements

During a company audit or roadside check, inspectors will verify the Download Timeline. A violation is triggered if:

• Deadline Exceedance: A gap of 29+ days for cards or 91+ days for vehicle units.
• Incomplete Records: Missing specific days or failing to record activities performed away from the vehicle.
• Loss of Continuity: Failing to provide a continuous 12-month archive during a Ministry of Transport audit.
• Digital Signature Failure: Presenting corrupted .DDD files that lack valid cryptographic authentication.

Common Management Pitfalls

Many operators face heavy sanctions due to manual process inefficiencies:

• The "Holiday" Trap: Forgetting that a driver on leave must have their card downloaded if they performed any duty in the preceding 28 days.
• Insecure Storage: Keeping files on a single office PC without backups, risking total data loss in case of hardware failure.
• Remote Fleet Challenges: Drivers being away from the main depot for weeks, making physical downloads impossible without Remote Download (RDL) technology.

The easiest infringement in the world to prove

Most tachograph questions involve interpretation. Was the break long enough, did the activity get recorded correctly, was that period rest or availability. Missing downloads involve none. Either the data exists for the period or it doesn't.

That is why it sits so badly with authorities and why it is a poor thing to be casual about. There is no version of events to put forward, no context to explain, no mitigating circumstance in the file itself. The absence is the evidence.

The intervals themselves are not demanding: the driver card at most every 28 days, the vehicle unit at most every 90, under Regulation (EU) 581/2010. Both are maximums, not a schedule — and reading the deadline as a due date is the mistake, because it leaves no room for the month with two bank holidays and the annual leave of whoever does it.

Two sources, and one doesn't cover the other

A gap that appears constantly in small operations, usually in good faith. The driver card and the vehicle unit are two separate obligations, and downloading one does not discharge the other.

They also answer different questions, which is why both are required:

• The card follows the person — everything that driver did, in whatever vehicle. It answers "what did this driver do in March?".
• The vehicle unit follows the truck — everything that moved, with a card or without. It answers "who was driving when this moved with no card in?".

That second question is precisely why the vehicle download can't be skipped. Driving without a card doesn't show up in the driver's file as an error — it doesn't show up at all. It exists only against the unit, and it is the hardest question in any investigation, because it isn't answered with a document but with a name.

Who answers, and why outsourcing doesn't move it

The question usually surfaces mid-inspection, by which point it's framed wrongly. The duty to download and retain sits with the operator — regardless of who was engaged to handle the IT or where the disks physically sit.

A supplier contract governs a relationship between two businesses. It does not transfer the regulatory duty. The authority asks the operator and expects the files from the operator; a third party's failure is settled afterwards and separately.

Which gives an unglamorous conclusion that saves real money: delegate the task, keep the oversight. Looking at the list of completed downloads once a month isn't distrust of a supplier — it's the difference between learning about a gap before the inspection or during it.

The occasional driver is the one who slips

Missing downloads rarely affect the whole fleet. They affect whoever falls outside the routine — and it's always the same profiles.

• The driver who works part-time or covers shifts. He isn't in the office on the usual day, so he isn't in the download list either.
• Anyone back from long-term absence. The period before the absence quietly ages past its deadline while nobody is thinking about him.
• The spare vehicle. Used for a fortnight, parked for two months, and forgotten by a routine built around the regular ones.

Which is why the monthly check has to run against the list of drivers and vehicles, not against the list of files. Files show you what you have. Only the roster shows you who is missing.

In short

28 days for the card, 90 for the unit — maximums, not a diary. Download on a fixed day, keep the originals, and check once a month that the periods still join up.

Downloading is the first of three steps

Getting the data off the card is where most operations stop, and it's where the exposure actually begins. A file that exists somewhere nobody can find is, for every practical purpose, a file that doesn't exist.

• Download from both sources, on an interval shorter than the deadline.
• Store the originals where they'll still be next year, ordered by period, kept apart from reports.
• Check the period closes against the previous download, with no days belonging to nobody.

The third step is the one that gets skipped, and it's the one that catches the failures. Downloads can run for months with a hole in the middle and nothing will flag it — the files are all present, they simply don't join up. It surfaces only when somebody lines up the periods and looks.

TachoTools: Automated Compliance Monitoring

Our platform acts as a Digital Compliance Officer, ensuring your fleet is always audit-ready. By centralizing your files in our secure cloud, you eliminate the risk of human error.