Calculate on-time performance among completed deliveries in one declared cohort. Undelivered orders, including overdue backlog, are excluded from this denominator.
Completed-cohort on-time delivery
93.52%Completed deliveries only. Every undelivered order, including overdue backlog, is excluded.
on-time completed ÷ eligible completed × 100
ONE DEFINED OPERATING COHORT
Aggregate-count-only; no timestamp/CSV ingestion, ETA prediction or live shipment lookup. Use one completed-in-period cohort and a consistent delivery/order/shipment unit; exclude overdue-undelivered and not-yet-due undelivered from both numerator and denominator. Use prevalidated counts from the same original customer promise, timezone and cutoff. Exactly at cutoff qualifies; no implicit grace or revised-promise substitution.
THE FIELD NOTES
Use the result now, then read the practical notes for assumptions, examples, limitations, and the choices behind it.
231 ÷ 247 × 100 = 93.522267…%; exactly 16 completed deliveries were late.
Divide on-time completed deliveries by all eligible completed deliveries in the same measurement period. Counts must use one consistent unit, customer promise, timezone and cutoff. A delivery exactly at cutoff counts as on time under this convention.
Of 247 completed deliveries, 231 on time gives 93.52% and exactly 16 late. At very large volumes the displayed percentage can round to 100.00% while a nonzero late count remains.
Exclude every undelivered order, both overdue and not yet due, from numerator and denominator. This can make completed-only OTD improve while overdue backlog worsens. Aggregate counts cannot verify timestamps or missing promise records; prevalidate them. This is not OTIF, ETA or a live carrier lookup.
For made-to-order goods, inspect queue, setup, run, move and wait with the manufacturing lead time calculator; OTD alone does not identify the cause of lateness. Track fulfillment spend separately with the fulfillment cost calculator, using its own fulfilled-order volume rather than copying the completed-delivery denominator.
THE PRODUCT IS NEXT
Divide on-time completed deliveries by all eligible completed deliveries in the same measurement period. Counts must use one consistent unit, customer promise, timezone and cutoff. A delivery exactly at cutoff counts as on time under this convention.
Of 247 completed deliveries, 231 on time gives 93.52% and exactly 16 late. At very large volumes the displayed percentage can round to 100.00% while a nonzero late count remains.
Exclude every undelivered order, both overdue and not yet due, from numerator and denominator. This can make completed-only OTD improve while overdue backlog worsens. Aggregate counts cannot verify timestamps or missing promise records; prevalidate them. This is not OTIF, ETA or a live carrier lookup.
For made-to-order goods, inspect queue, setup, run, move and wait with the manufacturing lead time calculator; OTD alone does not identify the cause of lateness. Track fulfillment spend separately with the fulfillment cost calculator, using its own fulfilled-order volume rather than copying the completed-delivery denominator.
No. This completed-cohort convention excludes all undelivered orders. Review overdue backlog separately; an improved completed-only percentage can conceal worsening backlog.
The percentage is unavailable because the denominator is zero. The tool does not report 0% or 100%.
No. It measures time-only performance from entered aggregate counts. It does not check completeness, damage, timestamps or current shipment status.
BUILT BY LOOK ATLAS
Turn a simple product photo into polished, campaign-ready creative for your store, ads, and social channels. No studio. No reshoots.
Create your first shoot free, then keep going when you’re ready.