On-Time In-Full | Measuring Whether the Real Delivery Promise Was Kept

On-Time In-Full, usually shortened to OTIF, asks whether the complete promised quantity reached the required receiver within the agreed delivery time or delivery window.

In one line: OTIF combines two questions that are too easy to separate—did it arrive when promised, and did the whole promised delivery arrive?

This is Article 21 in eduKateSG’s 100-article logistics authority build. The canonical parent remains How Logistics Works. Batch 05 established the logistics clock. Batch 06 begins measuring whether the receiver-facing promise was actually kept.

Why “Delivered” Is Too Weak

A shipment can be delivered and still fail the receiver.

• It arrived one day late.
• Ten cartons were promised but only nine arrived.
• The first half arrived on Monday and the rest on Wednesday.
• The order reached the right company but missed the receiving appointment.
• The goods arrived before the agreed window and the receiver had no capacity to accept them.

OTIF exists because a binary “delivered/not delivered” metric compresses too much of the actual promise.

OTIF Begins With the Promise Definition

There is no useful OTIF metric without a precise service agreement.

What counts as on time? Exact appointment? Calendar day? Business day? A two-hour delivery window? What counts as in full? Every ordered line? Every unit? The quantity confirmed at order acceptance? The quantity remaining after an agreed amendment?

Different organisations use different detailed rules. That is acceptable if the rules are explicit and consistently applied. It becomes dangerous when one team measures against the requested date, another against the confirmed date and a third quietly moves the promise after the shipment is already late.

A metric cannot be stricter than its definition and cannot be more honest than its denominator.

On-Time and In-Full Should Be Tested Together

Suppose a customer orders 100 units for Tuesday.

• 100 arrive Tuesday: on time and in full.
• 100 arrive Wednesday: in full, not on time.
• 80 arrive Tuesday: on time for what arrived, not in full.
• 80 arrive Tuesday and 20 Wednesday: the order is complete eventually, but the original Tuesday promise was not met in full.

Separating the two measures can hide the real failure. A company can report excellent on-time delivery for partial shipments while the receiver experiences shortages. Or it can report excellent fill performance while full orders consistently arrive late.

OTIF Can Be Measured at Different Levels

Measurement level changes the result.

• Order level: the entire order passes or fails.
• Order-line level: individual product lines are evaluated separately.
• Unit level: the proportion of individual units that met the promise is measured.
• Shipment level: each dispatched shipment is assessed rather than the customer’s original order.

For customer experience, order-level measurement is often severe but revealing: one missing critical line can make an otherwise large delivery operationally useless. Unit-level measures can show the scale of shortage but may understate the impact of a small missing component.

The Denominator Can Make OTIF Look Better Than Reality

Suppose one hundred customer orders were originally accepted. Ten become difficult. If those ten are cancelled, postponed or removed from the denominator after problems appear, the final OTIF number can improve without logistics improving.

This is a classic metric failure: redefine the measured population until the performance looks healthier.

Good governance therefore records the original promise, legitimate customer-approved changes and the final outcome separately.

Requested Date and Confirmed Date Are Different Claims

A customer may request Monday while the supplier confirms Wednesday. Measuring against Monday asks whether customer demand was met. Measuring against Wednesday asks whether the supplier kept the promise it accepted.

Both questions can be useful. They should not be confused.

This is especially important when upstream inventory or production constraints sit outside logistics execution. A logistics team can deliver perfectly against a Wednesday commitment even though the customer’s desired Monday date was not achievable.

Early Delivery Is Not Automatically On-Time

If a factory, hospital, shop or construction site has limited receiving capacity, arriving two days early can create storage, labour or safety problems.

“On time” therefore often means within an agreed window, not simply before a deadline.

This returns to the receiver principle: performance should be measured against the useful handoff, not against the carrier’s preference to finish the job early.

In-Full Depends on What Was Actually Promised

If an order requests 100 units and the supplier accepts only 80, the in-full test depends on the contractual or operational promise being measured.

For logistics execution, it may be fair to ask whether the 80 confirmed units arrived in full. For customer-demand performance, the missing 20 still matter.

Strong reporting can show both rather than forcing one number to answer two different questions.

OTIF Failure Should Be Decomposed by Cause

A failed OTIF order tells you that the promise was not met. It does not tell you why.

