Telematics for Small Haulage Firms: What Data to Track and What to Ignore
Telematics boxes are sold on the promise of data. The trouble for a five-truck operator is that the same system that tells you a wheel bearing is running warm will also tell you the ambient temperature in Aberdeen at 4am. Somewhere between those two facts is the handful of numbers that will actually change your week. The rest is noise that costs you attention, and attention is the scarcest thing in a small yard.
Here is a sensible way to sort them.
Start With the Money, Not the Hardware
Before you log into a dashboard, write down the three things that hurt most last quarter. For most small fleets it is fuel, unscheduled maintenance and driver hours. If a metric does not touch one of those three, it can wait.
That test kills a lot of features instantly. Tyre pressure monitoring is worth having when it feeds a weekly maintenance routine. It is not worth having if nobody reads the alerts. A report that no one acts on is worse than no report at all, because it teaches your drivers that warnings can be ignored.
The Five Numbers Worth Watching Weekly
These cover the vast majority of what a small haulage business can realistically control.
- Fuel used per mile or per kilometre, by vehicle. Not the fleet average. Compare each truck against its own last four weeks. A single vehicle drifting upward usually means a mechanical issue, a change of route, or a change of driver.
- Idling time as a share of engine hours. Idling burns fuel, wears the engine and clocks up hours you cannot bill. Track the percentage, not the raw minutes, so a busy week does not look like a bad week.
- Harsh braking and harsh acceleration events per 100 miles. These are rough proxies for how the truck is being driven, and they tend to cluster on particular routes or particular drivers. Treat them as a conversation starter, not a disciplinary tool.
- Over-revving and excessive speed banding. Look for time spent above the speed your trucks are limited to, and time spent in the highest rev band. Both are cheap to fix and expensive to ignore.
- Driver hours and break compliance. This is the one area where telematics pays for itself in avoided trouble rather than saved fuel. Keep the reports, keep them tidy, and make sure your transport manager can find them.
Five numbers. If your dashboard cannot show them on one screen, build the screen yourself in a spreadsheet once a week. Twenty minutes on a Friday beats an hour of scrolling on a Tuesday.
Where Harsh Braking Data Goes Wrong
A harsh braking event on a wet A-road at 6am is not the same as one in a depot at walking pace. Most systems flag them identically, which is why the raw event count is a poor target on its own.
Set the thresholds yourself if the platform allows it, and if it does not, interpret the numbers with context. Ask the driver what happened before you assume anything. The best fleets use these reports to spot patterns, such as a delivery point that forces an awkward reverse, rather than to hand out warnings. A delivery that causes three near-misses a week is a site problem, not a driver problem.
What to Ignore, at Least for Now
Small operators get buried by features designed for fleets of two hundred with a data analyst on the payroll.
- Live map tracking of every vehicle all day. Useful when a customer calls to ask where their load is. Not useful as a management tool. Check it when you need it.
- Second-by-second engine parameters. Coolant temperature traces and manifold pressure graphs rarely change a decision you would otherwise make.
- Driver league tables. They create resentment, encourage gaming of the numbers and tell you little that the fuel and braking trends do not.
- Detailed geofence time reports for every site. If you run the same twelve drops each week, you already know how long they take. Automate the exceptions instead.
- Anything you have not looked at in three months. Switch off the email alerts. A full inbox trains people to ignore all of it.
Making the Data Fit Your Week
The most common failure is not choosing the wrong metrics. It is choosing good ones and never looking at them.
Give the data a home in your routine. A short weekly review works well: pull the five numbers, flag anything that moved by more than a sensible margin, and decide one action per flag. That is it. One action might be booking a truck in for a check, moving a delivery slot, or having a five-minute word with a driver.
Monthly, step back and look at cost per mile across the fleet, including fuel, maintenance and tyres. Quarterly, compare your insurance renewal and any incident history against what the telematics reports showed. If the reports and your claims experience tell the same story, you are getting value. If they contradict each other, one of them is wrong.
Two Habits That Make Everything Easier
First, tell your drivers what you are measuring and why. People resist surveillance; they cooperate with a fuel bonus or a fair maintenance schedule. Second, keep the reports you would need in an audit or a customer query. Some customers and insurers ask for evidence of monitoring, and a tidy folder of monthly summaries is far more useful than a login to a system nobody understands.
If you are unsure what your operator licence or insurance policy obliges you to record, check the current guidance and take advice from a qualified transport consultant or your insurer rather than relying on a forum post.
A Short Checklist Before You Renew
When the contract comes up, ask three questions. Can I export my data easily? Can I set my own thresholds and alerts? Can I turn off what I do not use? A platform that answers yes to all three will serve a small fleet well for years. One that answers no will keep selling you dashboards instead of savings.
Pick five numbers. Review them weekly. Ignore the rest without guilt. That is the whole job, and it is more than most small operators manage.
Photo: chrissharkman / Pixabay



