Tachograph Analysis Software: Do You Need It?
The law requires you to analyse tachograph data. It does not require you to buy software to do it. Those are two different obligations and conflating them is how small operators end up paying for a system they do not need — or, more often, assuming the whole thing is optional because they cannot justify the subscription.
For a one or two vehicle operation with a single regular driver, a disciplined manual routine can meet the duty. Somewhere between three and five vehicles it usually stops being realistic, and the failure is rarely dramatic — it is a reference period that quietly went unchecked for four months.
General guidance, not legal advice. Drivers' hours and tachograph obligations are enforced by DVSA and are amended from time to time. Check current DVSA guidance for your operation.
What the Law Actually Requires
DVSA's tachograph guidance for goods vehicles states it in one sentence: "Operators must periodically download this data from digital and smart tachographs (known as the Vehicle Unit or VU) every 90 days and from driver cards every 28 days and analyse the information to ensure that the rules have been complied with."
Three separate duties sit inside that sentence:
- Download the vehicle unit — every 90 days
- Download driver cards — every 28 days
- Analyse the data to confirm compliance
DVSA's operator responsibilities guidance puts those two intervals in calendar terms — operators must download from the vehicle unit "at least every 90 calendar days" and from driver cards "at least every 28 calendar days" — and adds the enforcement dimension: "make regular checks of charts, manual records and digital data to ensure compliance" and "be able to produce records to enforcement officers for 12 months."
Note what is not specified: any particular method, format, or product. The obligation is outcome-shaped. You must be able to show you checked, and show what you found. Our tachograph downloads guide covers the download mechanics; this post is about the analysis half.
What "Analysis" Actually Involves
The word makes it sound like one task. It is really five, repeated every cycle:
- Infringement detection — driving over 9 or 10 hours, insufficient daily rest, missed 45-minute breaks, weekly and fortnightly driving limits
- Working time calculation — the separate 60-hour weekly cap and 48-hour average under the Working Time Directive, which the tachograph does not compute for you
- Missing mileage — gaps between the last recorded activity and the next, which is what DVSA examiners look for first
- Manual entry checking — whether drivers correctly recorded other work, availability and rest when away from the vehicle
- Follow-up evidence — the record showing an infringement was raised with the driver and addressed
The last one is the one most often missing. Finding an infringement and doing nothing about it is arguably worse than not looking, because you now have documented knowledge of a breach with no corrective action attached.
When the Manual Approach Genuinely Works
It works when all of these hold:
- One or two vehicles, and drivers you see every week
- Regular, predictable work — same routes, same hours, little night work
- No agency or occasional drivers
- Somebody who actually understands the rules doing the checking
- A fixed slot in the week when it happens, not "when there's time"
At that scale, downloading cards monthly and working through the printouts against a checklist is defensible. Keep the analysis output — the marked-up records, the infringement log, the driver conversations — for the full retention period. That paperwork is your compliance evidence.
When It Stops Working
The manual routine breaks down at predictable points, and it is usually one of these rather than fleet size alone:
- The 48-hour average. Working time averaged over a 17-week reference period is arithmetic no one does reliably by hand. This is the single most common reason operators move to software.
- More than one driver per vehicle, or drivers moving between vehicles. Reconciling driver cards against vehicle units by hand gets error-prone fast.
- Agency drivers. You are responsible for their hours on your vehicles, often without visibility of what they did elsewhere that week.
- Night work. The 10-hour cap in any 24-hour period containing night work needs checking every duty, not spot-checking.
- The moment you fall behind. Catching up three months of manual analysis in one sitting does not happen. The backlog just becomes permanent.
- An impending audit or Earned Recognition application, where digital drivers' hours management is an entry requirement rather than a nice-to-have.
What to Look For
If you do move to software, these are the criteria that actually matter for a small operation — as opposed to the ones that matter for a 200-vehicle fleet.
1. It reads your tachograph files without a conversion step. Standard digital tachograph download files should import directly. If getting data in requires a manual export-convert-upload dance, the routine will lapse.
2. It calculates working time, not just drivers' hours. Plenty of tools flag driving infringements well and quietly ignore the 48-hour average. Confirm the reference period calculation is there before you commit — it is the hardest part to do manually and therefore the main thing you are buying.
3. It produces evidence, not just alerts. You need an exportable record of what was checked, what was found, and what was done. A dashboard that shows current status but cannot produce a 12-month audit trail leaves you short at exactly the wrong moment.
4. Infringement letters and driver sign-off are built in. The follow-up step is a legal expectation, not admin. Tools that generate the driver letter and record acknowledgement close the loop properly.
5. Missing-mileage detection. This is what examiners check. If it is not in the tool, it is back on you.
6. Pricing that fits a small fleet. Per-vehicle pricing sounds proportionate but frequently carries a minimum monthly charge that makes a 2-vehicle operation pay a 10-vehicle price. Read the minimum, not the headline rate.
7. Contract length. Annual or multi-year commitments are common in this market. For a small operator whose fleet size may change, a monthly rolling arrangement is worth real money in flexibility — check before you sign.
8. Your data stays yours. You should be able to export raw and analysed data at any point. Tachograph records outlive software subscriptions, and the 12-month production duty follows you regardless of who you buy from.
What It Costs
Pricing in this market as of 2026 typically runs from around £20 per month for a basic analysis-only system up to £100 or more per month for broader compliance platforms, though minimum charges and contract terms vary widely between suppliers and are often where the real cost sits. Treat published per-vehicle rates as a starting point and ask directly about the minimum monthly charge and the notice period.
Set that against the alternative cost. The realistic manual figure is a few hours a month of someone's attention who understands the rules — and the risk that a reference-period breach goes unnoticed until DVSA finds it.
Making the Decision
Work through these honestly:
- Are your card and vehicle unit downloads currently inside the 28 and 90 day limits?
- Can you produce, today, evidence of analysis for the last 12 months?
- Do you know your current 17-week working time average per driver?
- Do you have a record of infringements raised and what happened next?
- If your regular checker were off for six weeks, would any of this still happen?
Two or more uncomfortable answers means the current arrangement is not meeting the duty, and the fix is a better routine or a system — not a bigger folder.
For the wider picture of what analysis is for and how it fits alongside downloads, see our tachograph analysis guide. To check where tachograph compliance sits against the rest of your O-licence obligations, the free O-Licence Compliance Health Check covers the main areas DVSA examines.