Home / Articles / Remote Tachograph Downloads: How They Work for UK HGV Fleets
Tachograph
Remote Tachograph Downloads: How They Work for UK HGV Fleets
Published 19/10/2026 · 7 min read
Rhys HughesDirector & Transport Manager at Operator Labs Ltd
How remote driver-card and vehicle-unit tachograph downloads work for UK HGV fleets: hardware, company-card auth, scheduling, failed downloads, and how files reach analysis.
This is general guidance for UK transport managers and operators. It does not replace official DVSA or Traffic Commissioner guidance, your operator licence conditions, or legal advice.
On this page
- Driver card and vehicle unit downloads
- Compatible tachographs and hardware
- Company-card authentication
- Scheduling and connectivity
- Failed downloads and contingencies
- Monitoring download success
- How files reach analysis
- What customers need to set up
- What remote download does and does not automate
- Questions operators ask
- Official sources
This guide explains the practical loop: what is downloaded, which hardware matters, how company-card authentication works, scheduling and connectivity, failed downloads, monitoring success, and how files eventually reach analysis. It is educational FleetPro practice and GOV.UK guidance — not a claim that remote download is live as a finished FleetPro product today.
Driver card and vehicle unit downloads
Digital and smart tachographs store two related records. The driver card holds the driver’s activity history. The vehicle unit (VU) holds what happened on that vehicle: card sessions, odometer, activity while a card was present, and events such as driving without a card.
GOV.UK’s tachograph rules and operator responsibilities require operators to download driver cards at least every 28 calendar days, and vehicle units at least every 90 calendar days, with earlier downloads when a driver leaves, a vehicle is transferred, a unit is removed, or data may be lost. Remote download does not change those deadlines — it changes how you obtain the files when the kit and service support it.
- Driver card download — pulls the card’s stored activity into the operator’s system before older days are overwritten.
- Vehicle unit download — pulls VU history so you can cross-check the fleet against cards, including cardless mileage and unit events.
- Both belong in the same compliance loop. Card-only or VU-only routines leave gaps a traffic commissioner can ask about.
Compatible tachographs and hardware
Remote download only works when the tachograph, wiring, telematics terminal and backend all support authorised company-card access. Not every GPS tracker can do this. Location, CAN fuel and behaviour events are separate capabilities from pulling .ddd-equivalent files from the tachograph.
In the FleetPro Tracking catalogue, remote tachograph download is intended only for compatible FMC650 installs with suitable tachograph wiring, on the HGV + Tacho plan (£14.99 per tracker per month ex VAT), when the service is available. The FMC003 OBD tracker (see live catalogue pricing) is for location and behaviour tracking — it does not provide remote tachograph download. Confirm compatibility before ordering or fitting; see the FMC650 in the FleetPro shop, and fleet GPS tracking for catalogue roles.
Company-card authentication
Remote download is not an anonymous scrape of the tachograph. Authorised company-card credentials are used so the operator can obtain data they are entitled to hold. Card control, PIN handling, and who may initiate downloads remain operator procedures — remote kits do not remove that duty.
Treat company cards like keys to the undertaking’s hours evidence. Limit who can insert or register them, record which vehicles they cover, and have a contingency if a card is lost, locked or expired. A remote schedule that fails because the card session is invalid still leaves you short of the download deadline.
Company-card controls
- Named holders and a clear PIN procedure
- Record of which cards cover which vehicles or depots
- Contingency for lost, locked or expired cards
- Manual download fallback if remote auth fails near a deadline
Scheduling and connectivity
Most remote systems schedule card and VU downloads against the 28- and 90-day windows, often with an earlier internal warning. The schedule only succeeds if the vehicle has power, the terminal has connectivity, and the tachograph link is healthy when the job runs.
Long-distance work, overnight parking without ignition, workshop downtime and weak coverage all interrupt jobs. Build the schedule around when vehicles are likely to be powered and online, and do not assume every overnight stop will complete a download.
| Factor | Why it matters |
|---|---|
| Ignition / power | Many terminals only complete tachograph jobs when powered |
| Mobile coverage | 4G outages leave files on the vehicle until the next opportunity |
| Wiring integrity | Loose tachograph or CAN links cause repeated failed jobs |
| Company-card session | Invalid or missing auth stops authorised downloads |
Failed downloads and contingencies
A failed remote job is still a compliance risk if it sits unnoticed until the legal window closes. Operators need a named person who reviews failures, a depot plug-in fallback, and earlier triggers when a driver is leaving or a vehicle is transferring.
- Retry on the next powered, covered opportunity — do not wait for the hard deadline.
- Fall back to manual company-card download at the depot when remote jobs keep failing.
- Download early when GOV.UK lists a trigger: leaver, vehicle transfer, unit removal, or risk of data loss.
- Keep evidence of the attempt and the contingency so you can show management control if asked.
Monitoring download success
Remote download only helps if someone watches success rates. A transport manager should be able to answer: which vehicles downloaded on time, which cards are overdue, which jobs failed, and what was done about it.
Use earlier warning bands than the legal maximums so a single failed week does not become a breach. Pair remote status with analysis overdue lists — a successful download that nobody opens still fails the analysis duty on GOV.UK.
How files reach analysis
Download and analysis are separate jobs. Remote download (when available) obtains files from the vehicle. Analysis reviews those files for hours, gaps, working time and card use. Filing unopened files is not analysis — see digital tachograph analysis.
Today, FleetPro analysis expects .ddd files uploaded in the web app or transferred with the Windows Upload Utility from the download page. That utility watches a folder, USB or manual pick for files you already hold — it is not remote download from the tachograph. Packages and add-ons are on pricing and tachograph compliance.
What customers need to set up
When remote download becomes available for eligible installs, expect a setup checklist along these lines — confirm the live offer before you commit hardware or wiring budgets.
Typical setup checklist
- Confirm the vehicle tachograph type and that remote-capable wiring is possible
- Select FMC650 (not a light tracker such as the FMC003) and the HGV + Tacho tracking plan when that service is offered
- Arrange professional hardwire fit — FleetPro does not book installs as a product
- Register company-card controls and name who monitors failures
- Agree how downloaded files will enter analysis (today: web upload or Windows Upload Utility)
- Write a depot fallback for failed remote jobs near a deadline
What remote download does and does not automate
Remote download can reduce depot plug-in journeys and make regular card and VU pulls more repeatable. It does not replace company-card control, professional wiring, connectivity, deadline ownership, or the transport manager’s review of findings.
| Automates (when working) | Still your job |
|---|---|
| Scheduled card / VU file pull over telematics | Meeting 28- and 90-day (and earlier) deadlines |
| Fewer routine depot downloads for covered vehicles | Investigating failed jobs and contingency downloads |
| Files available sooner for analysis intake | Analysing findings and closing infringements |
| Visibility of last successful download (in a good system) | Company-card security and leaver / transfer triggers |
Questions operators ask
Is FleetPro remote tachograph download available as a finished product today?
Which FleetPro tracker is intended for remote download?
The FMC650 on the HGV + Tacho plan, with suitable tachograph wiring, when the service is available. Light trackers such as the FMC003 do not do remote tachograph download.
Is the Windows Upload Utility the same as remote download?
No. The utility transfers already-downloaded .ddd files from a PC (watched folder, USB or manual pick). Remote download pulls files from the tachograph via telematics.
Does remote download replace analysis?
No. GOV.UK expects downloads to be analysed. Remote or manual intake only feeds that review.
Do you install the hardware?
We recommend professional hardwire fit for HGV tachograph-linked installs. FleetPro does not currently offer a bookable installation service.
Try FleetPro UK free for 14 days
Open a complimentary trial organisation, invite yourself as admin, and explore the package that matches how you operate. No card required. When the trial ends, features lock until you speak with us.
Official sources
- Tachograph rules for goods vehicles (GOV.UK)
- Responsibilities of vehicle operators (GOV.UK)
Related articles
- Manual vs Remote Tachograph Downloads: Which Suits Your Fleet?
- Tachograph Download Deadlines: Driver Cards, Vehicle Units and Missed Downloads
- Digital Tachograph Analysis: What UK Operators Need to Monitor
- Tachograph Company Cards: Lock-In, Lock-Out and Remote Download Authorisation
- FMC650 for HGV Fleets: Tracking and Remote Tachograph Downloads
- Choosing an HGV Tracker: Features That Matter to Transport Managers
