Kilometers or months in fleet maintenance? How to set the right interval

Everyone who manages a fleet faces a quiet problem: deciding when maintenance should be done. Most teams tie this decision to a single measure, either mileage or the calendar, and when they miss one of the two they pay for it with an unexpected breakdown. Yet in a fleet, not every vehicle lives at the same rhythm; some make a hundred stops a day, others hundreds of kilometers in a single trip.

The misleading side of a single measure

A plan that looks only at mileage shows a vehicle working in the city as healthier than it is. A delivery vehicle runs few kilometers but wears its engine, clutch and brakes heavily from constant stop-and-go; parts tire before the calendar runs out. Conversely, a plan that looks only at the calendar ends up servicing a long-haul vehicle too early, which adds unnecessary expense. Both extremes come from the same root mistake: a single number cannot carry the diversity of a fleet.

Two intervals together

In vitaFleet you define a maintenance item by kilometers, months or both; whichever comes due first sets the due date. This small distinction makes a big difference in practice:

• On a city vehicle, months usually come due first; time-related wear is not missed.
• On a long-haul vehicle, kilometers come due first; distance-related maintenance arrives right on time.
• The due calculation is made from the vehicle's current odometer and the last service date; since the odometer is updated from fuel entries and service records, the calculation works with current data.

The right question is not 'every how many kilometers?' but 'whichever comes first?'

Three states, a clear language

Every reminder is in one of three states:

• Overdue: the due date has passed and it generates a nightly notification.
• Approaching: it has entered the km or day threshold.
• Planned: there is time before the due date.

The threshold is also in your hands: in a reminder you define an approach threshold such as 'the last two weeks' or 'the last thousand kilometers'. This turns the 'approaching' state into a meaningful alert for every vehicle.

By rule, not one by one

Imagine fifty vehicles are on the same maintenance plan. Setting up a reminder for each of them one by one is both tiring and error-prone. There are two ways.

Service schedule

In a service schedule, you gather several tasks with their intervals into a single package. When a vehicle is added to the schedule, all the reminders are set up automatically. Changing an interval in the schedule updates the reminders of all linked vehicles. This removes the 'I updated one vehicle and forgot the other' problem.

Bulk and rule-based reminders

You choose criteria: vehicle type, brand, model, model year range and group. The number and list of matching vehicles appear instantly. For example, only minibuses, minibuses from 2015 to 2020, or, among those, only the vehicles of a specific model. If you save the rule, a reminder is opened automatically for vehicles added later, imported from Excel or GPS, or that come to match the criteria. Archived and sold vehicles are not included.

From due date to work order

A maintenance item that comes due doesn't hang in the void; it turns into a work order. Line items, labor, parts used and the supplier are gathered in a single work order. When the work order is completed, or when a service invoice is imported as a service record, the reminder moves forward automatically. For old records there is an update-from-service-records button.

Seeing early maintenance too

Just as late maintenance is a problem, maintenance done too early is a waste. If a significant part of the maintenance interval is still unused when the work is done, an early-service notification goes to the vehicle's watchers or managers, stating how early it was done. This is how you notice vehicles going to service needlessly early.

To the right person, in a single summary

The notification goes to the reminder's watcher; if there is none, to the vehicle's watchers, and if there are none, to the organization's managers. Instead of a flood of item-by-item notifications, a single summary email arrives each day. This ensures the reminder gets read, because a reminder lost among a hundred emails is useless.

Measuring compliance

The maintenance compliance report shows completion on time or late per reminder. This report reveals whether maintenance is really being done and which tasks are constantly late. Once the system is set up, the real question is not 'do the reminders exist' but 'are the reminders being followed'.

Linking service tasks to a catalog

If the language of maintenance is not consistent, reports are inconsistent too. If an oil change is written as 'oil service' in one place and 'engine oil' in another, the same job is gathered under two separate headings. The service task catalog solves this: you define jobs such as oil change, air filter and tire rotation once, with clear and consistent names. Work order line items and maintenance reminders are selected from this catalog; reports are grouped by these names.

If you give a task a default km or month interval, the interval comes ready when a reminder is set up with that task; it can still be changed per vehicle. If you enter an estimated labor time and cost, these values come pre-filled when a work order is opened, and a budget-versus-actual comparison can be made.

From inspection to fault, from fault to work order

Maintenance is triggered not only by the calendar but also by findings from the field. You define your own checklist as an inspection form, and the driver or technician fills out the form. An item marked as failed turns into a fault record; the fault turns into a work order. So the situation of 'the brake felt odd but I told no one' is tied to a record and tracked until it is closed.

Linking parts stock to maintenance

Maintenance requires parts, and if parts are missing the vehicle waits. Parts used in a work order are deducted from stock; you get an alert for a part that drops to the critical threshold. This closes the gap between the maintenance calendar and the warehouse: you can see upcoming maintenance and order the parts you will need in advance.

Not paying for work covered by warranty

Vehicle and part warranties are entered with mileage and date limits. You get a warning when opening a work order for a job under warranty; a notification is also produced before coverage ends. Paying for a repair covered by warranty is a direct loss and often nobody notices. This warning is an invisible savings item in the maintenance plan.

Setting up the maintenance budget

Because estimated costs come pre-filled in the work order and actual amounts are recorded when the work order is closed, you can see budget and actual side by side. Which task constantly exceeds the budget and which supplier quotes a higher price for the same job emerges from here. Supplier comparison is fed from the same data.

A starting plan

• Set up the service task catalog with clear names and enter the default intervals.
• Create a service schedule for the vehicles that fall under the same plan.
• Add vehicles to the schedule; let the reminders be set up automatically.
• Route notifications to the vehicle's person in charge and to managers.
• At month end, look at the maintenance compliance report and examine the tasks that are constantly late.

In the end, maintenance is done not 'when a breakdown occurs' but 'when it comes due'. Planned maintenance is both cheaper and doesn't leave the vehicle stranded in the middle of the road.