A mixed fleet isn't one maintenance schedule — it's a dozen running at once. The Freightliner keeps Detroit's clock, the Kenworth runs PACCAR's idle-based interval, the Volvo's drain depends on its oil spec, the refuse truck wears by engine hours, and the delivery van by miles and months. The single most common and most expensive mistake in mixed-fleet maintenance is forcing one generic PM template onto all of them — it over-services the light vehicles and quietly under-services the heavy ones. This guide shows how to schedule a many-make fleet the right way: by asset class, by the correct trigger, and balanced so the shop isn't slammed. Start free and put every make on its own interval.

Mixed Fleet · Miles & Engine Hours · PM Planning

Mixed Fleet Maintenance: Preventive Maintenance Scheduling & Planning Guide

Every make runs its own clock — the trick is one board that honors all of them. Truck Inspection & Maintenance Management Software templates each asset by make, engine and duty, schedules by miles or hours whichever lands first, and keeps the whole mixed fleet on one record.
VehicleEngineOil intervalScheduled by
Freightliner CascadiaDetroit DD15~45–75kMiles
Kenworth T680PACCAR MX-1350–75k by idleMiles + hours
Volvo VNLD13up to 90k by oilMiles
Refuse / vocationalVariesby run timeEngine hours
Delivery vanLight-duty5–10kMiles + months

Why One Template Fails a Mixed Fleet

A fixed mileage or calendar rule works only when every asset is used the same way — and a mixed fleet breaks that assumption within weeks. Force one interval on everything and you do two kinds of damage at the same time.

Over-servicedThe light vehicles and low-mileage units get pulled in too often — paying for oil, filters and labor the engine didn't need yet, and burning bay time.
Under-servicedThe heavy, hard-working units blow past the interval their duty cycle demands — and that's where the breakdowns, roadside events and major repairs come from.

Miles, Hours or Calendar: Pick the Right Trigger

The fix starts with choosing what actually measures wear for each asset. Mileage, engine hours and the calendar each fit a different kind of unit — and the best practice is to set a primary trigger and a backstop, then service on whichever comes first.

Asset typePrimary triggerBackstopTypical range
Highway tractorsMilesCalendar25k–75k by make & duty
Delivery vansMilesHours5k–10k mi
Refuse / vocationalEngine hoursMilesby run time
Construction equipmentEngine hoursCalendar200–500 hrs
Generators / APUsEngine hoursCalendar150–300 hrs
Low-use / specialtyCalendarHours6–12 months
Ranges are planning starting points; the real interval bakes in both the OEM baseline and the truck's actual duty cycle. Miles suit steady over-the-road distance; engine hours suit idle-, PTO- and jobsite-heavy work; the calendar catches low-use units that still age.

Why Engine Hours Catch What the Odometer Misses

This is the heart of a mixed fleet. An odometer says nothing about a truck that barely moves but idles for hours on a dock or a jobsite — yet that run time is real wear. An hour of idle is roughly 25 to 30 miles of engine wear that never shows on the dash. Schedule an idle-heavy or PTO-driven unit by miles alone and it's chronically overdue in a way the mileage never reveals; add the engine-hour trigger and service lands when wear actually demands it. Book a demo to schedule by miles and engine hours together.

Build It in Four Moves

A mixed-fleet program isn't a stack of reminders — it's a system you assemble once and run. Four moves take you from a scattered roster to a schedule that holds.

1
Group into classesSort the fleet by make, engine and duty — Class 8 line-haul, vocational, vans, equipment — not one undifferentiated list.
2
Set the triggersGive each class its primary trigger and backstop — miles, hours or calendar — on whichever-comes-first.
3
Attach task librariesBuild the A, B and C service task lists per class, so the right work appears at each interval automatically.
4
Track the KPIsWatch PM compliance and planned-vs-reactive by class, so you see which part of the fleet is slipping.

Balance the Workload So the Shop Isn't Slammed

Getting the intervals right is half the job; the other half is spreading the work. When ten units come due the same week, the bay backs up and PMs get deferred — which is how a well-planned schedule still turns reactive. Forecast the service windows and stagger them so each week's load fits the bays you have.

PM hours per week — leveled across the month
W1
W2
W3
W4
Un­planned
Leveled weeks keep the bays full but not buried. The tall bar is what a mixed fleet looks like with no staggering — everything due at once.

Many Makes, Many Clocks, One Record

A mixed fleet doesn't need one schedule — it needs one place that runs all of them. Put every asset's interval, trigger and history under its VIN, and the Freightliner, the Kenworth, the Volvo and the vans each stay on their own clock without a stack of spreadsheets.

The Payoff: Fewer Breakdowns, Lower Cost

The discipline pays off in the numbers that matter. The U.S. Department of Energy's maintenance best-practices work has reported that a predictive, planned approach can eliminate on the order of 70 to 75% of breakdowns and cut maintenance costs roughly 25 to 30% versus running to failure. The mechanism is simple: a reactive repair costs several times the same job done planned, so every unit you move from breakdown to scheduled service compounds into lower cost per mile across the fleet. On a mixed fleet, that only happens when each asset is on the interval its own wear demands. Start free and move your fleet from reactive to planned.

Why Mixed Fleets Run PM in Software

Per-asset templatesEach make, engine and duty on its own interval — never one generic template stretched across the fleet.
Miles and hours togetherPrimary trigger plus backstop, serviced on whichever comes first, so idle-heavy units don't slip.
Meter captureOdometer and engine-hour reads kept current per unit, so interval scheduling isn't a guess.
Capacity-aware staggeringService windows forecast and spread, so the bays stay full but not buried.
Defect to work orderAn inspection defect becomes a work order automatically, nothing lost between driver and bay.
Compliance by classPM completion and reactive ratio tracked per vehicle class, so you see exactly what's slipping.

Frequently Asked Questions

1
Why can't I use one PM schedule for my whole fleet?

Because the assets wear differently. A light van, a line-haul Class 8 and an idle-heavy vocational truck don't share an interval or even a trigger, so one schedule over-services the light units and under-services the heavy ones at the same time. Per-class templates fix both. Book a demo to template each class.

2
Should I schedule by miles or engine hours?

Both, with one as the primary. Miles fit steady over-the-road trucks; engine hours fit vocational, refuse, PTO- and idle-heavy units where run time, not distance, drives wear. Set a primary trigger and a backstop, and service on whichever comes first. Book a demo to set miles-and-hours triggers.

3
How do I keep the shop from getting overloaded?

Forecast each unit's service window and stagger the PMs so each week's workload fits your bay capacity, rather than letting ten units come due at once. Capacity-aware scheduling keeps the bays productive and stops deferred PMs from piling into a backlog. Book a demo to see workload leveling.

4
How do I start a mixed-fleet PM program?

Four moves: group the fleet into classes by make, engine and duty; set each class's miles, hours or calendar triggers; attach A/B/C task libraries per class; then track PM compliance and reactive ratio by class. Build it once and the schedule runs itself. Book a demo to build your program.

Every make · Right trigger · One board

Run a Many-Make Fleet Like It's One

Truck Inspection & Maintenance Management Software templates each asset by make, engine and duty, schedules by miles or engine hours whichever comes first, balances the shop's workload, and keeps the whole mixed fleet on one audit-ready record.

No credit card required. Free for up to 3 trucks. Built for FMCSA-compliant fleets.