Schedule Adherence vs. On-Time Delivery: Why You Need Both Metrics (They Measure Different Things)

Ask a plant manager how their delivery performance is and they will cite their on-time delivery rate. Ask how their production team is executing and they will probably cite the same number. The problem is that on-time delivery and schedule adherence are not the same metric. They measure different things, fail in different ways, and point to different corrective actions.

A manufacturer can run 92% on-time delivery with 65% schedule adherence — if the expediting team is skilled and the lead times are padded enough to absorb the chaos. That manufacturer looks successful on a customer scorecard while operating in daily firefighting mode. Another manufacturer can run 95% schedule adherence with 82% on-time delivery — if the sales team made promises the capacity plan could not support. That manufacturer has excellent operational discipline but a broken front-end process.

You need both metrics. They are not redundant — they are complementary, and the gap between them is where the most actionable diagnostic information lives.

Defining Each Metric Precisely

Schedule Adherence (SA)

Formula: SA = (Jobs completed on or before their scheduled completion date / Total jobs scheduled for the period) × 100

Schedule adherence is an internal metric. It measures the fidelity between what the production plan says will happen and what actually happens on the shop floor. A job is "adherent" if it finishes by the time the schedule said it would — regardless of whether that schedule date aligned with a customer promise date.

SA can be measured at two levels:

• Job level: Did the complete job finish on or before its scheduled due date?
• Operation level: Did each individual work center operation (turning, milling, deburring, inspection) finish on schedule?

Operation-level SA gives you diagnostic detail — you can see exactly which work center is the first to break the schedule. Job-level SA is the minimum viable measurement.

What high SA signals: The schedule is realistic and the shop floor is executing it. Finite capacity was accounted for. Machine availability, setup times, and operator capacity are reflected in the plan.

What low SA signals: The schedule is aspirational. It was built without accounting for actual capacity constraints, or the shop floor is being disrupted by events the schedule did not anticipate (machine failures, quality holds, material shortages, priority overrides from sales).

On-Time Delivery (OTD)

Formula: OTD = (Orders delivered on or before the customer-promised date / Total orders shipped) × 100

On-time delivery is an external metric. It measures whether the customer received their order when they were told to expect it — regardless of what the internal production schedule said. A shipment is "on time" relative to the promise date, not the production completion date.

OTD is the metric customers care about. It drives customer satisfaction scores, contract renewals, and penalty clauses in supply agreements. For Tier 1 automotive suppliers, OTD targets of 98%+ are standard contractual requirements.

What high OTD signals: Customers are getting orders when promised. This could be due to genuine operational excellence (high SA + realistic promises) or it could be due to padded lead times, heroic expediting, or selective measurement (only counting shipments that left the dock, not those that arrived at the customer).

What low OTD signals: Orders are consistently arriving late from the customer's perspective. This is almost always a revenue and retention risk.

The Four SA/OTD Combinations and What They Mean

The most useful way to use these two metrics together is the 2×2 diagnostic matrix:

High SA + High OTD: Healthy Operation

This is the target state. The schedule is realistic, the shop floor executes it, and customers receive orders on time. In this state, both metrics reinforce each other. Variability is managed, capacity is understood, and the planning process is connected to the shop floor.

High SA + Low OTD: Fix the Promise Dates

The production floor is doing exactly what the schedule asks — but customers are still not getting orders on time. The root cause is upstream: sales or customer service is committing to dates that are shorter than the true lead time embedded in the production schedule. Alternatively, the master production schedule is not aligned with the customer's requirement date.

The fix is not on the shop floor — it is in the quoting process, the MPS, and the rough-cut capacity planning that feeds promise date generation. RMDB's scheduling engine generates executable dates based on finite capacity, which can be used directly to generate customer promise dates rather than relying on sales team estimates.

Low SA + High OTD: The Dangerous Position

This combination looks fine from the outside — customers are happy, OTD is high. Internally, it is a warning sign. The shop floor is not executing the schedule, but the expediting team is working around it successfully. Every day is a heroic rescue operation.

This state is fragile. One bad week — a key machine down for three days, a senior scheduler on vacation, two critical jobs due simultaneously — and OTD collapses. The underlying SA problem that was being masked becomes suddenly visible, and customers feel it all at once.

It is also expensive. Expediting consumes planner time, creates WIP spikes (because everything is being expedited simultaneously), and drives unplanned overtime. The cost of maintaining 88% OTD through expediting is far higher than achieving 88% OTD through planning.

