On this page
Measure on-time delivery against an agreed milestone at each stop. If one site counts arrival at the gate and another counts completion of unloading, record both timestamps and use the milestone agreed for each booking.
Agree how to count rebookings
Keep the original window and any revised window with the approval time. Agree whether you report against the original, revised or both. A revised appointment can show that dispatch recovered the movement, while the original appointment still tells you whether the initial plan held.
Worked example: ten booked deliveries
Seven stops meet their original window, two miss it and one has no timestamp. Report 7 of 10 confirmed on time and one unknown. If you also report performance among stops with evidence, label it separately as 7 of 9. Ask the receiving team to confirm the missing record before changing the weekly result.
Use the result to change one thing
Group late stops by the confirmed reason. If most involve waiting for a bay, try confirming unloading capacity earlier. Record the owner and check whether the change helps next week. Pair this scorecard with the Synesys post-delivery review.
“An EPCIS event records what was involved in a business process step, when the event took place, where it took place”
For on-time delivery reporting, apply that principle by recording the shipment reference, gate or dock location and actual milestone time. Save the appointment window alongside that event, including who approved any revision. The event tells you what happened, while the appointment tells you what was promised.
Set up the review before the first trip. Have dispatch confirm which stops count, the receiver’s time zone, whether an early arrival is accepted and which evidence takes priority if records differ. Keep timestamps from the original source. Where a driver report and gate log disagree, leave the result provisional until the owner reconciles the records. Group the weekly results by site and milestone so that a change in the mix of deliveries does not look like a change in service.
Further reading Kweli’s freight job closeout guide.
On-time delivery checklist
Agree which timestamp counts, the delivery window and how rebooked jobs are treated. Keep the original and revised commitments to make the measure auditable.
Worked example
Of 20 deliveries, 16 met the original window and two met only a revised window. Original-window performance is 80%. If the agreed revised-window measure includes those two, report 90% separately.
When designing shared job records, capture what happened, the time and location, and the business context. See the GS1 EPCIS visibility standard.
Keep deliveries with a missing timestamp in a separate data-quality count. If 16 of 20 deliveries have usable timestamps and 14 were on time, report 14 of 16 with four missing. Show the missing count beside the percentage.
Cover photo by U.S. Army. Cropped and branded.
On-time delivery FAQs
Does on-time delivery mean gate arrival or completed unloading?
Use the milestone agreed with the receiver. Record both timestamps where possible, and compare only stops measured against the same milestone.
How should I count an approved rebooking?
Keep the original and approved revised windows. Report the original-window result separately from recovery against the revised slot.
How should I report a missing timestamp?
Mark the stop unknown and show the missing count beside your rate. If you publish a rate for stops with evidence only, show that denominator explicitly.