Fleet costs rarely rise for one large reason. It is usually a dozen small leaks, each of which looks trivial on its own: ten minutes of idling per shift, one empty run a week, a refuelling forty litres smaller than the card transaction, a service done five thousand kilometres late.
Telematics does not cut costs. A decision made on the data does — and that part, not the technology, determines the outcome of a rollout.
Where the money actually leaks
In a typical transport fleet the cost structure looks similar everywhere: fuel is usually 30–40%, driver wages are the second largest line, then maintenance, insurance and depreciation. Telematics has real leverage on four of them.
Fuel. Three independent sources of loss: excess consumption from driving style, idling, and shrinkage — from leaks through to siphoning. Each needs different measurement and a different response.
Idling. The most underrated line. An engine running while parked burns fuel without covering distance, and in refrigerated, construction and urban distribution fleets that can reach a low double-digit share of total consumption. It is also the fastest to change: measurement, communication and a regular report are enough.
Empty running. Unladen kilometres are cost without revenue. Telematics shows the scale; reducing it requires a change in planning, not in monitoring.
Reactive maintenance. A repair after failure costs several times more than a scheduled service, once downtime is counted. Engine hours and mileage let you move from a calendar to actual wear.
Step 1: measure the baseline before changing anything
This is the most commonly skipped stage and the most regretted one. Without a baseline, in six months there is no way to separate the effect of the rollout from seasonality, fuel price movement or a different mix of jobs.
The minimum baseline set, all obtainable from invoices and spreadsheets before installation:
- fuel cost per vehicle over twelve months,
- annual mileage per vehicle,
- number and cost of unplanned repairs,
- hours spent monthly on reporting and settlement.
The last line is often a surprise. In fleets of 30–50 vehicles, manually reconciling refuelling, mileage and routes can take several working days a month — a real cost that appears in no budget.
Step 2: three metrics to start
The platform will calculate dozens. The team will change behaviour on three:
- Consumption per 100 km within a group of comparable vehicles.
- Idle minutes per shift, per vehicle and per driver.
- Share of empty running in total kilometres.
The condition for any of this to mean anything is segmentation. Split the fleet into groups with similar duty cycles — urban, domestic, international, refrigerated, ADR — and compare only within groups. A ranking that mixes profiles will be dismissed by drivers as unfair, and they will be right.
Step 3: fuel — fastest return, most pitfalls
Fuel measurement produces the largest single effect and is also the most sensitive to configuration mistakes.
Choosing the data source. A CAN or OBD reading is sufficient in cars and light commercial vehicles. In trucks with large tanks the factory gauge is too coarse for billing, so a capacitive level sensor goes into the tank.
Calibration. An uncalibrated sensor generates false alarms, and a month of those teaches the team to ignore notifications. Calibration plus two to four weeks of observation before alerts reach the team is not optional — it is the condition for the system working at all. More on this on the fuel monitoring page.
Reconciliation against fuel cards. A 300-litre transaction against a 240-litre increase in tank level is a signal that needs explaining — sometimes a calibration error, sometimes fuel going into another tank. Automated comparison belongs in the monthly close, not in a quarterly review.
Step 4: idling — change without investment
Reducing idle time requires no hardware beyond the device already in the vehicle. It requires three things:
- measurement — minutes per shift, per vehicle,
- a threshold set separately per work type, because a reefer and an urban distribution van have different legitimate minimums,
- feedback — a weekly summary visible to drivers.
Measurement without feedback changes nothing. Feedback without a sensible threshold changes the wrong things: a reefer driver who shuts down the unit to improve their score creates a cost many times larger than the fuel saved.
Step 5: a weekly rhythm, not a quarterly report
| Day | Action | Time |
|---|---|---|
| Monday | Review KPIs and deviations from the past week | 30 min |
| Tuesday | Decisions: route corrections, driver conversations, service requests | — |
| Wednesday–Friday | Execution and follow-up | — |
Three conditions make this work: one person leading the review, one dashboard instead of twenty reports, and authority to decide without escalation. Missing the third is the most common reason rollouts stall at “we have the data”.
Step 6: from cost to profitability
Telematics stops being a cost line at the point where its data joins the system in which the company counts money. Only then can you answer:
- Which customer is profitable once empty runs to their site are counted?
- Which lane loses money at current rates?
- What does serving an order actually cost, as opposed to the quoting calculator’s version?
The simplest start is an automated export of mileage and fuel cost into the ERP — typically two to four weeks of work, with the immediate effect of removing a monthly manual summary. The sequence is covered in the article on Wialon–ERP integration.
Calculating the return honestly
Three numbers, compared after six months:
- Baseline cost — fuel, unplanned repairs, hours spent on reporting, over the twelve months before rollout.
- System cost — devices, installation, connectivity, licences, annualised. The breakdown is on our pricing page.
- The change — the same lines after six months, adjusted for external factors: fuel price movement and changes in job volume.
The third point is what separates a credible calculation from a sales deck. An 8% fall in fuel cost against a 6% fall in wholesale prices is a 2% effect from the rollout, not an 8% one.
Six mistakes that raise costs instead of cutting them
- No metric owner — a report nobody has to open will not be opened.
- Too many reports — twenty summaries produce zero decisions.
- No fleet segmentation — conclusions drawn from route differences attributed to people.
- Alerts with no reaction process — notifications landing in a filtered folder.
- Skipped baseline — no way to prove the effect, and therefore no way to defend the budget next year.
- Rollout without talking to drivers — resistance that costs more than the system.
Summary
The financial outcome of a telematics rollout is a function of process, not sensor count. Three metrics, one owner, a weekly rhythm and an honest baseline achieve more than a complete feature set used once a quarter.
To size the opportunity for your own fleet, start with a baseline measurement and a pilot on 10–20 vehicles — the step-by-step plan is in the article on GPS fleet tracking rollout.