Improve Fleet Utilization Before You Buy Another Vehicle
Depreciation, finance, insurance and licensing accrue whether a vehicle works or sits. KO Fleetz measures what each asset actually did with its available hours, and separates the standby you genuinely need from the excess you are paying for out of habit.
Fleet and logistics operators run KO Fleetz in production
A parked asset is not a saved cost. It is a cost with nothing to show.
Fixed costs do not pause. The finance payment, the insurance, the licensing and the depreciation all accrue on a Tuesday when the van does forty drops and on a Wednesday when it does nothing at all. That is the whole mechanism, and it is unusual among fleet cost problems in that nothing is being wasted, stolen or burned. Money is simply being spent to own capacity that produced no work. There is no event to detect, which is precisely why it persists: waste with a signature gets found, and waste that consists of an absence does not. KO Fleetz prices that absence directly, accruing each asset's fixed costs against the days it produced no work, so capacity with nothing to show finally carries a number.
Under-utilisation compounds quietly in every direction. A branch that needed six vehicles three years ago still has six, because nobody has ever been asked to hand one back and handing one back is a loss of local flexibility with no local upside. Vehicles assigned to named individuals sit idle whenever that person is on leave, sick, in a meeting or on a rest day, and an assigned vehicle is far harder to reclaim than an unassigned one because it has become somebody's. Meanwhile another depot forty kilometres away hires in cover at short notice at daily rates. Both facts are true at once, in the same company, in the same week. Then peak demand arrives, everyone points at the peak, and the fleet grows to meet a week that happens twice a year and is paid for on all fifty-two.
The trap is that utilisation feels like an obvious metric and is not. Vehicles in use over vehicles owned is easy to compute and tells you almost nothing, because it treats an hour of standby cover on a critical route and an hour of a van sitting behind a workshop as the same hour. Establish your own position with the Fleet Utilization Calculator, then check whether the vehicles that do move are moving with anything in them using the Payload Utilization Calculator. A fleet can be busy and empty at the same time.
Why nobody can prove the fleet is too big
Ask how many vehicles a depot needs and you will get a defensible answer from a person who genuinely believes it. It will be based on the worst week they remember, the job that went wrong when cover was short, and an entirely reasonable preference for not being the manager who caused a missed delivery to save a small standing cost. The incentives here are asymmetric and everyone knows it. Nobody has ever been disciplined for having a spare van, and people have absolutely been disciplined for not having one. Without measurement that asymmetry decides fleet size, and it only ever decides upward.
The data that would settle it does not exist in a usable form. Keys are signed out on a clipboard, or not. Booking runs through a shared calendar somebody stopped maintaining. Odometer readings are captured at service intervals months apart, which tells you a vehicle covered some distance across a quarter but nothing about whether it did so on nine days or on ninety. And the vehicle that never moves is the one least likely to generate any record at all, because records are generated by activity. The asset costing you the most for the least is, structurally, the one your paperwork is quietest about. KO Fleetz inverts that silence: because its record of use comes from the telematics feed rather than from activity someone logged, the vehicle that never moves is exactly the one it can point to.
- Vehicles in use over vehicles owned counts a van doing one drop and a van doing forty as identical, so the metric everyone starts with is the one that hides the problem.
- Utilisation is a time question and manual records are distance records. Kilometres between services cannot tell you how many days the asset sat.
- Assigned vehicles are measured by whether the person is at work, not whether the vehicle is needed, and no clipboard captures that distinction.
- The unused asset produces no paperwork by definition. It is invisible to any system that only records activity.
- Peak demand is remembered vividly and off-peak troughs are not, so fleet size gets set by anecdote from the worst week of the year.
- Hire-in spend sits in a different budget line from vehicle ownership, so one depot renting while another idles is arithmetically invisible to both.
How KO Fleetz resolves this
The KO Fleetz modules that fix it
Improve Fleet Utilization is not one feature — it is a few KO Fleetz modules working off the same records. These are the ones that carry it.
The workflow
Measure the hours, classify the idleness, then decide
Step 1: Establish available hours honestly
Availability starts from the working pattern that actually applies, minus workshop time and statutory off-road periods. Measuring against a notional round-the-clock week makes every asset look terrible and gives you a number nobody will act on.
Step 2: Measure productive use, not movement
Ignition hours, distance, trips completed and payload carried arrive from the telematics feed. A vehicle that moved is not automatically a vehicle that worked, and the difference between those two is where the finding usually sits.
Step 3: Classify why each idle hour happened
Idleness splits three ways: standby the operation genuinely requires, structural gaps where work exists but coverage does not reach it, and plain excess. Only the third is a fleet size question, and conflating them is how right-sizing programmes fail.
Step 4: Pool before you sell
Vehicles assigned to tasks rather than to people can absorb each other's troughs. Shifting from assigned to pooled is reversible in a week; disposing of an asset is not, so it is the cheaper experiment to run first.
Step 5: Right-size on the trough, cover the peak
Own the capacity your ordinary weeks require and meet genuine peaks with short-term hire or reallocation. Sizing a permanent fleet to an exceptional week means paying for that week all year.
What you use
The capabilities that do the work
Drawn from across the platform — this problem is not solved by one module.
Time-based utilisation per asset
KO Fleetz measures productive hours against realistically available hours for every vehicle, the only view that exposes the asset covering distance rarely but expensively.
Idle classification
Separates required standby from coverage gaps and true excess, so a right-sizing conversation starts from three lists rather than one contested number.
Payload and capacity utilisation
Weight or volume carried against what the vehicle could have carried, exposing a fleet that runs constantly and still moves air.
Pool booking and assignment
Vehicles allocate to jobs rather than to individuals, with booking, handover and return recorded, which makes reclaiming a vehicle a process instead of an argument.
Cross-depot visibility
Surfaces the branch hiring in cover while a comparable asset sits unused nearby, a pattern that is obvious on one screen and invisible across two budget lines.
Dormant asset alerts
KO Fleetz flags vehicles that have recorded no productive work for a defined period, catching the asset no report mentions because it generates no activity to report.
Demand pattern analysis
Shows utilisation by day, week and season, distinguishing a genuine recurring peak from the one memorable week that has been sizing the fleet ever since.
Standing cost per idle day
Prices each non-earning day using that asset's own fixed costs, converting a utilisation percentage into a figure a finance director will engage with.
In the product
What this looks like in KO Fleetz
What changes
The difference it makes
- A non-earning day carries the asset's own fixed cost
- Absence priced
- Standby, coverage gap and pure excess kept apart
- Idleness sorted
- The van that never moves is the one it points to
- Dormant surfaced
- Own the ordinary week, hire the twice-a-year spike
- Trough, not peak
How you will know it worked
Measure these
We publish no savings figure for your fleet, because we have not measured your fleet. These are the metrics that will move if this works.
| Metric | How to measure it |
|---|---|
| Time utilisation per vehicle | Productive hours divided by realistically available hours, per asset and per class. Report the distribution, never the fleet mean. The mean hides both the asset doing nothing and the one running so hard it is about to fail. |
| Idle hours split by classification | Required standby, structural coverage gap and true excess, tracked separately. If this ratio is not measured, a right-sizing programme will eventually cut standby, cause a service failure, and lose its mandate. |
| Dormant asset count | Vehicles with no productive work over a defined window, typically thirty days. Investigate each one individually. Reasons range from a genuine seasonal reserve to a vehicle nobody remembers owning. |
| Payload utilisation on completed trips | Weight or volume carried against rated capacity. A high time-utilisation figure paired with a low payload figure means the fleet is busy rather than productive, which is a different problem with a different fix. |
| Hire-in days against internal idle days | External hire days for the same period as idle days on comparable owned assets, compared across depots. Any overlap at all is free money, and it is the easiest finding to act on because it needs no disposal decision. |
| Fixed cost per productive hour | Accrued standing cost divided by productive hours. KO Fleetz reports it as the hinge between this page and reduce fleet operating costs, since it prices capacity rather than consumption and falls only when utilisation rises. |
Put a number on it before you talk to anyone
The fleet utilization calculator is free, shows its formula, and asks nothing of you. Work out your own figure, then bring it to a demo.
Customer evidence
Fleets using KO Fleetz to do this
Customer story pending. A short, attributed quote from a fleet that used KO Fleetz for improve fleet utilization belongs here — the result, in their words.
Frequently asked questions
No, and this is the most important caveat on the page. A fleet running at maximum has no slack, and a fleet with no slack turns a single breakdown into a cascade of missed jobs because there is nothing to reallocate. Very high utilisation also accelerates wear and compresses maintenance windows until services get deferred, and deferred services produce roadside failures. The goal is not the highest number. It is knowing which of your idle hours are deliberate resilience and which are simply unexamined, and letting KO Fleetz tell the difference on a screen rather than settling it in a meeting.
Reducing operating costs is about the cost of each unit of work you do. Utilisation is about how many units of work you get from assets you have already bought. They meet at exactly one number, fixed cost per productive hour, and diverge everywhere else. You can run a beautifully cost-controlled fleet that is forty percent too large, and every per-kilometre metric will look excellent while you pay for capacity you never use. Utilisation is the only view that catches that, because the waste appears as an absence of work rather than as a cost.
Assume they are arguing in good faith, because they usually are, and recognise the incentive. Nobody gets criticised for having a spare van, and people definitely get criticised for missing a job. Do not open with disposal. Open with measurement, agree what available hours actually means for that operation before looking at a single result, and classify the idle time together. Then run the reversible experiment first and pool the vehicles rather than sell them. Pooling can be undone in a week if it fails, and it usually reveals the true requirement more convincingly than any report, because the manager watches it happen.
It gets you most of the way and it will not make the decision. What it cannot know is your commercial risk appetite: what a missed job costs you in contract terms, which customers tolerate a delay and which do not, whether a new contract lands in March. It also cannot judge whether short-term hire is genuinely available in your area at the moment you need it, which is the assumption quietly underwriting every right-sizing plan and the one that fails first. Use KO Fleetz to establish the trough your ordinary weeks require. Then decide what buffer you are willing to pay for, deliberately, with the cost of that buffer in front of you.
Yes, and non-powered assets are frequently where the worst utilisation hides, precisely because they attract the least attention. Trailers, skips, containers and site equipment are cheap enough individually that nobody audits them and numerous enough collectively to matter a great deal. The denominator changes, since an excavator is measured per engine hour and a trailer by days under load rather than days moving, but the classification of idle time works identically. The practical constraint is telemetry: an asset with no tracker reports nothing, and a battery-powered tracker on an unpowered trailer needs its own health monitoring.
A month gives you dormant assets and the obvious cross-depot overlaps, and both are worth acting on immediately since neither requires a disposal decision. A defensible fleet-size argument needs a full seasonal cycle, because a fleet sized on data from your quiet quarter will fail in your busy one and it will fail publicly. If your work has an annual rhythm, whether agricultural, retail peak or construction season, wait for the cycle. The cost of one more quarter of measurement is small against the cost of disposing of the wrong six vehicles.
See which of your vehicles earned nothing last month
Give us one region's asset list and thirty days of telematics, and KO Fleetz will show you the dormant assets, the standby you actually need, and the hire-in you did not.