Tachograph compliance basics for GB goods vehicle operators

Tachograph compliance begins with a scope decision for each vehicle and journey. If the assimilated or AETR drivers' hours rules apply, the driver generally needs an approved tachograph, accurate activity records and the records required at the roadside. The operator needs a system to download, retain and check the data, act on infringements, maintain the equipment and train drivers. A dashboard or filing system cannot make an incorrect driving record compliant after the event. This guide is for goods vehicle operations based in England, Scotland and Wales; Northern Ireland and cross-border journeys need their own rule check.

The primary reference is the Driver and Vehicle Standards Agency's current drivers' hours and tachographs guide for goods vehicles. It was updated on 1 July 2026 and explains how DVSA currently applies the rules. Use its scope section, tachograph section and operator responsibilities together. Vehicle mass, construction, use, route and exemptions all matter. This page is an operational introduction, not a substitute for checking a marginal vehicle or journey against the full guide and applicable law.

1. Decide which hours regime applies before deciding what to record

For most goods vehicles with a maximum permissible mass, including trailer or semi-trailer, over 3.5 tonnes, assimilated drivers' hours rules normally apply, subject to exemptions and derogations. A vehicle does not escape those rules merely because it is registered or described as a van. From 1 July 2026, certain goods vehicles over 2.5 tonnes used on international transport operations for hire or reward also come into scope. The current DVSA guide sets out the conditions, including journeys and own-account distinctions. A domestic van under the threshold should not be labelled tachograph-mandatory just because the business also operates HGVs. Conversely, a qualifying international light-goods journey should not be treated as an ordinary domestic van journey.

AETR rules can apply on certain international journeys outside the assimilated regime. Great Britain domestic drivers' hours rules cover some operations outside assimilated or AETR scope; their record requirements differ. Passenger vehicles have a separate DVSA guide. Exemptions and mixed-rule weeks complicate the answer, so document why each vehicle and service is classified as it is. Include trailer weight, route, carriage purpose and the specific exception relied upon. Review the classification whenever a vehicle, trailer, route or business activity changes. Read the DVSA assimilated and AETR chapter and the GB domestic chapter before setting a blanket fleet policy.

An example: a 3.2-tonne permissible-mass goods vehicle used only for UK deliveries is not automatically required to have a tachograph under the assimilated regime. The same vehicle undertaking qualifying UK–EU hire-or-reward journeys after 1 July 2026 may be in scope. Its operator must assess the precise journey, vehicle and any exemption; the weight on the vehicle's own paperwork and any trailer cannot be guessed from a marketing name such as “3.5-tonne van”.

2. Identify the right tachograph for the vehicle and work

DVSA distinguishes analogue, digital, smart 1, transitional smart 2 and full smart 2 units. Which type is acceptable depends on registration date and whether the vehicle operates internationally. A domestic-only vehicle may retain its original compliant equipment in circumstances described by DVSA; the retrofit deadlines for international work are different. Since 24 December 2025, newly registered goods vehicles requiring a tachograph must have a full smart 2 unit. Since 1 July 2026, the DVSA guide requires full smart 2 in the over-2.5-tonne light-goods vehicles it identifies for international hire-or-reward journeys, with a stated own-account qualification. Do not use a generic “all vans need smart 2” rule.

Keep a vehicle-level equipment record showing type, calibration and sealing evidence, due checks, faults, repairs and any replacement decision. A new route can change the fitting requirement. A faulty device should be handled under the DVSA fault procedure rather than by quietly continuing with incomplete data. For commercial decisions about a retrofit or exception, get a competent tachograph specialist and, if necessary, legal advice. The DVSA tachograph chapter is the controlling operational source.

3. Make a complete daily activity record

When driving an in-scope vehicle with a digital or smart tachograph, a driver normally inserts their own valid driver card before moving and selects the correct activity modes throughout the duty period. The device records driving automatically, but it cannot infer every period of loading, other work, availability, break or rest. A driver who starts work in a yard, changes vehicles, works for another employer or leaves the vehicle may need a manual entry. The DVSA guide describes the acceptable forms for entries and corrections. An ordinary diary or timesheet is not a replacement for a legally required tachograph record.

The driver should check the device's calibration indication, card insertion, time display and available print roll. A digital unit's stored time uses UTC; the display can differ from British Summer Time. At the beginning and end of daily work, record the required country information. Border-crossing entries depend on the unit and journey. Use the correct mode for other work, availability, break and rest; a stationary vehicle is not automatically a legal break. If a wrong mode has been recorded, make the correction and reason in the way DVSA prescribes rather than deleting or obscuring the original evidence.

If a card is forgotten, driving an in-scope digital-tachograph vehicle without it is not made lawful by keeping handwritten notes. DVSA has a narrow procedure for a card that is lost, stolen, damaged or malfunctioning; it includes printouts, identification, notification and replacement deadlines. Apply the actual procedure to the facts. Keep the card and printouts available for roadside production. The current guide distinguishes a 28-day preceding-record period for certain AETR or domestic journeys from 56 days for international journeys to or from an EU member state. Do not publish a universal “28 days” statement for every route.

4. Understand drivers' hours without mistaking the tachograph for a scheduler

The tachograph creates evidence; it does not decide whether the planned job fits the legal limits. Under the assimilated rules, the familiar driving break is 45 minutes after no more than 4.5 hours of driving, or a qualifying 15 minutes followed by 30 minutes. The general daily driving limit is 9 hours, with a permitted extension to 10 hours twice in a fixed week. Daily and weekly rest, weekly driving, fortnightly driving and working-time requirements also matter. GB domestic and AETR duties have their own details. The DVSA hours chapter supplies the full conditions and exceptions.

