PM compliance is the single most predictive maintenance KPI for SMB teams. When it's high, unplanned downtime drops, MTTR shortens, and repair budgets become predictable. When it's low, you stay in firefighting mode no matter how many people you hire.
This guide explains the five PM compliance metrics that actually matter, how to calculate each, what "good" looks like, and the most common reasons teams stall at 50–60% compliance.
What "PM Compliance" Actually Means
The textbook definition:
PM Compliance Rate = (PMs completed on time) ÷ (PMs scheduled in the period) × 100
It sounds simple, but it hides three traps:
- "On time" — does it mean by the due date, or within a grace window (typically ±10–20%)?
- "Completed" — does partial completion count? What about PMs that were skipped because the asset was already in use?
- "Scheduled" — what about ad-hoc PMs that were added mid-period? Are they in the denominator?
Most CMMS platforms (including Maintoro) let you configure these definitions per organization. The point: agree on the definition before measuring, otherwise the number is meaningless.
The Five Metrics That Predict Maintenance Health
1. PM Compliance Rate (the headline number)
Target: ≥ 85% for a mature operation, ≥ 70% for a new CMMS rollout.
A single percentage that summarizes whether scheduled maintenance is happening. Below 70%, you have a process problem (resources, tooling, or culture). Above 90%, your schedule may be too aggressive — you might be over-PMing assets that don't need it.
2. Schedule Adherence (how close to plan)
Schedule Adherence = PMs completed within ±10% of due date ÷ PMs completed
Different from compliance. A PM completed 15 days late counts toward compliance (it eventually got done) but fails adherence. Tracks discipline, not just output.
Target: ≥ 80%. Below 60% means your team is constantly catching up.
3. Mean Time Between Failures (MTBF) — by asset class
MTBF = Total operating hours ÷ Number of failures
The leading indicator that PM is actually working. If your PM compliance is high but MTBF is flat, the PM tasks are wrong (you're doing the wrong work). If both improve together, the PM program is healthy.
Target: depends on asset class. Track the trend monthly — flat = bad, improving = good.
4. Deferred PM Ratio
Deferred PM Ratio = PMs deferred or rescheduled ÷ PMs scheduled
This is the early-warning signal. If 30% of PMs are being pushed out, your schedule is unrealistic or your team is undersized. Address this before it becomes a compliance crisis.
Target: < 15%. Above 25% requires a process review.
5. Reactive vs. Proactive Hours
Reactive % = Reactive work order hours ÷ Total maintenance hours
The North Star metric. World-class operations target < 30% reactive. SMB teams without a CMMS typically run 60–80% reactive. Reducing this number is the entire point of CMMS adoption.
Target: < 30% mature, < 50% in year 1 with a CMMS.
Why Most Teams Stall at 50–60% Compliance
After watching hundreds of PM rollouts, four patterns explain almost every stall:
Pattern 1: PM tasks are too long
A "weekly inspection" that takes 90 minutes will be skipped when the floor is busy. Most PMs should fit in 15–30 minutes. If yours don't, split them: a quick visual check weekly, a deep inspection monthly.
Pattern 2: Wrong frequency for the asset
A motor that runs 12 hours/day shouldn't share a PM schedule with one that runs 2 hours/day. Use runtime-based PMs (every X operating hours) instead of calendar-based when usage varies. Most modern CMMS platforms support this — see Maintoro's PM features.
Pattern 3: Parts not in stock when PM is due
Your team arrives at a scheduled filter change and the filter is on backorder. The PM gets deferred. This is a parts-management problem, not a maintenance problem. Link parts to PM schedules so consumption auto-triggers reorders.
Pattern 4: No accountability for completion
If "the maintenance team" owns a PM, nobody owns it. Assign each PM to a specific named technician. Review compliance per-tech in the weekly stand-up. People do what gets measured.
How to Build a PM Compliance Dashboard
A useful dashboard fits on one screen and updates daily:
Top section (1 row, 4 cards):
- PM Compliance Rate — current month %, with trend arrow
- Schedule Adherence — current %, with trend
- Deferred PMs — count this month
- Reactive Hours % — current month %
Middle section (table):
- Top 10 most-failed assets in last 30 days
- Includes: asset name, # failures, total downtime hours, last PM date
Bottom section (chart):
- 6-month trend of PM Compliance and Reactive %
- They should move in opposite directions if your PM program is working
In Maintoro, this is a one-click dashboard. Configure once, share with your operations lead and CFO monthly.
Common Pitfalls in PM Metric Reporting
Pitfall 1: Including PM exceptions as completed. A PM marked "skipped — asset offline" is not "completed." Make sure your CMMS distinguishes between completion and exception.
Pitfall 2: Tracking compliance without tracking quality. A PM marked "complete" with zero notes and zero photos may not have actually been done. Add quality checks: random spot-audits of completed PMs, mandatory photos for inspections.
Pitfall 3: Setting unrealistic compliance targets early. Targeting 95% compliance in your first 3 months sets you up for failure and demotivation. Start with 70%, raise the bar each quarter.
Pitfall 4: Punishing technicians for low scores. If compliance is low, the process is broken, not the people. Fix the schedule, parts availability, and tools first. Punitive metrics destroy adoption.
Pitfall 5: Ignoring the cost side. A 95% compliance rate that costs $500K/year may be worse than a 75% rate at $200K/year. Track cost per PM and cost per asset year alongside compliance.
A 90-Day Plan to Improve PM Compliance
If you're stuck at 50–60%:
Days 1–30: Diagnose
- Pull last 90 days of PM data — which schedules have lowest compliance?
- Interview the techs assigned — why are they skipping?
- Categorize causes: too long, parts missing, wrong frequency, no time
Days 31–60: Fix the top 3 problem schedules
- Split long PMs into shorter ones
- Adjust frequencies based on actual asset usage
- Pre-allocate parts for upcoming PMs
Days 61–90: Build accountability
- Assign each PM to a named technician
- Add weekly stand-up review (15 min, top 3 overdue PMs)
- Celebrate compliance wins publicly (a Slack post when monthly target is hit)
Most teams move from 60% to 85% in 90 days using this approach.
Where Maintoro Fits
Maintoro is built specifically for SMB teams trying to move from reactive to proactive. Built-in features that support PM compliance:
- Mobile PM execution — technicians complete PMs on their phone, no walking back to the desk
- Auto-reminders — emails or push notifications 1 day before PM due
- Parts-linked PMs — consumption triggers auto-reorder
- Compliance dashboard — one-click monthly compliance report
- Runtime-based PMs — schedule by hours of use, not just calendar
For a complete walkthrough of these features, see the preventive maintenance feature page or book a demo.
What to Do Next
- Measure your baseline: Run last 30 days of data through the formulas above. Document the numbers.
- Pick the top problem: Which metric is furthest from target?
- Apply the 90-day plan: Diagnose → Fix top 3 → Build accountability.
- Track monthly: Review with operations lead and CFO. Adjust as needed.
For a complete reference on related metrics, see the maintenance KPIs and metrics guide and the downtime cost calculator.
Ready to put this into practice?
Maintoro is free forever for 2 users. If you're stuck below 70% PM compliance, start free and run your top 10 critical-asset PMs through Maintoro for 30 days. By day 60, your compliance should be in the 80s. Start free or book a demo for a guided rollout.