Fleet Preventive Maintenance Program: How to Set One Up for 5 to 30 Vehicles

Most small fleets already do preventive maintenance. Vans get oil changes, trucks get inspected, and somebody remembers the trailer bearings most years. What they don’t have is a program: a written schedule, one person who owns it, and records that show what was done and what is due next. Without that, PM depends on whoever happens to notice the sticker on the windshield.

This guide is for fleets of roughly 5 to 30 vehicles, often a mix of vans, pickups, a box truck or two, trailers, and some hour-meter equipment, with no full-time fleet manager. It covers how to set up the program, a tiered interval table with typical numbers, how to split the jobs, a worked example of the yearly workload, and which federal records rules apply to which vehicles.

What a PM program actually includes

A schedule on its own is not a program. A working program has six parts:

1. An asset list. Every vehicle, trailer, and machine with its unit number, year, make, model, VIN or serial, and how it is measured: miles, hours, or both.
2. Service intervals for each asset. Built from the manufacturer’s schedule and grouped into tiers, each with a mileage or hour limit and a calendar limit.
3. An owner. One named person who checks what is due every week and books the work. On a 10-vehicle fleet that is a few hours a week, not a job title.
4. Meter readings. Odometers and hour meters recorded on a fixed day, so due dates can be worked out.
5. Defect reporting. A way for drivers to flag problems between services, and a rule for what takes a vehicle off the road.
6. Records and a review. Every service logged with date, reading, work done, and cost, and a quarterly look at what is breaking between services.

The pages that rank for this topic tend to stop at that list. The rest of this guide puts numbers on it.

Step 1: Build the asset list and group by class

Start with a spreadsheet row per asset. Add the current odometer or hour reading, the date and reading of the last oil change, and the last known date of anything bigger (brakes, transmission service, coolant). If you don’t know when something was last done, treat it as due now; a cheap fluid change beats guessing.

Then group assets into classes that share a schedule: gas cargo vans, diesel box trucks, half-ton pickups, trailers, skid steers. A fleet of 15 units usually has three to five classes. You set intervals once per class and adjust individual units only when their duty is very different, such as a van that tows every day.

Step 2: Set tiered intervals (A, B, and C services)

Most fleets organize PM into tiers. Each tier includes everything in the tier below it, so a B service is an A service with more work on top. No regulation defines the tiers; you set the contents and intervals from each manufacturer’s schedule. The table below is a typical starting shape for light and medium-duty vehicles in normal service, not a universal standard. Check your owner’s manual for each class.

The ranges are wide on purpose. Ford’s 2015 Transit owner’s manual, for example, lets the Intelligent Oil-Life Monitor set the oil change, with a normal range of 7,500 to 10,000 miles for highway commuting with moderate loads and no extended idling, and notes that intervals generally drop as use gets more severe. A van doing short urban delivery stops lands at the low end; one cruising the interstate lands at the high end.

Three rules keep the tiers honest:

• Every interval gets a calendar partner. A pickup that drives 6,000 miles a year still needs oil and brake fluid on time. Due at whichever comes first.
• Hour-meter equipment runs on hours. A skid steer or generator in the same fleet follows its own manual in operating hours, with the same calendar backstop. See our heavy equipment maintenance schedule for hour-based tiers.
• Severe duty shortens everything. Towing, heavy idling, stop-and-go delivery, dusty job sites, and extreme heat or cold all justify the manual’s severe-duty schedule.

Step 3: Give the program an owner and split the jobs

In a small fleet, the program fails at the handoffs, not at the wrench. Write down who does what. A simple split for a business without a fleet manager:

Put a backup next to the program owner’s name. The most common way a small-fleet program dies is the one person who knew the schedule going on vacation for two weeks.

Worked example: a 12-vehicle fleet’s PM year

Take a contractor with 12 units: 8 gas cargo vans, 2 diesel box trucks, 1 pickup, and 1 skid steer. Using intervals from the table above and each class’s typical use:

What the numbers tell you:

1. It is about three services a month. That is small enough to book one fixed slot a week with your shop and fill it from the due list, instead of calling around every time a sticker comes due.
2. The vans drive the workload. Eight vans produce more than two-thirds of the visits. If you have spare vehicles, keep one van as the rotation spare so a van in the shop doesn’t cancel a job.
3. Downtime is plannable. At half a day per service, 37 visits is about 18 vehicle-days a year. Unplanned breakdowns cost more days than that and arrive on the worst possible morning.
4. The pickup and the skid steer are the ones that get forgotten. They don’t rack up miles, so nothing reminds you. The calendar limit has to.

