It's quarter past seven. The job is booked, the customer is expecting someone, and the driver has just been told the van cannot go out because the MOT ran out last Thursday. Nobody knew. It was not on anyone's list, because it was on everyone's list.
That morning is the expensive one. You lose the job, you lose the driver's day, and if the van goes out anyway you have quietly moved from an operational problem to an insurance and compliance one.
The frustrating part is that none of it was a surprise in any real sense. The expiry date existed weeks ago. It just was not in front of anybody.
Why the spreadsheet stops working
Almost every fleet under about fifty vehicles is managed the same way: a spreadsheet, and somebody who is good at remembering.
That works fine at four vehicles. At forty it does not fail loudly, it fails quietly. The person who kept it up to date changes role, or has a busy fortnight, and the checking simply stops happening. There is no alarm, because nothing broke. The spreadsheet still opens. It is just gradually less true than it was.
The other reason it stops is that it is nobody's actual job. It sits between the operations manager, the office, and whoever happens to drive the van, and work in that gap gets done until the week it doesn't.
The information is already published
Here is the part most owners are surprised by: you do not need to check any of this by hand, and you do not need anyone to send you anything.
The DVLA publishes the current tax and MOT position for any UK registration. Give it a number plate and it tells you whether the vehicle is taxed, when that runs out, and when the MOT expires. It is authoritative, because it is the same record the enforcement side is working from.
Which means the entire fleet can be checked automatically, every morning, before anybody arrives. Forty vehicles or four hundred, it makes no difference, and no member of staff spends a minute on it.
The important design decision is what happens next, and this is where most systems go wrong. Checking is not the useful bit. Being told is the useful bit. A dashboard you have to remember to open is the spreadsheet again with better styling. What actually changes the outcome is a message that lands in somebody's inbox saying these three vehicles have something expiring in the next sixty days, while there is still time to book them in.
Sixty days matters more than it sounds. It is the difference between booking an MOT when it suits the workload and finding a slot on the day the van is already off the road.
The bit fleet owners do not expect: it also affects your tax bill
The same lookup returns each vehicle's CO2 emissions figure. That sounds like an environmental statistic and it is actually a financial one, because CO2 is what drives the company car benefit bands used for P11D reporting.
Two things fall out of that, and both are worth real money.
The first is that your benefit reporting is being calculated from the same authoritative figure the taxman is working from, rather than from whatever somebody typed in when the vehicle was bought. Transposed or guessed CO2 figures are a common and completely invisible source of error, because nothing about a wrong number looks wrong.
The second is more useful day to day. When you are choosing a replacement vehicle, you can see the tax consequence of that choice before you order it, rather than discovering it in the following year's reporting. Two vans at a similar price can sit in noticeably different bands, and that difference persists for as long as the vehicle is on the fleet.
What this will not do for you
We would rather be straight about the limits, because a system that quietly does less than you assumed is worse than no system.
- It does not know about your insurance. Nobody publishes that against a registration. Insurance renewal dates have to come from your own records, so they need to be entered once and then tracked alongside everything else.
- It is the current position, not the history. You get the MOT expiry date. Past advisories, the mileage trail, and what the tester actually flagged last time come from a separate service with its own access process, and are worth adding only if you will genuinely act on them.
- It does not check driving licences. Licence entitlement, penalty points and disqualifications are a completely separate scheme, with the driver's consent involved. Do not assume a compliant fleet means compliant drivers.
- It only knows about vehicles you told it about. The van bought last month and never added to the list is invisible, and so is the director's own car being used for work. That second one catches people out constantly.
The other half of "off the road"
Expiry dates are the predictable half. The unpredictable half is the vehicle that was perfectly legal yesterday and has a cracked mirror, a brake light out or a tyre below the limit this morning.
The daily walkaround check exists for exactly this, and for most operators it is a legal requirement rather than good practice. In our experience it is also the single most commonly fudged piece of paperwork in a fleet, because a paper pad in a cab either gets filled in at the end of the week from memory or gets lost.
Done properly, the driver works through the check on a phone before setting off, a defect is raised the moment it is found rather than at the end of the shift, and anything serious enough marks the vehicle off the road automatically so it cannot be allocated to a job by somebody who did not know. The record is kept for as long as it needs to be kept, which matters on the day somebody asks to see it.
The commercial argument is simpler than the compliance one. A defect found at half past seven is an inconvenience you can plan around. The same defect found at the roadside is a vehicle, a driver and a customer all lost at once.
Where to start
If you do nothing else, get the registrations into one place and get something checking them daily against the DVLA. That single step removes the most expensive version of this problem, and it does not require anybody to change how they work.
We build this into blu::vehicles, the fleet part of our platform, which refreshes the whole fleet against the DVLA every morning and sends one digest rather than forty notifications. The underlying data comes from the DVLA Vehicle Enquiry Service, which we integrate for clients directly as well.
If you are currently finding out about expiries on the morning they bite, get in touch and we will show you what your own fleet looks like.