Perspectives on operations technology

Most operational businesses don't struggle because their people aren't skilled or their processes aren't sound. They struggle because the tools they use to run those processes create unnecessary friction at every turn. The enemy isn't the operation itself, it's the complexity that has been layered on top of it over time, often without anyone noticing until it becomes a serious problem.

We see this pattern repeatedly across the organisations we work with. A business starts small, adopting a tool here and a workaround there. A spreadsheet for scheduling. A separate system for tracking vehicles. Another for invoicing. A third-party app that someone installed because it solved a specific problem three years ago. Over time, the patchwork grows, and before long, running the operation requires navigating five or six different systems that don't properly communicate with each other.

The hidden cost of operational complexity

The obvious cost is time. Planners spend hours each morning manually moving information between systems. Managers wait until the end of the day to understand what actually happened on the road. Exceptions, the vehicle that broke down, the job that overran, the customer who needed rescheduling, get handled reactively, by phone, rather than through a system that could flag them in real time.

But the less obvious cost is what we call decision lag. When information is fragmented across multiple systems, the people who need to make decisions don't have access to the full picture. They make do with partial data, approximations and educated guesses. Those decisions are rarely wrong in isolation, but they accumulate. Over a week, a month, a quarter, the gap between what the operation could achieve and what it actually delivers widens steadily.

Why more software is rarely the answer

The instinct when operations aren't working well is often to add another tool. A better reporting system. A new scheduling app. An analytics dashboard. And sometimes these additions do help, briefly. But each new layer of software adds another interface to learn, another data source to reconcile, another point where information can get lost or misinterpreted.

The answer to complexity is rarely more complexity. What operational businesses actually need is consolidation without compromise - the ability to bring their core operational capabilities into one environment without losing the specific functionality they depend on.

What genuine simplicity looks like in practice

Genuine operational simplicity has a few consistent characteristics. It means a planner can see everything they need on one screen — fleet status, job schedules, driver availability, route performance — without switching between applications. It means exceptions surface automatically rather than waiting to be discovered. It means the end-of-day report writes itself rather than requiring two hours of manual data entry.

• Planning decisions are made with complete, real-time information rather than yesterday's data
• Operational exceptions are visible the moment they happen, not hours later
• The technology supports the way teams actually work, rather than forcing teams to adapt to the technology
• New team members can become productive quickly, without weeks of system training

The path forward

Reducing operational complexity isn't a technology project in the traditional sense. It's a business decision about how the organisation wants to operate, and what kind of environment it wants to create for the people doing the work every day. The technology should follow that decision, not lead it.

What we've seen consistently is that when operational businesses make the move toward a simpler, more connected environment, the benefits compound quickly. Planning gets faster. Costs go down. Customer service improves. And crucially, the team has the headspace to focus on the work rather than the systems.

Complexity is not an inevitable feature of operational life. It is a problem with a solution, and the solution is simpler than most people expect.

Count the systems your operations team uses on a typical working day. Most businesses we speak to arrive at a number somewhere between five and eight, and that's before you include the spreadsheets that sit alongside those systems filling in the gaps. Each one was adopted for a good reason. Together, they've become a significant operational liability.

Fragmented software is one of the most common and least discussed sources of operational inefficiency in logistics and field service businesses. It's not visible on a P&L. It doesn't show up in board reports. But it shapes every working day for the people running the operation, and its costs are substantial.

Where the cost lives

The direct costs of fragmented software are relatively easy to identify once you look for them. Duplicate data entry across systems. Time spent reconciling information that doesn't match between platforms. Errors introduced when something is updated in one place but not another. Manual reports built by pulling data from multiple sources into a spreadsheet each week.

In logistics and field service businesses, these costs tend to concentrate in a few specific areas. Morning planning is often the most visible: planners spending the first two hours of the day building schedules by cross-referencing vehicle availability from one system, job lists from another, and driver hours from a third. What should take 30 minutes takes most of the morning.

