Maintenance schedule compliance is the percentage of scheduled maintenance work that actually gets completed in the period it was scheduled for. Measured in work orders or in hours, it answers one blunt question: did the plan you committed to on Monday survive the week? It is a formally defined work-management metric in the Society for Maintenance and Reliability Professionals (SMRP) Best Practices library, and it is the single most honest reading of whether a maintenance organization is running to plan or running to noise.
Most maintenance metrics are lagging, MTBF, cost per unit, downtime, and by the time they move, the cause is months behind you. Schedule compliance is different. It moves the same week the plan breaks, which makes it the earliest warning you have. This guide covers the formula, how to calculate it without fooling yourself, the target bands, and how to read the number so it tells you what to fix.
What is maintenance schedule compliance?
Schedule compliance is the ratio of scheduled work completed as scheduled to the total scheduled work, for a defined period, almost always a week. If you scheduled 40 jobs for this week and finished 34 of the ones you scheduled, you were 85% compliant. The metric does not care how busy the crew was or how many break-ins they heroically absorbed; it cares only whether the committed plan happened.
That indifference is the point. A maintenance crew can work flat out all week, close a hundred work orders, and still score 50% schedule compliance, because the hundred they closed were not the ones they planned. High activity with low compliance is the signature of a reactive plant: lots of motion, none of it to plan. Allied Reliability calls schedule compliance “the prime work-management metric” for exactly this reason: it exposes the gap between intention and reality that busyness hides (Allied Reliability, Schedule Compliance).
How do you calculate schedule compliance?
The formula is simple; the definitions underneath it are where plants differ. In plain form:
Schedule compliance = (work completed as scheduled ÷ total work scheduled) × 100
You can run the numerator and denominator in either of two units, and the choice matters:
| Basis | Counts | Best for | Watch out for |
|---|---|---|---|
| Work-order count | Number of scheduled WOs completed ÷ number scheduled | Quick weekly read; simple to gather | A 15-minute job and an 8-hour job count the same |
| Labor hours | Scheduled hours completed ÷ scheduled hours planned | A truer picture of capacity honored | Needs reliable hour estimates on every job |
Worked example, hours basis: you build a week loaded with 320 planned labor hours. During the week, break-ins pull the crew off two jobs worth 45 scheduled hours, which slip to next week. You completed 275 of the 320 scheduled hours. Compliance = 275 ÷ 320 × 100 = 86%. Note what is not in that math: the break-in hours the crew actually worked. They explain the 14% miss, but they never enter the ratio, they go in the break-in log.
Three definitions you must pin down before the number means anything. First, the compliance window: does a job scheduled for Tuesday but finished Thursday count as compliant? Most plants say a job counts if completed within the scheduled week; PM-heavy plants add a tolerance such as within 10% of the interval. Second, what “scheduled” means: only work that was frozen in the weekly schedule counts, not everything in the backlog. Third, rescheduling: a job you formally pushed to next week before the week started is not a compliance miss; a job you simply failed to do is. Write these rules down once, or the number will drift every time a different person reports it.
What is a good schedule compliance target?
A world-class target is 90% or higher. That figure aligns with the benchmarks published by SMRP, whose Best Practices metrics give each measure a definition, a formula, and a best-in-class target value (SMRP Best Practices, Metrics & Guidelines). The bands most reliability practitioners work to look like this:
Two honest cautions. First, 100% is a warning, not a trophy. Perfect compliance week after week usually means the schedule is padded, loaded so lightly that anything finishes, or that break-ins are being quietly added to the schedule after the fact. A lean schedule at 92% is healthier than a fat one at 100%. Second, compliance measures execution, not the value of the work. You can be 95% compliant on a schedule full of low-value PMs that find nothing. Pair it with the quality of what you schedule, covered in our PM schedule guide.
Why does schedule compliance matter?
Because it is the earliest indicator that a plant is slipping from proactive back toward reactive, and the slide is expensive. PNNL's federal O&M guidance puts the savings from moving off a heavily reactive posture toward planned maintenance at levels that can exceed 30–40% of maintenance cost, and schedule compliance is the weekly gauge of whether you are holding that proactive position or losing it (PNNL, O&M Best Practices: Maintenance Approaches). When compliance falls, the crew is being pulled off planned work to fight fires, wrench time drops from its already-thin 25–35% typical baseline (Reliable Plant, Facts About Maintenance Wrench Time), and the plant burns overtime doing reactively what it could have done cheaply on plan.
The metric earns its keep only when you read it with its companion, the break-in log. A falling compliance number tells you the plan broke; the break-in log tells you why, and the cure depends entirely on the why:
- Break-ins are mostly equipment failures? That is a reliability problem. The schedule is fine; the assets are not. Escalate PM coverage and condition monitoring on the offenders.
- Break-ins are mostly walk-up requests and “while you're here” jobs? That is a discipline problem. The schedule is being treated as a suggestion. Enforce the freeze and make break-ins displace a named job visibly.
- Compliance is fine but the backlog is growing? The schedule is under-loaded. You are honoring the plan because the plan asks too little. Check your backlog in crew-weeks.
How do you improve schedule compliance? A 6-step approach
Compliance rises when the plan becomes both honest and protected. The sequence that works:
- Schedule only ready work. A job with no parts on site is not schedulable, it is a wish. Filling the week from planned, parts-on-hand work removes the most common compliance killer: the technician who arrives and cannot start. This is the whole reason planning has to happen before scheduling.
- Load to honest capacity. Start from roster hours, then subtract vacation, training, committed PMs, and a realistic reactive allowance drawn from history. A schedule loaded to fantasy capacity misses by definition. Overstating capacity is the original sin of scheduling.
- Freeze the week and publish it. Once agreed with production, the week is the commitment. Break-ins must displace a named job, in the open, so the cost of every interruption is visible rather than absorbed silently.
- Log every break-in. Capture what interrupted the schedule and why. Without the log, compliance is a number with no story, and you will keep guessing at the cause.
- Capture actuals at the machine. Technicians close work orders with real hours and notes where the work happens, not from memory on Friday. Accurate close-out is what makes next week's estimates, and therefore next week's schedule, honest. Plants that moved close-out from paper to tablets get this as a byproduct, as the CLS case study shows.
- Review the number and the log together every week. Put compliance on the weekly KPI dashboard next to its break-in log, decide one thing to fix, and start again. The trend over a quarter is what moves.
How does schedule compliance relate to PM compliance?
They are cousins, not twins, and mixing them up is common. PM compliance asks a narrow question: were the preventive maintenance work orders completed within their due window? Schedule compliance asks a wider one: was all the scheduled work, PMs plus planned corrective jobs, completed as scheduled? A plant can hit 95% PM compliance by cherry-picking easy PMs while its broader schedule collapses. Track PM compliance to protect the preventive program specifically; track schedule compliance to protect the whole weekly plan. Both belong on the dashboard, and both are only as trustworthy as the CMMS that records completion. The distinction between which jobs count, and getting the work order types coded consistently, is what lets you separate the two cleanly.
Where does schedule compliance fit in the bigger picture?
Schedule compliance is the pulse of the weekly maintenance cycle described in our planning and scheduling guide. It sits on the maintenance KPI dashboard as the leading indicator, ahead of the lagging reliability and cost metrics. It rises when planning fills a ready backlog and scheduling protects the week, and it is the same coordination discipline, commit in writing, honor the commitment, that makes production scheduling work on the other side of the plant. If the reason your number is unmeasurable today is that work is logged on paper and the schedule lives in someone's head, that is a data problem before it is a maintenance problem, the kind of digitization described on our platform overview.