Scheduled preventive maintenance is the difference between a managed fleet and a fleet that reacts. But there is a well-known problem: most preventive plans are built in Excel, live on someone’s computer and are followed for the first 90 days. Then real operations kick in, vehicles don’t go to the shop when they should and, six months later, the calendar is a document nobody looks at.
A preventive maintenance calendar that gets followed does not depend on the team’s willpower. It depends on how it is built, how it is triggered and how each job is closed. If those three points are right, sustained compliance of 85% to 95% is achievable. If they are wrong, the best plan in the world falls apart on its own.
It is the system that defines, for each vehicle in your fleet, what work it needs to receive and when. The smallest unit is the task (oil change, tire rotation, filter change). Tasks are grouped into services (10,000 km service, major service at 50,000 km). Services are organized into a maintenance plan per vehicle model.
The full Plan → Service → Task hierarchy is the backbone of preventive maintenance, and it is configured inside the Maintenance module. Without that structure, you don’t have a calendar: you have a to-do list.
Each preventive task is set off by one of two possible triggers:
By time. Every X months or X days since the last job. It applies to tasks that depend on the passage of time rather than usage (battery replacement, fluid check, general inspection).
By mileage. Every X kilometers driven. It applies to tasks that depend on wear from use (oil, filters, brakes, tires).
Most tasks have both triggers configured and are carried out according to whichever comes first. A vehicle that drives little will get its service by time. A vehicle that drives a lot will get it by mileage. If you configure only one trigger, you will miss half of the fleet.
Rule 1: Calibrate intervals to real usage, not to the manufacturer’s manual.
The manufacturer’s manual assumes average conditions. Your fleet has specific conditions: typical load, type of route, climate, local fuel quality. If you copy the intervals from the manual, your vehicles will fail sooner or you will be spending more than necessary. Make the adjustment based on the history of actual failures in the first 6 months.
Rule 2: Every preventive task is born as a ticket, not as a reminder.
The difference is huge. A reminder gets ignored; a ticket with a due date and an owner gets done. The system has to generate the Preventive ticket when the interval is reached, without anyone having to remember.
Rule 3: Differentiate due items by urgency with a green/yellow/red indicator.
Not all preventive jobs are equal. An oil change 500 km overdue is green. 2,000 km overdue is yellow. 5,000 km overdue is red and starts to create a risk of failure. The system has to show all three states so the manager knows what to prioritize.
Rule 4: Closing a Preventive ticket requires evidence.
A task closed without the shop invoice or the details of the work performed is not considered complete. Traceability is what later lets you file warranty claims and defend the quality of your preventive work in an audit.
Rule 5: Review the plan quarterly.
The plan you built on day one will not be the right plan in year two. Operations change, models change, suppliers change. A quarterly review with real data is what keeps the calendar alive.
If preventive maintenance is not being done, it is almost always because of one of these five mistakes:
Three metrics you need to look at every month:
These three metrics live in the maintenance manager’s dashboard and are reported to the operations director every month.
To make the Plan → Service → Task hierarchy concrete, here is how preventive maintenance is configured for three representative models in a mid-sized mixed fleet:
Model A — Diesel light commercial vehicle for urban use (delivery)
Model B — 4×4 diesel pickup for mixed urban/highway use
Model C — Long-haul light truck
For each model, the plan is built only once in the Maintenance module and stays linked to that model in the catalog. Configuring the three plans for a new fleet takes no more than one day of work if the manufacturer’s data is at hand.
→ Explore the Maintenance module
→ Book a demo of VEC Fleet
In practice they are synonyms. Some manuals separate “preventive” (generic, avoiding failures) from “scheduled” (carried out at defined intervals). In fleet management they are used interchangeably to refer to the same concept: planned work done before the vehicle fails.
Every 3 months as a routine, and whenever you add a new vehicle model or change service provider. The plan is a living thing: adjusting it is part of the job, not an exception.
Between 7 and 21 days, depending on the type of task and the capacity of your shop network. Simple tasks like an oil change or a tire rotation need less lead time; those that require coordination or ordered parts need the full three weeks.
The ticket stays open with an overdue flag, and the calendar indicator turns from green to yellow and then to red depending on the days or kilometers of delay. It is recorded, and that is what gets reviewed later in the monthly compliance audit.
Each model has its own Maintenance Plan, built only once and linked to that model in the catalog. The heavy lifting is the initial loading of the plans; after that, adding units of an already configured model is much faster than starting from scratch.
In practice they are synonyms. Some manuals separate “preventive” (generic, avoiding failures) from “scheduled” (carried out at defined intervals). In fleet management they are used interchangeably to refer to the same concept: planned work done before the vehicle fails.
Every 3 months as a routine, and whenever you add a new vehicle model or change service provider. The plan is a living thing: adjusting it is part of the job, not an exception.
Between 7 and 21 days, depending on the type of task and the capacity of your shop network. Simple tasks like an oil change or a tire rotation need less lead time; those that require coordination or ordered parts need the full three weeks.
The ticket stays open with an overdue flag, and the calendar indicator turns from green to yellow and then to red depending on the days or kilometers of delay. It is recorded, and that is what gets reviewed later in the monthly compliance audit.
Each model has its own Maintenance Plan, built only once and linked to that model in the catalog. The heavy lifting is the initial loading of the plans; after that, adding units of an already configured model is much faster than starting from scratch.