The integration myth

Most businesses with fragmented software have attempted integration at some point. APIs have been built. Data feeds have been established. Middleware has been introduced. And often, these integrations do help, for a while. But integrations between systems not designed to work together require ongoing maintenance. When one system updates its API, the integration breaks. When the business changes its processes, the integration no longer reflects reality. The technical debt accumulates.

True consolidation is fundamentally different from integration. It doesn't mean connecting separate systems — it means replacing them with a single environment where the data lives in one place from the start, and every part of the operation draws from the same source of truth.

What consolidation actually delivers

The operational businesses that have moved to a consolidated platform consistently report the same outcomes. Planning time drops significantly, typically by 30 to 50 percent, because planners are working with a single, complete picture rather than building one manually each day. Errors reduce because data is entered once and flows through the system rather than being re-keyed at each stage. And management visibility improves immediately, because the information is already structured and doesn't need to be compiled.

• Eliminate the time spent manually reconciling data between systems
• Reduce errors caused by information existing in multiple, inconsistent places
• Give managers real-time visibility without requiring manual report compilation
• Free planners and operators to focus on decisions rather than data management

The transition concern

The most common reason businesses delay consolidation is the concern about transition, the disruption of moving away from systems that, however imperfect, the team knows how to use. This concern is legitimate. Poorly managed transitions do cause disruption. But the risk of transition is finite. The cost of continuing with fragmented software is ongoing, compounding, and growing as the business scales.

The question isn't whether to consolidate. For most operational businesses of meaningful scale, the case is clear. The question is when, and the honest answer is that the longer the delay, the more embedded the fragmentation becomes and the harder the transition gets.

Local authorities are under pressure from every direction. Budgets are tightening. Resident expectations are rising. Scrutiny of service delivery has never been more intense. And the systems many councils use to plan, dispatch and manage their operational services were built for a different era, one where paper-based processes and end-of-week reporting were considered adequate.

Meanwhile, in the private sector, logistics and field service businesses have been quietly transforming their operations for the better part of a decade. Not through big-bang IT programmes with multi-year delivery timescales, but through practical, modular technology that addresses specific operational problems and delivers measurable results quickly. Local authorities have a lot to learn from this approach, and increasingly, the technology that drove those private sector improvements is directly applicable to public sector operational challenges.

The operational challenge councils share with logistics businesses

At the core, the operational challenge facing a council managing waste collection, highways maintenance and grounds services is structurally similar to the challenge facing a logistics business managing deliveries across multiple depots. There are vehicles to track. There are jobs to schedule and dispatch. There are field teams whose time needs to be allocated efficiently. There are performance targets to evidence and report against. And there are customers, residents, in the council's case, who expect reliability and communication.

What private sector operators got right

The logistics and field service businesses that modernised their operations most effectively shared a common approach. They started with the operational problem, not the technology. They asked: where does our planning take too long? Where do we lose visibility of what's happening in the field? Where do errors occur most often? And then they found technology that addressed those specific problems, rather than procuring large enterprise systems on the basis of specification documents and hoping the operational reality would fit.

They also prioritised usability. Technology that frontline teams can't or won't use doesn't deliver results, however sophisticated it is. The most successful implementations in the private sector involved systems that drivers, planners and dispatchers could adopt quickly, with minimal training and without requiring significant changes to how work actually happens day to day.

What local authorities can adopt right now

• Route optimisation - the same technology that saves logistics businesses 20% on fuel costs can be applied directly to waste collection and highways maintenance routes
• Live operational visibility - real-time tracking of vehicles and field teams, replacing end-of-day phone-based reporting with live dashboards accessible to managers and service leads
• Digital job management - structured job scheduling and dispatch that replaces paper-based or phone-based work allocation, with a full digital record of every task completed
• Performance evidencing - automatic reporting of service delivery data, giving service managers the evidence they need for portfolio holder briefings and public scrutiny without hours of manual compilation

