Glossary · Planned preventive maintenance (PPM)

PPM (planned preventive maintenance): servicing booked ahead, not after a breakdown

Planned preventive maintenance (PPM) is work done on a schedule rather than after something breaks: filter changes, fire system inspections, pool tests, lift servicing, backflow testing. The schedule comes from a calendar, run hours or a regulatory cycle. Setting up the calendar is easy. Getting external contractors to attend on time and leave evidence is the hard part.

OpsChase runs PPM through Assets and planned maintenance, with the same tracking as reactive jobs.

Why multi-site teams care about PPM

When you run ten or a hundred sites, PPM is where small misses add up. One skipped filter change is a comfort complaint. A skipped fire inspection across a region is an audit finding. Planned work also protects your reactive budget: plant that is serviced on time breaks down less often, and when it does, the service history tells the technician what has already been done.

PPM is also the work that slips quietly. A broken door has someone on site complaining. A planned service that never happened looks exactly like one that did, until someone checks.

What good PPM looks like

  • Every asset that needs servicing is on a list, with its site, its trade and how often it is due.
  • Work orders are raised ahead of the due date, so the contractor has time to confirm a visit.
  • The visit goes to the contractor you expect, from your regular list for that site and trade.
  • Each visit ends with the evidence your policy needs: a service sheet, test results, photos or a certificate.
  • Late or missed visits show up before the next due date, not at the annual review.

Common PPM mistakes

  • Keeping the schedule in a spreadsheet separate from the jobs, so nobody can tell which services actually happened.
  • Treating a contractor’s monthly report as proof of attendance at every site.
  • Letting planned jobs skip tracking because they are “routine”.
  • Raising work orders on the due date, which leaves no time to deal with a quiet contractor.
  • Splitting planned and reactive work across two tools, so the same contractor gets two sets of instructions.

How planned maintenance fits jobs tracked until the work is done

With Assets and planned maintenance switched on, you keep an asset list for each site and set schedules on each asset or on a template. Planned work orders are raised ahead of due dates and go to your own team or your contractors, just like reactive jobs. If a contractor does not confirm, tracking starts the same way it does for any other job. The job closes only when the proof you set for that asset is on the work order, and the record stays on the asset’s history for the next visit and the next audit.

See CMMS and work order for how the records link together, and service level agreement (SLA) for attendance windows on planned work.

On OpsChase: one queue for your team and contractors, each job tracked until the work is done, then photos or sign-off. Book a demo — one site or many.

Is Assets & planned maintenance available now?
Yes. It adds asset lists and planned schedules to OpsChase, and planned jobs run on the same tracking and proof rules as reactive work.
Can planned and reactive jobs share contractors?
Yes. Your regular contractor list covers both.
Do planned jobs skip tracking?
No. A quiet contractor on a scheduled fire inspection is as serious as one on a breakdown, so the same reminder steps apply.
Can we pause planned work around holidays or trading peaks?
Yes. Site blackout and quiet-hour rules shift the scheduling windows.
What counts as proof for a planned service?
Whatever your policy says for that asset: a service sheet, test results, before-and-after photos or a certificate. Set it once on the template and every visit asks for the same evidence.
OpsChaseOpsChase

Start with the part you need today and add the rest when you’re ready. One site or many.

Book a demo