Managing Tachographs in Cooperatives

In a cooperative, who is the operator?

This is the question everything else hangs on, and it is rarely asked out loud. Drivers' hours duties fall on the operator — whoever actually runs the transport and organises the work. Who that is depends on how things work in practice, not on the legal form of the group.

• If the member runs his own business, with his own licence, vehicle and planning, then downloading, retention and working time records are his. The cooperative introduces work; it does not operate the vehicles.
• If the cooperative operates and plans, it is the operator, with everything that follows.

In practice most groups sit somewhere between the two, and that is precisely where the trouble starts. Not because anyone breaches a duty, but because each side assumes the other is discharging it. Settling that question once, in writing, is worth more than any software.

What a cooperative can genuinely improve

Not the liability — that follows the role. But three things individual members rarely manage alone, and they are the real value of grouping together:

• The rhythm. A shared, announced download date each month works better with self-employed members than any individual reminder — because it arrives as an appointment rather than as supervision.
• The knowledge. Card validity, periodic inspection intervals and training deadlines explained once centrally saves every member the same research.
• The cover. Whoever is on holiday otherwise misses precisely the cycle in which the memory starts overwriting.

That sounds more modest than "collective risk management", but it is what demonstrably works. The group can supply the rhythm; the duty stays where it belongs.

In short

In a cooperative it isn't the legal form that decides, but who runs and plans the transport. Answer that once in writing and everything else — data separation, download rhythm, who chases whom — follows from it.

Where the liability actually reaches

A point underestimated in groups because it sounds like a driver matter and isn't. Enforcement does not stop at the person behind the wheel. Depending on the jurisdiction, duties and penalties can reach the operator, and in some regimes consignors, forwarders and tour operators as well.

What matters for a cooperative is the criterion rather than the list: whoever plans the work is within the circle of those addressed. A central office that allocates jobs and sets time slots cannot fall back on the members being self-employed — and a group that genuinely only introduces work should make that visible in how it operates.

Which brings the discussion back to the same place: settle who the operator is before buying anything. Every technical decision that follows — access rights, download rhythm, who chases whom — is downstream of that one answer.

Central oversight without pooling personal data

A group wants the overview; data protection demands separation. Both are achievable, but only if you distinguish what may be aggregated from what must stay with the individual member. Tachograph files are personal data about a named driver: his hours, his card number, and on newer units positions as well.

• Sensible at group level: download completion rates, outstanding deadlines, completeness of periods per member. Management indicators, from which no individual driver's week can be reconstructed.
• Stays with the member: anything that leads to a named driver.

The dividing line is easier to draw than it first appears: the centre sees where something isn't working; whoever is entitled to look sees why. "Put everything on a shared drive so anyone can get at it" is the wrong answer to both requirements at once — it opens access too far and makes it harder to show who examined what and when.

Advisory

Direct guidance on appealing sanctions.