Your team may be scheduling PMs every week, but that doesn’t mean preventive maintenance is getting done on time, consistently, and at a level that reduces downtime risk.
That is where preventive maintenance compliance (PMC or PM compliance) comes in.
PM compliance helps you answer a simple but important question: are you actually following through on preventive work? It’s one of the clearest ways to understand if production pressure, resource gaps, and reactive work are quietly pulling your team off schedule.
This guide breaks down what PM compliance is, why it matters, and how to use it as a practical metric instead of a checkbox. You’ll learn how to calculate it, where teams run into trouble, and what to do when compliance starts to slip.
Key takeaways
- Preventive maintenance compliance measures whether preventive maintenance gets done on time, not just whether it gets done. That makes it a more useful metric than PM completion alone when you want to understand schedule discipline and uptime risk.
- Low PM compliance usually points to bigger operational problems like overloaded schedules, labor constraints, production conflicts, missing parts, or weak planning.
- PM compliance is most valuable when you use it to make decisions. Track it with clear rules, review it alongside other maintenance KPIs, and use it to improve schedule quality, field execution, and visibility into what is slipping and why.
What is preventive maintenance compliance?
PM compliance measures the percentage of scheduled preventive maintenance work completed on time. PM compliance isn’t about whether preventive maintenance tasks got done, but rather if they got done when they were supposed to. In other words, it’s a schedule adherence metric.
That distinction is important. A PM that gets completed a week late may still show up as finished in your system, but it did not protect the asset the way you intended. If lubrication, inspection, cleaning, calibration, or replacement tasks happen too late, you increase the chance that failures go unnoticed. You also increase the chances that a breakdown occurs before technicians can complete the work order.
That’s why PM compliance is a useful leading indicator. It gives you an early read on how disciplined your maintenance program is, how realistic your schedule is, and how well your team is set up to execute planned work. When compliance is consistently strong, it points to better planning, clearer priorities, and fewer execution gaps. When it’s weak, it signals that maintenance processes are broken.
PM compliance vs. PM completion
PM completion tells you whether the work got done. PM compliance tells you whether it got done on time.
Those metrics can look similar, but they answer different questions.
If your team completes 95 out of 100 preventive maintenance tasks in a month, your PM completion rate looks strong. But if only 78 of those PMs were finished on time, your PM compliance rate tells a different story. The work happened, but the risk to your operation increased, leaving assets vulnerable to breakdowns.
That matters for a few reasons:
- Preventive maintenance only works when it happens at the right interval. If the timing slips too often, you lose some of the value of the program.
- In regulated environments, “completed” is not the same as “completed on schedule.
- Only focusing on PM completion can hide scheduling and resource problems. PM compliance uncovers weaknesses in your maintenance plan under real operating conditions.
A strong maintenance team should watch both metrics. Completion shows follow-through. Compliance shows control.
Why PM compliance matters
PM compliance tells you whether your maintenance workflows are set up correctly and how well maintenance is prioritized at your facility and company.
When PM compliance is high, it means stronger training, planning, coordination, and consistent execution. It suggests scheduled maintenance is not being cut because of emergencies, production demands, or missing resources. At the most foundational level, technicians know what to do and how to do it without facing too many obstacles.
When PM compliance is low, the issue is usually deeper operational problems like unrealistic schedules, labor shortages, production conflicts, incomplete procedures, missing parts, or poor data. The metric surfaces those problems, which are often the root cause of downtime and higher costs.
Both plant leaders and maintenance managers should care about PM compliance because missed PMs increase risk. When preventive work slips, assets are more likely to fail unexpectedly. That affects uptime, labor efficiency, schedule attainment, and maintenance costs. It can also create compliance and audit risk when inspections are delayed or poorly documented.
It also shows whether the team is protecting uptime or just reacting to breakdowns. A team can stay busy every day and still fall behind on the work that prevents bigger failures. PM compliance shows whether your maintenance program is operating proactively or whether reactive work is quietly taking over.
Even as 74% of organizations report fewer unplanned outages, 31% say those incidents are more expensive than they were last year. Troubleshooting speed and accuracy have never mattered more.
What PM compliance tells you about your maintenance program
PM compliance gives you a window into how your maintenance program is functioning. Some of the things it can tell you are:
- Whether preventive work is realistic and prioritized. If the schedule is overloaded, poorly sequenced, or full of low-value tasks, compliance will usually suffer.
- Whether technicians have what they need to execute. When preventive maintenance tasks are missed because of unclear instructions, missing parts, or lack of access to asset information, the problem is not just execution. It’s planning.
- If operations and maintenance are aligned. If equipment windows keep disappearing because production always wins time on equipment, compliance will show the strain long before leadership sees the full cost in downtime or repair spend.
- Whether the value of maintenance is understood. High PM compliance usually reflects a team that is making time for planned work, following processes, and capturing work consistently. Low compliance can be a sign that the team is slipping back into reactive habits, where urgent work keeps beating important work.
PM compliance is a practical signal of whether your maintenance program is set up to prevent problems or just recover from them.
How to calculate preventive maintenance compliance with a PM compliance formula
PM compliance is calculated using the following formula:
PM compliance (%) = (Number of PMs completed on time / Number of PMs scheduled) × 100
To calculate PM compliance correctly, you need to be clear about three things:
- How many PMs were scheduled in the reporting period
- How many of those PMs were completed
- How your team defines on time
That last point is essential. If “on time” is vague, the metric becomes unreliable. One planner may count a PM as compliant if it’s done anytime that week. Another may count it late the moment the due date passes. A third may define ‘late’ differently based on the asset. Once that happens, the number is useless because it no longer means the same thing every time you report it.
What counts as “on time”?
There is no universal rule for what counts as on time. Your team has to define it based on how your PM program works. Many teams use grace windows or due-date rules to reflect operating reality, like shutdown access, labor availability, or production timing. Document those rules before you start reporting PM compliance or it becomes too easy to misinterpret after the fact.
For calendar-based PMs, on time usually means the work was completed by the due date or within an approved window. For example, a monthly PM may need to be completed within a few days before or after its target date to count as compliant. A good rule of thumb is the 10% rule, which allows a grace period equal to 10% of the maintenance interval.
For meter-based PMs, the definition is usually tied to usage. A PM due every 500 run hours might be considered on time if it is completed within an acceptable range around that threshold.
An example of calculating PM compliance
Let’s say your team scheduled 120 PMs for the month.
Out of those 120:
- 102 were completed on time
- 10 were completed late
- 8 were not completed during the reporting period
Using the standard formula:
PM compliance = (102 / 120) × 100 = 85%
Common calculation mistakes
The most common mistakes when measuring PM compliance come from inconsistent rules and overly generous reporting.
One common mistake is counting completed PM tasks without checking if they were completed on time. This removes the timing element that gives the metric its value.
Another mistake is excluding overdue work. If a PM was scheduled, it should be counted, unless there is a documented reason it was canceled or deferred, such as a change in production schedule.
Teams also run into trouble when they mix scheduled, deferred, canceled, and rescheduled work without clear rules. If one person marks a PM as deferred and another leaves it overdue, the metric can shift based on data habits instead of actual maintenance performance.
Inconsistent date windows across assets or sites create another problem. Compliance rates only work as a management metric if the underlying standards are consistent enough to compare over time.
What is a good preventive maintenance compliance score?
Establishing a target for PM compliance depends on:
- What assets you run
- The maturity level of your maintenance program
- Your labor capacity
- How often production constraints force schedule changes
A plant with stable shutdown windows and a disciplined planning process may be able to sustain a much higher score than a team dealing with chronic staffing shortages and schedule disruptions.
That said, teams still need practical reference points. Benchmarks are not perfect, but they help you interpret the number and decide whether you are looking at healthy control or a warning sign.
Practical benchmarks for PM compliance
You can think about PM compliance in three broad ranges.
- Below 80% is usually a warning sign. It often means planned work is being pushed aside too often, or the PM schedule is not realistic enough to execute consistently, pointing to a planning, staffing, or coordination problem.
- 80% to 90% is workable, but often inconsistent. Many teams operate in this range when balancing preventive work against heavy reactive demand. It’s acceptable in the short term, but leaves room for too many missed or delayed tasks.
- 90% and above usually reflects stronger control for maintenance teams. It suggests the schedule is stable, the work is supported, and preventive maintenance is treated as a priority.
One element to factor into this benchmarking is PM criticality. A PM compliance of 90% can hide gaps if the 10% being missed are tied to your most failure-sensitive equipment. That’s why PM compliance should also be reviewed by asset criticality when possible.
When a high PM compliance score can be misleading
A high preventive maintenance compliance score does not automatically mean the maintenance program is healthy. There are a few reasons for this:
- If tasks are too infrequent, too shallow, or poorly scoped, a team may hit a strong compliance number without doing enough to improve reliability.
- If work orders are being closed without clear notes, readings, inspection detail, or sign offs, the metric can give a false sense of control.
- If failures are not decreasing, reactive work is still high, or downtime remains unstable, strong PM compliance on its own does not prove the preventive maintenance strategy is working.
- If the schedule is bloated or poorly prioritized, it can mean a high score against the wrong work. It may show discipline, but not necessarily effectiveness.
PM compliance can tell you how consistently the team is executing a plan, but not whether the plan is the right one.
- Maintenance mission statement
- Maintenance tasks
- work instructions
- Maintenance schedule
- Maintenance technicians
- Third-party contractors
- Replacement parts
What causes low PM compliance?
Low preventive maintenance compliance often has less to do with technician effort and more to do with operating reality.
When PMs are missed or late, the root cause is usually upstream, such as an overloaded schedule, a lack of access to machines, missing parts, or an uptick in emergency work.
In these cases, low PM compliance should be treated as a diagnostic signal that helps you understand what is keeping planned work from happening on time.
Let’s take a deeper look at some of these factors and why they can impact PM compliance.
Production keeps crowding out planned work
A PM schedule might look manageable on paper, but, in practice, preventive work keeps losing to short-term production pressure. Equipment stays in service longer than planned, access windows disappear, and PMs get deferred because stopping production feels harder than delaying maintenance.
But delayed PM tasks don’t disappear. As preventive work gets pushed further out, the risk of failure rises with it. In this case, low PM compliance is a sign of poor alignment between operations and maintenance.
Labor and scheduling are stretched too thin
Sometimes, the issue is simple: there is more PM work scheduled than your team can support.
Maybe your team is understaffed, the PM program has grown without being rebalanced, or work is being planned without a realistic view of available hours.
Reactive maintenance makes the problem worse. A week that starts with a solid PM plan can fall apart quickly if breakdowns or urgent requests consume the hours meant for preventive tasks.
When that happens repeatedly, low preventive maintenance compliance is less about technician execution and more about scheduling discipline and labor capacity.
Parts, tools, or instructions are missing
A PM can fail if technicians don’t have what they need to complete it.
That missing piece can take the form of a spare part, a tool, a permit, access to an asset, or a clear procedure. Sometimes, a work order is too vague, especially for newer technicians or more complex tasks. A technician shows up ready to do the work, but the job stalls because they weren’t set up to succeed.
When PM compliance is slipping for this reason, it’s because of weak job readiness.
The PM program needs cleanup
PM schedules often accumulate duplicate tasks, outdated frequencies, and low-value work that no longer reflects the actual needs of equipment. Teams keep adding work without removing anything. The PM load eventually becomes harder to execute than it looks on paper.
That creates two problems: the team gets buried in low-priority scheduled pm tasks and truly critical PMs have to compete for time and attention. If your schedule is full of work that adds little reliability value, low PM compliance may be telling you to clean up the program before asking the team to run faster.
Tracking is inconsistent
PM compliance looks low in some cases because the tracking is weak.
Manual systems, late data entry, inconsistent closeout habits, and unclear ownership can all distort the metric. A PM may have been completed on time but entered late. Another may have been deferred informally without documentation. Another may be sitting open because no one owns the exception process.
That’s why data discipline matters. A reliable PM compliance score depends on reliable work order habits, not just a reliable formula.
How to improve preventive maintenance compliance
Improving PM compliance starts with understanding all the factors that impact on time PM execution, identifying (and fixing) any broken areas, and optimizing the processes that are already strong.
1. Fix your schedule
If your PM schedule is overloaded, outdated, or full of low-value tasks, compliance will always be harder than it should be. Review PM frequencies, remove duplicate work, and make sure critical assets get the most attention.
2. Build a weekly planning rhythm
PM compliance usually improves when planning becomes more consistent. That means locking in the PM schedule ahead of time, balancing preventive work against known production needs, and assigning ownership clearly so PMs aren’t pushed aside by urgent work.
3. Make PMs easier to execute
Technicians are more likely to complete PMs on time when the work is clear and obstacle-free. PMs should include usable procedures, asset history, standardized checklists, and clear closeout expectations. Make sure technicians have access to all these things on a mobile device so they don’t need to chase paperwork or re-enter notes later.
4. Reduce avoidable delays
A lot of PMs get missed because of preventable planning gaps. Stage parts in advance, confirm labor availability and flag access issues early. When a technician shows up to do a PM, the job should be ready.
5. Separate emergency work from chronic planning problems
Reactive work will always disrupt some PMs. Success depends on how often this happens and why it happens. Look for patterns in emergency work that regularly knocks preventive work off the schedule, like staffing limitations, failure modes, or production pressure. That makes it easier to fix the root cause instead of treating every missed PM as an isolated event.
6. Review compliance by asset criticality and crew
Not all PMs carry the same risk, which is why you shouldn’t treat them all the same in reporting. Break down PM compliance by critical assets, lines, areas, or crews so you can see where the schedule is slipping and where it matters most.
7. Use software to automate tracking and follow-up
The more manual your PM process is, the harder it is to maintain strong compliance. Using a computerized maintenance management system (CMMS) for automatic scheduling, real-time work status, easier documentation, and better reporting makes it easier to stay on top of planned work.
How to use PM compliance as a management metric
Used well, PM compliance can help you spot risk, review execution discipline, and understand where your maintenance plan is breaking down. It gives structure to a bigger question: are we protecting uptime through planned work, or are we losing control of our preventive maintenance schedules?
Metrics to track alongside PM compliance
PM compliance works best when paired with other maintenance metrics, including:
- PM completion
- Planned maintenance percentage
- Maintenance backlog
- Mean time between failure (MTBF)
- Mean time to repair (MTTR)
- Downtime by asset
Combining these metrics gives you more context. PM compliance shows whether work is being done on time. The others help show whether that work is improving reliability, reducing disruption, and supporting better planning.
Questions PM compliance should help you answer
Tracking PM compliance should help you answer questions like:
- Are we following through on preventive maintenance activities?
- Where is the schedule breaking down?
- Which assets, lines, or teams are consistently slipping?
- Are missed PMs being caused by labor constraints, planning gaps, or production conflicts?
- Are we deferring important work too often?
Answering these questions takes PM compliance from a number on a report to a decision-making tool you can use to diagnose problems and make your team more efficient.
The limitations of PM compliance
PM compliance is an important metric, but it has limits:
- It measures timeliness, not quality. A PM can be completed on time and still be rushed, poorly documented, or done inconsistently.
- It doesn’t prove PMs are effective. A team can have strong compliance and still struggle with failures if the PM program is built around the wrong tasks, intervals or standards.
- It can be gamed. If work orders are closed without enough execution detail, or if overdue work is quietly reclassified to protect the number, the score can look stronger than it is.
- It doesn’t tell the whole story of maintenance performance. A low score may reflect an issue, but it may also highlight smart prioritization during a shutdown change, staffing shortage, or period of heavy reactive demand.
PM compliance works best as part of a broader reliability picture. It tells you whether the team is executing the schedule on time. It does not tell you, by itself, whether the work is high quality, strategically sound, or improving asset performance.
Best practices for tracking PM compliance
PM compliance is only useful when tracking rules are clear and data is consistent. Here are a few tips for achieving that:
- Define rules before reporting. Be clear about what counts as scheduled work, completed work, and on time completion. Establish how your team handles deferred, canceled, and rescheduled PM tasks.
- Standardize due dates and grace periods across similar asset types or PM categories. This makes it easier to compare performance across time, teams, and sites.
- Separate canceled, deferred, overdue, and completed work in reporting. They’re different situations with different root causes. A deferred PM might be a deliberate decision while an overdue PM could be a planning failure. If both are lumped together, you lose context.
- PM compliance is more useful when reviewed regularly. Weekly reviews help teams catch slippage early, while monthly reporting helps leaders spot trends, bottlenecks, and chronic problems
- Make PM compliance visible to the maintenance and operations teams. Treat it as a shared metric. If missed PMs are being driven by schedule conflicts, production access, or resource tradeoffs, both groups need to see the same picture.
Embrace PM compliance as a decision-making tool for better maintenance
PM compliance is one of the clearest ways to see whether your preventive maintenance program is working as intended. It shows whether planned work is actually happening on time, or whether reactive demands, scheduling issues, and execution gaps are quietly taking over.
But the metric only becomes useful when you define it clearly, track it consistently, and use it to fix planning and execution problems. On its own, PM compliance is just a percentage. Used well, it becomes an early warning sign, a management tool, and a way to keep preventive maintenance connected to uptime, cost, and operational control.
If you want PM compliance to improve, focus on three things: schedule quality, field execution, and visibility into what is slipping and why. That is where the real gains usually come from.
PM compliance FAQs
What does PM compliance mean in maintenance?
PM compliance measures the percentage of scheduled preventive maintenance tasks completed on time. It shows whether your team is following the PM schedule as planned, not just whether work eventually gets done.
How is PM compliance different from PM completion?
PM completion measures whether scheduled PMs were finished. PM compliance measures whether they were finished on time. A task can count toward completion but still miss the compliance window if it was completed late.
How often should you review PM compliance?
Most teams should review PM compliance weekly for operational control and monthly for trend reporting. Weekly reviews help catch missed work early. Monthly reviews help show patterns and support broader planning decisions.
What is a good PM compliance score?
There is no universal target, but 80% is a typical benchmark with a percentage of over 90% being an exceptional score. The right benchmark depends on asset criticality, staffing, production constraints, and how realistic the PM schedule is.
What causes poor PM compliance?
Poor PM compliance is usually caused by overloaded schedules, labor shortages, production conflicts, missing parts, weak planning, or inconsistent tracking. In some cases, the PM program itself needs cleanup because it includes too much low-value or outdated work.
How do you improve PM compliance without adding more labor?
Start by cleaning up the PM schedule, prioritizing critical work, improving weekly planning, and making jobs easier to execute. Many teams improve compliance more by reducing friction and removing low-value work than by simply adding headcount.
The MaintainX team is made up of maintenance and manufacturing experts. They’re here to share industry knowledge, explain product features, and help workers get more done with MaintainX!
.webp)
.webp)