Ninety percent. That’s the number most maintenance teams chase when they talk about preventive maintenance compliance. It’s the industry benchmark, it looks great in a board report, and it’s usually the first KPI a maintenance manager points to when asked how the program is doing.
But a high PM compliance metric doesn’t automatically mean equipment is being cared for the way it should be. It’s entirely possible to hit 90%+ compliance every month while breakdowns keep climbing, backlogs keep growing, and technicians keep getting blindsided by failures that “preventive” maintenance was supposed to catch. When that happens, PM compliance has stopped measuring maintenance effectiveness and started measuring something else: how good the team is at closing work orders, regardless of whether the work actually protected the asset.
That’s the vanity metric trap. Here’s how it happens, and how to build a version of PM compliance that actually reflects the health of your maintenance program.
What PM Compliance Is Actually Measuring
Preventive maintenance compliance is a straightforward calculation: the number of scheduled PM tasks completed in a given period, divided by the total number of PM tasks that were scheduled, multiplied by 100.
PM Compliance = (Completed PM Tasks ÷ Scheduled PM Tasks) x 100
If a plant scheduled 100 PM tasks for the month and closed out 90 of them, that’s a 90% PM compliance score, right at the world-class benchmark most facilities aim for.
On paper, that’s a strong number. The problem is what the formula leaves out.
Why a High PM Compliance Metric Can Still Be Misleading
The basic PM compliance formula only asks one question: was the task marked complete? It doesn’t ask when it was completed, how well it was done, or whether it should have existed on the schedule in the first place. That’s where the metric starts to drift from reality.
Late completions still count as “compliant”
A PM task finished the day it was due and a PM task finished three weeks late both count as a completed task in the standard formula. But a preventive task performed weeks after its scheduled window has already lost most of its value. The whole point of PM is to catch wear and failure risk before it turns into downtime, not to eventually get around to it. A team can post a 95% compliance rate while running a maintenance program that’s chronically, quietly late, and the metric will never tell them that.
Irrelevant tasks inflate the score without protecting anything
Preventive maintenance plans are rarely revisited once they’re built. Equipment gets upgraded, parts get replaced with more durable versions, and processes change, but the original PM schedule often stays frozen in time. Technicians end up completing tasks that no longer meaningfully reduce failure risk, simply because the work order exists and gets checked off. Every one of those tasks boosts the PM compliance metric while doing nothing for actual asset reliability.
A completed checklist isn’t the same as a quality inspection
Compliance tracks whether a task was closed, not whether it was done well. A rushed five-minute inspection and a thorough one both close the same work order. When technicians are under pressure to hit a compliance target, the incentive quietly shifts from “protect the asset” to “close the ticket,” especially if PM tasks take longer to execute than the schedule allows for.
It says nothing about downtime, MTBF, or repeat failures
This is the clearest sign PM compliance has become a vanity metric: compliance is high, but mean time between failures (MTBF) isn’t improving, and the same assets keep showing up on the unplanned work order list. When PM compliance and reliability outcomes stop moving in the same direction, the compliance number has become a metric for its own sake rather than a signal of maintenance program health.
The 10% Rule: A Simple Fix for a Flawed Formula
One of the most effective ways to stop PM compliance from rewarding lateness is to apply the 10% rule. Instead of counting any completed task as compliant, a PM task only counts if it’s finished within 10% of its scheduled interval.
A task scheduled every 100 days, for example, needs to be completed within 10 days of its due date to count toward compliance. A task scheduled every 30 days needs to be completed within 3 days.
This single adjustment turns PM compliance from “did we eventually do it” into “did we do it on time,” which is a far more honest reflection of whether preventive maintenance is actually preventing anything.
How to Fix a Vanity PM Compliance Metric
Turning PM compliance back into a meaningful KPI usually comes down to five changes:
- Apply the 10% rule (or a similar on-time window). Stop crediting late completions as full compliance.
- Audit the PM task list for relevance. Remove or extend the interval on tasks that no longer reflect how the equipment actually performs today. A shorter, accurate PM list produces a more honest compliance score than a bloated, outdated one.
- Pair PM compliance with outcome metrics. Track it alongside MTBF, mean time to repair (MTTR), and unplanned downtime. If compliance rises but those numbers don’t improve, the program has a quality problem, not a scheduling problem.
- Give technicians the time and tools to do PM tasks properly, not just quickly. Mobile access to procedures, parts data, and asset history reduces the pressure to rush a checklist just to hit a number.
- Review compliance data regularly, not just at audit time. Recurring reviews surface which tasks are chronically late or chronically skipped, which is usually where the real maintenance gaps are hiding.
Signs Your PM Compliance Metric May Be a Vanity Number
| Warning Sign | What It Usually Means |
|---|---|
| Compliance is 90%+ but breakdowns aren’t decreasing | PM tasks are being closed but not protecting reliability |
| PM tasks are frequently completed close to the deadline | The 10% rule would likely reveal a much lower real compliance rate |
| Technicians describe certain PM tasks as “pointless” | The PM plan hasn’t been reviewed or updated in a long time |
| PM compliance and MTBF/MTTR move in opposite directions | Compliance is being tracked in isolation from actual outcomes |
| Compliance spikes right before audits or reviews | Tasks may be batch-closed rather than genuinely completed on schedule |
FAQ
Is 90% PM compliance always a good result? Not necessarily. A 90% score using the basic formula can still include tasks completed well past their due date or tasks that no longer meaningfully protect the equipment. Applying the 10% rule and reviewing the PM task list gives a much clearer picture of whether that 90% is real.
How is PM compliance different from planned maintenance percentage (PMP)? PM compliance measures how well a preventive schedule is being followed. PMP measures what portion of total maintenance work is planned versus reactive. Both are useful, but neither one alone tells the full story of maintenance program health.
What’s a realistic PM compliance target for most facilities? World-class PM compliance is generally considered to be around 90%, but the number matters less than the method behind it. A facility applying the 10% rule and regularly pruning outdated tasks can have a more reliable 80% score than a facility with a “loose” 95%.
Track PM Compliance the Right Way with FacilityBot
Getting an honest PM compliance metric starts with visibility into when tasks are actually completed, not just whether they’re checked off. FacilityBot is a cloud based CMMS software platform that gives maintenance teams a single, real-time view of every scheduled PM task, due date, and completion window, so compliance numbers reflect what’s actually happening on the floor. As preventive maintenance software, FacilityBot automates scheduling, flags overdue and at-risk tasks before they slip past the 10% window, and ties PM completion data to asset history and downtime records. Combined with FacilityBot’s broader facilities management software suite, teams get one connected platform to plan, track, and continuously refine their preventive maintenance program instead of managing it around a single, easily-gamed number.