5 myths about the G2V2 smart tachograph still tripping up Italian fleet managers

On a Telegram group of Italian fleet managers, last Wednesday, in 20 minutes I read three false statements about how the G2V2 actually works. One was dangerous, two only costly. All three were presented as facts, confirmed by other members, in the reinforcement loop that is exactly how myths consolidate. Time to set the record straight.

Three weeks into the G2V2 mandate on 2.5-3.5 t vans, informal sector channels have settled on five misconceptions. We bust them one by one, with the regulatory reference where needed and with the operational translation for fleet operators. The first fines from summer enforcement confirm that some of these myths are already the root cause of most of the penalties.

Myth 1 — “Once it’s installed, I’m covered”

False. Installing the G2V2 at an authorised workshop is the first step, not the last. To be compliant, five more things are needed:

• Company card in the firm’s name, active in the device
• Driver cards for each operator using the vehicle, valid and not expired
• Periodic data download (28 days driver, 90 days VU)
• Compliant archiving of .ddd/.v2b files for at least 1 year
• Documented operational training of the driver on the device

Without these 5 elements, the physically installed G2V2 does not protect: in case of inspection, the company is exposed both for the violation (e.g. late download) and for the autonomous organisational liability.

How to know if it’s you: try to answer these 3 questions without thinking. How many days until the next VU download on vehicle X? Where are the .ddd files of the last 12 months stored? Which driver has already completed the training course? If you can’t answer in 30 seconds, you are in myth 1.

Myth 2 — “Data stays in the tachograph, I don’t have to give it to anyone”

False. Regulation (EU) 165/2014, art. 33, sets three precise obligations:

1. Download: data must be extracted from the device periodically. Driver card within 28 days, VU memory within 90 days. Penalty for late download: €419-1,689 per vehicle or driver.
2. Retention: downloaded files must be kept for at least 12 months, in original format signed by the tachograph.
3. Production: on request by enforcement authorities, the company must produce the data in “reasonable” time — interpreted in case law as within 7 days.

The VU’s internal memory keeps 56 days of data (G2V2 regime). Beyond that, older data is overwritten: if the company hasn’t already downloaded them, they are lost. The driver card is even tighter: 28 days rolling.

Operational implication: an inspection 4 months later asking for data from 5 months earlier finds only the company archive. If the archive isn’t there, the company is in violation even if the driver had done nothing wrong during that period.

See the full G2V2 data download playbook for SMEs.

Myth 3 — “If I lose the GNSS signal, that’s a serious violation”

False, and it’s the most dangerous myth because it induces wrong behaviour.

The G2V2 records the vehicle’s position via a GNSS receiver (GPS, Galileo, GLONASS). When the signal isn’t available — tunnels, underground parks, urban shielding, receiver issues — the device records a “GNSS unavailable” anomaly event. Various circulating interpretations paint this event as a sanctionable infringement, equating it with device tampering. It is not.

Regulation (EU) 165/2014 clearly distinguishes between:

• Functional anomalies (lost GNSS, restarts, temporary power loss): recorded by the device as technical events. They do not constitute a violation of the Regulation.
• Tampering and violations: malicious alteration of the device, of the motion sensor, of the driver card. These are sanctioned, even heavily (up to €31,200 + licence withdrawal).

The conceptual error doing the rounds in informal channels is treating every technical event as a potential infraction. The legal distinction exists and has been clarified by technical sector commentators.

What to do if many GNSS events show up in reports:

1. Check whether they are geographically correlated (tunnels, underground warehouses) — normal situation.
2. If events recur on a single vehicle in open scenarios, have the receiver checked at an authorised workshop.
3. Document systemic anomalies in the fleet log to demonstrate good faith in case of inspection.

Myth 4 — “Own-account is exempt”

False/True conditional. The own-account regime is exempt from the G2V2 obligation only if driving is not the driver’s main activity (restrictive interpretation of art. 3 of Reg. (EC) 561/2006, confirmed by Italian MIT circular 9674 of 16 April 2026). The regulation and circular do not set a quantitative hourly threshold: the assessment is case by case and the burden of proof falls on the company.

In practice:

• Craftsman using the van to deliver their own production twice a week, driving marginal to the trade: typically reasonable exemption.
• Distribution shop doing daily deliveries with its own van, driver hired specifically for it: main-activity driving → G2V2 mandatory also in international own-account.

The burden of proof falls on the company: in case of inspection it must document the non-principal nature of the driving role. Job description, timesheet, employment contract, trip plans.

For grey cases see cabotage, own-account and occasional trips for vans.

Myth 5 — “With the G2V2 I don’t need fleet management any more”

False. It is the most frequent myth in conversations with fleet managers running their first procurement. The apparent logic — “if the G2V2 tracks everything, that’s enough” — confuses two different things:

• The G2V2 records: driving times, GNSS positions, events. It is a compliance black box.
• Fleet management decides and acts: it plans routes, optimises trips, manages customer ETAs, captures digital POD, computes KPIs, feeds ESG reporting.

Two different layers of the system. The G2V2 data is an input to fleet management via the ITS interface (driver consent, standardised access — see EU Data Act). One doesn’t replace the other.

We dedicated a full article to the technical and functional difference: G2V2 vs fleet telematics — what one records, what the other provides. The short read: it helps you avoid two common purchasing mistakes — buying a G2V2 with non-scalable embedded “fleet apps”, or giving up on fleet management thinking the tachograph is enough.

In short: 5 actions that close the risk

The 5 myths close down with 5 concrete operational actions, doable in 30 days:

1. Internal deadline audit: verify by this week the data-download and archiving status of every G2V2 vehicle.
2. Training programme: plan within 30 days the 8h course for drivers who haven’t done it yet (~€150/driver).
3. Procedural manual: write a 3-4 page document setting out who does what for download/archiving/anomalies. Signed by the owner.
4. Unified system: if you run more than 8 vehicles and still work in Excel, evaluate a fleet management platform that integrates G2V2 + planning.
5. Decision tree for grey cases: for vehicles at the edge of the perimeter (own-account, occasional trips, mixed regime), formalise the equipment decision.

If you want to figure out how to automate data download, audit trail and fleet reporting in a single platform aligned to the Mobility Package 2026, download the checklist or book a demo with an Optivo specialist.