The dates that ground a truck are not the ones in your service plan

The vehicle is fine. The driver is rested and rostered, the load is booked, the customer is expecting it at eleven. And the truck does not go, because a date passed three weeks ago and nobody was looking at it.

This is not a maintenance failure. Nothing is worn, nothing is broken, no warning lamp came on. It is an administrative failure with an operational consequence, which is the most frustrating kind: the fix would have taken one phone call at the right moment, and instead it takes a cancelled run, an apology and a workshop slot at whatever notice you can get.

Fleets lose days to this every year, and it is not because nobody cares. It is because the dates that can stop a vehicle are set by four or five different rulebooks, renewed by four or five different parties, recorded on four or five different bits of paper, and each has its own clock.

Four clocks, none of them yours

Start by separating them, because they behave differently.

Roadworthiness testing. Under Directive 2014/45/EU, vehicles in categories M2, M3, N2, N3, O3 and O4 — buses, trucks over 3.5 tonnes and their larger trailers — are tested one year after first registration and annually thereafter. That is the EU floor; the test itself is run under national law, which can ask for more. It is the date most fleets do track, because it is the one that feels official.

Tachograph inspection. Under Regulation (EU) 165/2014, the tachograph must be inspected by an approved workshop at least every two years. Two years is an awkward interval: long enough that it never becomes routine, and decoupled from the annual test, so the two dates drift apart and the second one is the one that gets forgotten.

ADR driver training certificates. Valid five years, and the renewal rule has a trap in it that costs drivers time. The certificate is renewed if the driver has passed a refresher examination in the twelve months before the expiry date, and the new five years then run from that expiry date. Sit the refresher earlier than that window and the new certificate runs from the exam date instead — you have paid for a course and thrown away the months you were early by. Renewing “in good time” is exactly the wrong instinct here.

Driver CPC. Thirty-five hours of periodic training every five years, taken in blocks of at least seven hours. Unlike the others it is not one appointment you either kept or missed; it is a balance you draw down, which means it can be quietly on track for four years and impossible to finish in the fifth.

Around those sit the dates that are yours rather than the regulator’s: insurance renewal, ATP certification for temperature-controlled bodies, tail lift and crane examinations, driver licence expiry, permits. Different authority, same shape of problem.

Some of these refuse; others only warn

This is the distinction worth building your process around, and it is not the same as “important” versus “unimportant”.

A lapsed roadworthiness test or tachograph inspection is a hard stop. The vehicle does not become slightly less compliant; it becomes a vehicle you cannot legally dispatch, and if it goes anyway the exposure is a roadside check, a penalty, and a conversation with an insurer who now has an opinion about the claim. There is no version of this that you manage by being careful on the day.

A lapsed ADR certificate is a stop for that driver on that kind of load and fine for everything else — a scheduling constraint rather than a grounded vehicle. An insurance renewal that slips is a commercial and contractual problem before it is anything else. An ATP certificate that has run out matters enormously on temperature-controlled work and not at all on dry freight.

So a useful register does not just hold dates. It holds, per date, what happens when it passes: refuse to dispatch this vehicle, refuse this driver for ADR loads, tell someone. Treat all of them as reminders and the hard stops get lost among the soft ones. Treat all of them as blockers and people start overriding the system, which is worse, because then the blocks that matter are being overridden too.

The event is not the expiry — it is the last day you could act

A calendar that tells you a certificate expired yesterday has told you something you can no longer use. Every one of these dates has a lead time in front of it: the test station’s next slot, the tachograph workshop’s next appointment, a refresher course that runs monthly and is full, an insurer who needs documents. That lead time is knowable — it is in your own history of booking these things — and it is what turns a date into a task.

Set the alarm at expiry minus lead time and the alert becomes actionable: book this now, or you will be short. Set it at expiry and you have built a system that reports failures it could have prevented.

The second half of the same argument: the alert needs a person on it. “The office” does not book anything. A reminder addressed to everyone is addressed to nobody, and the failure mode is not that people ignore it — it is that each person reasonably assumes another one is dealing with it. One named owner per date, and a second reminder that escalates to someone else if the first went unanswered.

Two registers that have to agree on one day

The other structural trap: vehicle dates and driver dates almost always live in different places. Vehicle compliance sits with the workshop or the fleet office. Driver qualifications sit with whoever handles payroll and training.

A run needs both valid on the same day, for the same job. An ADR consignment needs a certified driver and, depending on what it is, an appropriately equipped vehicle; a temperature-controlled load needs a driver who is available and a body whose ATP certificate has not run out. When those two lists are maintained separately, nobody is checking the combination — and the combination is what the run actually depends on.

The check that matters is therefore not a monthly report. It is at the moment of assignment, when this driver is put on this vehicle for this load, and it has to consult both registers at once.

Keep it boring

None of this needs to be sophisticated. A register with an owner per row, a lead time per date type, an alert that names a person, and a hard check at dispatch will out-perform anything more elaborate, because the failure mode here is never analytical. Nobody misjudges a compliance date. They simply never see it at the moment when seeing it would have mattered.

There is a fair objection: a system that refuses to dispatch is a system that can stop your day over a data-entry mistake. That is real, and the answer is not to soften the refusal but to make the date easy to correct and obvious when it is wrong — a certificate that expires in 2019 should be visible as a bad record long before someone tries to dispatch against it. A block you can see coming for a month is not the same kind of event as one that lands at seven in the morning.

The measure of whether you have solved this is not that the list is complete. It is that nobody in the office can remember the last time a vehicle was surprised by a date.

Where navichain fits

navichain keeps trucks, trailers and equipment with their specs, documents and compliance dates in one place, and it does the enforcing rather than the reminding: roadworthiness and tachograph expiry stop a run, while insurance and ATP raise an alert — the distinction above, applied where a vehicle is assigned rather than in a monthly review. A failed inspection grounds the vehicle and a critical defect keeps it grounded, and maintenance due on distance or on the calendar sits in the same view as the statutory dates, which we have written about separately. All of it is on every plan — you pay for scale, not capabilities — from 995 kr a month, billed monthly with no lock-in. The platform page has the detail, and pricing is public.