Planned Maintenance Percentage vs. PM Compliance %: What's the Difference?

The Report That Looked Great and Still Felt Wrong

Your PM compliance number says 94%. You completed 47 of 50 scheduled preventive tasks this month, right on the window, and the dashboard cell is green. But the shop floor doesn't feel like a program running at 94% anything. Technicians spent Tuesday chasing a conveyor gearbox that seized without warning. Wednesday was a forklift hydraulic leak nobody had on a worksheet. By Friday the planner is wondering how a number that high can coexist with a week that reactive.

The answer is that 94% is answering a narrower question than it looks like it's answering. PM compliance only measures whether the preventive tasks that were already on the schedule got done. It says nothing about how much of your crew's total time that schedule actually consumed, or how much of the week got eaten by work nobody planned for. That second question has its own metric, with its own formula, and it's commonly confused with PM compliance because the two names sound like synonyms. They aren't.

By the end of this piece you'll be able to calculate both numbers from your own work-order data, know exactly what each one is telling you, and know which one to look at first when the shop feels busier than the dashboard admits.

PM Compliance % Measures Whether the Schedule Got Executed

PM compliance percentage answers one question: of the preventive maintenance tasks you scheduled, how many actually got completed within the allowed window?

The formula is straightforward:

PM Compliance % = (Completed PMs ÷ Scheduled PMs) × 100, calculated over a rolling period — typically a month.

A worked example with round numbers: if your annual PM schedule called for 50 tasks in March and your technicians closed out 47 of them on time, that's 47 ÷ 50 × 100 = 94%. The three that slipped — a conveyor belt tension check, a monthly compressor filter swap, and a quarterly motor vibration reading — are now overdue, and depending on how your program defines "on time," they may or may not still count once they finally get closed.

That "on time" definition matters more than most planners initially realize. MaintainX's maintenance learning materials describe a widely used convention sometimes called the "10% rule": a task only counts as compliant if it's completed within 10% of its scheduled interval. A monthly PM due on the 1st has to close by roughly the 4th; a quarterly task has a window of about nine days. Confirm how your own program defines the compliance window before you compare your number against anyone else's — a looser window will always produce a higher compliance percentage than a strict one, even with identical work.

Where do you stand against the field? SMRP best-practice guidance, cited by eWorkOrders, puts world-class PM compliance at 90% or higher — at least nine of every ten scheduled PMs completed within the window — and treats anything below 80% as a sign the program isn't functioning effectively. MaintainX's own learning center frames 90% as the world-class standard as well, while placing the industry average closer to 75%–80%. If your number is sitting in that 75–80% band, you're not failing — you're typical. You're just not yet where the best programs are.

PM compliance is a schedule-adherence metric. It tells you nothing about whether the schedule itself is the right size, or whether your crew had time left over for anything else. That's the gap planned maintenance percentage fills. For a deeper walkthrough of the compliance formula, including how to handle tasks closed late versus tasks skipped entirely, see our dedicated guide on PM compliance percentage.

Planned Maintenance Percentage Measures How the Week Was Actually Spent

Planned maintenance percentage (PMP) asks a completely different question: of all the maintenance labor hours logged in a period, what fraction were spent on work that was planned in advance, versus work that came in as an unplanned, reactive interruption?

Planned Maintenance Percentage = (Planned/Scheduled Labor Hours ÷ Total Labor Hours) × 100

Here's a worked example. Say your two-technician crew logs 80 total labor hours in a week. Of those, 60 hours went to tasks that were on the weekly work plan before Monday morning — PM rounds, scheduled inspections, planned component swaps. The other 20 hours went to a bearing failure nobody saw coming and a electrical fault that pulled a technician off a scheduled lubrication route. That's 60 ÷ 80 × 100 = 75% planned maintenance percentage for the week.

Notice what that number captures that PM compliance doesn't: it doesn't care whether the 60 planned hours were all PM tasks specifically — they could include planned corrective work, a scheduled overhaul, or a planned parts replacement identified from a prior inspection. PMP is measuring the planning discipline of the whole operation, not just the preventive subset of it.

MaintainX's learning center cites 80% planned maintenance percentage as a widely accepted industry benchmark, with world-class operations reaching 85%–95%. That's a meaningfully higher bar than the 50/50 split many reactive shops are actually running at.