The procurement advantage councils already have

One significant advantage local authorities have that is often underutilised is G-Cloud. The Crown Commercial Service's digital marketplace allows councils to procure cloud-based operational technology without the time and cost of a full tender process, enabling them to move at a pace that reflects operational urgency rather than procurement convention. For technology that has already been proven in comparable operational environments, G-Cloud procurement represents a genuine opportunity to accelerate modernisation.

The gap between public and private sector operational technology is closing. The tools exist. The procurement routes exist. What's needed now is the organisational confidence to move, and the recognition that the operational challenges councils face are not uniquely public sector problems. They are operational problems, and operational technology can solve them.

Sustainability commitments are now a boardroom priority for most organisations operating vehicle fleets. Net Zero targets have been set. Carbon reduction plans have been published. Electrification timelines have been agreed. But in the gap between these strategic commitments and the day-to-day decisions being made by planners and dispatchers, most organisations are struggling, not because they don't want to reduce their environmental impact, but because their operational technology doesn't make it easy to do so.

The sustainability conversation in fleet operations has historically been dominated by procurement decisions: which vehicles to buy, when to electrify, how to manage charging infrastructure. These decisions matter. But they represent only part of the picture. The other part, the part that drives carbon reduction in the short term, before widespread electrification is achieved, is operational. And it starts with routing.

The routing opportunity

Inefficient routing is one of the largest sources of avoidable carbon emissions in fleet operations. Vehicles travelling more miles than necessary, running with suboptimal loads, taking routes that were efficient a year ago but aren't today, these are common patterns in operations where routing decisions are made manually or using outdated optimisation logic.

AI-driven route optimisation addresses this directly. By processing real-time data on traffic, vehicle availability, job requirements, load capacity and driver hours simultaneously, modern optimisation tools can identify routing solutions that reduce total mileage significantly, typically in the range of 15 to 25 percent, without compromising service levels.

Beyond routing: the data question

Route optimisation is the most immediate operational lever for carbon reduction. But there is a broader question that many fleet operators haven't yet addressed: how do you measure your operational carbon footprint accurately, and how do you track reduction over time?

Most organisations operating fleets have some mechanism for tracking fuel consumption. Fewer have connected that consumption data to specific routes, jobs, vehicles or drivers in a way that enables meaningful analysis. And almost none have built the kind of operational data infrastructure that allows them to model the carbon impact of different routing or scheduling decisions before making them.

This is where operational technology becomes a sustainability tool in the fullest sense, not just optimising today's routes, but building the data foundation that enables evidence-based sustainability decision-making over time.

The electrification planning challenge

Fleet electrification is coming. For most operators, the question is not whether to electrify but how to sequence the transition sensibly. That sequencing decision, which vehicles to replace first, which routes are best suited to electric vehicles, where charging infrastructure is needed, requires operational data that many businesses don't currently have in a usable form.

• Which vehicles cover routes within the range of current EV technology?
• Which depot locations would benefit most from charging infrastructure investment?
• How do daily utilisation patterns vary across the fleet, and what does that mean for charge cycle management?
• What is the carbon reduction impact of electrifying specific vehicle categories first?

Connecting the strategic and the operational

The organisations making the fastest progress on fleet sustainability are those that have connected their strategic commitments to their operational technology. They're not managing sustainability as a separate workstream that runs alongside the operation, they're embedding it into the way the operation runs every day. Routing decisions factor in carbon as well as time and cost. Performance reporting includes emissions data alongside traditional KPIs. And the data generated by daily operations is being used to inform longer-term electrification and infrastructure decisions.

Net Zero targets don't deliver themselves. They require the operational infrastructure to make better decisions every day, and that infrastructure starts with the technology used to plan, dispatch and track the fleet. The sustainability conversation and the operational efficiency conversation, it turns out, are the same conversation.