• Inventory was not physically available.
• Receiving or putaway errors created phantom stock.
• Picking was incomplete.
• Packing missed the carrier cut-off.
• The carrier arrived late.
• A hub connection was missed.
• Border release took longer than expected.
• The final-mile delivery attempt failed.
• The receiver could not accept the load.

This is why metric decomposition matters. ASCM’s SCOR framework explicitly organises metrics hierarchically so lower-level measures can diagnose performance gaps in higher-level outcomes.

OTIF Is a Receiver Metric, Not a Department Trophy

A warehouse may hit its dispatch target. A carrier may hit its transit target. A terminal may process within standard time. The order can still fail OTIF if the connected sequence does not reach the receiver as promised.

This is a useful antidote to local optimisation. Departmental success does not add automatically to receiver success.

OTIF and Lead Time Are Different

Lead time measures elapsed duration. OTIF tests that duration and quantity against a promise.

A five-day route can have excellent OTIF if five days is the agreed service and it performs reliably. A two-day route can have poor OTIF if it repeatedly promises one day and misses.

OTIF and Arrival Variability Are Connected

A narrow delivery window is harder to meet when arrival variability is high.

Arrival Variability explains why late tails matter. OTIF converts that distribution into a service outcome: did each order fall inside or outside the accepted window?

A High OTIF Can Still Hide Damage

An order can arrive on time and in the full ordered quantity while some goods are damaged, temperature-compromised or supported by incorrect documentation.

That is why OTIF is not the final definition of a perfect order. Article 22 expands the promise to condition, documentation and other receipt requirements.

How to Make OTIF Useful

1. Define the promise. Record requested, confirmed and revised dates separately.
2. Define the time rule. Exact time, day or window.
3. Define in-full. Order, line, unit and tolerance rules.
4. Preserve the denominator. Do not silently remove difficult orders.
5. Freeze legitimate amendments with timestamps. Changes after failure should not rewrite history.
6. Measure the receiver event. Dispatch is not delivery.
7. Decompose failure causes. Inventory, warehouse, carrier, border, receiver and other categories.
8. Segment intelligently. Customer, lane, product, site and service level can behave differently.
9. Pair OTIF with quality metrics. Damage and documentation still matter.
10. Use trends and distributions. One monthly percentage can hide unstable subgroups.

OTIF at Three Zoom Levels

One order

Did the complete promised quantity reach the receiver inside the agreed window?

One customer or lane

Which recurring failure mode prevents promises from being kept?

One network

Are poor results caused by shared capacity, inventory, handoff or timing dependencies across several routes?

A Singapore Lens

Singapore’s dense distribution environment can make physical distances short while service windows remain demanding. Retail receiving slots, industrial sites, air-cargo connections and port-linked flows all depend on more than simply “arriving in Singapore”.

The relevant event is the agreed receiver handoff. OTIF makes that boundary explicit.

Hostile Test: “Our OTIF Is 98%, So Logistics Is Excellent”

Ask how the 98 per cent was built.

Which date is used? What tolerance counts as on time? Are partial orders excluded? Are customer-approved changes separated from supplier-driven changes? Are failures concentrated in one critical customer or product? Does damaged freight still count as success?

A percentage is the end of a calculation, not the end of an investigation.

OTIF Audit

• What exact promise is being measured?
• Requested date or confirmed date?
• What delivery window counts as on time?
• What level defines in full?
• How are legitimate amendments recorded?
• Can failed orders disappear from the denominator?
• Is the receiver event used rather than warehouse dispatch?
• Are early deliveries treated appropriately?
• Which cause categories explain OTIF failure?
• Do different customers or lanes behave differently?
• Is OTIF paired with damage and documentation quality?
• Did improving the metric improve the receiver’s actual operation?

Evidence and Further Reading

The World Bank’s Logistics Performance Indicators 2.0 provide the wider current evidence frame by measuring observed supply-chain speed and reliability. ASCM’s SCOR Digital Standard treats reliability and responsiveness as explicit performance attributes and uses hierarchical metrics so operational causes can be connected to strategic service outcomes.

Return to the Logistics Hub

OTIF measures one of the most important receiver-facing promises. Return to How Logistics Works for the full execution chain. Continue next to The Perfect Order | When Accuracy, Condition, Documentation and Timing Must All Hold.

---

Final compression: OTIF is powerful because it refuses to let speed hide shortage or completeness hide lateness. It asks the receiver’s practical question: did the whole promised delivery arrive when we agreed it would?