Ask three people in the same department what the preventive maintenance compliance rate is, and you may get three different answers. One counts every task done eventually, another counts only tasks done inside the window, and a third excludes whatever was deferred. For government teams with overdue PM piling up, the number matters because it shows whether planned work is actually happening. This post defines PM compliance, shows how to calculate it correctly, and lists the scheduling rules and reminders that raise it. It also shows where Oxmaint preventive maintenance software helps.
Preventive Maintenance Compliance Rate: How to Improve
Define it once, measure it the same way every month, and use it to find out why planned work slips.
What PM compliance rate actually measures
PM compliance is the share of scheduled preventive tasks completed within an agreed window. It measures discipline, not asset health.
Worked example
- 120 PM tasks fell due in the month.
- 96 were completed inside their allowed window.
- Compliance is 96 ÷ 120, which equals 80%.
- The other 24 are overdue or late and need reasons recorded.
Three ways to count, three different answers
Suppose 100 PM tasks were due. Seventy were done on time, 15 were done late, and 15 were never done.
| Method | What it counts | Result | Risk |
|---|---|---|---|
| Strict, in window | Only tasks done inside the allowed window | 70% | Can feel harsh but shows true schedule discipline |
| Completed eventually | Any task done, even long after the due date | 85% | Hides lateness and rewards deferral |
| Excluding deferrals | Removes tasks someone postponed | Higher than 70% | Makes backlog disappear on paper |
- Choose the strict method for your headline KPI.
- Report late completion and overdue count beside it.
- Require a reason code for every deferral.
Set a window that fits each task
A task due on a single day is almost never done on that day. Define an early and late tolerance, scaled to the interval.
- A weekly task may allow a day or two, while an annual task may allow weeks.
- Write window rules in policy so every supervisor applies them equally.
- Do not widen windows just to improve the number.
Why compliance drops: symptom and root cause
Low compliance is a symptom. Find the cause before adding pressure on the crews.
Stop losing PM tasks in the shuffle
Generate preventive work orders automatically, send reminders, and see overdue tasks by asset and by crew in one view.
Scheduling rules that raise compliance
Small structural changes often help more than reminders. Apply these rules to the PM library.
- Protect planned labor hoursReserve a fixed share of weekly crew time for PM before emergency work absorbs it.
- Level the workloadSpread due dates across weeks instead of stacking many tasks on the first of the month.
- Bundle by locationGroup tasks at the same site or route to cut travel and access problems.
- Choose fixed or floating intervals deliberatelyCalendar-based schedules suit regulated tasks, while completion-based intervals suit wear-driven work.
- Pre-stage parts and kitsReserve filters, belts, and consumables when the work order is generated.
- Coordinate with operationsAgree access windows for pumps, buildings, and fleet before the due date.
An escalation ladder for overdue PM
Reminders work when each level has a clear owner and a clear next step.
Report compliance by criticality, not as one number
A single average can hide the problem. Missing a lubrication task on a spare is not the same as missing a safety inspection.
| Segment | Why split it | How to act |
|---|---|---|
| Safety and regulatory tasks | Misses carry compliance and liability consequences | Review every miss, and aim for the highest target |
| High-criticality assets | Failure has the biggest service impact | Protect labor and parts first |
| Routine assets | Lower consequence, more tolerance | Allow wider windows, review intervals |
| By crew or area | Reveals capacity or access problems | Rebalance work or add resources |
Clean up the PM library
Low compliance sometimes reflects a library full of tasks nobody believes in. Review it once a year.
Keep
- Tasks required by regulation or warranty
- Tasks that regularly find defects
- Tasks on critical assets
Rewrite
- Vague instructions with no pass or fail limit
- Intervals not matched to usage
- Tasks missing parts or tools lists
Retire
- Tasks for assets no longer in service
- Tasks that never find anything and carry little risk
- Duplicates created by merged schedules
A fifteen-minute weekly PM review
A short, regular meeting keeps compliance from becoming a month-end surprise.
- Minutes 1 to 3Review last week's compliance and overdue count.
- Minutes 4 to 8Walk through overdue tasks on high-criticality assets.
- Minutes 9 to 12Resolve blockers such as parts, access, or labor.
- Minutes 13 to 15Confirm next week's schedule and any tasks to rewrite.
How Oxmaint helps raise PM compliance
Oxmaint is maintenance management software. It keeps schedules, work, and reporting in one place.
- Recurring PM schedulesTime-based and usage-based tasks generate work orders automatically.
- Mobile checklistsTechnicians complete tasks in the field and close them immediately.
- Assignment and schedulingBalance work across crews and weeks.
- InventoryTrack filters, belts, and kits needed for scheduled work.
- DashboardsSee compliance, overdue tasks, and backlog by asset, crew, or tier.
- Compliance recordsKeep an auditable history of completed inspections.
Pair compliance with these metrics
Compliance alone can be gamed. These companions keep it honest.
Overdue PM count
Tasks past due and not completedPM yield
Defects found ÷ PM tasks completedPlanned-to-reactive ratio
Planned hours ÷ reactive hoursRepeat failures
Assets with repeat corrective work ÷ assets with corrective workPM compliance rate FAQs
What is a good PM compliance rate?
Set targets from your baseline and criticality. Safety and regulatory tasks usually warrant the highest target.
Should deferred tasks count against compliance?
Yes for the headline number. Track deferral reasons separately so the pattern is visible.
Can compliance be too high?
It can if tasks are trivial or windows too wide. Check PM yield alongside it.
How quickly can compliance improve?
Often within a few cycles once scheduling and reminders are fixed. Book a demo to see how.
Do we need software to track it?
Spreadsheets work at small scale, but automation helps. Try Oxmaint free to compare.
Set the compliance window by task interval
A common mistake is applying one tolerance to every task. Scale it to the interval and write it into policy.
| Task interval | Tolerance pattern | Example |
|---|---|---|
| Daily or weekly | Very short window, often within the same day or week | Operator rounds, safety checks |
| Monthly | A few days either side of the due date | Filter checks, fluid levels |
| Quarterly | One or two weeks of tolerance | Valve exercising, electrical inspections |
| Annual | Several weeks, tied to regulation where applicable | Backflow tests, generator service |
| Usage-based | Tolerance in hours or miles, not days | Engine service, pump rebuilds |
Use deferral reason codes
Knowing why PM slips is more useful than knowing that it slipped. Require a code whenever a task is deferred.
- Parts not availablePoints to inventory or kitting problems, which are fixable with better stocking.
- Asset not accessibleSignals a coordination gap with operations and a need for agreed access windows.
- Labor reassigned to emergencyShows the cost of reactive work in planned hours lost.
- Asset out of serviceIndicates the task should be paused or the asset record updated.
- Task unclear or obsoleteFlags tasks for rewrite or retirement during the next library review.
- Awaiting contractorHighlights vendor scheduling or contract issues that need follow-up.
Common crew objections, and what to do about them
Technicians often have good reasons for skipping tasks. Listen first, then fix the cause.
- This task never finds anythingCheck PM yield. If the task rarely finds a defect and carries little risk, extend the interval or retire it.
- I do not know what done looks likeThe instructions are too vague to follow, so add pass or fail limits, tools, and parts lists.
- We do not have the partsReserve parts when the work order is generated, and check stock a week ahead.
- Operations will not release the equipmentAgree access windows in advance and schedule jobs around them.
- The paperwork takes longer than the jobMove to short mobile checklists with defaults, and remove fields nobody uses.
- Emergencies leave no timeProtect a fixed share of weekly hours and report how often it is breached.
A 60-day plan to lift compliance
You can improve compliance in a single quarter by changing structure first and pressure second.
- Weeks 1 to 2Agree the definition and windows, and measure the current baseline honestly.
- Weeks 3 to 4Retire dead tasks, rewrite unclear ones, and level due dates across weeks.
- Weeks 5 to 6Turn on reminders and escalation, and start the weekly fifteen-minute review.
- Weeks 7 to 8Review deferral reasons, fix the top two blockers, and share results with crews.
Compliance traps specific to public agencies
Government maintenance has its own quirks that can distort the number.
- Seasonal surges. Winter operations and storm response pull crews away from PM, so plan lighter preventive loads in those months.
- Grant-funded assets. Some funding agreements require documented upkeep, so track those assets and their tasks separately.
- Contractor-performed PM. Count it only when a signed report is received and entered, not when the visit was scheduled.
- Backdated entries. Late data entry can make compliance look better or worse than the field reality, so record the actual completion date.
- Auto-closing tasks. Closing overdue tasks automatically hides the backlog, so require a reason and a new due date.
- Shared facilities. Assets used by several departments often fall between owners, so assign a single responsible team.
Who should get which reminder, and when
Too many alerts get ignored. Send fewer, more targeted messages to the right person.
| Audience | Message | Timing |
|---|---|---|
| Assigned technician | Upcoming task, location, parts reserved, and estimated time | About a week ahead, then on the due date |
| Crew supervisor | Tasks nearing the end of their window and tasks without an assignee | Daily during the week the window closes |
| Division manager | Overdue critical tasks and deferrals by reason code | Weekly review |
| Department director | Compliance trend, overdue count, and top blockers | Monthly report |
Questions to ask about every overdue task
Walking through the same questions each week turns overdue lists into decisions.
How critical is the asset?
Overdue work on a critical asset should be scheduled first, with labor and parts confirmed.What is blocking it?
Name the blocker: parts, access, labor, or clarity. Assign an owner to remove it.Is the task still right?
If crews keep skipping it, check whether the interval or content needs to change.What is the new date?
Never leave a task overdue without a committed new date and a named person.Reporting compliance to leadership
Leaders will act on a clear story. Keep the report short and consistent.
- Lead with the headline compliance rate using the strict definition, and show the trend over the last several months.
- Break it out by criticality and by crew, so leaders can see where the problem concentrates.
- Show the overdue count and age of the oldest overdue tasks, since a falling rate with a growing backlog is a warning.
- List the top three blockers by deferral reason, with one action and one owner for each.
- Report PM yield, so leaders know the tasks are finding problems and are not just being ticked off.
- Keep the format identical each month, so changes in the numbers are visible and not hidden by redesign.
Get preventive maintenance back on schedule
Define compliance clearly, automate the schedule, and give your team a simple view of what is due, late, and done.
