Preventive Maintenance Compliance

Preventive maintenance is planned work intended to keep assets functioning and identify problems early, and compliance compares scheduled tasks with tasks done on time, so state the reporting period and timing rule before calculating it. A fictional factory that schedules 100 inspections this month and completes 85 within its approved window has compliance of 85% on that basis, and late inspections are not counted as on-time.

Only planned preventive tasks belong in the denominator, because emergency repairs and unplanned breakdown work answer different questions and mixing them makes the rate hard to interpret. A fictional maintenance crew that performs ten urgent pump repairs has done real work, but it does not increase the preventive compliance numerator.

Define "on time", since some organisations require completion by the due date and others allow a narrow window linked to the task frequency, and record the rule and apply it consistently. A fictional 30-day inspection with a three-day grace period under company policy that is completed four days late remains non-compliant for that cycle.

The maintenance platform eMaint defines PM compliance as completed on-time planned tasks divided by scheduled planned tasks, and its guidance notes that the headline percentage alone does not reveal how late missed work became. Treat its suggested timing window as an example, not a regulatory rule.

A fictional team reporting 90% compliance may hide a safety inspection overdue by two weeks, which needs more attention than a minor cleaning task. A completion record should show actual work, not merely a closed ticket, so technicians may need readings, test results, parts and notes, and audit samples should check whether the task was performed, with asset IDs and scheduled dates keeping records traceable.

Risk varies, because a life-safety check and a low-risk cosmetic task should not receive identical attention solely because both count as one job, so segment compliance by criticality. A fictional hospital that completes most routine filter changes but misses a generator test has an aggregate score that looks high, yet the critical miss requires immediate escalation.

Scheduled work can be blocked by missing parts, access, shutdown windows or staffing, so record reasons instead of quietly moving due dates; replanning may be appropriate but the original obligation should be preserved. Avoid gaming the metric by deleting overdue tasks or pushing deadlines forward, because a current schedule should reflect reality and historical records should show original dates and authorised changes.

A fictional site that shows 100% compliance after removing five uncompleted work orders is exposed by its audit trail. A high rate does not prove the plan is effective, since tasks can be too frequent, too shallow or unrelated to common failure modes, and a low rate may indicate unrealistic volume rather than careless technicians, so compare compliance with breakdowns and asset condition before changing the plan through a controlled decision.

Distinguish tasks due this period from backlog inherited from earlier periods and report overdue work separately, without counting the same task twice. Regulated assets may have legally mandated inspections that a flexible internal window cannot override, so track follow-up work found during inspections, share the measure with operations to solve access constraints jointly, and use trends to improve scheduling rather than to punish the reporting of genuine issues.