From Workshop Records to Fleet Intelligence: The Next Stage of Council Fleet Management

By Dave Jones, Managing Director of Pullman Fleet Solutions

Council fleets generate a detailed record of inspections, repairs, vehicle use, and costs. Connecting that information can improve fleet availability and financial planning. It can also support better asset decisions and future AI analysis.

Which vehicles are off the road right now, why are they unavailable, and when will each one return to service?

Answering those questions typically means opening several systems, checking a spreadsheet, reading workshop emails, and chasing a service partner. That fragmented process delays decisions and can leave fleet teams working from information that is already out of date.

Your fleet produces valuable information every day. The next stage of fleet management is turning multiple data points into one reliable operational view.

This article explains which maintenance data councils should connect, which KPIs support action, how on-site maintenance improves data quality, and how reliable records strengthen cost, replacement, predictive maintenance, and AI decisions.

What is fleet data management?

Fleet data management connects each vehicle’s history and current status in one usable operational view.

For a council, that information may sit across workshop systems and telematics platforms. Further records come from suppliers, hire providers, finance systems, and fleet replacement plans.

The Local Government Association’s State of Digital Local Government report identifies data silos and inconsistent formats as common barriers across councils.

A consistent asset identifier should link every relevant record across these systems. Fleet teams can then see each vehicle’s maintenance history, current status, and emerging issues in one operational view.

What fleet maintenance data should councils track?

Councils should track information that supports roadworthiness and vehicle availability. A useful maintenance record should include:

  • Asset identity and current operating status
  • Planned maintenance dates and MOT dates
  • Driver defects and technician findings
  • Diagnosis, repair action, parts used, and labour time
  • VOR start time, delay reason, responsible party, and expected return date
  • External repair costs and warranty recovery
  • Mileage, utilisation, battery condition, and energy use
  • Planned replacement date and financing position

Each field needs an agreed source and a named owner.

Where operator licensing requirements apply, the DVSA Guide to Maintaining Roadworthiness recognises electronic maintenance systems, provided that records contain the required information and maintain a clear audit trail.

The same information can help a council understand how every asset is performing over time.

Which fleet maintenance KPIs matter most?

Councils should focus on fleet maintenance KPIs that prompt a clear action. Useful measures include:

  • Fleet availability and total VOR hours
  • Inspection completion and MOT completion
  • Average repair turnaround
  • Repeat-defect rate and first-time fix rate
  • Maintenance cost per asset and per mile
  • Scheduled work compared with unplanned repairs
  • Supplier response time and parts delays
  • Vehicle utilisation and maintenance budget variance

Every KPI needs a named owner, a review frequency, and an agreed threshold that triggers intervention.

A rising repeat-defect rate should prompt an engineering review. Increasing VOR caused by parts delays may require changes to stockholding or supplier arrangements.

The most useful dashboard is the one that helps somebody make a decision.

How can connected fleet data reduce VOR time?

Live VOR reporting should show the asset, the cause of the delay, the responsible party, the next action, and the expected return-to-service date.

That information tells fleet teams where intervention is needed. A vehicle awaiting authorisation can be escalated. A parts delay may require alternative sourcing. External repair work can be monitored against agreed timescales.

For example, if a refuse vehicle remains VOR for 24 hours because a part is awaiting approval rather than unavailable, a live dashboard can expose the approval delay and allow the fleet team to intervene before further service disruption occurs.

Service departments also gain earlier warning of availability problems. Replacement cover can be planned with a clearer view of likely return dates.

A Rapid Maintenance Unit, or RMU, can shorten the information flow by bringing maintenance closer to the fleet. Capturing repair status when work begins and updating it throughout the job gives fleet teams a more current operational view.

Pullman’s approach to on-site Vehicle Maintenance Unit management combines local maintenance capability with wider engineering support and compliance oversight.

How can an on-site RMU improve data quality?

Accurate fleet data begins where the maintenance work takes place.

Every job should use the same asset identifier, defect descriptions, status codes, and timestamps. Technicians also need a practical way to update the record as work progresses.

Shared definitions are important. Terms such as “awaiting parts” and “return to service” need one agreed meaning across the council and its suppliers.

An on-site RMU creates a controlled point for capturing this information. Maintenance follows an agreed process and updates can feed into the council’s wider systems.

By managing maintenance on-site, Pullman can help councils capture consistent workshop data at source. This provides a clearer view of current activity and creates a dependable vehicle history.

How can fleet data improve cost and replacement decisions?

Connected maintenance records reveal the cost of each asset over time. The calculation can include labour, parts, external charges, and replacement vehicle hire.

A series of individually low-cost repairs can become an expensive pattern over the asset’s life. VOR history also reveals the operational cost of downtime, including the pressure placed on replacement vehicles and service delivery.

Technicians with vehicle

Supplier performance can be measured through repair turnaround, first-time fix rates, parts delays, and invoice variance. These measures give contract managers objective evidence for performance reviews, corrective action, and future procurement decisions.

For replacement planning, age and mileage provide a starting point. Maintenance spend, VOR hours, utilisation, and condition add a fuller operational picture.

Electric vehicles create further information for lifecycle planning. Battery condition, charging behaviour, energy use, and seasonal range can be assessed against the vehicle’s actual duty cycle. This helps councils make informed decisions about deployment and replacement timing. Councils preparing for electric fleets can also explore accredited electric and hybrid vehicle training through Pullman Academy.

How do predictive maintenance and AI use fleet data?

Predictive maintenance uses historical records and live vehicle information to identify patterns that may indicate a component requires attention.

Previous inspection findings can be compared with the repair history. Telematics alerts and sensor data add a current view of vehicle condition. Engineering teams can then plan work before an emerging fault causes an unplanned VOR event.

AI can analyse larger volumes of information. It may help forecast workshop demand and parts requirements. It could also identify assets with increasing failure risk and model replacement scenarios. Read more about how connected technology and real-time operational insight are shaping Pullman’s approach to fleet maintenance.

Government guidance on preparing datasets for AI states that data must be accurate and trustworthy for AI systems to function reliably.

When maintenance records are incomplete or inconsistent, AI can analyse the data confidently while producing misleading conclusions. Statutory inspection schedules and engineering judgement must therefore remain central to every maintenance decision.

Tomorrow’s analysis may depend on how accurately today’s technician closes a job card.

Where should a council start?

Start with one operational question: which vehicles are VOR right now?

Record the asset, reason, responsible party, expected return date, VOR start time, and return-to-service time.

Once this information is dependable, expand the connected view into inspection planning, defect analysis, cost reporting, supplier performance, and asset lifecycle planning.

Pullman can help councils review their maintenance delivery and identify where connected data could improve operational visibility. Our five-question council fleet maintenance review provides a practical starting point.

My view is simple: the next stage of council fleet management begins with disciplined data capture in the workshop.

Connecting that workshop record with the council’s wider systems improves operational and asset decisions today while creating a trustworthy foundation for predictive maintenance and future AI analysis.

Councils considering their next step can contact our team to discuss where better workshop data, connected systems, and clearer maintenance oversight could improve fleet availability and decision-making.

We love talking all things fleet, from VMUs to keeping your trucks and trailers in top shape.

You can contact the team via enquiries@pullmanfleet.com

Share

Related posts

View all news