Vehicle Unit Download 90 Days: A UK Operator Guide

A vehicle comes back into the yard after a busy seasonal period. The workshop has dealt with defects, the driver has gone off sick, and the planned tachograph download has slipped. Someone checks the diary and realises the vehicle unit download is already outside the 90 calendar day limit.

That situation is common, but the recovery shouldn't be casual. The legal interval is only one part of the control. You also need the correct company-card process, reliable file retention, proper tachograph analysis, named sign-off and evidence that a transport manager can produce during a DVSA examination or Traffic Commissioner public inquiry.

Table of Contents

• The 90-Day Rule and Why It Trips Operators Up
• Legal Basis and GOV.UK Guidance for VU Downloads
  • Keep the different download duties separate
• Running the Vehicle Unit Download in Practice
  • Control the file from transfer to vehicle record
• Retention, Tachograph Analysis and Sign-Off
  • Make the review readable to a third party
• Scheduling, Alerts and Compliance Pack Evidence
• Handling Missed, Overdue and Event-Driven Downloads
  • Control the exception, not just the deadline
• A Practical VU Download Checklist and Next Step
  • Weekly reconciliation

The 90-Day Rule and Why It Trips Operators Up

For a UK operator, the routine vehicle unit download interval is at least every 90 calendar days. The rule was changed from 56 days to 90 days by the 2015 downloading regulations, which amended section 97D of the Transport Act 1968 and aligned Great Britain with the 90-day ceiling set by Commission Regulation (EU) No 581/2010.

That makes 90 days the legal maximum routine interval. It doesn't make day 90 a sensible target for your internal diary. A download scheduled on the final permitted day can fail because the vehicle is away, the company card is unavailable, the download key won't connect, or the responsible person is off sick.

Practical rule: Treat 90 days as the compliance floor. Build your operating routine so an ordinary disruption doesn't push a vehicle beyond it.

Christmas and other seasonal shutdowns expose weak systems quickly. A lightly used rigid vehicle may not attract attention in the same way as a daily trunking artic, but the calendar still runs while the vehicle is parked. Mixed fleets create another trap, particularly where one person manages goods vehicles, PSVs, trailers and workshop dates from separate spreadsheets.

The safest approach is to separate four controls:

• The download date: Record the last successful VU download, not merely the date a job was planned.
• The company-card process: Make sure the vehicle unit is locked to the operator's company card during the download.
• The evidence trail: Keep the original file, its analysis and the action taken on any infringement.
• The review cycle: Give a named person responsibility for checking due dates and exceptions.

A monthly download routine can be useful, but it still needs a vehicle-by-vehicle record. “We normally download every month” won't explain why one vehicle has no file for a particular period. A practical tachograph rules guide for operators should help your team distinguish a routine interval from the wider management duty.

Legal Basis and GOV.UK Guidance for VU Downloads

A 90-day VU deadline is only one part of the operator's legal control. Tachographs, drivers' hours, working time and operator-licence undertakings all connect to the same evidence trail. Check current legislation and official guidance for the fleet's circumstances, rather than relying on an old compliance sheet.

The previously cited GOV.UK operator responsibilities guidance sets out the routine requirement for vehicle-unit data to be downloaded at least every 90 calendar days. It also covers off-cycle events. Download the data immediately before transferring the vehicle to another person, without delay if the unit is removed from service or malfunctions, and whenever data loss is foreseeable. These triggers need their own workflow in OperatorCompliance, not just a recurring 90-day reminder.

The Passenger and Goods Vehicles (Recording Equipment) (Downloading of Data) Regulations 2015 amended section 97D of the Transport Act 1968. The domestic framework also includes the Road Transport (Working Time and Tachographs) Regulations 2005. Assimilated tachograph regulations provide the wider recording and drivers' hours framework, while the Senior Traffic Commissioner's statutory guidance, including Statutory Document No. 3, helps explain how vocational-driver compliance should be managed and evidenced.

Keep the different download duties separate