On a spreadsheet, this means 12 rows, each with a different interval, and someone recalculating the next due mileage every time a reading changes. That works until the week it doesn’t.

Records and FMCSA rules for regulated vehicles

Federal maintenance rules apply to commercial motor vehicles as defined in 49 CFR 390.5, which includes vehicles with a gross vehicle or combination weight rating of 10,001 pounds or more used in interstate commerce. In the example above, the box trucks likely qualify; whether the vans do depends on their weight rating and where they run. Check the rating on each vehicle’s door-jamb label, and check your state’s rules for intrastate work.

For vehicles that are covered, the main requirements are:

• A systematic program. 49 CFR 396.3 requires carriers to systematically inspect, repair, and maintain the vehicles they control. It does not set intervals; your program does.
• Records per vehicle. The same section requires, for each vehicle controlled for 30 consecutive days or more: identification (unit number, make, serial number, year), a means of showing the nature and due dates of inspections and maintenance, and a record of inspections, repairs, and maintenance with their dates and nature.
• Retention. Keep those records for 1 year where the vehicle is housed or maintained, and for 6 months after it leaves your control.
• Driver vehicle inspection reports. Under 49 CFR 396.11, drivers report defects in writing at the end of each day’s work; no report is required if none are found, and carriers running a single commercial vehicle are excluded. The carrier repairs safety defects and certifies the repair before the vehicle runs again, and keeps the reports for three months.
• Annual inspection. Each covered vehicle needs a periodic inspection at least every 12 months under 49 CFR 396.17, and 49 CFR 396.21 requires the inspection report to be kept for 14 months.

Note the second record requirement: a means of showing when maintenance is due. A shoebox of invoices shows what was done; it doesn’t show what is next. A PM schedule with due dates is part of the record. For vehicles outside these rules, the same records still pay off at resale and in warranty claims. If you need the inspection side, our free DOT vehicle inspection checklist covers the walkaround.

A 30-day rollout plan

You don’t need a quarter-long project. For a fleet under 30 units:

1. Week 1: inventory. List every asset, its current reading, and its last known services. Pull the scheduled maintenance pages from each owner’s manual.
2. Week 1: classes and intervals. Group assets into classes and fill in A, B, and C intervals for each, with calendar limits.
3. Week 2: catch up. Anything overdue or unknown gets an A service now. This resets every vehicle to a known starting point.
4. Week 2: name the owner and backup. Write the role table above on one page and hand it to the people in it.
5. Week 3: start the weekly reading. Pick a day. Drivers send odometer or hour readings; the owner updates the due list and books the week’s slot.
6. Week 3: set up defect reporting. A paper form in each vehicle, a group text, or software. The rule that matters: safety defects take the vehicle out of service until fixed.
7. Week 4: log the first services properly. Date, reading, work done, parts, cost, who did it, and the invoice attached. Check that next due dates updated.
8. After 90 days: first review. Look at what broke between services. Repeat brake jobs on one van, or batteries dying in winter, mean an interval or a checklist needs to change.

If you’re starting in Excel, our preventive maintenance schedule template has columns for mileage, hour, and date intervals, and the fleet maintenance spreadsheet tracks history and cost per vehicle. When several people start logging work, read maintenance spreadsheet vs software before the sheet gets out of hand.

How to tell if the program is working

Skip the 20-metric dashboard. Four numbers, checked quarterly, tell a small fleet almost everything:

• PM completion on time: services done before they were overdue, as a share of services due. Aim for nearly all of them; a pattern of late services means the booking routine is broken, not the intervals.
• Unplanned repairs per vehicle: roadside breakdowns and shop visits that weren’t scheduled. This should drop over the first year.
• Maintenance cost per vehicle: total service and repair spend per unit per quarter. The unit that keeps climbing is your next replacement.
• Repeat repairs: the same fix on the same vehicle within a few months. That is either a bad repair or an interval that is too long.

Common mistakes

• One schedule for every vehicle. A diesel box truck, a gas van, and a skid steer don’t share intervals. Set them per class.
• Mileage only. Low-use vehicles and seasonal equipment age on the calendar. Fluids, batteries, and tires don’t care that the truck sat.
• No owner. “Everyone keeps an eye on it” means nobody books the shop.
• Records that only show the past. Invoices without a next-due date are history, not a program, and for regulated vehicles the due dates are part of what 396.3 asks for.
• Ignoring driver reports. If defect reports disappear into a glovebox, drivers stop filing them. Close every report with what was done and when.
• Never revisiting intervals. The manual is the starting point. Your own repair history is what tells you whether to shorten an interval for your routes and drivers.