Preventive maintenance schedule for fleet vehicles: by kilometers, engine hours, and date

Why you need a written maintenance schedule

Most expensive vehicle failures don't happen suddenly. An engine wears out because the oil stayed in twice as long as it should have; a transmission overheats because its fluid hasn't been checked in two years; brake discs are replaced outright because worn pads were ignored until metal ground on metal. In each case, a small and cheap service came due and nobody noticed.

A preventive maintenance schedule is the tool that prevents this: a list of service items, each with a clear due interval, and a record per vehicle showing when each item was last done and when it is next due. For one private car, an oil sticker on the windshield is enough. For a fleet of dozens of vehicles with different models, ages, and duty cycles, memory and stickers don't scale — a written, then automated, schedule becomes a precondition for disciplined operations.

The schedule has a second benefit that matters just as much: it turns maintenance from a reaction into a plan. Instead of a vehicle breaking down mid-trip and being towed to the nearest workshop at any price, it goes in on a day you choose, with parts ready and a replacement vehicle scheduled in advance.

Three due triggers: kilometers, engine hours, and date

Every service item is due by one of three measures, and many items are tied to more than one on a "whichever comes first" basis:

• Kilometers: the most familiar measure for road vehicles — oil changes, filters, tire rotation. It suits vehicles that cover regular distances.
• Engine hours: the right measure for equipment and trucks that work while stationary: concrete mixers, cranes, reefer units, and vehicles that spend hours idling. An engine running ten hours a day on a construction site may cover fifty kilometers, yet it uses up its oil as if it had covered hundreds.
• Date: for items that age with time rather than use — coolant, brake fluid, the battery — plus regulatory documents such as insurance, registration, and periodic inspection.

The common mistake is using kilometers alone for the whole fleet. A vehicle that works long hours while stationary looks "far from due" in the odometer record, while its engine is already past due. That is why each vehicle class gets its own primary measure — a truck, a piece of equipment, and a sales car are not managed by one rule.

A preventive maintenance schedule: items and reference intervals

The table below covers the core items for light and medium fleet vehicles. The figures are common reference ranges that vary widely across models, oil types, and engines; always check the manufacturer's manual, and use the shorter end under severe service.

Diesel vehicles need extra attention on two items: the fuel filter and water separator, because any contamination or moisture in the fuel goes straight to high-precision injectors; and regular oil changes, because diesel engines produce more soot that ends up in the oil. On trucks and equipment, the engine-hour meter becomes the most accurate reference for most items.

Severe service: why intervals are shorter in Saudi Arabia

Manufacturer manuals usually carry two schedules: "normal service" and "severe service," with shorter intervals. Most manuals define severe service to include high temperatures, dusty roads, frequent stop-and-go driving, long idling, and towing or heavy loads. Most fleets in the Kingdom meet several of these conditions at once.

• Heat: long summers raise oil and coolant temperatures and stress batteries and tires.
• Dust: clogs air and cabin filters faster, and reaches the engine if the filter is neglected.
• Idling: waiting at gates and loading queues with the A/C running adds engine hours without kilometers — covered in detail in Engine idling: the hidden cost.
• Urban delivery: dozens of stops a day mean brakes and transmissions work far harder than the distance suggests.

The practical outcome: if your fleet runs in these conditions, build your schedule on the shorter end of the ranges, then adjust it with data — not impressions — after a few months of actual records.

From a paper schedule to a plan computed from real measurements

An Excel sheet or workshop logbook works until the fleet grows. Then the same problems show up everywhere: odometer readings are entered by hand, late or not at all; due dates are estimated; and nobody knows three vehicles have missed their oil change until one of them breaks down.

In Pixa's Maintenance & Workshop module, the plan is built on what the vehicle itself measures:

• Plans by kilometers, engine hours, and date: intervals are computed from actual vehicle readings, not manual entry, so the next due service is known for every item on every vehicle.
• Reminders before due: on the channels your team actually reads — including WhatsApp — through the rules and alerts engine.
• Complete work orders: costs, parts, attachments, and a service history per vehicle that answers "when was it last serviced, and for how much?"
• Document reminders: registration, insurance, periodic inspection, and driver licenses on a "due soon" board.
• Built-in vendor market: spare-part RFQs, quote comparison, purchase orders, and warranties.

Once maintenance is linked to the rest of your fleet data, patterns emerge that a paper schedule never shows: a vehicle whose fuel consumption rises before a recurring fault, or a model whose brakes wear faster than others on a particular route. That reading becomes possible when maintenance, trip, and fuel records live in one place and come out of reports in both Hijri and Gregorian calendars.

Common mistakes that break a maintenance schedule

Even fleets with a written schedule tend to make the same mistakes, all of which leave the schedule on paper and absent from the workshop:

• One schedule for every vehicle: copying sedan intervals onto a diesel truck or site equipment means some vehicles are serviced too early and others are always overdue.
• Stale odometer readings: if mileage is collected once a month, every due calculation built on it can be a full month late.
• Reminders with no owner: an alert sent to a shared inbox nobody reads is no better than no alert. Every reminder needs a named person who receives it and is accountable for it.
• Undocumented service: an oil change that never makes it into the vehicle record will look like it never happened at the next calculation — so work is repeated, or trust in the whole schedule is lost.
• Ignoring documents: a mechanically sound vehicle with expired insurance or periodic inspection is off the road by regulation, so document dates belong in the same schedule.

What these mistakes share is that they are data-entry and follow-up failures, not knowledge failures. Everyone knows the oil needs changing; nobody has an accurate, current number saying when. That is why schedules fed directly by vehicle readings succeed, and schedules that wait for someone to remember to enter data fail.

How to get started in a week

• Days 1–2: group your fleet into classes (light vehicles, trucks, equipment) and set each class's primary measure: kilometers or hours.
• Day 3: collect the manufacturer manuals for each model, and adopt the severe-service schedule where it applies.
• Day 4: record the last service of each item on each vehicle, even as an estimate, so calculations start from a known point.
• Day 5: decide who receives reminders, and how many kilometers or days before due.
• After that: review the records monthly, and shorten or extend intervals based on what the data shows, not on habit.

If you want to see a maintenance plan computed from your fleet's actual odometers instead of manual spreadsheets, contact us for a live demo on your own vehicle data.