Most transport operations directors sitting on six-figure cost overruns are not short of data. They have dashboards, KPI reports, utilisation percentages, and route summaries. The real problem is that none of that reporting tells them what to change or why the same inefficiency keeps recurring. This is the core distinction in transport operations decision making that almost every operator misses: the difference between an information problem and a decision problem. And solving the wrong one wastes both money and time.
Table of Contents
- Quick Takeaways
- What Is the Difference Between Information and Decision Problems?
- Why Transport Operators Default to More Reporting
- Where Decision Problems Hide in Fleet Operations
- The Logistics Decision Problem in Practice
- Comparing Approaches to Transport Operational Efficiency
- How to Identify Your Decision Problems Without Disrupting Operations
- Fleet Management UK: Where the Cost Leaks Actually Come From
- Frequently Asked Questions
- References
Quick Takeaways
| Key Insight | Explanation |
|---|---|
| More data does not fix a decision problem | If your routing logic or fleet allocation rules are flawed, better reporting only shows you the same mistake in higher resolution. |
| Most transport cost overruns are decision-layer failures | The waste is not caused by missing information. It is caused by persistent rules, assumptions, and planning logic that have never been challenged. |
| Reporting systems and optimisation systems are not the same | A TMS or fleet dashboard tells you what happened. A decision optimisation process tells you what to change and exactly why it will save money. |
| Route assumptions age badly | Routing rules built on traffic, demand, or load data from three years ago routinely cost UK operators tens of thousands of pounds annually in unnecessary mileage. |
| Operational disruption is not required to find decision problems | Diagnosing flawed decision logic can be done within a live operation without changing systems, stopping runs, or retraining staff. |
| Fleet underutilisation is a decision symptom, not a data gap | When vehicles run at 60 percent load consistently, that signals a fleet allocation decision problem, not a reporting deficiency. |
| The cost of inaction compounds | A decision problem that costs £2,000 per week becomes £104,000 per year. Operators who delay diagnosis pay for that delay with real money, not just inefficiency. |
What Is the Difference Between Information and Decision Problems?
An information problem is when you do not have the data you need to understand what is happening. An information problem is solved by better reporting, improved sensors, or cleaner data integration. These are real problems, but they are not the dominant cause of cost overruns in mature transport operations.
A decision problem is when you have the data, you can see the outcome, but the underlying rules, assumptions, or logic used to make operational choices are wrong or outdated. No amount of additional reporting resolves this. The decisions keep producing the same costly outcome because the decision logic itself has not changed.
In practice, the two are frequently confused. An operations director sees high fuel spend per kilometre and commissions a new reporting layer to track it more precisely. But if the root cause is that vehicles are being dispatched from the wrong depot based on a routing assumption written five years ago, the new report only shows the same mistake in more detail. The cost continues.
Why Transport Operators Default to More Reporting
The default response to underperformance in transport operations is almost always to ask for more data. This is understandable. Data requests are visible, they produce deliverables, and they give the impression of forward movement. Procurement teams can buy a reporting tool. IT teams can build dashboards. These actions feel like progress.
Decision problems are far less comfortable to diagnose because they implicate existing processes, planning assumptions, and sometimes historical decisions made by the people still in the room. Questioning whether the three-shift scheduling model still makes sense, or whether the load grouping logic should be rebuilt from scratch, requires a kind of organisational honesty that reporting upgrades conveniently avoid.
McKinsey research on operational decision quality found that organisations consistently overinvest in data collection and underinvest in improving the quality of the decisions that data is supposed to inform. Transport operations are a textbook example of this pattern.
“The goal is not to have better information about a bad decision. The goal is to make a better decision.” – A principle consistently observed in operational efficiency engagements across UK logistics operators.
Pro tip: Before commissioning any new reporting tool or dashboard, ask this question first: if this report showed us exactly what we expected, what decision would we make differently? If the answer is nothing, you have an information solution to a decision problem.
Where Decision Problems Hide in Fleet Operations
Decision problems in fleet management do not announce themselves. They embed in what feels like normal operational practice. The three most common locations are fleet allocation logic, route planning assumptions, and load grouping rules.
Fleet Allocation Logic Built on Historical Convenience
Many UK fleet operations assign vehicle types to routes or depots based on decisions made during the initial network design, sometimes decades ago. The logic made sense at the time. But as demand patterns shift, customer locations change, and vehicle specifications evolve, the original allocation logic becomes a cost leak. The data will show that certain vehicles are running low-utilisation routes consistently. The decision problem is that the allocation rule itself has never been reviewed.
Route Planning Assumptions That No Longer Reflect Reality
A common mistake is to treat route plans as infrastructure rather than assumptions. Routes built around historical traffic windows, customer delivery preferences from previous contracts, or depot catchment areas drawn years ago will generate avoidable mileage and time costs every single day they run. The reporting system will show mileage. It will not tell you that the mileage exists because the planning assumption is wrong.
Load Grouping Rules That Preserve Familiarity Over Efficiency
How loads are grouped for dispatch is a decision made at the planning stage, and it is one of the least reviewed decisions in most operations. Planners tend to group by familiarity: by customer, by geography, or by whatever grouping pattern was established during onboarding. The data consistently shows that rigid load grouping rules produce vehicles running at 55 to 70 percent of capacity when dynamic grouping logic would push that figure well above 85 percent.
The Logistics Decision Problem in Practice
Consider a distribution operation running 40 vehicles across a regional network. Their TMS produces a weekly utilisation report. Average load factor: 68 percent. The response is typically to investigate whether the reporting is accurate, whether the data inputs are correct, and whether a new planning module might surface better figures. This is the information instinct at work.
The real logistics decision problem in this scenario is the planning rule that fixes vehicle departure windows at 06:00 and 14:00 regardless of actual load volumes ready for dispatch. That rule was set to match a shift pattern that was changed 18 months ago. No one reviewed the departure logic when the shift pattern changed. Every week, vehicles depart with partial loads because the decision rule says they must leave at those times, not because the volumes demand it.
Identifying this takes observation within the live operation, not a new software licence. The fix is a decision change, not a system change. And the annual saving from that single decision correction in a 40-vehicle fleet is typically well above £100,000 when calculated across fuel, driver time, and load efficiency.
Pro tip: Map your top five recurring cost complaints against the decisions that govern them. In most cases, each complaint traces back to a single planning rule or allocation assumption that has not been reviewed in over 12 months. That is where the money is.
Comparing Approaches to Transport Operational Efficiency
Not every approach to improving transport operational efficiency addresses decision problems. The table below compares three distinct approaches by what they actually solve, how long they take, and what they cost operationally.
| Approach | What It Actually Solves | Operational Impact and Cost |
|---|---|---|
| TMS Reporting Upgrade (e.g., new dashboard or analytics module) | Information visibility. Shows existing problems with greater clarity. Does not change any decision rule or planning logic. | High cost, 3 to 12 month implementation, requires system integration and staff retraining. Does not reduce costs directly. |
| Generic Route Optimisation Software (e.g., off-the-shelf route planning tools) | Addresses routing as an isolated variable. Often improves individual route geometry but does not interrogate fleet allocation logic, load grouping rules, or planning assumptions. | Medium cost, ongoing subscription, moderate disruption. Savings depend heavily on whether the decision problems sit in routing or elsewhere. |
| Live Operational Decision Diagnosis (e.g., Flow Dynamics model) | Identifies specific decision failures across fleet allocation, routing logic, and load planning within a live operation. Surfaces realistic annual savings with no system replacement required. | 5-day hardware deployment within live operations, no disruption, no upfront fee if minimum savings threshold is not identified. Targets the decision layer directly. |
How to Identify Your Decision Problems Without Disrupting Operations
The standard objection to any operational diagnostic is that it will slow things down. This is a legitimate concern in transport, where margins are thin and schedules are tight. But the diagnosis of decision problems does not require stopping operations, replacing systems, or retraining teams. It requires observation within live conditions.
The method that produces reliable results is deploying data capture within the actual running operation, not in a simulation or a planning tool. When you observe what decisions are made in real time, by planners, dispatchers, and drivers, against what the documented rules say should happen, the gaps between intent and action reveal themselves quickly. Those gaps are almost always where the cost sits.
In practice, a five-day live observation period within a mid-size UK fleet operation is sufficient to identify the primary decision failures producing the largest cost leaks. The reason is that operational decision patterns repeat on weekly cycles. Five days captures the full decision rhythm of most operations.
What this process is not: it is not a consultancy audit that produces a 60-page report full of recommendations you may or may not implement over the next two years. It is a diagnosis of specific, named decision problems with calculable annual cost attached to each one.
Fleet Management UK: Where the Cost Leaks Actually Come From
Across fleet management UK operations, the data consistently points to three categories of decision problem that account for the majority of recoverable cost. These are not theoretical. They appear repeatedly across sectors including food distribution, parcel delivery, industrial supply, and construction logistics.
Depot Assignment Decisions Based on Outdated Network Models
When a fleet was designed around a network that has since changed, vehicles are routinely assigned to depots that are no longer the closest or most logical starting point for their routes. This adds empty running miles at the start and end of every shift. In a 30-vehicle operation, this can account for 12 to 18 percent of total fuel spend annually.
Fixed Schedule Rules That Ignore Variable Demand
Many UK operators run fixed departure schedules regardless of actual order volumes. This is a decision rule that prioritises operational simplicity over cost efficiency. The result is vehicles dispatched at low capacity on high-schedule days and customers waiting unnecessarily on high-volume days. The annual cost of this single decision pattern in medium-sized fleets routinely exceeds £80,000.
Driver Assignment Logic That Ignores Skill-Route Matching
Driver assignment is treated as a scheduling problem in most operations, matching available drivers to available vehicles. But when driver familiarity with specific routes, customer sites, or vehicle types is not factored into assignment logic, dwell times increase, fuel efficiency drops, and customer satisfaction erodes. This is a decision problem dressed up as a staffing problem.
The important thing to understand is that none of these cost leaks require a new system to fix. They require a decision change. The system you already have can execute the corrected logic. What was missing was the diagnosis that identified the decision failure in the first place.
Frequently Asked Questions
What is a decision problem in transport operations?
A decision problem is when the rules, assumptions, or logic used to make operational choices produce consistently poor outcomes, regardless of how much data you have available. In transport, this typically shows up as recurring cost overruns, low load utilisation, or excessive empty running that persists even after reporting improvements are made.
How is a decision problem different from a reporting or information problem?
An information problem is solved by getting better or more complete data. A decision problem is solved by changing the logic that governs how operational choices are made. Most transport operators have enough data. The issue is that the data feeds into flawed decision rules that have never been reviewed or challenged.
Can decision problems be identified without replacing existing transport management systems?
Yes. Decision problems exist in the planning logic, allocation rules, and scheduling assumptions that run on top of any system. Identifying them requires observation within live operations, not a system change. Once identified, the corrected decision logic can typically be implemented within existing TMS or planning tools without any system replacement.
What types of transport operations typically have the largest decision problem cost leaks?
Operations that have grown through acquisition, changed their network without reviewing their planning rules, or have planning teams that have been in place for five or more years without external challenge tend to carry the largest decision problem cost leaks. Regional distribution, multi-depot fleets, and operations with mixed vehicle types are the most common profiles.
How long does it take to identify decision problems in a live fleet operation?
In most medium to large UK fleet operations, five days of live operational observation is sufficient to identify the primary decision failures and calculate their annual cost impact. This is because operational decision patterns repeat on weekly cycles, so a full working week captures the complete decision rhythm of the operation.
Why do transport operators keep investing in reporting tools when the problem is in decision logic?
Reporting tools are easier to justify, easier to procure, and produce visible deliverables quickly. Decision problem diagnosis requires questioning existing processes and sometimes the judgement of experienced staff, which creates internal friction. The reporting investment feels safer even when it does not address the actual source of cost overruns.
What is a realistic annual saving from fixing a decision problem in a UK fleet operation?
The figure varies by fleet size and sector, but in practice, a single corrected decision rule in a 20 to 50 vehicle operation commonly produces annual savings of £80,000 to £200,000 when the impact on fuel, driver hours, vehicle wear, and load efficiency is calculated together. Operations with multiple uncorrected decision problems compound those savings significantly.
If you are currently investing in reporting upgrades while the same cost overruns persist quarter after quarter, we would be interested to hear what your experience has been and whether the distinction between decision problems and information problems resonates with what you are seeing in your own operation.
We would love your feedback and any insights you would share with others. What perspective would you add?
References
- McKinsey and Company research on operational decision quality and how organisations misallocate improvement investment
- UK Department for Transport official statistics and guidance on fleet efficiency and transport cost benchmarks
- Statista data on logistics and fleet management cost benchmarks across UK and European transport sectors
- Forbes analysis of operational efficiency failures in logistics and supply chain decision making
- Ahrefs blog resource for understanding how transport and logistics audiences search for operational efficiency solutions online