Build a preventive maintenance program from scratch by first creating a complete asset list, then ranking each asset by business criticality, assigning sensible service intervals, and turning those intervals into repeatable job plans with clear inspections, lubricants, parts, and labour time. After that, schedule the work, track completion and defects, and adjust the program based on failures, operating hours, and real-world conditions. In plain terms: know what you own, decide what hurts most when it stops, service it before it fails, and make the work consistent enough that “we thought someone checked it” stops being a maintenance strategy.
Start with the assets, not the software
A preventive maintenance program fails early when people jump straight into schedules without knowing exactly what they are maintaining. Start with a basic asset register.
For each asset, capture:
- Asset ID or fleet number
- Make and model
- Serial number
- Asset type
- Year of manufacture
- Current hours or distance
- Primary location or site
- Typical duty cycle
- Service manual reference
- Warranty status, if relevant
- Key consumables and fluid specifications
For heavy equipment fleets, include both mobile and support assets:
- Excavators
- Wheel loaders
- Dump trucks
- Cranes
- Telehandlers
- Generators
- Compressors
- Light vehicles
- Pumps and attachments
If an asset burns fuel, leaks oil, lifts weight, or can shut down production when it sulks, put it on the list.
Rank assets by criticality
Not every machine deserves the same level of planning. A site fuel trailer and a production excavator are both assets, but only one can stop a job in half an hour and ruin everyone’s week.
Use a simple criticality score based on:
| Factor | Ask this question | Simple score range |
|---|---|---|
| Safety impact | Could failure injure someone? | 1–5 |
| Operational impact | Does failure stop production or delivery? | 1–5 |
| Repair cost | Is failure expensive to correct? | 1–5 |
| Failure frequency | Does it fail often? | 1–5 |
| Redundancy | Is there a backup asset available? | 1–5 |
Add the scores and split assets into groups such as:
- Critical: high safety or production impact
- Important: disruption is manageable but costly
- Routine: lower consequence, easier to replace or defer
This matters because critical assets need tighter inspection routines, better parts planning, and higher PM compliance targets.
Choose the right maintenance triggers
A preventive maintenance program needs a trigger for when work happens. For mixed fleets, the best trigger depends on how the asset is used.
Common triggers:
- Engine hours: best for earthmoving, lifting, generators, and other equipment with variable use
- Distance (km / miles): best for trucks and road vehicles
- Calendar time: best for low-use assets, inspections, statutory checks, batteries, and fluid age limits
- Fuel burn or cycles: useful for specialised assets where hours alone miss actual workload
In practice, most fleets use a combination:
- Engine oil and filters every 250 hours on many heavy machines, though some OEMs specify 500 hours or condition-based intervals
- Hydraulic filters often at 500 to 1,000 hours depending on system design and contamination control
- Cooling system checks monthly, with coolant replacement commonly every 2 years or per OEM specification
- Final drives, axles, swing gearboxes, and differentials often inspected or serviced at 500 to 1,000 hours
- Greasing daily, every shift, or every 10 hours for pins, bushes, slew rings, and articulation points in harsh duty
- Road vehicles commonly serviced every 10,000 to 20,000 km (about 6,000 to 12,000 miles) or by time if usage is low
Treat these as starting points, not gospel. The manual wins, contamination laughs at optimism, and severe duty shortens intervals fast.
Build standard PM levels
Most good programs use service levels so the work is structured and predictable.
A practical framework looks like this:
Daily or pre-start inspection
Usually operator-led:
- Walkaround for leaks, damage, loose hardware
- Engine oil, coolant, hydraulic oil, and fuel levels
- Tyre or track condition
- Lights, alarms, wipers, mirrors, camera systems
- Attachments, hoses, couplers, cylinders
- Safety items: seat belt, fire extinguisher, horn, park brake
- Drain water separators if fitted
- Grease designated daily points
Minor PM
Typically every 250 hours or equivalent:
- Change engine oil and filter
- Replace fuel pre-filter or separator element if scheduled
- Inspect air cleaner restriction and intake system
- Check belt tension and condition
- Inspect batteries and cable connections
- Sample fluids if using oil analysis
- Torque check key fasteners where specified
- Record defects found during inspection
Major PM
Typically every 500 to 1,000 hours:
- All minor PM tasks
- Replace additional fuel and hydraulic filters
- Check axle, transmission, and final drive oil condition
- Inspect brake systems
- Inspect steering, suspension, articulation joints, slew bearing, wear pads, boom structures, and undercarriage wear
- Clean coolers and radiator pack
- Test charging and starting systems
- Review trend data from previous defects and oil reports
Annual or statutory inspection
- Full safety and compliance inspections
- Load testing where required for lifting equipment
- Structural crack inspection
- Calibration or certification tasks
- Replacement of age-limited items
Write job plans that a different technician could follow
If the PM exists only in one experienced mechanic’s head, it is not a program. It is a hostage situation.
Each PM task should have a standard job plan with:
- Asset class or exact model covered
- Trigger: hours, km, cycles, or date
- Estimated labour time
- Required parts and quantities
- Correct fluid grades and fill volumes from OEM data
- Tools and special equipment needed
- Step-by-step tasks
- Inspection points and limits
- Safety isolation steps
- Required photos or measurements
- Defect reporting instructions
Good job plans reduce missed steps and make labour estimates more accurate. They also help buyers compare maintenance systems properly: the useful platforms are the ones that let you store repeatable service templates, trigger work automatically, and record defects against the asset history. That is more valuable than a very pretty dashboard nobody trusts by month three.
Set realistic schedules and capacity
The biggest beginner mistake is scheduling more PM work than the workshop or field team can actually complete.
Start by calculating:
- How many PMs are due each week or month
- How many labour hours each PM takes
- How many technician hours are genuinely available
- How much travel, breakdown, and parts delay time you usually lose
Example approach:
- 20 machines
- Average minor PM every 250 hours
- Average use 125 hours per month
- Roughly half the fleet needs a 250-hour service each month
- If each PM takes 4 labour hours, that is about 40 labour hours monthly before travel, washing, defects, and paperwork
Then add contingency. PM tasks find defects. That is the point. If your schedule assumes every service goes perfectly and nobody discovers a torn hose, cracked mount, or metal in a final drive sample, that optimism will be punished.
Decide what gets inspected, measured, and replaced
Preventive maintenance is not just oil changes. The useful part is catching wear before it becomes a failure.
Include measurable checks where possible:
- Brake lining thickness in mm
- Undercarriage wear percentages
- Tyre tread depth and inflation pressure in bar (psi)
- Battery voltage
- Starter charging voltage
- Pin and bush movement or clearance
- Filter restriction indicators
- Fluid contamination trends
- Crack length or structural defect progression
- Hose chafe depth or exposed reinforcement
Use limits from OEM manuals where available. If you have no limit, define a practical internal standard and improve it over time.
Build the parts and lubricant plan alongside the PM plan
A schedule without parts support becomes an elegant way to create overdue work orders.
For each PM level, define:
- Filter kits required
- Typical seal kits or consumables
- Grease type
- Engine oil grade
- Hydraulic oil type
- Coolant specification
- Common wear parts likely to be found during inspection
Then set minimum stock for fast-moving PM items, especially for critical assets or remote sites. Too much stock ties up cash; too little stock guarantees “service delayed awaiting one filter,” which is maintenance code for “we will revisit this after the avoidable breakdown.”
Track a small set of KPIs from day one
Do not drown the program in metrics. Start with a few numbers that actually tell you whether the system is working.
Useful starter KPIs:
| KPI | What it tells you |
|---|---|
| PM compliance (%) | Were scheduled PMs completed on time? |
| Schedule compliance (%) | Did the workshop complete planned work as scheduled? |
| Planned vs unplanned labour (%) | Are you preventing failures or living inside them? |
| Breakdown count | Are failures becoming less frequent? |
| Mean time between failures | Are critical assets becoming more reliable? |
| Defects found per PM | Are inspections identifying issues early? |
| Repeat defects | Are repairs actually fixing the problem? |
A simple starting target is to keep PM compliance high enough that critical assets are not regularly slipping past their interval. Exact targets vary, but if overdue services are normal, the program is decorative.
Roll it out in phases
Do not try to perfect the entire fleet in one week. Start with the assets that hurt most when they fail.
Recommended rollout:
- Build the asset register
- Rank criticality
- Create PM templates for the top 20% most critical assets
- Load schedules for those assets first
- Train operators on pre-start checks and defect reporting
- Review the first 30 to 60 days of results
- Fix bad intervals, missing parts, unrealistic labour times, and vague checklists
- Expand to the rest of the fleet
This phased approach is usually faster overall because the early mistakes happen on a controlled scale instead of across every machine you own.
Use a system that can actually sustain the program
You can start with spreadsheets, and many people do. They work right up until version control, missed intervals, incomplete histories, and mystery defects make the whole thing feel like an archaeological dig.
A maintenance management system helps when it can:
- Store asset histories in one place
- Trigger PMs by hours, km, or date
- Use standard service templates
- Track defects from inspection to repair
- Record parts usage and downtime
- Report PM compliance and overdue work
For mixed fleets, even a straightforward platform such as AM Fleet Integrity is useful if it keeps asset records, service schedules, and defect follow-up tied together. The value is not glamour. The value is knowing what was done, what was missed, and which machine is quietly preparing to embarrass you next.
Common mistakes when building a PM program
Watch for these early failures:
- Using generic intervals for every asset: a crane, excavator, and road truck do not live the same life
- Ignoring operating severity: dust, shock loading, idling, water exposure, and short cycles all matter
- Writing vague job plans: “inspect machine” is not a useful instruction
- No defect closeout process: finding problems without fixing them is just organised disappointment
- Overloading technicians with PM volume: missed services become routine
- Not training operators: poor pre-start checks let obvious failures mature into expensive ones
- No review cycle: intervals and tasks should change when failure history says they should
Bottom line
To build a preventive maintenance program from scratch, list every asset, rank what is most critical, assign manufacturer-based intervals adjusted for real operating conditions, and turn those intervals into standard job plans with parts, fluids, inspections, and labour time. Then schedule the work, track PM compliance and defects, and refine the program using breakdown history and technician feedback. Done well, PM looks boring on paper and expensive failures become less exciting in real life, which is exactly the point.
Frequently asked questions
What is the first step in creating a preventive maintenance program?
The first step is building a complete asset register so you know exactly what equipment, vehicles, and support assets you maintain. Without that, you cannot set intervals, estimate labour, plan parts, or measure compliance properly.
How do I choose preventive maintenance intervals?
Start with the manufacturer’s recommended intervals, then adjust them for actual operating conditions such as dust, heavy loading, idling, water exposure, and low or high utilisation. Use hours for most heavy equipment, distance for road vehicles, and calendar-based triggers for low-use or statutory tasks.
What should be included in a preventive maintenance checklist?
A good checklist includes fluid checks, filter and lubricant tasks, safety inspections, wear measurements, leak and damage checks, and model-specific inspection points. It should also state the correct parts, fluid specifications, labour time, and defect reporting steps so the work is repeatable.
How do you measure whether a PM program is working?
Track a small set of KPIs such as PM compliance, schedule compliance, planned versus unplanned labour, breakdown count, and repeat defects. If overdue PMs are common and emergency repairs are still dominating workshop time, the program needs adjustment.
Can I build a preventive maintenance program in a spreadsheet?
Yes, you can start in a spreadsheet, especially for a small fleet, but it becomes harder to control intervals, histories, defects, and overdue work as the fleet grows. A maintenance system is usually better once you need automatic scheduling, asset histories, and reliable reporting across multiple machines or sites.