Building a preventive maintenance program that drivers actually follow

Every carrier says they do preventive maintenance. Far fewer can tell you, without looking, which trucks are overdue right now and what the last three repairs on unit 104 were.

The gap is not effort. It is that PM programs are usually built as a calendar and real trucks run on odometers.

Mileage, not dates

A truck that ran 14,000 miles last month and one that ran 3,000 do not need the same service on the same day. Calendar-based PM either over-services the parked truck or under-services the busy one, and the busy one is the one carrying your freight.

Set intervals by miles, with a calendar backstop for the things that genuinely age — DOT inspection, coolant, fluids that degrade sitting still.

Typical starting points for a day-cab or sleeper in regional work:

• A service (oil, filters, lube, basic inspection): every 20,000–25,000 miles
• B service (A plus fuel filters, more thorough inspection): every 50,000
• C service (B plus valve adjust, coolant service, deeper driveline): every 100,000–150,000
• Brakes: inspected at every A, measured and recorded, not eyeballed
• DOT annual: calendar, no exceptions

Adjust to your engines and your duty cycle. The specific numbers matter less than having them written down and driven by actual odometer readings.

Getting real odometer readings

This is where most programs quietly fail. If odometer capture depends on someone asking a driver and typing it in, readings will be sporadic and wrong.

Three ways that work, in order of reliability:

1. From the ELD, automatically. If you have telematics, the number is already there.
2. At fueling, since drivers already enter it at the pump and it comes through on the fuel card feed.
3. At every shop visit, recorded on the invoice.

Any of these beats a monthly email asking for mileage.

A breakdown report should become a record, not a ticket

Most systems treat a repair as a task: open it, do it, close it, done. A year later all you have is a line in a spend report.

What you actually want from a closed repair is four things:

• The reported symptom. What the driver said, in their words. "Pulling right and shaking over 55" is more useful than "steering."
• The root cause. What was actually wrong. Often different from the symptom, and this is the part that gets lost.
• The work performed. What was replaced or repaired, specifically.
• The mileage at service. Without it you cannot spot patterns.

With those four fields, a year of history tells you things a spend report never will: that unit 104 has had the same aftertreatment fault three times, that a particular trailer's door seals fail every winter, that one driver's trucks consistently need brake work early.

Without them, you know only that you spent $41,000 on truck 104, which is a number that makes you feel bad and tells you nothing.

Down units have to be visible everywhere

When a truck cannot run, that fact needs to reach dispatch immediately and unmistakably. Not as a note in the maintenance module that dispatch doesn't open — on the board, on the truck, wherever anyone might try to assign it.

The cost of this going wrong is specific and expensive: a load booked against a truck in a shop bay, discovered at 5am, covered by a scramble or a TONU.

Who pays, decided before the work

For owner-operators and lease drivers, most repairs involve a conversation about the split. Have it before the work is authorized, and record the outcome as a number, not a vibe.

The agreement is usually one of:

• Company pays entirely — warranty, company-caused, or goodwill
• Driver pays a fixed amount — "driver covers $200 of this tire"
• Percentage split — less common than software assumes
• Driver pays, spread over several settlements

The failure mode is always the same: the work gets done, the invoice arrives, and the split is reconstructed from memory two weeks later during payroll. By then the driver remembers a different number than the shop manager.

What to review monthly

Thirty minutes, once a month:

• Which units are overdue by miles?
• Cost per mile by unit, current quarter versus last
• Any unit with the same repair twice in six months
• Any repair over a threshold you set, with a cause written down
• Roadside inspection results, and whether any violation traces to a missed PM

The last one is the one that bites hardest. A CSA violation for something a PM would have caught is expensive twice — the fine, and the score.