How to Build a Fleet Preventive Maintenance Program From Scratch
- 2 days ago
- 7 min read
A fleet PM program that runs itself starts with the right setup. Here's a step-by-step guide to building a preventive maintenance program that actually holds up at scale.
Most fleet PM programs start the same way: someone builds a spreadsheet with service intervals, sets a calendar reminder to check it, and calls it a program. It works reasonably well when the fleet is small, the team is consistent, and nothing unexpected happens. It falls apart when any of those conditions change.
A PM program that holds up at scale — across dozens of vehicles, multiple vehicle classes, different maintenance staff, and the daily chaos of an active fleet operation — needs to be built differently. It needs to be structured, automated where possible, and connected to the real operational data driving your vehicles.
This guide walks through the steps to build that kind of PM program, whether you're starting from nothing or rebuilding a program that's lost reliability over time.
01 Step 1: Audit your current maintenance state
Before you can build a forward-looking PM program, you need an honest picture of where you are today. This audit serves two purposes: it reveals the gaps you're working from, and it gives you a baseline to measure improvement against.
For each active vehicle in your fleet, answer:
When was the last oil change, and what was the odometer at that service?
Is there a configured PM schedule for this vehicle — and if so, is it in writing somewhere accessible?
What is the current odometer reading, and does it reflect real mileage or a manually entered figure that may be outdated?
Are there any open issues, outstanding repairs, or deferred services on this vehicle
When is the next state inspection, DOT inspection, or emissions check due?
This audit is often uncomfortable. Gaps in service history, vehicles without configured schedules, and mileage figures nobody trusts are common findings. That's the point — you can't fix what you can't see.
For fleets connecting to EKOS, this audit also serves as the data-gathering phase before setup: you'll need current odometer readings, last service dates, and service interval targets for each vehicle to configure PM schedules correctly.
02 Step 2: Define your asset classes and service types
Not all vehicles need the same PM program. A school bus running 60,000 miles per year in urban stop-and-go service has different maintenance needs than a pickup truck used occasionally by field staff. Building effective PM requires defining your asset classes and the service types that apply to each.
Asset classes
Group your vehicles by type and duty cycle. Common groupings for municipal and school district fleets:
Light-duty vehicles
Cars, vans, and pickups under Class 4.
Medium-duty trucks
Class 4–6 service trucks, utility vehicles, box trucks.
Heavy-duty trucks
Class 7–8 vehicles, dump trucks, tankers, large service vehicles.
School buses
Class-specific with state-mandated inspection requirements.
Non-road equipment
Generators, trailers, pumps, mowers — serviced by engine hours rather than mileage.
Vehicles within the same class often share PM schedules, which simplifies setup significantly.
Service types
For each asset class, define the service events that belong in the PM program. A standard light-duty vehicle PM program typically includes:
Engine oil and filter change
Air filter inspection and replacement
Cabin air filter replacement
Fuel filter replacement (where applicable)
Tire rotation and pressure check
Brake inspection
Belt and hose inspection
Fluid level checks and top-offs
Battery test
Annual state safety inspection
Heavy-duty trucks and buses require additional items: transmission service, differential fluid, coolant flush, air brake inspection, fifth wheel lubrication, and manufacturer-specific major service milestones.
03 Step 3: Set PM intervals for each service type
Every service type needs a trigger: the condition under which the service becomes due. Fleet PM intervals typically use one or more of three trigger types:
Mileage-based intervals
The most common trigger for on-road vehicles. Examples:
Oil change: every 5,000 miles (synthetic) or 3,000–4,000 miles (conventional)
Tire rotation: every 6,000–8,000 miles
Brake inspection: every 12,000 miles
Major service: every 30,000 or 60,000 miles
Mileage-based intervals require accurate, current odometer data. When EKOS connects to Samsara, Geotab, or Teletrac Navman, odometer readings update automatically — so mileage-based intervals are always triggered by real vehicle data, not manually entered figures. EKOS GPS & Telematics
Engine-hour-based intervals
Used for equipment where service need correlates with operating time rather than distance. Examples:
Generator oil change: every 100–150 engine hours
Hydraulic fluid service: every 500 engine hours
Equipment major service: every 1,000 engine hours
Engine hour data flows from telematics integrations the same way odometer data does. For mixed fleets managing both on-road vehicles and equipment, EKOS handles both interval types in the same system.
Calendar-based intervals
Some services are triggered by time rather than use. Examples:
Annual state safety inspection
Annual emissions inspection (where required)
Coolant flush: every two years regardless of mileage
Battery replacement: on a time-based schedule for high-reliability applications
Seasonal services: winter tire changeover, antifreeze concentration check
Calendar-based intervals are often combined with mileage or hour triggers — "whichever comes first" — to catch high-utilization vehicles that hit time-based service needs before their mileage intervals trigger.
04 Step 4: Configure advance notification windows
A PM trigger that fires exactly when a service becomes due gives you zero lead time to schedule the work. Most PM programs work better with an advance notification window — a threshold before the actual interval where the service appears as "upcoming" in the maintenance queue.
Common advance notification settings:
Mileage-based: 500 miles before the service interval triggers
Engine hours: 10–25 hours before the interval triggers
Calendar-based: 30 days before the service due date
The right window depends on your scheduling flexibility. Fleets where vehicles can be pulled from service on short notice can use shorter windows. Fleets where scheduling requires coordination with operations — school buses that can't be pulled during school hours, utility trucks committed to active job sites — benefit from longer advance windows.
In EKOS, advance notification windows are configured per service type and generate upcoming service alerts that appear in the fleet manager's dashboard before services become due. The goal is giving your team enough lead time to schedule work proactively rather than reactively.
05 Step 5: Connect your PM program to work orders
A PM schedule that generates notifications is useful. A PM schedule that automatically generates work orders is operational infrastructure. The difference is whether someone has to manually create a work order every time a service comes due, or whether the system creates a draft that just needs review and dispatch.
In EKOS, when a PM service triggers, it creates a work order pre-populated with the vehicle, the service type, and the scheduled tasks. The work order is assigned to the appropriate technician and appears in their queue on any device. When the service is complete, the technician closes the work order from their phone — labor, parts, and notes all captured — and the PM interval resets automatically for the next cycle. EKOS Work Orders
"This connection between PM scheduling and work order execution is what makes a PM program self-sustaining rather than dependent on someone manually tracking what's been done and what's next." - EKOS Fleet Maintenance
06 Step 6: Assign ownership and accountability
A PM program without assigned ownership is a suggestion, not a system. Every element of the program needs a clear owner:
Who is responsible for reviewing the upcoming services queue each week?
Who approves work orders and assigns them to technicians?
Who is responsible for ensuring work orders close with complete documentation before a vehicle is returned to service?
Who reviews PM compliance monthly and flags vehicles that are overdue?
In smaller fleet operations — a school district with one fleet manager and two mechanics, for example — these roles may all belong to the same person. What matters is that they're explicitly assigned, not assumed.
07 Step 7: Track compliance and iterate
A PM program improves over time when it's measured. The key metric is PM compliance rate: the percentage of services completed on time (within the configured interval threshold) vs. services completed late or missed.
A compliance rate below 85% typically indicates one of three problems: intervals are set too aggressively for the actual fleet utilization, the advance notification window is too short to allow scheduling, or there's a workflow breakdown between PM triggers and work order completion.
Reviewing compliance quarterly — and adjusting intervals, notification windows, or workflows based on what you find — is what turns a PM program from a setup project into a continuous improvement practice.
Common PM program setup mistakes to avoid
Setting intervals based on manufacturer recommendations without adjusting for actual duty cycle. A vehicle in severe-duty service (frequent starts, short trips, dusty environment) needs shorter intervals than the owner's manual assumes.
Configuring PM schedules once and never revisiting them. As vehicles age, intervals should be reviewed and often shortened.
Treating PM compliance as a fleet manager responsibility rather than a shared operational one. When operations teams understand why PM matters — fewer breakdowns, more vehicles available — compliance becomes a shared interest.
Not connecting PM to actual vehicle data. A PM schedule running on manually entered mileage that's two weeks stale is not a PM schedule — it's a guess.
Frequently asked questions
What is a fleet preventive maintenance program?
A fleet preventive maintenance program is a structured system for scheduling, tracking, and completing routine vehicle maintenance before problems develop. It defines service types, intervals (mileage, engine hours, or calendar), notification windows, and the workflow for executing and documenting services.
How do I set fleet maintenance intervals?
Start with manufacturer recommendations for each vehicle class, then adjust based on actual duty cycle. High-utilization vehicles in demanding conditions (urban stop-and-go, dusty environments, frequent short trips) typically need shorter intervals than standard recommendations. Review and adjust intervals annually based on actual maintenance history and failure patterns.
How does fleet management software help run a PM program?
Fleet management software automates the most failure-prone parts of a PM program: mileage tracking, interval monitoring, service notifications, and work order creation. When connected to GPS telematics, mileage updates automatically — eliminating the manual entry that causes PM programs to drift. When PM triggers connect to work orders, services happen because the system drives them, not because someone remembered to check.
THE BOTTOM LINE
Build it once. Let the data drive it.
EKOS automates every step of your PM program — mileage updates from Samsara, Geotab, or Teletrac Navman, automatic service triggers, draft work orders, and compliance tracking, all in one place.
ONE PLATFORM, FUEL AND FLEET
Build your PM program in EKOS.
EKOS automates every step of your PM program — mileage updates from Samsara, Geotab, or Teletrac Navman, automatic service triggers, draft work orders, and compliance tracking, all in one place. Start your 30-day free trial.
