By the RAAD team
Fleet Analytics Finds Where Leasing Fleets Lose Money
Listen to this article
Leasing fleets lose money in places a live map never shows: fuel that disappears, engines running with no operational reason, vehicles sitting broken, and assets that earn nothing while the lease runs on. Fleet analytics turns each of those into a named cost, so the losses can be managed rather than felt.
What fleet analytics measures that a map misses
Fleet analytics turns raw telematics signals, such as trips, stops, fuel events and engine hours, into costs and trends an operator can act on. A live map answers where a vehicle is. Analytics answers what it costs and why.
The pressure on a leasing operator is familiar. Fuel rises faster than budgets, congestion burns paid hours, some vehicles stay in service long past their prime, compliance paperwork keeps growing, and customers do not always treat the asset with care. None of that shows on a map pin.
In RAAD, Track feeds trips, stop history, zone entries and driver behaviour into one estate. Power adds the fuel and energy ledger, and Assets, Drivers, Documents and Maintenance keep the paperwork alongside it. Analytics drawn from one connected record beats exports stitched together by hand.
Where the losses sit
Most avoidable loss in a leasing fleet falls into six measurable places, and each has a control that follows once it is measured.
| Cost driver | What analytics measures | The control that follows |
|---|---|---|
| Fuel | Litres claimed on receipts against litres the tank took, and loss with the engine off | Fill checks, automatic fuel-loss cases, eco-driving coaching |
| Idling | Engine-running minutes with no operational need | Idle thresholds per vehicle type, driver and site coaching |
| Theft exposure | Zone entries and dwell time in high-risk areas, unscheduled stops | Geofence rules, permitted-hours limits, route changes |
| Maintenance | Cost per vehicle against odometer and service history | Planned servicing, expiry and inspection reminders, better procurement |
| Downtime | Days out of service priced against lease revenue | Root-cause review, honest service-level reporting |
| Utilisation | Productive hours against standing time per asset | Redeploy, reprice or retire idle equipment |
Fuel: check every fill against the tank
Fuel is usually the largest controllable line in a fleet's operating costs, and it leaks in two distinct places: at the pump and while parked.
Fuel reconciliation means checking every fill receipt against the change in tank level the sensor reports. RAAD's Power module does this on every fill, so a receipt claiming more than the tank took shows up the same day instead of at month end.
The parked leak is blunter. Fuel loss with the engine off opens a case on its own, because a tank that drains while nobody is driving is either theft or a fault, and both need a person. Driving style is the third lever: comparing litres per kilometre across drivers, routes and regions shows where the extra burn lives, and eco-driving scores point to the harsh acceleration and speeding that cause it.
Idling: split working minutes from wasted ones
Not every engine hour is waste, and treating all of it as waste erodes trust in the numbers.
Operational idling is engine time the work genuinely requires: a refrigeration unit holding a cold load, a power take-off running a pump or crane, or a queue at a busy gate. Avoidable idling is the engine running with no operational reason, most often a parked cab kept on for comfort. The split matters because the first is a cost of doing business and the second is pure loss.
Set thresholds per vehicle application, then report engine-running time without movement against those thresholds, priced in money using the engine's idle burn rate. Patterns show up quickly by driver, by customer site and by day of week, and rules plus coaching close the gap.
Security: control where vehicles dwell
Theft and cargo loss cluster by place and hour, which means the data shows your exposure before an incident and gives you time to act on it.
A geofence is a virtual line you draw around a place on the map, and RAAD notices each time a vehicle crosses it. Stop history shows where vehicles actually spend their standing time, or dwell time. Compare that with where you already know incidents happen, and the overlaps become your exposure map. Geofences with rules flag entry into high-risk zones outside permitted hours, long dwell inside sensitive areas, and unscheduled stops that were never part of the plan.
An avoided incident saves more than the asset: it also saves the insurance exposure, the unscheduled downtime and the customer conversations that follow. When a claim does land, Cam clips with time, place and speed settle disputes that would otherwise be paid for twice, and the same dashcams flag phone use, drowsiness and unclipped belts before those habits turn into larger losses.
Maintenance: from surprise bills to a rolling forecast
Maintenance stops being a surprise when service history sits next to usage on the same record.
Correlating odometer readings and engine hours with what each vehicle actually cost turns maintenance from a monthly shock into a rolling forecast. Units that age expensively stand out early, service gets planned before failures instead of after them, and expiry and inspection reminders keep the schedule honest.
The same record answers the procurement questions a leasing operator lives with: which models hold up in your duty cycles, and which ones to stop buying. If your fleet runs vehicles well past their prime, as many cost-conscious operators do, that question gets more valuable every year.
Downtime and utilisation: count the days an asset earns nothing
A leased vehicle earns nothing on the day it sits in the workshop, and an under-used asset loses quietly every week it stands.
Downtime compounds, because the repair bill, the missed lease revenue and the strained customer relationship land together. Price it as days out of service multiplied by the daily rate the asset should be earning, and it becomes a number you can negotiate service level agreements and contracts around. Repeat offenders show up by unit and by cause.
Utilisation needs a definition before it needs a dashboard, since productive time differs by vehicle type and by customer. Set the definition for each, measure standing time across the fleet, and act on what you find: redeploy, reprice or sell the equipment that does not earn. For a leasing operator the finding is commercial as well as operational, because an asset that stands idle at a customer's site is a conversation about the contract. The same trip data also feeds indicative carbon reporting for the customers who increasingly ask for it.
Compliance: keep the paperwork ahead of the audit
Commercial transport rules differ by market, but the protection is the same everywhere: an operator who can produce records on demand never pays for disorganisation.
Many markets require detailed operational documentation from commercial fleets, and failure brings fines, grounded vehicles and lasting reputational harm. In RAAD, the Documents, Drivers and Assets records carry expiry dates with reminders, so licences, insurance and inspections never lapse unnoticed, and scheduled reports produce the trail an auditor or a customer asks for.
One estate, one costed picture
The aim is fewer, truer numbers, and fewer places to look for them. RAAD keeps tracking, fuel and energy, cameras, site sensors and paperwork in one console on the hardware you already own, so the analytics is grounded in a single estate rather than stitched-together exports.
Reading it all is where AI Insights earns its keep: it reads every alert, holds back what does not need a person, and brings the rest with a reason and a proposed fix. Nothing touches a vehicle until someone approves it, so judgement stays with your team. Partners who serve leasing operators deliver the same estate under their own brand, which turns one-off hardware sales into monthly recurring revenue.
Common questions
Can we run fleet analytics on the trackers we already have?
Yes. RAAD takes over the hardware you already run rather than replacing it, so a mixed estate of existing trackers feeds one console and the analytics starts from live data instead of a procurement project.
Does the AI act on vehicles by itself?
No. AI Insights triages alerts, holds back what does not need a person and brings the rest with a reason and a proposed fix. Nothing touches a vehicle until a person approves it.
Which loss should we tackle first?
Fuel, usually, because the data already exists: every fill is checked against the tank, and engine-off losses open cases on their own. Idling is the natural next step, since it needs only one threshold decision per vehicle type.
One platform for every connected asset
Tracking, power, cameras, metering and compliance in one console — resold under your own brand and billed by you.
Explore the RAAD platform

