Vehicle maintenance program: scheduling by use, not by calendar

A vehicle maintenance program is the planned schedule of inspections, servicing and component replacement for a fleet, together with the records proving it was carried out. It exists for two reasons that pull in the same direction: vehicles that are maintained on a plan fail less often and less expensively than vehicles maintained after they break, and in most regulated operations the carrier has to be able to show a systematic programme rather than a habit.

The commonest design mistake is scheduling everything by date. A van doing four hundred kilometres a week and one doing four thousand are on the same calendar and in completely different condition, and a date-based plan services the wrong one first for years before anybody notices.

What a vehicle maintenance program covers

• A record per vehicle: identification, specification, ownership or lease, registration and inspection dates.
• The service schedule for each vehicle type, from the manufacturer’s intervals adjusted for how the vehicle is actually used.
• The trigger for each task: distance, engine hours, fuel consumed or elapsed time, whichever comes first.
• Statutory inspections and certifications, with their due dates tracked separately from servicing.
• Defect reports arriving from drivers, and their repair records — the loop that connects the daily inspection to the workshop.
• Parts and tyre history, which is where a recurring fault becomes visible.
• Cost per vehicle, so a machine that is quietly consuming its own value can be identified and replaced.

Severe service is the norm, not the exception

Manufacturer intervals assume ordinary use. Short trips, heavy loads, dusty sites, stop-start urban work, idling and towing all fall under what the schedules call severe service, and most working fleets are in that category all of the time despite reading the ordinary column. If your vehicles do short urban runs with a full load, the severe interval is the real one, and a programme built on the standard one is systematically late.

Track cost per vehicle, not just cost per repair. Fleets replace the vehicle that had one dramatic failure and keep the one that quietly absorbed a small repair every month for two years — which is the more expensive machine by a wide margin, and it is invisible unless the costs are attached to the vehicle rather than to the invoices.

Records are half the programme

1. List every vehicle with its identifiers and current odometer or hour reading.
2. Set the schedule per vehicle type against the interval that matches its actual duty, not the default column.
3. Decide the trigger for each task and who is responsible for noticing it is due.
4. Feed driver defect reports into the same queue as planned work, so nothing sits in a separate pile.
5. Record every job with date, reading, parts and cost, attached to the vehicle.
6. Review quarterly: which vehicles are consuming the budget, which faults recur, which intervals need shortening.

Once the schedule covers more than a few vehicles it stops fitting on a wall chart. Fleet maintenance management software holds intervals, defects, inspections and document expiry per vehicle, and answers what falls due in the next month across the whole fleet.

Where it lives

Ettex Records holds the file per vehicle — documents, certifications, service history and costs in one place, retrievable when an inspector or an insurer asks; Ettex Sheets carries the schedule and the cost-per-vehicle view, alongside the fuel and distance workbook behind ifta reporting; and the daily reports that feed it come in through Ettex Forms, as covered in dvir.

Being clear: this is records and scheduling, not fleet maintenance software. There is no telematics feed, no odometer sync, no parts catalogue and no workshop integration. For a large fleet those are worth buying. For a small one, the failure is almost never the absence of software — it is that nobody owns the schedule.

The same logic applies off the road. Planned preventive maintenance for fixed plant is the identical exercise — interval, task, completion record — with the difference that a vehicle carries its own usage meter and a compressor usually does not, so someone has to decide what the interval is counted against.