Planning versus break-in: reading your schedule compliance
Schedule compliance and break-in say more about a maintenance organisation than most dashboards. How to read them together, and what the patterns actually mean.
Key takeaways
- Schedule compliance measures whether committed work happened. Break-in measures what displaced it. Read alone, either one can lie.
- Fixed definitions beat clever targets: a number that changes meaning weekly starts arguments, not improvement.
- Each pattern of the pair points at a different failing gate: readiness, protection or capacity.
- Compliance is decided before the week starts, by job packs, kitting and access.
Most sites report schedule compliance. Fewer report break-in alongside it, and fewer again define either the same way two weeks running. Read together and defined consistently, the pair tells you more about maintenance health than a page of KPIs.
The definitions matter more than the targets. Quote a number without stating the definition and you have started an argument, not a conversation.
The two measures
Schedule compliance measures how much of the work you committed to in the frozen schedule was actually completed as scheduled. Break-in measures work that was added after the schedule was frozen.
Both need a single agreed definition, and it matters far more that the definition is fixed than where it came from. Plenty of operations have their own; where one is needed, published sets such as the SMRP best practice metrics give formulas and component definitions so a number means the same thing across sites and over time.
Reading the patterns
- Low compliance with high break-in: the schedule is not being protected. Urgency is unmanaged and the weekly plan is decorative.
- Low compliance with low break-in: the schedule is being protected but the work is not ready. Look at planning quality, materials kitting and access rather than discipline.
- High compliance with high break-in: the schedule may be padded, or break-in is quietly being absorbed into scheduled time. Check how much scheduled capacity is committed.
- High compliance with low break-in and a growing backlog: you are scheduling too little. Compliance is healthy but throughput is not.
What actually moves them
Compliance is decided before the week starts. If a job reaches the schedule without a complete job pack, kitted materials and confirmed access, it will fail and the metric will simply record that fact.
Break-in is decided by whether urgency has a gate. A single approval path, with someone senior enough to say no, turns break-in from a habit into a decision. The point is not to eliminate it, since genuine emergencies exist, but to make each instance visible and deliberate.
A frozen schedule is a promise the whole site can see kept or broken. That visibility is the point.
Using them honestly
Measure weekly, publish the same way every time, and review both numbers in the same forum with the backlog. Targets are worth setting, but a target without a stable definition invites gaming rather than improvement.
The useful question is never why compliance dropped two points. It is which gate failed: readiness, protection, or capacity.
Getting the measures working
Fix the definitions
Adopt standard formulas so the same number means the same thing every week.
Measure the baseline
Compliance, break-in, PM compliance and backlog in crew-weeks, measured consistently.
Diagnose the pattern
Read the two measures together to find whether readiness, protection or capacity is failing.
Fix the failing gate
Job pack quality, materials kitting and access, or the break-in approval path.
Review in the routine
Weekly review in the management operating system so drift gets corrected early.
Fix the definitions
Adopt standard formulas so the same number means the same thing every week.
Measure the baseline
Compliance, break-in, PM compliance and backlog in crew-weeks, measured consistently.
Diagnose the pattern
Read the two measures together to find whether readiness, protection or capacity is failing.
Fix the failing gate
Job pack quality, materials kitting and access, or the break-in approval path.
Review in the routine
Weekly review in the management operating system so drift gets corrected early.
Common questions
What is a good schedule compliance number?
One measured the same way every week, first. Published guidance such as the SMRP metrics gives reference ranges, but the trend against a stable definition tells you more than any absolute target.
Should break-in ever be zero?
No. Genuine emergencies exist, and a zero would mean urgency is being hidden inside the schedule. The aim is that every break-in is a visible, signed decision rather than a habit.
Should we measure weekly or monthly?
Weekly, matched to the scheduling cadence, and reviewed in the same forum as the backlog. Monthly averages smooth out exactly the pattern you are trying to see.
Key terms
Plain-language definitions from our glossary for the concepts this article leans on.
Standards and further reading
- Best practices, metrics and guidelines for maintenance and reliability (SMRP)
- ISO 55001:2024 Asset management system requirements (ISO)
- The Asset Management Landscape, third edition (GFMAM)
- Operations and maintenance best practices guide (US DOE Federal Energy Management Program)
- ISO 22400-2:2014 KPIs for manufacturing operations management (ISO)
Related case studies and tools
- Schedule Compliance Calculator (tool)
- Work management and scheduling uplift (case study)
Related reading
Working through something like this?
See how we approach these initiatives, or tell us what you are dealing with.