Resources/Glossary/
On-Time Delivery
Lean Metrics and Measurement

On-Time Delivery

The customer-facing grade. Everything else is a story you tell yourself.

Updated
·
4
min read
Definition

What is On-Time Delivery?

On-time delivery, or OTD, is the share of customer orders delivered by the date promised, usually expressed as a percentage. A shop running 95 percent OTD ships 95 of every 100 orders by the committed date. OTD is the most visible customer-facing quality metric in manufacturing because it is the one customers feel directly, and it is the first number purchasing departments cite when they consider switching suppliers.

On-time delivery is the metric the customer keeps. Every other quality and flow metric in the shop is internal. OTD is the one your purchasing contact reports up the chain on a quarterly basis. It is also the one most likely to be defined dishonestly inside the shop. A 96 percent number generated by counting ship date against promised date can sit alongside a 78 percent number generated the way the customer sees it, and both are accurate to their definitions. The conversation worth having is which one is true.

"The customer keeps their own scorecard. Your version is for you."

How on-time delivery works

The calculation is simple in form and contentious in practice: orders delivered on time divided by total orders in the period, expressed as a percentage. The contention is in every word of that sentence.

The definitions that matter

A real OTD definition pins down each of these before the first measurement:

  • On time against what date. The customer's originally requested date is the strict version. The mutually agreed promise date is the operational version. Both are defensible; you cannot use the second one and claim the first.
  • By shipment or by line. A single order with twelve line items where one ships late is one missed line or one missed order, depending on the rule. Customers usually count by line.
  • Ship date or delivery date. Ship date is easier to measure and softer. Delivery date is what the customer experiences. A two-day transit gap can swing the number by several points.
  • Window or strict. Some customers accept a delivery window of plus or minus one day. Others want the date exactly. The rule should match the customer's expectation, not the shop's preference.

When the customer's scorecard and the shop's internal report disagree, the customer is right by definition. Aligning the internal definition with what the customer measures is the first improvement most shops make to OTD without changing anything else.

Where on-time delivery fits on the shop floor

Imagine a 50-person fab shop running stainless steel components for two food-equipment OEMs. The shop reports 94 percent OTD internally. The bigger customer just sent a quarterly review showing the shop at 81 percent on their scorecard. The owner is upset; the data feels wrong.

The reconciliation walks through the definition gap. The shop counts ship date against the date the shop's order desk promised. The customer counts delivery date against the date the customer originally requested when they placed the order. Two days of transit and an average four-day push of the promise date account for almost all of the gap. The customer is not wrong. The shop's internal number was measuring the wrong thing.

The fix is structural. The order desk starts logging both the requested date and the promised date on every order. OTD gets reported against both. The shop now sees what the customer sees, which exposes a pattern: a single bottleneck operation is responsible for almost every late commitment, and the order desk has been quietly padding lead times around it. Fixing the bottleneck moves OTD against requested date from 81 to 92 over two quarters. The customer notices first. Not the dashboard.

Common mistakes with on-time delivery

  • Counting ship date instead of delivery date. Ship date is easier and looks better. Delivery is what the customer feels.
  • Counting partials as on-time. A nine-of-ten line shipment is not nine-tenths on time. The customer placed one order.
  • Averaging across customers. A flattering shop-wide number can hide a punishing miss rate at the customer that matters most.
  • Padding the promise. Quoting longer lead times to make the date easy to hit looks fine on the scorecard until a competitor quotes a shorter lead time the customer prefers.
  • Logging misses without root causes. Counting the misses is bookkeeping. Identifying the recurring reasons is the actual improvement work.

On-time delivery and related Lean tools

On-time delivery is the customer-facing twin of schedule adherence, which measures whether the shop hit its own internal plan. It depends directly on stable lead time, because OTD is impossible to honor reliably when the time from order to ship swings unpredictably. In high-mix environments, build-to-schedule is the upstream metric that determines whether OTD is achievable in the first place. OTD belongs on the short list of lean KPIs every shop watches weekly.

Common questions

The questions we hear most about this term.

How does on-time delivery work in practice?
You decide what counts as on time, then you count. The decision matters: ship date or delivery date, promised date or required date, by shipment or by line item. Most customers care about delivery date by line item against the date they originally asked for. Most suppliers measure ship date against the date they promised, which is almost always a softer measure. You count orders that hit the window, divide by total orders shipped in the period, multiply by 100. The number is honest only if the definition matches what the customer is grading you against.
How is on-time delivery different from schedule adherence?
OTD is customer-facing. Schedule adherence is internal. OTD measures whether the customer got their order when they expected it. Schedule adherence measures whether the shop produced what its own internal schedule said it would on that day. A shop can run high schedule adherence and still miss customer dates if the schedule itself was wrong. A shop can run good OTD with poor schedule adherence if it is constantly expediting to recover. Both metrics matter; they answer different questions.
What are common mistakes with on-time delivery?
The biggest is using a definition that flatters the shop. Counting ship date against the promised date instead of delivery date against the customer's requested date. Counting partial shipments as on-time when the customer wanted the whole order. Excluding orders that were rescheduled at the shop's request. The second is averaging across customers and products. A 90 percent OTD that hides 70 percent for your biggest customer is a number that lies. The third is gaming the promise: pad the lead time so the date is easy to hit. The customer notices.
When should I worry about on-time delivery?
Worry the moment a single high-value customer's OTD drops, regardless of the overall average. That customer's purchasing department is already talking about it internally. Worry when OTD is trending down even slightly over several weeks, because the cause is structural and waiting will not fix it. Worry when the same root cause shows up repeatedly in your miss log. A flat OTD with rotating excuses is masking a single underlying problem nobody has solved.
What does on-time delivery look like as a working metric?
A weekly review where every miss is logged with a root-cause note: late supplier, machine breakdown, scheduling error, order change. A trend chart visible to the shop, not just to management, because the floor is where the misses happen and where they get fixed. A customer-specific cut for the top three to five customers by revenue. A monthly look at the miss reasons in aggregate, with the top one or two becoming the next problem-solving project. Not a dashboard. A working number that drives the next thing the shop fixes.

Ditch the whiteboards and spreadsheets.

Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.