The VU deadline and driver-card deadline must sit on separate controls. GOV.UK operator-licensing guidance identifies at least every 90 days for vehicle-unit data and at least every 28 days for drivers' smart-card data in the relevant operator controls. Set separate due dates, owners and escalation rules. Combining them in one spreadsheet is an easy way to miss one while believing the other is covered.

Operator undertakings generally require the business to:

1. download the relevant tachograph data;
2. analyse it for compliance;
3. retain the records for at least 12 months; and
4. produce them when requested.

The GOV.UK goods vehicle operator licensing guide also places responsibility on operators to keep tachograph arrangements and vehicle-maintenance controls current. A downloaded file alone will not satisfy a Traffic Commissioner if nobody can show analysis, action on infringements and review by a named person. OperatorCompliance should therefore connect the original file, analysis result, corrective action and analyst sign-off to the vehicle record.

Instrument	What it covers	Why it matters for VU downloads
Transport Act 1968, section 97D	Domestic downloading duties	Provides the basis for the UK vehicle-unit interval
2015 downloading regulations	Amendment of the earlier interval	Changed the routine VU maximum from 56 days to 90 days
Assimilated tachograph regulations	Recording equipment and drivers' hours	Provides the wider tachograph compliance framework
Road Transport (Working Time and Tachographs) Regulations 2005	Working time and tachograph-related duties	Connects record management with wider operator controls
Operator undertakings	Downloading, analysis, retention and production	Sets the standard your evidence system needs to demonstrate

Use the GOV.UK tachograph rules guidance as a current reference, while checking the legislation and guidance version held in the compliance system. Remove obsolete 56-day instructions from live procedures. Keep the current rule, off-cycle triggers, 12-month retention requirement and sign-off record visible to the transport manager.

Running the Vehicle Unit Download in Practice

A vehicle can leave the depot before its download is complete, particularly when workshop and transport-office records are separate. Start by identifying the vehicle, checking the last successful download, and confirming which company card is authorised for the job.

For a typical LGV or one-man-operated artic, insert and leave the company card in the vehicle unit during the transfer. Switch the ignition on, with the key in position two, and remove the driver card. Allowing the unit to sit idle briefly can help it settle before downloading.

The equipment must suit the tachograph and remain within its licence or approval period. Operators may use TACESOLTacho or a manufacturer-approved device such as Digipost, Stoneridge or VDO. A wireless dongle can work well where the yard has suitable connectivity, but remote retrieval still requires monitoring and verification. The practical trade-off is clear: remote access reduces depot dependency, while a failed connection or corrupt file can leave the operator with no usable evidence.

Control the file from transfer to vehicle record

The download may produce .ddd, .esm or .v1b files, depending on the equipment and system. Apply a consistent name containing the vehicle registration mark, download date and operator code. Keep the original in a restricted network location, then upload that named file to the correct vehicle record in the tachograph system.

Traceability matters during an audit. A file in a general folder does not show whether it belongs to the artic, a spare rigid or a vehicle that has left the fleet. OperatorCompliance can link the original file and download history to the vehicle record, giving the transport office a clear audit trail.

Check these points immediately after transfer:

• Vehicle identity: Match the VRN and unit details to the intended vehicle.
• Date coverage: Confirm that the expected period is present and the file is not empty or partial.
• File integrity: Open it in the analysis system and check for import errors.
• Company ownership: Confirm that the operator's company card completed the download.
• Next action: Record the next due date and route the file for analysis.

Where vehicles rarely return to base, remote tachograph downloads can reduce reliance on depot visits. They do not remove the need to check the result, investigate exceptions and keep the records complete.

Before closing the task, confirm that the upload is attached to the correct vehicle and that the download history has updated. A successful transfer records the file. It does not, by itself, complete the compliance process.

Retention, Tachograph Analysis and Sign-Off

A shared drive containing tachograph files is an archive. It isn't, by itself, an analysis system. The operator's responsibility extends beyond downloading because the data must be reviewed to establish whether drivers' hours, working time and recording requirements have been followed.

