PM Compliance % Explained: Calculation, Targets, and How to Improve It

The PM That Nobody Knew Was Late

It's a Monday morning. Your three-axis CNC router has been throwing intermittent feed-axis faults since Friday. The operator flagged it, the weekend crew looked at it, nobody touched anything. Now you're pulling the maintenance log and you notice the last scheduled lubrication service was supposed to happen six weeks ago — but there's no completed record. It's not in the paper binder. It's not in the shared drive. It just didn't happen, and nobody caught it, because nobody was tracking whether it happened.

That gap between scheduled and actually done is exactly what PM compliance percentage measures. It's the single most honest health metric your PM program has — not how many work orders you wrote, not how busy your technician looked, but how reliably your planned preventive maintenance is actually being executed on time.

By the end of this article you'll know the exact formula, how to read what your current number is telling you, what a realistic target looks like at each tier of your asset criticality, and — most importantly — the specific levers that move that number up and keep it there.

---

What PM Compliance % Actually Measures

PM compliance percentage (also called PM compliance rate or preventive maintenance compliance) answers one question: of all the PMs that were due in a given period, what fraction were completed?

It is a ratio of execution against plan. A low number does not automatically mean your technicians are slacking — it usually means the plan has a structural problem: too many tasks, wrong intervals, unclear ownership, or no system to generate and track the work-order queue in the first place.

The metric matters because it is a leading indicator. A PM compliance rate that slides quietly below the healthy range predicts equipment failures, unplanned downtime events, and rising reactive repair costs — before those costs actually land. If you want to understand the broader set of KPIs it lives alongside, the maintenance KPI glossary hub and the core KPIs that matter most are the right starting points.

---

The PM Compliance Formula

The calculation is straightforward:

PM Compliance % = (PMs Completed on Time ÷ PMs Scheduled) × 100

Every term needs a clear definition before you start counting, or the number becomes meaningless.

PMs Completed on Time — a PM is "completed" when it has a recorded completion entry (technician, date, and findings captured). "On time" is defined by a tolerance window around the due date — see the 10% rule below. A PM completed three months late should not count as a compliant completion.

PMs Scheduled — every PM that had a due date fall within the measurement period. If a task was on the calendar for the period, it counts in the denominator whether or not the technician got to it.

Measurement period — typically one calendar month, reviewed quarterly and trended over a rolling twelve months. Monthly gives you enough signal to act; quarterly smooths seasonal noise.

Applying the 10% Rule for "On Time"

Industry practice — as documented by eMaint (Fluke Reliability), 2026 — defines an on-time PM as one completed within 10% of the scheduled interval. For a monthly PM (roughly every 30 days), that means the task must be completed within approximately three days of the due date in either direction. For a quarterly PM (~90 days), the window is about nine days.

This is a tighter standard than most spreadsheet-managed shops are currently holding themselves to. If your current "completed" column includes tasks finished two or three weeks late, you are overstating your compliance rate.

Worked Example

Say your plant has 40 PMs due in March. By month-end, 34 were completed within their 10% windows. Two were completed late (outside the window). Four were not done at all.

PM Compliance % = (34 ÷ 40) × 100 = 85%

The two late completions do not count. The four missed tasks do not count. This is the number your program actually earned in March — not 36/40 = 90%.

---

What a Good PM Compliance Target Looks Like

Targets are not one-size-fits-all. They vary by asset criticality. The Society for Maintenance & Reliability Professionals (SMRP Best Practices, cited via eWorkOrders, 2026) defines the benchmarks this way:

Tier	PM Compliance % Target	What It Signals
World-class (overall program)	≥ 90%	PM program functioning effectively
Critical / A-class assets	≥ 95%	No room for drift on high-consequence equipment
Minimum acceptable	≥ 80%	Below this, the program is not functioning effectively
Reactive-heavy zone	< 80%	Structural problem — interval overload, no tracking system, or ownership gaps

Below 80% PM compliance, the maintenance program is not functioning effectively. — SMRP Best Practices (cited via eWorkOrders, 2026)

These are not aspirational stretch goals. They are the thresholds the reliability profession uses to diagnose whether a PM program is actually protecting equipment — or just generating paperwork.

A 90% overall target with a 95% sub-target for your most critical assets is the right place to anchor your program. If you are currently at 60–70%, the goal is not to jump straight to 95%; it's to understand why tasks are being missed and fix the structural causes, then build the number up.

---

Four Reasons PM Compliance % Falls — and What to Do About Each

Most programs that track PM compliance for the first time discover their number is lower than expected. That's normal, and it's the point of measuring. Here are the four most common structural causes.

1. The Schedule Has Too Many Tasks

A technician who has 45 PMs due in a month and realistically has time for 30 will not complete 45. The PMs that get deferred are usually the ones that seem routine and low-urgency — right up until they aren't. Over-scheduled intervals are often a legacy of copying a PM template without checking it against actual duty cycle and staffing capacity.

The fix: Audit your PM library against your technician's available wrench time. A ballpark target: world-class plants achieve planned:unplanned work ratios of 80:20 or better, with leading programs reaching 90:10 (Reliamag, referencing SMRP, 2026). If you're spending most of your labor on reactive repairs, your schedule is almost certainly overloaded relative to capacity. The preventive maintenance planning guide walks through how to right-size a PM program.

