Fleet Management Software for Government and Municipal Fleets
There is no such thing as a typical vehicle in a council yard. A refuse truck, a gritter, a ride-on mower, a highways inspection van and a mayoral car sit on one asset list, funded from an annual budget that is published, argued over in a committee and audited afterwards. KO Fleetz holds all of it on one register, in a form that survives being read by the public.
Operational reality
What makes government & municipal fleets different
The fleet has no common denominator
A sweeper, a gritter, a tractor with a flail arm, a pool hatchback and a van full of drainage kit. Different meters, different inspection regimes, different lifespans, different departments. Software written for a fleet of one vehicle type describes about a fifth of what is in the yard.
The budget year is a wall
Capital not spent by the closing date is lost rather than carried. Revenue overspent becomes an item on an agenda with your name next to it. The replacement decision is therefore not about when the vehicle is worn out. It is about which financial year can accommodate it.
You cannot simply buy the thing
Procurement runs through thresholds, published tenders or a framework somebody else competed. Specifying a system means writing requirements that will be scored against competitors by an evaluation panel, months before anyone drives a vehicle or logs in.
Every record is potentially public
An information request, an internal audit, a scrutiny committee or a local reporter can ask what a vehicle cost and why it was replaced. The answer has to be retrievable, consistent and boring. Data that only makes sense to the person who maintains the spreadsheet is a liability.
Seasonal assets that must work on one specific night
A gritter earns nothing for eight months, then has to start at three in the morning on the first hard frost, with a spreader that has been sitting in a corner since March. Readiness is a date in the calendar, and the failure is on the news.
The vehicles belong to departments, the workshop belongs to you
Waste owns the trucks, parks owns the mowers, and the fleet team owns the fitters who repair both while being recharged internally for the privilege. Every job is a negotiation with a colleague who has their own cost centre to protect.
The round happens regardless
A statutory collection is not a service level you can renegotiate with a customer. If the truck is off the road, another truck does two rounds, or bins stay on the pavement and the phones start. There is no commercial lever to pull.
How a council yard actually works
The workshop is the centre of gravity, and it is an internal supplier rather than a cost line. Fitters take in a refuse truck at seven, a mower at nine and a van from environmental health at eleven, and every job has to end up charged back to whichever service owns the asset. That is the part manual systems fail at, because a job card in a tray records the repair and never records the recharge, and by year end the fleet team is defending a budget for work it did for somebody else. KO Fleetz records the recharge on the same job card as the repair, so the hours a fitter spent on a waste truck or a parks mower land on that service's budget rather than on the workshop's.
Meanwhile the assets accumulate wear in units that disagree with each other. A pool car counts kilometres. A mower counts engine hours and does nothing at all for five months. A gritter counts nights out and hours with the spreader running. Scheduling maintenance off a single mileage rule across that mix produces a hydraulic failure on a machine that had barely moved and a pointless service on a car that had. KO Fleetz reads each machine on the meter that fits it — distance for the pool car, engine hours for the mower, nights out for the gritter — because the meter has to match the machine.
Then there is the annual rhythm nobody outside the public sector quite believes. Bids go in months before the money is available, capital is spent against a closing date rather than a condition assessment, and the case for replacing eleven vehicles is made to a committee of people who are not engineers and will reasonably ask why last year's eleven were not enough. That argument is won with a cost history per asset. It is lost with an opinion about reliability.
Feature mapping
Which modules matter here, and why
Not every fleet needs every module. This is what actually earns its place in this industry.
The in-house workshop repairs assets it does not own on behalf of departments that pay for the work, so a job card is simultaneously a repair record and an internal invoice. It also has to handle machines with no odometer at all, where the service interval runs on engine hours and a mower that sat in a barn all winter needs different treatment from one that cut verges every day.
One register has to describe a gully sucker and a pool car without pretending they are the same kind of thing, and it has to survive a scrutiny committee asking why a vehicle bought nine years ago is still in service. Replacement here is a business case against a capital programme with a closing date, not a total cost curve you can act on whenever it crosses.
Most councils bunker their own fuel behind a depot gate, which concentrates a large quantity of publicly funded liquid in one place with a pump that everybody's key opens. Rebated fuel for plant adds a second problem, because it is legally restricted to particular uses and the record of who drew what has to hold up when somebody asks.
The complaint is from a resident and it is specific: their road was never gritted, their bin was never emptied, a van was parked on their verge for two hours. Position history is how a council answers a member of the public, and how it answers a claim after somebody slipped on a road the treatment record says was covered.
Numbers produced here get published, quoted back at you and compared with the neighbouring authority. That raises the bar on definitions rather than on presentation: a cost per asset that a councillor can understand and an auditor can trace to a transaction is worth more than any chart, because the follow-up question is always where the figure came from. KO Fleetz builds every published number back down to the job card, the parts issue or the fuel drawing beneath it, so that question has an answer ready.
Outcomes
What changes
- Sweepers, mowers, gritters and pool cars on a single list
- One register
- Each machine metered the way it actually wears
- Hours or distance
- Every figure followable back to a job card and a transaction
- Traceable
- Seasonal readiness treated as a date, not a hope
- Before the frost
The systems a public sector fleet has to live with
The corporate finance or ERP platform owns the budget line and the ledger, and it is not negotiable, so fleet cost has to arrive there in a form the accountants already recognise. Purchasing and framework catalogues govern how parts and vehicles are bought. Works management systems for waste rounds, highways and grounds hold the job the vehicle was sent to do. Depot fuel site controllers and tank gauges report drawings at the pump. Parts distributors, external garages, HR and payroll all touch the record. Where a corporate asset register exists, fleet is one class within it rather than a rival list.
Explore integrationsFrequently asked questions
That depends on your thresholds and the routes available to you, and it is your procurement team's call rather than ours. In practice authorities reach us three ways: a direct award below threshold, a call-off from a framework that has already been competed, or an open tender we respond to like anyone else. We are comfortable with all three. What we can do early is help you write requirements that describe the yard you actually have, because specifications copied from a haulage template routinely score vendors on features no council needs and omit plant entirely.
Yes, and this is usually the first thing that breaks in fleet systems built for road vehicles. An asset can be metered on engine hours, on distance, on a cycle count or on the calendar, and the service schedule follows whichever is right for that machine. A ride-on mower coming off a winter of standing still needs attention driven by the date; a gully sucker needs attention driven by pump hours that its odometer knows nothing about. Attachments and bodies are held as assets in their own right with their own examination dates.
It can prove the vehicle was there, and that is not the same claim. Position history gives you a defensible record that a gritter travelled a route at a given time, which answers most resident complaints outright. Proving that the spreader was running and laying salt at a set rate requires the spreader controller to publish that data and to be integrated. If your machine does, the treatment record can be tied to the position. If it does not, be precise about what you are claiming, because a winter service claim is examined carefully and an overstated record is worse than none.
It means the design brief is retrievability rather than dashboards. Every cost should trace back to a job card, a parts issue or a fuel drawing, with a date and a person attached, so an auditor can follow a published figure to the transaction underneath it. It also means being deliberate about what you hold, particularly anything identifying a driver, since disclosure obligations and data protection pull in opposite directions. Your information governance team should see the retention settings before go-live, not after the first request lands.
It produces the substantiated charge; your finance system moves the money. Labour hours, parts issued and external invoices attach to the job, the job attaches to the asset, and the asset carries the service that owns it. That gives you a recharge line per department that will hold up when a colleague queries it, which they will. Posting into the general ledger is a job for the corporate finance platform through an interface, and no fleet system should be inventing journal entries behind your accountants.
By replacing an opinion with a history. The argument that fails is the one where a fleet manager says a truck is past it. The argument that works shows a named asset, its cumulative maintenance spend by year, its downtime, and what that pattern looks like against comparable units in the same yard. KO Fleetz holds all of that from the day you start recording, which is the honest catch: it is worth most in year three. Bring in whatever historic cost you can at implementation, because the case is stronger with it.
Bring the oldest vehicle in the yard and its job cards
We will rebuild its cost history the way a committee would want to see it, and you can decide whether the case makes itself.