Every fleet above a handful of vehicles analyses tachograph data through software - the days of reading charts by hand are gone. But the tachograph rules do not require software; they require outcomes: downloads from driver cards every 28 days and from vehicle units every 90 days, and analysis of the information to ensure the rules have been complied with. The software is the means, and choosing it means knowing which of its features are legal necessities dressed as product features, and which are genuinely optional polish.
Start from the obligation, because it defines the specification. The rules put three demands on the operator: capture the data on the statutory rhythm, analyse it against the drivers’ hours rules, and be able to show that the analysis happened and mattered. Any analysis package worth buying therefore has to do four things well. It must get the data in - from every vehicle unit and every driver card in the fleet, on schedule, including the awkward cases: agency drivers’ cards, spare vehicles, trucks off the road for repair. It must check the data against the actual rules - driving time, breaks, daily and weekly rest, weekly and fortnightly driving limits - and produce findings a manager can act on. It must support the follow-through: debriefs issued, drivers signed, repeat patterns escalated. And it must keep the evidence, because DVSA’s interest in your analysis is satisfied by records, not recollections.
The differentiation that counts is rarely in the brochure’s headline list. Automated remote downloading heads it: a system that pulls card and VU data over the air removes the operational failure mode - the forgotten card read, the truck that is never at base on download day - and turns the 28 and 90-day limits into non-events. Completeness monitoring follows: the software should tell you which vehicles and cards missed their download window, because the gap you do not know about is the one the examiner finds. Infringement logic that matches the rules as they actually are - split breaks in the right order, reduced rest counting, weekly rest compensation - rather than a simplified approximation, because a tool that flags wrongly in either direction trains your drivers to ignore it. And audit trail integrity: debriefs, acknowledgements and escalations stored against the driver record, exportable in a form an examiner can read.
The integration question matters more each year: analysis that sits inside a wider fleet system - linking hours data to rosters, tracking and maintenance - lets the operator spot the scheduling patterns that generate infringements, not just the infringements themselves. The best use of analysis software is preventive: discovering that Tuesday’s route always produces a marginal break before Tuesday produces another one.
Price-led buying fails in predictable places. The cheapest tier often excludes remote downloading - which is the feature that most reduces the compliance workload - or caps the number of drivers, or charges extra for the working-time analysis the operator assumed was included. Proprietary lock-in is the second trap: card and VU data is yours, and the contract should let you take it with you - a supplier change should not mean losing the historical record your licence defence depends on. And the human trap is the deepest: software that produces beautiful reports nobody reads. The rules require analysis to ensure compliance, which is a management act; a dashboard no one opens is, in regulatory terms, indistinguishable from no analysis at all.
The sensible selection process inverts the sales demo. Start from your fleet’s actual failure modes: missed downloads, unread reports, agency-driver blind spots, records an examiner could not navigate. Score each package against those, in your operation, with your data - most suppliers will run a pilot, and a month of live downloads reveals more than any presentation. Check the working assumptions: how the system handles multi-manning, split rests, the out-of-scope selections the rules allow for journeys outside the assimilated rules, and drivers who mix tacho and non-tacho work. And price the whole arrangement - hardware, cards, licences, support - against the cost of the alternative, which is measured in examiner hours and public inquiry risk, not software subscriptions.
The 28 and 90-day clocks run whether or not the software is watching. The right package is the one that makes the statutory rhythm automatic, the analysis genuine, and the evidence trail effortless - because when the examiner asks how you ensure hours compliance, the honest answer should be a system, not a hope.