Overview
Schedule Compliance measures whether maintenance completes the work it committed to perform in a frozen schedule. The arithmetic is simple. The difficult part is controlling the baseline, defining what counts as complete, keeping missed and emergent work visible, and classifying why scheduled work was not completed.
A schedule compliance percentage without those controls can look precise while hiding weak schedule discipline. The useful management question is not only, “What was the percentage?” It is, “What happened to every item we committed to, and what should we fix before the next schedule?”
What It Is
The Reliability Method formula is:
Schedule Compliance = Completed Scheduled Work Orders ÷ Total Scheduled Work Orders × 100
Schedule Compliance is therefore both a KPI and a management process around that KPI. A trustworthy process requires:
- one frozen, timestamped baseline for the review period;
- a completion rule defined before execution;
- a disposition for every scheduled item;
- separate visibility for emergent or break-in work;
- variance-cause classification for misses;
- a recurring review that assigns corrective actions.
Schedule Compliance is not the same as PM compliance, schedule attainment based on a changing schedule, backlog completion, or technician productivity.
Why It Matters
Good schedule discipline improves the maintenance-operations relationship. Operations can plan around maintenance commitments, maintenance can identify capacity and readiness problems, and leaders can distinguish planning failures from material, labor, access, or operational constraints.
The percentage alone is a lagging result. The variance causes behind the percentage provide the actionable information.
When to Use It
Use Schedule Compliance when a maintenance organization operates from a defined weekly, daily, shutdown, or other committed schedule with a clear freeze point.
It is most useful when:
- work is selected from schedule-ready backlog;
- operations and maintenance agree on the committed window;
- schedule changes after freeze are controlled;
- work-order status history is reliable;
- missed work can be classified by cause.
Do not treat the KPI as meaningful when the schedule is continuously rewritten during the measurement period or when missed work can disappear from the denominator without control.
Core Principles
- A baseline that can be rewritten after execution starts is not a trustworthy baseline.
- “Completed” must have one documented meaning for the period.
- Every baseline item must receive a disposition.
- Emergent work must remain visible separately from baseline work.
- A miss is information, not a blame mechanism.
- Correct the cause before changing the target.
- Safety, quality, environmental, and regulatory controls take precedence over the KPI.
Process or Lifecycle
- Schedule-Ready Backlog leads to Build Committed Schedule.
- Build Committed Schedule leads to Freeze and Timestamp Baseline.
- Freeze and Timestamp Baseline leads to Execute Schedule.
- Execute Schedule leads to Disposition at Window Close.
- Disposition at Window Close, when Completed per rule, leads to Completed.
- Disposition at Window Close, when Approved deferral, leads to Deferred.
- Disposition at Window Close, when Approved exception, leads to Cancelled.
- Disposition at Window Close, when Not completed, leads to Missed.
- Execute Schedule, when New work after freeze, leads to Emergent Work Log.
- Missed leads to Classify Variance Cause.
- Completed leads to Compliance Review.
- Deferred leads to Compliance Review.
- Cancelled leads to Compliance Review.
- Classify Variance Cause leads to Compliance Review.
- Emergent Work Log leads to Compliance Review.
- Compliance Review leads to Corrective Actions.
- Corrective Actions leads to Build Next Baseline.
Roles and Responsibilities
| Role | Responsibility |
|---|---|
| Maintenance Scheduler | Builds and freezes the baseline, maintains the emergent-work log, reconciles dispositions |
| Maintenance Manager | Chairs compliance review, approves controlled exceptions, owns corrective-action follow-through |
| Maintenance Planner | Investigates readiness and planning-related misses |
| Operations Leader | Confirms access and operations-driven changes |
| Storeroom / Procurement | Confirms material-availability causes |
| Reliability Engineer | Reviews repeat causes and systemic patterns |
Required Inputs
- Frozen baseline and freeze timestamp
- Scheduled work-order population
- Completion evidence and status history
- Deferred and cancelled disposition records
- Emergent or break-in work log
- Variance-cause codes
- Material, labor, access, and readiness evidence
- Prior-period variance history
Required Outputs
- Schedule Compliance percentage
- Baseline count and freeze timestamp
- Completed, deferred, cancelled, and missed disposition reconciliation
- Variance-cause distribution
- Emergent-work count
- Baseline-exception log
- Corrective actions with owners and due dates
Step-by-Step Implementation
1. Define the measurement period
Choose the schedule window used by the organization and apply it consistently.
2. Define completion before the period starts
Document what qualifies a work order as completed. If partial credit is permitted, define the rule before execution rather than after results are known.
3. Freeze the baseline
At the agreed freeze point, capture the committed work-order population and timestamp it. Preserve this snapshot even if the live schedule later changes.
4. Track emergent work separately
Work identified after freeze should be logged as emergent or break-in work. Do not silently insert it into the original baseline.
5. Reconcile every baseline item
At window close, every baseline item should be traceable to an outcome such as completed, approved deferred, approved cancelled/exception, or missed.
6. Classify misses
Useful variance categories supported by the source include:
- readiness/planning gap;
- access denied by operations;
- materials unavailable;
- labor unavailable;
- operations-driven change;
- scope change.
7. Review causes
Discuss the percentage together with the disposition and cause breakdown. Assign actions to the function capable of correcting the cause.
8. Preserve the record
Retain the baseline, exception record, variance causes, emergent-work log, and corrective actions so trends can be compared across periods.
Decision Rules
- Scheduled Work Not Completed leads to Ready at Freeze?.
- Ready at Freeze?, when No, leads to Readiness / Planning Gap.
- Ready at Freeze?, when Yes, leads to Operations Denied Access?.
- Operations Denied Access?, when Yes, leads to Access Denied by Operations.
- Operations Denied Access?, when No, leads to Materials Available?.
- Materials Available?, when No, leads to Materials Unavailable.
- Materials Available?, when Yes, leads to Required Labor Available?.
- Required Labor Available?, when No, leads to Labor Unavailable.
- Required Labor Available?, when Yes, leads to Operations Changed Commitment?.
- Operations Changed Commitment?, when Yes, leads to Operations-Driven Change.
- Operations Changed Commitment?, when No, leads to Scope Changed?.
- Scope Changed?, when Yes, leads to Scope Change.
- Scope Changed?, when No, leads to Escalate for Classification.
Do not leave missed work uncoded simply because the cause is disputed. Escalate the classification instead.
CMMS Considerations
A CMMS supporting Schedule Compliance should provide:
- baseline snapshot or equivalent frozen-schedule record;
- freeze timestamp;
- disposition fields separate from generic work-order status;
- variance-cause code;
- emergent/break-in flag;
- controlled cancellation or exception reason;
- audit history;
- reporting that reconciles the baseline population automatically.
The live schedule should not overwrite the historical baseline used for the KPI.
SAP PM Considerations
In SAP PM, the frozen baseline may require a scheduled-order extract or site-specific snapshot because the system does not inherently make a weekly schedule immutable as a separate object. System statuses such as released, confirmed, or technically complete can support the process, but a status alone should not override the organization’s documented completion rule.
Deferred and cancelled work should use controlled, queryable reason codes where the site configuration permits. Variance causes should be represented through controlled coding rather than free text when practical. Exact implementation depends on SAP release and local configuration.
Metrics and KPIs
Schedule Compliance
Definition: Percentage of frozen-baseline scheduled work orders completed according to the documented completion rule.
Formula:
Schedule Compliance = Completed Scheduled Work Orders ÷ Total Scheduled Work Orders × 100
Units: Percent
Interpretation: Shows how reliably the organization executes the schedule it committed to.
Limitations: Easily distorted when the baseline changes, completion rules change mid-period, or missed work is cancelled or removed after freeze.
Example: 64 completed orders from an 80-order frozen baseline:
64 ÷ 80 × 100 = 80%
Compliance Variance Classification Rate
Definition: Share of missed baseline items carrying an approved variance-cause code by review time.
Formula:
Coded Missed Items ÷ Total Missed Items × 100
Units: Percent
Interpretation: Indicates whether misses are being converted into usable cause information.
Limitations: High coding coverage does not prove that classifications are accurate.
Repeat-Cause Variance Rate
Definition: Share of classified misses repeating a previously identified cause for the defined asset, work center, or crew population.
Formula:
Repeat-Cause Classified Misses ÷ Total Classified Misses × 100
Units: Percent
Interpretation: Highlights recurring systemic causes requiring upstream action.
Limitations: Requires consistent cause definitions and comparable review periods.
Baseline Integrity Rate
Definition: Share of baseline items that remained unchanged after freeze or changed only through an approved exception or break-in process.
Formula:
Unaltered or Approved-Exception Baseline Items ÷ Total Baseline Items × 100
Units: Percent
Interpretation: Tests whether schedule changes are controlled.
Limitations: Does not mean the schedule itself was good; it measures integrity of change control.
No universal target is defined for these metrics. Targets must reflect local risk and operating context.
Common Failure Modes
- Removing missed work from the denominator after freeze
- Cancelling difficult work without an approved exception
- Changing the completion rule after results are known
- Folding emergent work into the original baseline
- Leaving missed work without a cause code
- Treating deferred work as completed
- Reporting the percentage without the disposition reconciliation
- Lowering the target instead of correcting recurring causes
- Using Schedule Compliance as an individual technician score
Best Practices
- Freeze at the same defined point each period.
- Preserve the original baseline.
- Publish the completion rule before execution.
- Reconcile all dispositions before reporting.
- Report emergent work alongside the KPI.
- Classify every miss before the review discussion.
- Track repeat causes across periods.
- Assign corrective actions to planning, operations, materials, labor/capacity, or other responsible functions based on evidence.
- Never compromise safe work or required verification to protect the number.
Maturity Levels
| Level | Practice |
|---|---|
| 1 — Ad hoc | Percentage reported without controlled baseline or cause classification |
| 2 — Defined | Freeze point and completion rule documented |
| 3 — Managed | Baseline reconciled; misses classified; recurring review in place |
| 4 — Integrated | Variance causes route to responsible functions and supporting metrics are tracked |
| 5 — Learning | Recurring causes drive upstream process changes |
Real-World Example
A packaging plant freezes 80 work orders for the week. At window close, 64 meet the site’s completion rule. The initial Schedule Compliance result is 80%.
The useful analysis begins with the 16 orders that were not completed. Two have documented, approved baseline exceptions. The remaining misses are classified by cause. The largest category is readiness/planning gaps, followed by unavailable materials.
The review therefore does not conclude simply that “maintenance needs to improve compliance.” Planning reviews its readiness criteria, while the storeroom and procurement teams investigate the material constraint. The next week’s percentage is measured using the same baseline and completion rules so the trend remains comparable.
Audit Questions
- Was exactly one baseline frozen for the period?
- Is the freeze timestamp recorded?
- Was the completion rule defined before execution?
- Does every baseline item have a disposition?
- Does the disposition total reconcile to the baseline?
- Are cancellations supported by approved exception records?
- Is emergent work reported separately?
- Does every missed item have a variance cause?
- Are causes supported by evidence?
- Are recurring causes receiving corrective action?
- Were safety or quality requirements ever relaxed to protect the metric?
- Can the reported percentage be reproduced from source records?
Related Reliability Method Topics
- Maintenance Scheduling
- Maintenance Planning
- Backlog Management
- Planning and Scheduling Governance
Related Tools and Assets
Potential future assets include:
- Schedule Compliance Calculator
- Frozen Schedule Baseline Template
- Variance Cause Classification Guide
- Schedule Compliance Review Agenda
- Baseline Exception Form
- Schedule Compliance Dashboard
- Schedule Compliance Audit Checklist
These assets are not created by this document.
References
- RM-MKS-6013 — Schedule Compliance
- RM-MKS-6003 — Maintenance Scheduling, authoritative Schedule Compliance formula
- RM-MKS-6002 — Maintenance Planning
- RM-MKS-6007 — Backlog Management
Public derivative source: Draft. Publication status: Not Authorized.