Scheduled preventive vehicle maintenance: how to build a calendar that actually gets followed

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.

Vista aérea de una flota de camiones estacionada en filas ordenadas en un depósito

What a scheduled preventive maintenance calendar is

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.

The two dimensions of preventive maintenance: time vs. mileage

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.

How to build a calendar that gets followed: 5 rules

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.

Mistakes that kill the preventive calendar

If preventive maintenance is not being done, it is almost always because of one of these five mistakes:

  • Preventive tickets opened too late. If the ticket is generated on the due date itself, there is no time to coordinate the shop and the driver. It has to be opened days in advance, depending on the type of task.
  • There is no clear rule for which shop each ticket goes to. If every time a Preventive ticket is opened you have to discuss where the work will be done, that friction slows the flow. Define in writing which shop serves each base and each type of task, so assigning it is a click and not a decision.
  • Tasks are too generic. A service that says “20,000 km service” doesn’t tell the mechanic what to do. Each task has to be broken down in enough detail to be carried out without asking.
  • Nobody tells the driver. If drivers don’t find out that their unit has a pending preventive job, they will keep operating until someone stops them. The notice has to be part of the base supervisor’s daily routine.
  • Compliance is not measured. Without a compliance metric there is no way to improve the plan. It has to be a monthly KPI for the fleet manager.

How to measure whether your calendar is working

Three metrics you need to look at every month:

  • Preventive compliance rate. Preventive tickets closed on time over Preventive tickets generated. A managed fleet is between 85% and 95%. Below 70%, the calendar is not operating, it is stalled.
  • Average days overdue per Preventive ticket. If the average grows month after month, you are heading toward corrective mode. If it decreases, the system is maturing.
  • Corrective / Preventive ratio. A healthy fleet closes between 2 and 4 preventive tickets for every corrective one. If the ratio is reversed, the calendar has lost control.

These three metrics live in the maintenance manager’s dashboard and are reported to the operations director every month.

What a preventive calendar looks like for 3 typical models

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)

  • 10,000 km / 6-month service: oil and filter, fluid level check, tire rotation, lights and brakes check. 8 tasks, about 2 hours.
  • 20,000 km / 12-month service: all of the above plus air filter, full brake inspection, battery and alternator check. 14 tasks.
  • 60,000 km / 36-month service: major service with fluid replacement, timing belt if applicable, front suspension inspection. 22 tasks.

Model B — 4×4 diesel pickup for mixed urban/highway use

  • 8,000 km / 6-month service, with a shorter interval due to demanding operation: premium oil, filter, suspension check.
  • 30,000 km / 12-month service: all of the above plus fuel and air filters, brake and clutch inspection.
  • 80,000 km / 36-month service: major service plus injector and turbo diagnostics.

Model C — Long-haul light truck

  • 15,000 km service, with no time trigger because mileage always triggers first: heavy-duty oil, filter, tire check in 6 positions.
  • 50,000 km service: in-depth inspection of the transmission, differential and complete brake system.
  • 150,000 km service: major service with fluid replacement, engine and transmission inspection, chassis check.

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.

How VEC Fleet implements the preventive calendar

  • Maintenance Plan → Service → Task configurable by vehicle model from the Maintenance module.
  • Time and mileage triggers, with the vehicle’s Meter as the source of distance driven.
  • Automatic generation of Preventive tickets as the due date approaches.
  • Visual calendar with upcoming expirations and preventive jobs marked with the letter V or P, a green/yellow/red indicator and the letter T when a ticket is already open.
  • Network of suppliers and shops loaded in the system, to assign the ticket to the right shop without leaving the platform.
  • Ticket closing with the job documentation attached, which is what validates the work and backs up the warranty claim.
  • Native reports on compliance by base, by model and by manager.

→ Explore the Maintenance module
→ Book a demo of VEC Fleet

Facebook
LinkedIn
X