Schedule attainment is the percentage of the planned production schedule a line actually completed in a given period. The clean formula is completed planned work ÷ planned work, with the numerator capped at the plan for each product so that overbuilding one item cannot paper over shortfalls on another.

Here is the trap in one sentence: a plant can report 100% schedule attainment and still have shipped none of what a customer ordered. If you measure attainment as one big volume number, total units built over total units planned, then building extra of an easy product hides a total miss on a hard one. The aggregate looks perfect; the shipping dock is on fire. This post covers how to calculate schedule attainment so it can't lie, why volume and mix are different questions, and where attainment ends and adherence to plan begins.

What is schedule attainment?

Schedule attainment answers one question: did we build what we said we would? It compares what the plan called for against what the line actually produced, over a defined window, a shift, a day, a week. Stated simply, Schedule attainment % = completed planned units ÷ planned units × 100. A line that planned 1,000 units and built 1,000 of the right ones is at 100%.

The word that does the work is planned. Attainment is not "how much did we make", it is "how much of the plan did we make." That distinction forces one rule that separates a real metric from a vanity one: cap the numerator at the plan, product by product. If you planned 500 of Product A and built 700, you get credit for 500, not 700. Without the cap, overproduction on the easy items inflates the score and the metric quietly stops measuring the schedule at all.

Same total volume, missed mix: A overbuilt, C not built (illustrative)1000 planned, 1000 built, but not the right 1000 (illustrative)unitsProduct Aplan 500built 700Product Bplan 300built 300Product Cplan 200built 0Volume attainment reads 100%. Mix-aware schedule attainment reads 80%. Product C shipped nothing.
Illustrative. Overbuilding Product A exactly offsets the miss on Product C, so a naive total-volume attainment reads 100% while a customer waiting on Product C got nothing.

How do you calculate schedule attainment correctly?

Score each product against its own plan, cap at the planned quantity, then sum. Using the numbers above with hypothetical quantities:

ProductPlannedBuiltCounted (capped at plan)
A500700500
B300300300
C20000
Total1,0001,000800
Hypothetical. Capping each product at its plan gives 800 counted units against 1,000 planned, a true schedule attainment of 80%, not the 100% a raw volume total would report.

True schedule attainment = 800 ÷ 1,000 = 80%. The uncapped volume version = 1,000 ÷ 1,000 = 100%. Same shift, same line, a 20-point difference, and the 20 points are exactly the customer promises that just slipped. The cap is not a technicality; it is the entire difference between a number that manages the plan and a number that flatters it.

Two more rules keep the metric honest. Count only good units toward attainment, a unit built but scrapped did not attain anything, and count against the schedule that was frozen at the start of the window, not one quietly rewritten mid-shift to match whatever the line happened to produce. A schedule you edit to fit the output is a schedule that always reads 100% and never tells you anything.

Why is hitting the volume but missing the mix still a miss?

Because customers order products, not units. Schedule attainment treats a unit of Product A as interchangeable with a unit of Product B, and in a mixed-model plant that assumption is simply false. The volume can be perfect while the mix is a disaster, and the mix is where late shipments, expedited freight, and angry phone calls actually come from. A single aggregate percentage can hide a serious mix problem behind a comfortable-looking number.

Volume attainment 100% versus mix-aware schedule attainment 80% (illustrative)Two numbers, one shift (illustrative)100%Volume attainment80%Mix-aware schedule attainment
Illustrative. The two dials describe the same shift. The volume gauge says the plant hit its number; the mix-aware gauge says one in five planned units never got built.

What is the difference between schedule attainment and schedule adherence?

Schedule attainment asks whether you hit the planned volume; adherence asks whether you made the right things, in the right quantities, in the right sequence. Attainment is a scoreboard at the end of the window. Adherence is a moment-by-moment question about whether the line followed the plan as written, and a line can be at 100% attainment and badly out of adherence if it built everything the plan called for but in the wrong order, finishing the low-priority job first and the hot customer order last.

The two metrics answer to different owners. Attainment is a planning-and-output number the plant manager watches; adherence is a sequencing-and-discipline number the scheduler and supervisor watch. You want both green. Attainment without adherence means you eventually built the right stuff but shipped it late; adherence without attainment means you followed the plan faithfully until the line stopped producing. Measuring only one leaves half the failure invisible, which is why mature plants track schedule attainment, mix, and plan adherence together rather than collapsing them into a single percentage.

By the numbers. Schedule attainment is a standard, benchmarked manufacturing metric, APQC tracks "production schedule attainment" as a process-efficiency measure in its Open Standards Benchmarking program, reported as a percentage across top, median, and bottom performers. Because the honest version depends on capping to plan and counting the right mix, published benchmarks are only comparable when everyone defines the numerator the same way, which is exactly why the definition, not the target, is the thing to nail down first.

How do you measure schedule attainment without fooling yourself?

Freeze the plan, score to it, and refuse the shortcuts that turn the number green. The sequence:

  1. Freeze the schedule at the start of the window. Snapshot the planned quantity per product before the shift runs. This is the yardstick; if it moves, there is no measurement.
  2. Count only good units, per product. Scrap and rework do not attain the schedule. Tie the count to the same records that feed first pass yield so quality and attainment can't disagree.
  3. Cap each product at its planned quantity before summing. This one step is the difference between measuring the plan and measuring your own optimism.
  4. Report attainment and the mix, not just the total. A single percentage hides which products missed. Show the per-product shortfalls next to the roll-up.
  5. Log a reason code for every miss. Downtime, changeover overrun, material short, quality hold, a missed schedule without a cause is a complaint, not data. Feed the codes to a Pareto to rank what's actually breaking the plan.
  6. Review attainment, adherence, and the top miss reasons together, every day. The daily cadence is what turns the metric into corrective action instead of a monthly autopsy.

What breaks schedule attainment most often?

Attainment misses cluster into a short list of usual suspects, and naming them is how you stop re-solving the same one every week. The most common are, in rough order:

The pattern across all four is that attainment is downstream of decisions made in production scheduling and staging, not just execution on the floor. That is why the fix is rarely "run faster" and usually "plan to real capacity, stage completely, and shrink the changeovers", and why reason codes on every miss are what tell you which of the four is actually costing you the schedule.

How does schedule attainment connect to OEE and the losses?

Schedule attainment is the plan-level scoreboard; OEE and the six big losses are the machine-level explanation for why it came out the way it did. When attainment misses, the cause almost always lives in the losses: a breakdown ate the hours, changeovers ran long, minor stops dragged the throughput below what the plan assumed, or a quality hold pulled good units off the count. Reading attainment next to OEE turns "we missed the schedule" into "we missed because Availability collapsed on line 3 at 2 p.m.", a fixable statement instead of a lament. It also sits at the top of the manufacturing KPI stack, where it connects the floor to the promises sales made to customers.

The honest version of the metric is only as good as the production count and the reason codes behind it, and both are exactly what paper tracking loses. Hand-tallied output invites the quiet mid-shift schedule edit; missed-reason codes scribbled from memory at end of day rank nothing. Plants that capture good counts and stop reasons live off the equipment, the way Harmony feeds production and downtime data into dashboards the whole shift can see (see the platform or the CLS field story), get a schedule attainment number they can actually stand behind, with the mix and the miss reasons attached. That is when attainment stops being a report and starts being a steering wheel.