Reactive maintenance is expensive: you pay overtime, premium parts and the cost of unplanned downtime every time something fails mid-job. A preventive maintenance program flips that, planning work before failure so assets stay available and costs become predictable. The hard part is not the idea, it is building a program that holds up across every asset class and keeps improving instead of going stale.
This guide is for maintenance managers, asset managers and operations leads setting up a program from the ground up. It covers building the asset base, ranking assets by criticality, choosing the right maintenance strategy per class, writing task lists, scheduling the work and measuring the result. It is broader than a single fleet maintenance schedule and applies to all your plant and equipment, not just vehicles.
Before you start
You need a complete asset register before you can plan any maintenance, so build that first if it does not exist. Gather the OEM service manuals for your main asset types and have a preventive maintenance schedule template to work from. Decide who owns the program and who does the work, in-house or contracted, before you load up the schedule.
Step-by-step setup
1. Build a complete asset register
A preventive maintenance program is only as good as the asset list behind it. Capture every asset you intend to maintain with its make, model, serial number, location, current meter reading and service history. Without a complete register you cannot schedule work, forecast parts or measure reliability. Start here even if it means a short delay. Our asset register guide walks through it.
2. Rank assets by criticality
You cannot maintain everything to the same standard, so rank assets by how badly a failure would hurt: safety, downtime cost, replacement cost and whether a backup exists. Focus the heaviest preventive effort on the critical few. Low-criticality, low-cost items can often run to failure deliberately rather than absorb scheduled effort.
3. Choose a maintenance strategy per asset class
Decide how each asset class is maintained: time-based (every month), usage-based (every 250 hours or 10,000 km), condition-based (triggered by readings or inspection) or run-to-failure for non-critical items. Critical assets often justify usage or condition-based maintenance; simple assets suit fixed time intervals. Document the choice and the reasoning.
4. Define intervals and write task lists
For each asset, set the trigger from the OEM schedule and, where you have it, your own failure history. Write a clear task list for each service type covering the steps, parts, consumables, tools and the estimated labour time. Standard maintenance procedures make the work repeatable regardless of who performs it and feed accurate parts forecasting.
5. Schedule, assign and resource the work
Load every asset and its triggers into a schedule so due and overdue work is visible. Assign each job to internal technicians or external workshops, and stagger the plan so you are not pulling too many assets out of service at once. Set automated reminders ahead of the due date so parts can be ordered and downtime booked.
6. Capture completion, then measure and improve
Record every completed job with the date, meter reading, parts used, labour and findings. Track KPIs such as PM compliance (planned work done on time), the planned-to-unplanned work ratio and mean time between failures. Review the data each quarter and adjust intervals and task lists so the program tightens over time instead of going stale.
Preventive maintenance strategies
| Strategy | Trigger | Best for |
|---|---|---|
| Time-based | Fixed calendar interval (e.g. every month) | Assets with steady, low usage; statutory inspections |
| Usage-based (meter) | Hours, kilometres or cycles run | Plant and vehicles where wear tracks usage |
| Condition-based | Readings or inspection (vibration, oil, temperature) | Critical assets where condition can be monitored |
| Run-to-failure | None; repair or replace on failure | Low-cost, low-criticality, easily replaced items |
Most programs blend these: apply the shorter of a time or usage trigger to important assets, layer condition monitoring on the critical few, and consciously choose run-to-failure for the rest. Our types of maintenance guide explains how preventive, predictive and reactive maintenance fit together.
Measuring success (KPIs)
| KPI | What it tells you |
|---|---|
| PM compliance | Share of scheduled preventive work completed on time |
| Planned vs unplanned ratio | How much work is proactive; should trend toward planned |
| Mean time between failures (MTBF) | Reliability; rising MTBF means fewer breakdowns |
| Maintenance cost vs asset value | Efficiency of spend relative to what is maintained |
Track a small set consistently rather than a large dashboard nobody reviews. A program that improves PM compliance and shifts work from unplanned to planned is doing its job.
Common mistakes to avoid
- Starting without a complete asset register, so the schedule has gaps from day one.
- Maintaining everything to the same level instead of ranking by criticality.
- Over-maintaining low-value assets and starving the critical few of attention.
- Writing intervals but no task lists, so the work varies by who does it.
- Never reviewing the data, so intervals stay wrong and the program goes stale.
Going digital with MapTrack
A preventive maintenance program lives or dies on follow-through, and a spreadsheet schedule rarely survives contact with a busy workshop. With MapTrack, preventive maintenance scheduling triggers work from time or meter readings automatically, so nothing slips because someone forgot to check the planner.
Technicians complete standardised task lists from their phone by scanning the asset's QR code, and every completed job updates the service history. Due and overdue work surfaces as automated alerts, and the reporting shows your PM compliance and planned-to-unplanned ratio so you can tighten the program with real data instead of guesswork.
