Why Your PM Compliance Rate Is Lying to You

A 95% PM completion rate is the number every maintenance manager wants to show in a board meeting. It feels like control. It feels like proof that the system is working. In most hotels and facilities I have seen, it is a lie.

Not a malicious lie. An accidental one, built into how most CMMS platforms measure completion, and amplified by the incentive structure of engineering teams under pressure.

What "completed" actually means in most systems

In a calendar-based PM system, a work order is "complete" when a technician taps the close button. The system records the timestamp, increments your completion counter, and moves on. It does not know whether the technician spent 45 minutes doing the actual inspection or 30 seconds closing the tab because they were already running late to a guest callout.

This is not a hypothetical. It is the default behavior of almost every CMMS in the market today. The checkbox exists. The incentive to check it fast also exists. The outcome is predictable.

Three signs your compliance rate is fiction

• Technicians are closing PMs in under 5 minutes for tasks that should take 20–30. If your average time-in-task on HVAC filter checks is 4 minutes, your filters are not being checked.
• Repeat failures on assets with high PM compliance. If an asset that shows 100% PM completion has three unplanned breakdowns in a quarter, the PMs are not actually preventing anything.
• No variance in PM completion time across technicians. Real inspections have natural variance: the unit is harder to access, or a problem is spotted and logged. Identical 3-minute completions across all techs is a signal that nobody is actually inspecting.

What to measure instead

Completion rate tells you that the work order was closed. What you actually want to know is whether the maintenance action had any effect on asset reliability. That requires a different set of metrics.

Time-in-task tracking

Log the timestamp when a technician starts a work order and when they close it. Flag any PM closed in under 60% of the estimated task duration. This will not catch every fake completion, but it will surface the pattern.

Photo evidence requirements

Require at least one photo for every PM closure. A filter check requires a photo of the clean or dirty filter. A belt inspection requires a photo of the belt condition. This adds 30 seconds to the task and makes falsification obvious.

Reactive-to-preventive ratio per asset

Track unplanned work orders per asset against PM completion for that asset. A well-maintained asset with genuine PMs should show declining reactive maintenance over time. If your PM rate is high but your reactive rate is not falling, the PMs are not working.

The cultural fix

No software feature fixes a culture where closing work orders faster is implicitly rewarded. The deeper problem is that engineering teams under pressure route their time toward visible urgency (guest calls, breakdown repairs) and treat PMs as administrative overhead. That is a management problem, not a technology problem.

The fix is to make PM quality visible and valued. Review time-in-task data in shift handovers. Celebrate asset reliability milestones. Track the cost of reactive maintenance per asset and connect it to PM quality in team discussions.

A PM completion that counts is one where the asset's condition was actually assessed and documented. Everything else is just closing a tab.

What Arckium does differently

Arckium's PM scheduler requires photo evidence and logs time-in-task for every work order. The compliance dashboard separates "closed" from "verified": a PM is only marked verified when it meets the minimum time and evidence requirements set by the maintenance manager. Your board report shows the number that actually means something.