Across fifteen years of embedded service inside cargo-owner operations — beverages, FMCG, oil and gas, cement, courier — the same five mistakes show up in nearly every fleet management programme that fails to produce the outcomes its sponsor expected. They are not exotic mistakes. They are not the result of weak intent or low budget. The teams making them are usually capable, well-funded, and aware that something is not working. They simply have the wrong diagnosis of what.
This post names the five, in the order they tend to compound. Each one is the same shape underneath: a missing operating discipline filled in with hopeful technology, or hopeful procurement, or hopeful contracting. Each one is cheap to recognise once you know what to look for. Each one is expensive to leave in place.
Mistake 1Buying the technology before deciding what to measure.
The most common starting condition is a fleet management programme whose first concrete decision was a procurement decision — a telematics platform, a fuel monitoring system, a route optimisation tool — taken before the operating team had agreed what the technology was supposed to make visible. The technology arrives. The dashboards arrive. Someone is paid to log in. And then the actual question — what decision is this dashboard meant to support, and who is meant to make it? — is asked for the first time, six months in, by an executive who has noticed the line item without noticing the outcome.
The discipline that fixes this is unfashionably simple. Before any technology is selected, the operating team writes down the ten questions the fleet ought to be able to answer at any moment — about uptime, about transporter performance, about cost, about exceptions. The technology is then chosen for its ability to answer those ten questions, in a format the relevant decision-maker can act on within the same shift. That conversation rarely happens. When it does, the procurement decision sharpens by an order of magnitude.
Mistake 2Outsourcing fleet management responsibility to the transporter.
The second mistake is a contracting mistake that looks like a sensible delegation. A cargo-owner signs a transport contract that names the transporter as responsible for vehicle uptime, driver behaviour, fuel discipline, and safety performance — and then has no independent way to verify any of it. The data sits with the transporter. The reports sit with the transporter. The investigation, when something fails, sits with the transporter.
This is structurally untenable. The cargo-owner is the party with the commercial exposure — late deliveries lose revenue, missing cargo loses inventory, accidents lose reputation — and is also the party with no operating visibility. The transporter is the party with the visibility and a different commercial incentive. Asking the transporter to grade their own performance is a category mistake, not a relationship mistake.
The fix is not to terminate the transporter relationship. The fix is to install independent visibility on the cargo-owner's side. That can be the cargo-owner's own platform, the cargo-owner's own analyst team, or — as in SALCOMMS's embedded model — a third party sitting inside the cargo-owner's premises producing the same daily evidence the transporter sees. The point is that someone other than the party being measured holds the data the measurement is built on.
Mistake 3Treating telematics as a procurement decision rather than an operating decision.
Closely related to mistake one, but distinct. Even where the right questions are asked up front, telematics is often handled inside the cargo-owner organisation as a procurement project — solicited via RFP, won by the lowest-priced compliant vendor, signed off by the function with the smallest direct stake in the outcome. The platform is delivered, the SLAs are checked, the procurement function records a win.
Meanwhile the operating team — the people who have to use the data to manage transporters — is two steps removed from the implementation. They were not in the room when device specifications were set. They were not consulted on report formats. They were not asked which exceptions matter and which are noise. They inherit the platform on the day it goes live and spend the next six months adapting their work around its limitations rather than the other way around.
The shift here is structural. Telematics belongs to operations. Procurement supports the decision; operations makes it. The signature that matters is not the head of procurement's — it is the head of supply chain's, or the COO's. When the right signature is missing, the implementation finds the gap and falls into it.
Mistake 4Producing reports that no one is required to act on.
By month four of most fleet management programmes, the reports exist. The control tower exists. The dashboards exist. People are receiving daily emails and weekly summaries. And yet — when you ask the operating team what decision they last made on the basis of one of those reports — there is often a longer pause than the answer needs.
A report that has not driven a decision in 90 days is not a report. It is a screensaver.
The discipline that fixes this is to define, for every report, the named role that owns it, the cadence on which they are required to act on it, and the meeting where that action is reviewed. Without those three things, reports drift into background noise. With them, reports become operating triggers — the artefact that opens the conversation rather than the artefact that closes it.
Most cargo-owner programmes have at least three reports they could quietly retire and at least two reports they should be producing but are not. The 15-minute reporting audit at the foot of this post is the structured way to find out which is which.
Mistake 5Measuring activity instead of outcome.
The most subtle of the five, and the most expensive over time. A programme starts measuring what is easy to measure — number of trips, kilometres driven, hours logged, devices online, alerts triggered — and treats those numbers as a proxy for fleet performance. They are not. They are activity. They tell you the system is running. They tell you nothing about whether the system is producing the outcome the business actually cares about.
The outcomes that matter to a cargo-owner are usually a short list: delivery reliability against the customer SLA, cost-per-kilometre against the budget, asset uptime against the maintenance plan, safety performance against the incident rate. Each of these is harder to measure than activity. Each of these requires the operating team to define what "on time" means, what counts in the cost-per-kilometre denominator, what counts as an incident worth reporting. The work to define them is the work that distinguishes a fleet management programme from a fleet monitoring programme.
A programme can run for two years on activity measures and still be on its way to failure. A programme that names three or four outcome measures and runs to them — even imperfectly — usually does not need a third year.
The 15-Minute Fleet Reporting Audit.
A printable worksheet that walks you through the five sections of your reporting layer — the five core reports, the audience map, the decision check, the data integrity check, and the 90-day plan to fix what is broken. Free, no account required.
Get the auditHow the five compound.
The five mistakes are listed separately, but they almost never appear separately. An organisation that has made mistake one — bought the technology before deciding what to measure — has usually also made mistake three, because the procurement function ran the implementation and the operating function inherited the result. An organisation that has made mistake two — outsourced fleet responsibility to the transporter — almost always presents with mistake four as well, because there is nothing on the cargo-owner side to act on. Mistake five — measuring activity instead of outcome — is the silent condition that makes the other four sustainable, because activity numbers always tell a flattering story.
That compounding is what makes the diagnosis hard from the inside. The leadership team sees a programme that produces dashboards, runs meetings, generates reports, and has named owners. None of the individual pieces look broken. The discipline is missing, not the activity. And missing discipline is the thing that is hardest to see from inside the operation that is missing it.
From the outside, the diagnosis is usually quick. A practitioner who has run engagements at a dozen cargo-owner operations can usually name the dominant mistake within an hour of seeing the operating reports, the transporter scorecard if one exists, and the minutes of the last three monthly review meetings. If those three artefacts cannot be produced on request — or if they are produced and read flat — the diagnosis is already most of the way made.
The root cause underneath all five.
The five mistakes look different on the surface — procurement, contracting, governance, reporting, measurement — but they share a single root cause. Each one is what happens when an operating discipline is missing and someone tries to fill the gap with a purchased object: a platform, a contract, a dashboard, a report. The purchased object is real. The discipline it replaces is not.
The remedy is not more platforms or harder contracts. The remedy is the operating discipline itself — built bottom-up across seven layers, owned by the operating function, measured against outcomes, and reviewed on a rhythm. The book this post is drawn from describes that discipline in full. The free First Look — the foreword, the introduction, Chapter 1, and the opening of the Guinness Nigeria case study — is the cleanest place to start if any of the five mistakes above match what you are seeing in your own operation.
Forty pages of the operating playbook — free.
The First Look. The foreword, the introduction, Chapter 1, the opening of the Guinness Nigeria case study, and the maturity-model framework. Enough to know whether the rest of the book is for you.