2. Intervals Are Set and Forgotten

A PM interval that was reasonable when the equipment ran one shift may be wrong now that it runs two. Intervals copied from a generic template and never calibrated against your actual machine duty cycle will create either over-maintenance (burnout) or under-maintenance (failures). Start with OEM documentation as your baseline, then adjust based on your own operating conditions — hours, throughput, environment, and failure history.

Always confirm specific intervals against the equipment OEM manual and any applicable industry standards (ASHRAE for HVAC systems, NFPA 70B for electrical equipment, OSHA for powered industrial trucks). The PM interval library built into Maintenance Planning Manager provides 20 equipment categories as a general starting point, explicitly for calibration — not as universal prescriptions.

3. No One Knows a Task Was Due

The most common failure mode in spreadsheet-managed programs: the tab wasn't checked, the calendar wasn't opened, the shared file was locked by a co-worker. A task that is past-due but invisible is a missed PM waiting to become a reactive repair.

A system that automatically generates a rolling work-order queue from the PM schedule — and sends notifications when tasks approach their due dates — eliminates this class of failure entirely. If you're tracking overdue tasks manually, the overdue task aging report guide describes a structured method for catching drift before it compounds. For a broader look at why planned PMs still get missed even with a schedule in place, this article on the causes of missed PM tasks is worth the read.

4. Completion Isn't Being Recorded

A PM was done. The technician initialed the paper card. Nobody entered it in the system. So it shows as missed, and the compliance number is artificially low — but the effect is the same as a genuinely missed PM: no record, no audit trail, no proof if an inspector or an insurer asks.

The fix: Record completion at the point of work, not at the end of the week. Mobile-friendly work-order forms that capture technician, date, time, and findings — closed in the field — fix this. CMMS platforms with a four-stage work-order lifecycle (Open → In Progress → Completed → Verified) create a structural record that a spreadsheet simply cannot.

---

How PM Compliance % Connects to Your Other KPIs

PM compliance percentage does not live in isolation. It is the upstream driver of the metrics that show up on executive dashboards and in reliability reviews.

MTBF and MTTR. Plants with strong PM compliance consistently see higher mean time between failures (MTBF) and lower mean time to repair (MTTR) — because well-maintained equipment fails less often and, when it does fail, is better documented and faster to diagnose. Industry research summarized by Re-Leased (2025) finds that PM programs correlate with MTBF improvements of 50–75% and MTTR reductions of 30–50%. The MTBF and MTTR calculation guide covers how to calculate and track both.

Planned vs. unplanned ratio. Every PM missed is a potential reactive repair. As PM compliance falls, the planned:unplanned ratio falls with it, wrench time gets consumed by emergency work, and the technician has even less time to complete scheduled PMs — a self-reinforcing spiral.

Maintenance cost as % of Replacement Asset Value (MC/RAV). SMRP-aligned benchmarks (Factory AI, 2026) put world-class MC/RAV at 2.0–3.0% of Replacement Asset Value annually. Programs with chronically low PM compliance tend to sit above that range because reactive repairs — the U.S. Department of Energy documents these as costing 3–5× more per repair than planned PM (cited via eWorkOrders, 2026) — inflate the cost numerator without improving asset condition.

---

How to Start Tracking PM Compliance % Today

If you're currently running your PM program from a spreadsheet, here's a practical starting sequence:

1. Define your denominator first. List every PM that was due in the most recent complete month. This is your schedule. If you don't have a clear list, that's the first problem to solve.
2. Apply the 10% rule. For each task, define the on-time window. A monthly PM is on time if completed within ±3 days of its due date.
3. Count actual completions with records. Not "probably done" — recorded completions with a date and a technician.
4. Calculate and trend monthly. A single month's number is a data point. Three to six months of monthly numbers is a trend you can act on.
5. Segment by asset criticality. Overall compliance tells you the program's health. Compliance on your A-class assets tells you whether your most consequential equipment is protected.

For a ready-to-use tracking setup, the Maintenance KPI Dashboard — available in the Maintenance Planning Manager digital store for around $29 — includes a pre-built PM compliance % tracker alongside the other core reliability KPIs, structured so you can start entering your numbers immediately without building the formulas from scratch.

If you're ready to move from a spreadsheet to a system that auto-generates your PM work-order queue and calculates compliance for you, the Maintenance Planning Manager 14-day free trial lets you bring your asset list in and see what your PM schedule actually looks like when it's structured — before you commit to a plan.

---

The Number You're Allowed to Ignore — Until You Can't

PM compliance percentage is easy to deprioritize when everything is running. When nothing is breaking, it's tempting to assume the maintenance program is working. It usually takes one significant unplanned failure — one that traces back to a PM that was consistently deferred — before the compliance number gets taken seriously.

The plants that avoid that lesson track PM compliance before something breaks. They know their number. They have defined targets by asset class. They catch the drift from 88% to 79% before it becomes a equipment failure, an OSHA inspection, or a lost production run. The formula is simple. The discipline to track it consistently is where most SMB maintenance programs fall short — and where a planning-first system earns its place.