A manager should plan routes, loading windows and handovers with these constraints in mind. For example, scheduling a four-hour outbound drive, two hours loading and another four-hour drive without checking the driving break and working-time position creates a predictable infringement risk. Loading is usually work, not a rest period. A delayed job is not a standing permission to exceed hours; the limited unforeseen-events provisions have specific conditions and record requirements. Record and investigate the reasons for recurring violations rather than telling drivers to “make up time”.

5. Download, protect and examine the evidence

DVSA's operator responsibilities chapter requires operators to download vehicle-unit data at least every 90 calendar days and driver-card data at least every 28 calendar days, with additional trigger downloads in circumstances such as a driver leaving or a vehicle changing control. These are maximum routine intervals, not a reason to wait until a card is full or a sale is complete. Keep a schedule that still works when the vehicle is remote, a driver is on leave or an agency driver leaves suddenly.

The operator must make regular checks of charts, manual records and digital data and be able to produce records to enforcement officers for 12 months. A file downloaded on time but never reviewed is an incomplete compliance process. Assign someone competent to analyse exceptions, document questions to the driver, distinguish data faults from actual infringements and record corrective action. A single late break may need explanation and training; repeated late breaks on the same route may demand a new schedule. Keep original data intact, control access and make backups so that a system failure does not destroy the evidence.

Roadworthiness maintenance has different record rules. Do not conflate the DVSA tachograph retention period with the maintenance-record period in the Guide to Maintaining Roadworthiness. If your internal record policy uses a longer period for lawful business reasons, state that separately from the tachograph minimum and apply appropriate privacy controls.

6. Put responsibility on both the driver and operator

The driver operates the unit, card and mode controls correctly and reports faults. The operator equips the vehicle correctly, sets a workable schedule, trains and instructs drivers, collects and checks records, responds to breaches, and keeps auditable evidence. A subcontracted or agency driver still needs a clear handoff: who gives the vehicle, who downloads the card, who receives charts or printouts, and how an infringement is escalated. DVSA lists the operator's duties explicitly; a generic clause saying “driver responsible for all tachographs” is inadequate.

A practical ownership table can be short:

Test the process with one vehicle and one driver: can you retrieve the right evidence quickly, explain a manual entry, identify the last card download, find the analysis and show what happened after an infringement? If the answer depends on one person's inbox, build a proper handover before scale makes the gap harder to see.

7. Common failures and a monthly manager review

Common weaknesses include an unrecorded vehicle change, wrong activity mode, treating loading as rest, missing manual entries, assuming every domestic van is exempt, using an old tachograph on a route that needs smart 2, missing a leaving driver's card download, failing to retrieve remote-vehicle data, and retaining a pile of downloads without analysis. A manager's monthly review should sample at least one record from each operating pattern, check overdue downloads, investigate repeated exceptions and confirm that fault or repair records close the loop. The review frequency and sample size should reflect fleet risk; the law does not prescribe this exact monthly checklist.

Ask six questions: (1) Are scope decisions current? (2) Are every vehicle's equipment and calibration status known? (3) Were card and vehicle-unit data downloaded within the applicable windows? (4) Were data and manual records checked and exceptions resolved? (5) Can the records be produced for the required period? (6) Have routes, drivers or operating conditions changed since the last review? Record decisions, owner and due date. Where a rule is uncertain, consult the current DVSA chapter and a qualified adviser rather than embedding a guess in a permanent workflow.

Where Complys fits

Complys's HGV and operator compliance page describes a launching vehicle and operator record platform and lists tachograph-related record management among planned launch capabilities. It does not establish a currently live tachograph analysis engine, automatic legal-hours calculation, remote card download or DVSA accreditation. Its fleet page likewise labels vehicle features as launching and some advanced features as planned. A business evaluating Complys should ask for a demonstration of the exact available workflow and any relevant integrations before relying on it for a statutory process. Until capability is verified, retain a separate competent tachograph analysis and download process.

For adjacent tasks, keep tachograph evidence linked to driver, vehicle and operator records but preserve each control's own rules. The Complys HGV page is a product exploration route, while this guide owns the practical tachograph-basics intent. A vehicle walkaround check is an adjacent roadworthiness task, not a tachograph analysis substitute.

Questions operators often ask

Does every goods vehicle need a tachograph? No. Check maximum permissible mass with trailers, journey, use and exemptions against the DVSA guide. The post-July-2026 international light-goods rules are a particular reason to revisit an old van policy.

Can a driver use a paper log if they forget their card? Not simply because it was forgotten. The limited lost, stolen or faulty-card procedure is separate. Follow the DVSA instructions and investigate the circumstances.

Is downloading every 28 and 90 days enough? No. Trigger events may call for earlier downloads, and the operator must also check and retain the data, act on breaches and make records available.

Does tachograph data replace working-time or roadworthiness management? No. The regimes interact but have separate duties and evidence. A fleet system can organise records; management still has to understand the applicable rules and verify compliance.

Source, claim and writer-side QA register

Owner and cannibalisation: Search of the current live .co.uk estate found broad transport and HGV product pages and a transport operator overview but no dedicated tachograph-basics owner. This guide is limited to tachograph scope, record use and operator workflow; the product page keeps commercial feature intent and the broader transport guide keeps operator-licence overview intent. Recheck current repository before integration.

Internal-link decisions: HGV product page is the commercial next step; fleet page gives mixed-fleet context; DVSA pages carry the legal detail. Walkaround tool is an adjacent practical task. Verify exact route at integration. No invented pricing, live features or integrations.

Writer-side QA: Direct answer, GB jurisdiction, scope distinctions, dates, daily process, operator responsibilities, common errors, examples, sources, product boundary, links, metadata and CTA checked. READY means completed copy for independent QA, not permission to publish. Publication-day DVSA and Complys checks and whole-host review remain open.