What Is Schedule Adherence and Why Is It the KPI Nobody Tracks?
Your OTIF looks fine. Your utilization numbers look fine. And yet, every week, the plan you published on Monday barely resembles what actually happened on the floor by Friday. If that sounds familiar, you're not measuring the one KPI that would explain the gap.
Schedule Adherence measures how closely actual production matches the planned schedule, in sequence, timing, and duration, not just whether the order shipped on time. It's the metric that connects the plan to the execution, and it's almost entirely absent from most manufacturers' KPI dashboards, even though it's often the earliest warning sign of a scheduling process in trouble.
What is Schedule Adherence, exactly?
Schedule Adherence (sometimes called Schedule Compliance or Plan Adherence) is the percentage of scheduled operations that start and finish within their planned time window, in the planned sequence, on the planned resource.
It's not the same as OTIF. OTIF tells you whether the customer order shipped complete and on time. Schedule Adherence tells you whether the internal production plan was actually followed to get there and a plant can hit OTIF while quietly missing its schedule on nearly every job, simply by expediting, overtime, and last-minute resequencing.
- Measures start-time accuracy, finish-time accuracy, and sequence accuracy
- Calculated per resource, per shift, or plant-wide
- Distinct from OTIF, which measures customer-facing delivery performance
- A leading indicator which moves before OTIF does
Why does nobody track it?
Three practical reasons explain why Schedule Adherence rarely makes it onto a dashboard, even at plants with mature MES and ERP systems.
First, it requires two data sets that rarely talk to each other. You need the planned schedule (usually from an APS or a scheduler's spreadsheet) and the actual execution data (from the MES or manual shop-floor logs), timestamped and matched operation by operation. Most plants have one or the other, not both cleanly linked.
Second, it's uncomfortable to measure. Low adherence exposes how much firefighting is really happening and how many jobs get resequenced, expedited, or split mid-shift. Teams that are used to being judged on OTIF alone have little incentive to surface a metric that shows the plan itself isn't being followed.
Third, without an APS, there often isn't a real schedule to adhere to. If planning happens at the day level in the ERP with infinite-capacity assumptions, there's no minute-by-minute sequence to compare execution against in the first place, so the KPI has nothing to measure itself against.
How do you calculate Schedule Adherence?
The formula is straightforward once the two data sets are aligned:
"Within tolerance" is typically defined per plant : a common industry starting point is a ±15% time window on planned start and finish times, though high-precision environments (pharma, food safety with strict CIP timing) often tighten this to ±5–10%.
- Extract the planned schedule for the period (from APS or scheduling tool), including planned start time, end time, and resource for each operation.
- Extract actual execution data for the same operations from the MES or shop-floor logs.
- Match planned vs. actual operations on a common key (work order + operation + resource).
- Flag each operation as "adherent" or "non-adherent" based on your tolerance window for start time, duration, and sequence.
- Divide adherent operations by total scheduled operations to get the percentage.
- Segment the result by resource, shift, and product family to locate where deviation concentrates.
What is a good Schedule Adherence target?
There's no universal number, but industry benchmarks give a useful reference point for discrete and process manufacturers running moderate-to-high SKU complexity.
A realistic target for most plants moving from ERP-only planning to a finite-capacity APS is a 20–30 percentage point improvement in Schedule Adherence within the first two quarters, alongside the OTIF and changeover gains typically seen in that window (see our "5 KPIs in 90 Days" article).
Why does low Schedule Adherence quietly cost more than it looks like?
Think of Schedule Adherence like a GPS's estimated arrival time versus what actually happens when you ignore every rerouting alert. The destination might still get reached eventually, but every ignored deviation compounds — more fuel, more stress, more unplanned stops. On the shop floor, that compounding shows up as three concrete costs.
Work-in-Progress (WIP) inflates. When operations don't start when planned, downstream stations either sit idle or get starved, and WIP buffers grow to absorb the mismatch. That's capital sitting on the floor instead of shipping.
Changeover costs multiply silently. A sequence built around a changeover matrix to minimize setup time only works if operations actually run in that sequence. Every resequenced job on the floor can reintroduce a changeover the schedule was specifically built to avoid.
Root cause analysis becomes guesswork. Without adherence data, a plant manager sees that OTIF dropped but can't tell whether it was a machine breakdown, a material delay, or simply that the schedule was never followed in the first place.
How does Schedule Adherence connect to APS and MES?
Schedule Adherence is, structurally, the metric that closes the loop between an APS (Advanced Planning and Scheduling) system and an MES (Manufacturing Execution System). The APS produces the finite-capacity plan; the MES reports what actually happened; Schedule Adherence is the comparison between the two.
This is also why the KPI is nearly impossible to track meaningfully with an ERP-only setup. An ERP's infinite-capacity, day-level plan doesn't carry enough granularity to compare against real execution timestamps. There's no minute-by-minute sequence to hold the floor accountable to.
Where MangoGem fits
This is exactly the gap MangoGem APS Optimizer is built to close. Because it generates a finite-capacity, resource-level, minute-by-minute schedule, the planned side of the equation that most plants simply don't have at the right granularity, it gives Schedule Adherence a precise baseline to measure against for the first time. Where real-time status is fed back from the MES, that plan can then be compared against actual execution and re-optimized as deviations appear.
When a deviation shows up, wether it is a late material, an unplanned downtime, an operator running a job out of sequence, the downstream schedule can be re-optimized immediately instead of letting the gap between plan and execution silently widen for the rest of the shift. The plan adjusts to reality instead of becoming irrelevant by 10 a.m.
If you're moving from this article into the product, the industry terms used above map onto MangoGem's own model like this:
The practical outcome: schedulers get a schedule worth adhering to, and management gets a leading indicator that predicts OTIF problems before they show up on the customer-facing dashboard.
FAQ
1. Is Schedule Adherence the same as OTIF?
No. OTIF measures whether customer orders shipped complete and on time. Schedule Adherence measures whether internal production actually followed the planned sequence, timing, and resource assignment to get there. A plant can maintain OTIF through expediting while still having poor Schedule Adherence.
2. What tolerance window should I use to calculate Schedule Adherence?
Most manufacturers start with a ±15% window on planned start and finish times, then tighten it for high-precision environments such as pharmaceutical or food production with strict CIP timing requirements.
3. Can I track Schedule Adherence without an APS?
It's difficult. Without a finite-capacity, minute-by-minute schedule to compare against, there's no meaningful baseline for "on schedule." ERP-only, day-level plans generally lack the granularity needed.
4. What's a realistic Schedule Adherence target?
Above 90% typically indicates a tightly coupled plan-and-execution loop, usually achieved with an integrated APS and MES. Plants moving from ERP-only planning often see 20–30 percentage point gains within the first two quarters of implementing finite-capacity scheduling.
5. Why does Schedule Adherence matter more than utilization alone?
High utilization can coexist with a schedule that's constantly reshuffled. Machines stay busy, but on the wrong jobs, in the wrong order, at the wrong time. Schedule Adherence catches that misalignment; utilization alone does not.
Want to know more about the APS? Request a MangoGem APS demo and we will show you what it could make for you.