PMP connects directly to a number most planners have heard of without always being able to calculate: wrench time, the share of a technician's shift spent on actual hands-on repair and PM work rather than walking, waiting on parts, or hunting for a work order. Cryotos, citing Plant Engineering and Reliable Plant benchmarks, puts typical wrench time at only 25%–35% of a shift. The Reliability Academy's research suggests that effective maintenance planning and scheduling can lift that figure from roughly 30% toward 45%–55% or higher — which amounts to adding real capacity to a crew without hiring anyone new. A low PMP and low wrench time tend to travel together: when the week isn't planned, technicians spend more of it reacting, searching, and waiting instead of turning wrenches.

For the full list of KPIs worth tracking alongside these two — MTBF, MTTR, backlog aging, and schedule compliance — see our roundup of the maintenance KPIs that matter and the companion MTBF/MTTR calculation guide.

Why the Two Numbers Diverge in Real Plants

Here's the scenario from the opening section, explained. PM compliance was 94% because the 50 tasks that were already on the annual schedule mostly got done. But PMP for that same month would likely be far lower, because the conveyor gearbox seizure, the forklift hydraulic leak, and whatever else came in unplanned all consumed labor hours that weren't part of any plan — hours that don't show up in the PM compliance calculation at all, because that calculation only looks at the preventive task list, not the full week.

This is the core distinction to hold onto: PM compliance measures the preventive schedule's own execution rate. Planned maintenance percentage measures how much of total labor time the preventive schedule — and all other planned work — actually occupied. A shop can score high on the first while scoring low on the second, and that combination is a specific diagnostic signal: your preventive tasks are getting done, but they're a smaller and smaller share of what your crew is actually doing all week, because reactive work keeps crowding in around them.

A program can hit 90%-plus PM compliance and still be running mostly reactive — the two numbers are measuring different halves of the same week, and reading only one of them hides the other half.

This pattern lines up with a broader finding from the U.S. Department of Energy's Federal Energy Management Program: more than 55% of maintenance resources and activities at an average facility are still reactive, even in plants that maintain a functioning PM schedule on paper. High PM compliance doesn't contradict that reactive baseline — it can coexist with it, because compliance only ever measures the planned slice of the work, never the unplanned slice crowding in around it.

If your overdue-task backlog is growing even while compliance looks fine, that's often the earliest visible symptom of this gap — worth tracking through an aging report rather than the compliance percentage alone. And if you're trying to understand the reactive-vs-planned ratio in more depth — what counts as "reactive," how it's tracked, and what shifting the ratio actually takes — our guide on preventive vs. reactive maintenance covers that ground directly.

Which One Should You Track First?

If you're running a program with no formal KPIs today, start with PM compliance. It's simpler to calculate — you only need your scheduled-task list and your completion log, which most annual PM schedules and work-order logs already contain. It answers the most urgent early question: is the preventive schedule you built actually getting worked?

Once compliance is stable — consistently above that 80% floor SMRP identifies as the line below which a program isn't functioning effectively — start tracking planned maintenance percentage alongside it. PMP requires a slightly higher data bar: technicians need to log hours against work orders and categorize each one as planned or reactive at the point of closing it out, not after the fact. That's a habit, not a spreadsheet formula, and it's usually the harder of the two numbers to get clean data for in month one. Expect some noise in early PMP readings while technicians get used to the categorization — that's normal, not a sign the metric is broken.

Track both over a rolling 90-day window rather than any single week or month. A single bad week — one major breakdown — can swing PMP by ten or fifteen points without reflecting anything about your underlying planning discipline. The trend line matters more than any one data point.

Building a Dashboard That Tracks Both Without Conflating Them

The mistake we see most often isn't choosing the wrong metric — it's putting both numbers on the same chart with the same label, so a reader can't tell which question is being answered. Keep PM compliance and PMP in separate rows or separate charts, each with its own formula documented next to it, so anyone pulling the report six months from now doesn't have to guess which denominator was used.

A maintenance KPI dashboard built for this distinction tracks PM compliance, planned maintenance percentage, MTBF, MTTR, and backlog aging on one sheet, with the formulas visible rather than buried in a macro — useful both for your own monthly review and for an auditor who wants to see how a number was derived, not just what it says. If you're setting this up from scratch, our KPI glossary walks through every formula definition in one place, and the Maintenance KPI Dashboard template is built around exactly this compliance-versus-PMP distinction, with both metrics calculated from the same underlying work-order log so you're never reconciling two spreadsheets to get one answer.

None of this requires new software to start. It requires a work-order log that records planned-versus-reactive status on every entry, and a compliance window you've written down and applied consistently. Get those two habits in place, and both numbers — not just the one that happens to look good this month — will tell you something true about how your week was actually spent.