Fleet
Turning fault codes into work, without drowning
October 10, 2025 · 6 minute read
A telematics system will send you thousands of fault codes and alerts a month. Almost none of them get acted on, because a list nobody can triage is the same as no list. The fix is to choose a small number that always mean work, and to deliberately ignore the rest.
Start with three
Not thirty. Pick three codes or conditions where the right response is always the same, and make each one raise a job with the vehicle already attached.
- Anything that puts the vehicle into a reduced-power or limp mode
- Emissions or after-treatment faults, which get expensive quickly and rarely fix themselves
- Any condition affecting braking, steering or lights
Add the odometer and hours automatically while you are there
The least glamorous and most valuable part of a telematics connection is that it removes manual mileage entry. Accurate readings arriving on their own make usage-based servicing possible, and that is worth more than any alert.
Route by severity, not by code
Drivers and workshops do not know what a code means. Translate it before it reaches anybody: stop now, get it seen today, or add it to the next service. Three outcomes, decided once when you set the rule, not by whoever opens the message.
Watch the alerts you chose to ignore
Once a quarter, look at what the ignored alerts preceded. If a code you filtered out turns up before three breakdowns, promote it. This keeps the small list small and honest, and it is the step that never happens unless somebody diaries it.
Do not let the feed replace the driver
Telematics sees engine and system faults. It does not see a cracked mirror, a worn tyre, a loose load restraint or a fluid leak on the ground. The daily walk round remains the better detector for everything physical, and a fleet that quietly stops doing it because the boxes are fitted has traded down.
