Fleet management software holds the vehicle as the unit: what it is, who drives it, how many days it earned against how many it was available, what it cost to run, what maintenance it has had, which documents are valid and until when, and whether it made money last month. With Pentoggle, an operator can describe how the fleet actually runs and generate the starting application around it.
This page covers fleets of any composition, including mixed fleets of trucks, tempos, tankers, trailers and light commercial vehicles. If your fleet is specifically long-haul goods trucking and your question is about cost and freight per kilometre, empty running and driver rotation on multi-day trips, start with Truck Fleet Management Software instead.
Many operators already run Tally for accounting and a GPS or telematics provider for vehicle data. Those systems handle the books and the vehicle position and they stay where they are. What is often still managed outside them is the vehicle as a commercial object: what it earned, what it cost, how much of the month it worked, and whether it should still be in the fleet.
Key takeaways
- Fleet-level totals are outcomes rather than levers. The vehicle is the unit you can redeploy, reassign, repair or sell, so it has to be the unit the software reports on.
- Utilisation has two distinct failure modes, idle and off-road, and they need completely different responses despite producing the same number.
- Fixed costs continue on a standing vehicle, which is why a load that contributes positively after its incremental costs can be better than no load, and why a chronically idle vehicle is expensive in a way that never appears as a bill.
- Replacement decisions are usually made on age or on a breakdown rather than on cost per kilometre trending upward, which is often the more useful signal.
- A useful number is vehicle utilisation, meaning revenue-earning days against available days, per vehicle.
The spreadsheet is often not the problem
A vehicle list with a maintenance column and a monthly trip count is a working system for a small fleet, and it should not be replaced for the sake of it.
The trouble starts at identifiable points.
When the fleet outgrows one person's memory
At ten vehicles the operations head knows each truck's condition, driver and document status. At thirty the same person is still the only place that knowledge exists, and it is now incomplete.
When cost and revenue live in different places
Diesel and repairs are in one sheet, freight billed is in another, and nothing connects a rupee earned to the vehicle that earned it. Per-vehicle profitability is therefore an annual exercise rather than a monthly fact.
When availability is not recorded
You know a vehicle ran fourteen trips. You do not know it was off-road for nine days, so its performance looks poor when it was actually fine on the days it worked.
When document expiry is a diary entry
The documents your vehicles require, such as permit, fitness, insurance, PUC and tax, run to well over a hundred dates across thirty vehicles. A diary holds them until the one week somebody is on leave.
What fleet management software holds
Vehicle master
Registration, type, capacity, ownership basis, purchase details, finance and EMI, and current status.
Driver assignment
Which driver is on which vehicle, current and historical.
Availability and utilisation
Days available, days earning, days idle and days off-road, with the reason for each non-earning day.
Running cost
Diesel, tolls, driver expenses and other variable cost, attributed to the vehicle.
Fixed cost
EMI, insurance, permit, tax and depreciation, allocated per period.
Maintenance and breakdowns
Scheduled services, repairs, parts, tyres, and the downtime each caused.
Documents and validity
The documents your vehicles require, such as permit, fitness, insurance, PUC, tax and any route-specific requirement, with expiry visible in advance.
Revenue and profitability
Freight earned attributed to the vehicle, against total cost, per period.
The average hides the fleet
A common reporting mistake in fleet operations is to look only at fleet totals and fleet averages.
A fleet of thirty vehicles returning an average cost per kilometre that looks acceptable can contain four vehicles well above it and four well below. The average is real and it is not actionable, because you cannot repair, redeploy or sell an average.
What is worth building instead is a distribution. The same figure for every vehicle, sorted, looked at monthly. Fleets that do this for the first time commonly find a similar shape: a majority clustered around a sensible number, a small group performing notably better, and a small group performing much worse and carrying the rest.
The vehicles at the bad end usually have identifiable and different reasons. One is old and its maintenance cost has crossed the point where it should have been replaced. One is on a lane that does not suit it. One has a driver problem. One is being kept for a customer who no longer gives enough volume to justify it. None of these is visible in a fleet total, all of them are actionable individually, and each needs a different action.
The same logic applies to every fleet metric. Mileage, maintenance cost, utilisation and revenue all mean something as a distribution and very little as an average.
Idle and off-road are not the same problem
Utilisation is one of the few figures that reflects the whole fleet at once, and the way it is commonly calculated takes most of the use out of it.
A vehicle that did not earn on a given day did not earn for one of two reasons, and they belong to different people.
Idle means the vehicle was available and there was no work for it, or the work went elsewhere. This is a commercial problem. It belongs to sales and to whoever decides load placement. The response is more contracted volume, better return-load sourcing, or a smaller fleet.
Off-road means the vehicle was not available. Breakdown, workshop, accident, an expired document, a driver who did not report. This is an operations problem. The response is preventive maintenance, document tracking, driver bench strength.
Both produce a non-earning day and a single utilisation percentage blends them. A fleet at 68 percent utilisation because of poor load availability and a fleet at 68 percent because vehicles keep breaking down are in entirely different situations, and a manager who sees only the percentage has no way to tell which remedy applies.
Recording a reason against every non-earning day is a small operational discipline with a large analytical payoff. It costs one field. It turns a number into a diagnosis.
Replacement is a cost signal, not a birthday
Most fleets replace vehicles on age, on a major breakdown, or when finance terms make it convenient. None of these is necessarily the point at which replacement makes economic sense.
A vehicle's cost per kilometre can change materially over its life as fixed costs are spread over distance and maintenance, downtime and other operating costs change. The useful signal is a sustained increase in total cost per kilometre, particularly when it coincides with rising downtime. That signal is knowable and it is frequently not known, because nobody is tracking the figure over time.
Three things are needed and they are all things a fleet application holds anyway: cumulative cost per kilometre by vehicle over time, downtime days by vehicle, and revenue per vehicle. A vehicle whose cost per kilometre has risen over several consecutive quarters while its downtime increases is telling you something the annual accounts will not.
There is also a second-order cost that rarely gets counted. An unreliable vehicle does not just cost repairs. It costs missed commitments, hired substitutes at short notice at market rates, and in some cases a customer. Those costs land in other lines of the accounts and are rarely attributed back to the vehicle that caused them.
Where fleet management looks different by business type
- Transport Contractor and Fleet Owner Software, where owned, attached and market vehicles need separate cost treatment.
- Bulk and Tanker Transport Software, where product compatibility constrains deployment before economics does.
- Container Transporter and CFS Software, where trailer availability is measured in hours rather than days.
- City Distribution Software, where the vehicle is committed to a route-day rather than to a trip.
- Packers and Movers Software, where vehicles are scheduled around crews and job dates.
- Tempo and Small Commercial Vehicle Software, where the fleet is small enough that fixed cost per day is the whole analysis.
Why operators choose Pentoggle for fleet management
Per vehicle, not per fleet
Every figure reportable as a distribution across vehicles, because the vehicle is the unit you can act on.
Non-earning days carry a reason
Idle and off-road separated, so the number points at whoever can fix it.
Cost and revenue in the same record
Freight attributed to the vehicle that earned it, against the full cost of running it including the fixed costs.
Documents with lead time
Expiry visible weeks ahead rather than discovered at a check post.
Sits around your accounting
Tally and comparable systems continue handling accounting, invoicing and GST. Pentoggle adds the operational layer around vehicles, utilisation, cost and condition.
A useful number for fleet management
Vehicle utilisation, meaning revenue-earning days against available days, per vehicle.
It is the closest thing to a single health measure a fleet has, because almost every other problem eventually shows up in it. A maintenance problem reduces available days. A commercial problem reduces earning days. A driver availability problem reduces both.
Two conditions make it meaningful.
Define available days honestly. A vehicle that is unavailable for operations because it is in the workshop should not be counted as available, and counting it as available understates utilisation while hiding the maintenance problem. Counting it as unavailable and reporting the off-road days separately keeps both facts visible.
And always report it with the non-earning reason breakdown beside it. Utilisation alone tells you the size of the gap. The reasons tell you whose gap it is.
Read it alongside revenue per vehicle. High utilisation with low revenue means the vehicle is busy on work that does not pay, which is a different and often worse problem than a vehicle that stands.
Ready to build fleet management software?
Your fleet average will tell you the operation is roughly fine.
A few of your vehicles are probably carrying the rest, and the average is how they stay hidden.
Describe your vehicles, how they are deployed and what they cost to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.