For a competent VU review, the analyst should consider whether the expected period is complete, whether calibration information raises a warning, whether motion or consumption sensors show a change, and whether manual entries need explanation. The analyst should also compare vehicle-unit activity with the relevant driver-card downloads. Unassigned movement may require investigation, not an assumption that the data is harmless.

Make the review readable to a third party

A Traffic Commissioner doesn't need a folder full of unexplained files. They need to see who reviewed the record, when the review happened, what was found and what action followed. If an infringement was identified, the evidence should show how it was considered, whether the driver was contacted and whether the issue was closed or remains open.

The GOV.UK operator guidance on downloading and checking data applies the same core VU rule to buses and coaches. PSV operators therefore need the same discipline as goods operators, even where their working patterns and vehicle movements differ.

Duty	Legal source	Frequency	Evidence expected	OperatorCompliance record
Download VU data	Transport Act 1968 and current GOV.UK guidance	At least every 90 calendar days, plus event-driven downloads	Original file and successful upload	Vehicle download history
Download driver-card data	Transport Act 1968 and current operator guidance	At least every 28 days	Driver file and download date	Driver tachograph record
Analyse records	Operator undertaking and official guidance	Periodically after download	Analyst findings and actions	Review notes and status
Retain tachograph data	Current operator guidance	At least 12 months	Searchable original records	Retained file and audit trail
Resolve infringements	Operator management controls	After analysis identifies an issue	Debrief, action and closure evidence	Infringement report and sign-off

A system such as tachograph analysis software for operator compliance can keep the downloaded file, analysis notes and analyst sign-off together. The software supports the process, but it doesn't replace the operator, transport manager, maintenance provider or competent tachograph analyst.

Scheduling, Alerts and Compliance Pack Evidence

Set the control from the last successful download, not from the date someone planned to do the work. Record the completion date for every vehicle, calculate its next due date, name the person responsible and flag exceptions. If a vehicle is off the road, record that status and the reason. “Not in use” alone does not provide a controlled audit trail.

OperatorCompliance can issue reminders at 30, 14 and 7 days before the due date, then raise an overdue alert when the 90-day period is missed. Route each alert to a depot, role or named owner. A shared inbox is not an ownership system.

The useful test is whether a transport manager can open the monthly pack and answer these questions without reconstructing the history:

• Download status: Which vehicles are complete, nearing their due date or overdue?
• Exception record: Why has a vehicle left the normal cycle, and who is managing it?
• Analyst review: Has every uploaded file been examined and signed off?
• Calibration control: Is the relevant calibration evidence attached and current?
• Open actions: Which infringements or follow-up tasks remain unresolved?
• Maintenance context: Are safety inspection and vehicle or trailer dates still controlled?

Keep the download record, exception note, analyst sign-off and supporting documents together. That gives the transport manager one management view and shows whether the operator uses a shorter internal cycle instead of running close to the legal limit.

An overdue item should have a plain-English explanation beside its corrective action. Examples include a vehicle transfer, faulty download equipment, a prolonged off-road period or an internal task that was missed. Record who owns the action, what has been done and when the matter will be checked again.

At a Traffic Commissioner public inquiry, a calendar entry carries little weight on its own. A named owner, recorded exception, completed review and monthly management sign-off demonstrate that the system detected the problem and responded to it. That evidence also exposes whether the control was genuinely operated, rather than written after the event.

Handling Missed, Overdue and Event-Driven Downloads

A vehicle returns from a long workshop visit and its download is already overdue. The correct response is controlled recovery, not a rushed attempt to conceal the gap. Record the vehicle, last successful download, exact number of calendar days involved and reason for the failure. Driver sickness, depot closure, faulty download equipment and workshop time may explain the delay, but each exception still needs a named owner and a written record.

Download the data without waiting for the next planned cycle. The unit's memory is finite. Current GOV.UK guidance states that a vehicle unit holds 365 days of average data before the oldest records begin to be overwritten, as explained in the current tachograph download guidance. Once recovered, attach the original file to the vehicle record, send it for analysis and record the analyst's sign-off.