Vehicle maintenance software covers everything that keeps a vehicle serviceable: preventive schedules triggered by distance or time, service history, breakdowns with cause and cost, workshop jobs in-house or outsourced, spares and consumables, and tyres from fitment to removal. With Pentoggle, an operator can describe how maintenance actually works and generate the starting application around it.
Tyres are covered on this page rather than separately. They behave like a maintenance item, they are managed by the same people, and splitting them into their own system produces two records of the same vehicle.
Many operators already run Tally for accounting and a GPS or telematics provider for vehicle data. Those stay where they are. What is often still managed outside them is the maintenance record: what was done, when it is next due, what failed and why, and what the downtime cost.
Key takeaways
- The useful split is planned against unplanned downtime, not total downtime, because the first is an investment and the second is a loss.
- Deferring maintenance when cash is tight is a common way a viable fleet becomes an unreliable one, and the cost lands later as an unplanned bill nobody connects to the deferral.
- The true cost of a breakdown is the repair plus the downtime plus the substitute vehicle plus the missed commitment, and only the first of these is usually recorded.
- Tyres are typically among the largest consumables after fuel, and are managed by position and by kilometres run rather than by purchase date.
- A useful number is unplanned off-road days as a share of total off-road days.
The spreadsheet is often not the problem
A service register and a folder of workshop bills is a real system and it works at small scale.
The trouble starts at identifiable points.
When schedules are triggered by kilometres nobody is tracking
A service due every fifteen thousand kilometres requires knowing current odometer readings across the fleet. Without that, services happen when someone remembers or when something breaks.
When repairs are recorded as amounts
The bill says a figure. What failed, why, and whether it has failed before on this vehicle is not captured, so recurring faults are paid for repeatedly without ever being recognised as recurring.
When downtime is not measured
The vehicle was in the workshop. For how long, and whether that was planned, is not in the register, so the cost of poor reliability never appears anywhere.
When tyres are bought rather than managed
Tyres are purchased as an expense. Which tyre went on which position on which vehicle at what odometer, and how long it lasted, is not tracked, so tyre life per rupee is unknown.
What vehicle maintenance software holds
Preventive schedules
Service intervals by distance and by time, per vehicle type, with what is due and when.
Service history
Every service performed, what was done, by whom, at what odometer and cost.
Breakdowns and repairs
What failed, where, the cause where known, the repair, the cost, and the downtime it caused.
Workshop jobs
Jobs in-house or at an outside workshop, with status, estimated and actual cost, and turnaround.
Spares and consumables
Parts issued against jobs, with stock where the operator holds one.
Tyres
Fitment by position with serial or identification, odometer at fitment, removal, retreading and final disposal.
Downtime
Days off-road per vehicle, split planned and unplanned, with reason.
Maintenance cost per kilometre
Cost by vehicle over distance run, trended over time.
Planned and unplanned downtime are opposites
Total downtime is a misleading figure because it combines two things with opposite meanings.
Planned downtime is a vehicle taken out of operation for a scheduled service, at a time chosen to suit the operation, with the work known and the duration predictable. It is an investment in availability. A fleet with zero planned downtime is not efficient, it is deferring.
Unplanned downtime is a vehicle off the road because something failed. The timing is chosen by the failure, the duration is unknown, and the operational cost extends well beyond the repair: a load that has to be moved another way, a customer told, a substitute hired at short notice at whatever the market charges.
Adding them together produces a number that improves when preventive maintenance is cut, which is precisely the wrong incentive.
The ratio between them is a better health measure. A fleet where most off-road days are planned is being managed. A fleet where most are unplanned is reacting, and the cost of that tends to show up well beyond the maintenance line.
Holding the two figures apart over time is what turns the argument for preventive maintenance from a principle into a number specific to your own fleet. That argument is most needed when cash is tight and a service is about to be postponed, which is exactly when a principle loses and a figure may not.
Deferral is how fleets deteriorate
Almost no operator decides to run an unreliable fleet. They arrive at one through a sequence of individually reasonable decisions.
Money is tight this month. A service is due on a vehicle that is running fine. Postponing it saves cash now and appears to cost nothing. The vehicle continues running. Next month the same logic applies, and the month after.
Eventually something fails. The failure is expensive, it happens at an inconvenient time, and it is experienced as bad luck rather than as the accumulated result of six deferrals. Because the connection is not visible, the lesson is not learned, and the cycle repeats.
What makes this hard to break is that the saving is immediate and visible while the cost is delayed and diffuse. The practical counter is to make the deferral itself visible: a record of what was due, what was postponed, by how long, and what subsequently failed on that vehicle.
A fleet that can show its most expensive breakdowns occurred on vehicles carrying deferred services has an argument that survives a cash-flow conversation. Without the record, the argument is a general principle competing against a specific and immediate saving, and the general principle usually loses.
The same applies to the repair-or-replace decision at component level. A component repaired repeatedly over a short period is telling you something, and it is only visible if repairs record what failed rather than just what was paid.
Tyres are managed by position and distance
Tyres are typically among the largest consumables in a road transport operation after fuel, and they are often managed less carefully than fuel, largely because they are bought occasionally rather than continuously.
Treated as a purchase, a tyre is an amount on a bill. Treated as an asset with a life, it is a unit fitted to a specific position on a specific vehicle at a specific odometer reading, which runs a measurable distance before removal, may be retreaded and refitted, and eventually goes for disposal at some residual value.
Tracking fitment by position rather than by vehicle is what makes the data useful, because positions wear differently. Steer, drive and trailer positions have different lives, so comparing a steer tyre's life to a drive tyre's is not a like-for-like comparison.
Once tyre life per position is measured across a fleet, several things become visible that are otherwise invisible. Which brand or pattern actually delivers more kilometres per rupee on your routes, which is frequently not the cheapest option and frequently not the most expensive one either. Which vehicles consume tyres faster than others, which usually indicates an alignment, suspension or loading issue rather than a tyre issue. Whether retreading is returning acceptable value in your operation, which varies considerably by route and load. And which drivers are associated with shorter tyre life, though this needs the same fairness caution that applies to mileage.
Rotation and pressure discipline are the operational side and they are worth recording precisely because they are easy to skip. Underinflation can cost tyre life and fuel at the same time, which makes it a maintenance item with an immediate as well as a deferred cost.
Where vehicle maintenance looks different by business type
- Truck Fleet Management Software, where breakdowns happen hundreds of kilometres from any workshop you control.
- City Distribution Software, where stop-start running drives brake and clutch wear rather than engine hours.
- Bulk and Tanker Transport Software, where the tank and its fittings carry their own inspection requirements alongside the vehicle.
- Container Transporter and CFS Software, where trailers have a separate maintenance cycle from the prime mover.
- Transport Contractor and Fleet Owner Software, where attached vehicles are maintained by their owners and reliability is managed contractually.
- Tempo and Small Commercial Vehicle Software, where deferral is most common because cash is tightest.
Why operators choose Pentoggle for vehicle maintenance
Planned and unplanned held apart
The ratio that shows whether the fleet is being managed or reacted to.
Schedules driven by actual odometer
Services due by distance as well as by date, against readings the operation is already capturing.
Failures recorded, not just paid for
What failed and why, so recurring faults on a vehicle become visible instead of being paid for repeatedly.
Tyres tracked by position and distance
Life per position, retread value and vehicles consuming tyres faster than they should.
Sits around your accounting
Tally and comparable systems continue handling accounting and supplier payments. Pentoggle adds the operational layer around schedules, jobs, failures and downtime.
A useful number for vehicle maintenance
Unplanned off-road days as a share of total off-road days.
It measures whether maintenance is being managed or is happening to you, and it moves in the right direction when the right things are done, which is not true of total downtime.
Read it per vehicle as well as fleet-wide. A fleet at 40 percent unplanned may contain most vehicles well below that and three that are almost entirely unplanned, and those three are candidates for either a serious intervention or replacement.
Track maintenance cost per kilometre alongside it, trended per vehicle over quarters. The two together give the replacement signal described on the fleet management page. A vehicle whose maintenance cost per kilometre is rising while its unplanned share increases is approaching the point where it may cost more to keep than to replace, and that is visible well before the breakdown that usually forces the decision.
Ready to build vehicle maintenance software?
You know what you spent on repairs last year.
You probably cannot show whether your worst breakdowns were on vehicles carrying services you postponed.
Describe your schedules, workshops and how you record failures to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.