Preventive maintenance schedules that actually get followed

Almost every fleet has a preventive maintenance schedule. Far fewer have one that gets followed. The gap is rarely about commitment — it is about friction: schedules built on calendar guesses instead of real usage, work orders that live in someone’s head, and no visibility into what was skipped. Reactive repairs cost three to nine times more than the planned service that would have prevented them, and that is before counting the towing, the missed jobs, and the rental vehicle. Fixing PM compliance is usually the highest-ROI project in fleet operations.

Start by matching the trigger to the component. Engine oil and filters wear with engine time and distance, so they should trigger on miles or engine-hours — not months. Equipment that idles heavily (utility trucks running PTOs, refrigerated units) needs engine-hour triggers, because a truck can accumulate a year of engine wear in six calendar months while barely moving. Brake inspections, DOT inspections, and coolant changes fit calendar or mileage intervals. A schedule with the wrong trigger either services too early (wasted money) or too late (the failure you were trying to prevent).

The single biggest unlock is feeding the schedule with automatic odometer and engine-hour readings from your telematics platform instead of asking drivers or technicians to report them. Manual readings arrive late, get transposed, and stop entirely during busy weeks — and a PM schedule running on stale odometer data is fiction. With live readings, a service due at 60,000 miles can generate its work order automatically at 59,000, with enough lead time to schedule the bay and order parts before the vehicle is overdue.

Design the workflow so the easiest path is the compliant one. Every PM trigger should produce a work order with the vehicle, the service checklist, the due date, and the parts list already attached. Give shop managers a single queue sorted by urgency, and give operations a forecast view — what is coming due in the next two weeks — so vehicles can be scheduled into the shop during natural downtime instead of being pulled off jobs. The fleets with the best PM compliance treat scheduling as a dispatch problem, not a maintenance problem.

Close the loop with driver inspections. DVIR defects should flow into the same work-order system as PM tasks, so a driver-reported soft brake pedal is triaged the same day rather than rediscovered at the next scheduled service. Drivers stop reporting defects when nothing happens to their reports; showing them the repair status of what they flagged is the cheapest driver-engagement program you will ever run.

Measure the program with two numbers. PM on-time percentage — services completed within their window divided by services due — is your compliance score; healthy fleets run above 90%. Planned-versus-unplanned maintenance ratio tells you whether the program is working; as PM compliance climbs, unplanned repairs should fall toward 20–30% of total maintenance events. Review both monthly, by vehicle group. When a group’s unplanned ratio rises, the schedule is wrong for that duty cycle — tighten the intervals before the breakdowns teach you the same lesson expensively.

Finally, build slack into the system. Define soft and hard windows: a service due at 10,000-mile intervals might have a soft window opening at 9,000 and a hard stop at 11,000. The soft window gives schedulers room to be smart; the hard stop gives managers a clean, non-negotiable escalation point. Schedules fail when every service is either "whenever" or "right now" — graduated urgency is what makes a PM program livable for the people running it.