Low SA + Low OTD: Broken System

This is the most common state for manufacturers who contact us for help. The schedule does not reflect reality, the shop floor cannot execute it, and customers are experiencing persistent late deliveries. The fix requires a systematic approach: rebuild the scheduling process from finite capacity fundamentals, instrument SA at the work center level to find the first failure points, and stabilize the system before making customer-facing commitments.

Target Ranges for Each Metric

For most discrete manufacturers, raising SA from 75% to 90% will raise OTD by 8–12 percentage points over 6–12 months — assuming the promise-date process is also fixed.

Weekly Tracking Cadence

Both metrics should be reviewed weekly, not monthly. Monthly aggregation is too slow for corrective action — you do not want to discover a 10-point SA drop after 30 days of accumulated schedule disruptions.

Weekly SA review:

• Total jobs due this week vs. total completed on schedule
• SA by work center (to identify breakdown points)
• Trend vs. prior 4 weeks
• Top 5 jobs that missed schedule this week and root cause

Weekly OTD review:

• Total shipments due this week vs. shipped on time
• OTD by customer tier or product line
• Late shipments: days late and customer notification status
• Schedule adherence trend as leading indicator for next week's OTD risk

The SA review drives internal corrective action (capacity adjustments, constraint management, planner priorities). The OTD review drives external communication (customer notifications, expedite decisions, sales alignment).

How MPS and Rough-Cut Capacity Planning Connect Both Metrics

The Master Production Schedule (MPS) is where SA and OTD originate. The MPS translates customer demand into specific production quantities and timing. If the MPS is built without a realistic view of available capacity, it will generate promise dates that the shop floor cannot honor — creating the High SA + Low OTD or Low SA + Low OTD conditions.

Rough-cut capacity planning (RCCP) validates the MPS against available capacity at bottleneck work centers. A properly constructed RCCP check will catch over-committed periods before they hit the shop floor — allowing planners to push out promise dates, add capacity, or prioritize jobs before the schedule becomes unexecutable.

The workflow in RMDB:

1. Demand signals (orders, forecasts) feed into the MPS
2. RCCP validates MPS against machine capacity, labor, and tooling
3. Adjusted MPS generates finite-capacity job schedules
4. Schedule adherence is tracked against those finite-capacity dates
5. EDGEBI dashboards show both SA and OTD in real time, with SA as the leading indicator for on-time delivery risk

This closed loop — from demand signal through finite scheduling through SA monitoring to OTD tracking — is the operational backbone of manufacturers who consistently outperform on delivery.

Three Root Causes of the SA/OTD Gap

When SA and OTD diverge significantly, the diagnosis almost always falls into one of three root causes:

Root Cause 1: Over-promising. Sales commits to lead times shorter than the scheduling system can support. The schedule is broken before the first operation runs. Fix: connect quoting lead times to RCCP output, not sales team intuition.

Root Cause 2: Unmanaged variability. Machine downtime, quality holds, supplier late deliveries, and operator absenteeism are not reflected in the schedule. Each disruption cascades because there is no buffer management strategy. Fix: build finite-capacity schedules with realistic availability factors; add planned maintenance to the schedule rather than treating it as unplanned downtime.

Root Cause 3: Poor sequencing on constraints. Bottleneck work centers are not sequenced by due-date criticality. A lower-priority, larger batch job runs first on the constraint while a due-date-critical job waits. Fix: implement due-date-based sequencing rules on constrained work centers; review the constraint schedule daily, not weekly.

Practical Implementation Steps

1. Instrument SA at the job level immediately. If your ERP or scheduling system does not capture scheduled vs. actual completion dates by job, this is the first gap to close.
2. Add work center SA reporting within 30 days. This requires operation-level tracking — scheduled start/finish vs. actual start/finish per work center per job.
3. Plot the SA/OTD matrix monthly. Which quadrant are you in? Has the quadrant changed over the past 6 months?
4. Identify the first SA breakdown point. Which work center consistently misses its scheduled window? That is your constraint, whether it appears on a capacity report or not.
5. Fix the promise-date process. Do not allow customer promise dates to be committed without a finite-capacity check in the scheduling system.

---

---

Ready to close the gap between your schedule and your delivery performance? Contact User Solutions to see how RMDB builds finite-capacity schedules that are executable — and how EDGEBI tracks both schedule adherence and on-time delivery in a single dashboard. Trusted by GE, Cummins, and BAE Systems for 35+ years.