Define the promise, completion milestone and clock before measuring lateness. Dispatch, arrival and customer acceptance answer different questions. Preserve original and revised promises, compare eligible cases consistently, and distinguish confirmed delay from missing evidence about when a milestone occurred.
Choose the milestone that matches the service question
A warehouse may meet its dispatch target while the customer receives the order late. A project may finish technical work before approval makes it usable. State exactly what event ends the clock and where its timestamp comes from. Decide whether the measure concerns internal process reliability, a customer commitment or a contractual obligation; those questions can require different dates and qualified interpretation.
Define the promise at the same level of detail. A date, a time window and an estimated range are different commitments. Record time zone, working-day convention and exceptions such as agreed customer deferral. Do not treat the latest revised promise as the original promise. Retaining both allows separate reporting of initial reliability and performance against the currently agreed schedule.
Build a population that includes incomplete and uncertain cases
Define eligibility using the promise window or another clear cohort rule. Looking only at completed deliveries can exclude the most overdue items still in transit. Show open cases that have passed their promise separately from completed late cases. If receipt confirmation is absent, distinguish unknown delivery status from confirmed lateness; the right classification depends on available evidence and the reporting purpose.
Inspect timestamp quality and the process that records each event. Batch updates can make several deliveries appear to arrive together, and a scan may record a handoff rather than customer receipt. Review time conversions and out-of-order events before calculating durations. Keep negative or impossible intervals in an exception queue instead of converting them into zero-day delivery and making performance look faster.
Investigate the stage where delay accumulates
Break the journey into meaningful intervals such as ready-to-dispatch, carrier transit and arrival-to-acceptance. Compare like service types and routes before ranking teams. A longer international route or a required inspection can change expected duration. Stage analysis helps identify where to investigate, but a long interval alone does not establish responsibility without operational context.
Use the review to agree an action, owner and follow-up measure. A dispatch improvement should be assessed against dispatch performance and the customer outcome, because it may not resolve transit delays. Keep revisions and customer deferrals auditable. The final report should say which promise was assessed, how incomplete cases were handled and what remains unknown, rather than presenting a single on-time percentage as a complete account of service reliability.
A fictional shipment milestone review
A fictional scenario to explain the method, not a customer result or a market benchmark.
A fictional distributor promises ten orders to customers by Friday. Eight are dispatched by Wednesday and two by Thursday. By Friday's close, seven have confirmed customer receipt, two are confirmed still in transit and one lacks a reliable receipt update. Dispatch performance alone would not answer whether the ten customer promises were met.
The report shows seven confirmed on-time receipts out of ten promised orders, two confirmed overdue open orders and one unknown status. It does not call the unknown order on time, nor claim that all three remaining orders are confirmed late. On Monday, receipt evidence establishes that the unknown order arrived Friday; the dated revision raises confirmed on-time receipt to eight of ten. The team then investigates the two transit delays and retains the earlier snapshot. This preserves what was known at each cut-off while distinguishing missing evidence from an actual late arrival. The distributor also checks whether the promise was a date or a specific receiving window. If one customer required delivery before noon, a Friday afternoon arrival would need a different classification under that agreement. The rule is confirmed before comparing carriers or publishing a performance ranking.
TAKE THIS INTO YOUR NEXT CONVERSATION
A practical next-step checklist.
- Define the promise and completion milestone.
- Retain original and revised commitment dates.
- Include overdue open cases in the review.
- Separate unknown timestamps from confirmed delay.
Common questions.
Can dispatch on time prove delivery on time?
No. It measures an earlier milestone; transit and receipt evidence are needed for the customer delivery question.
Should completed-only reports include a limitation?
Yes. They can omit the most delayed cases still open, so scope and open-case status should be visible.
Further reading & source context.
These primary references provide background. They are not evidence for the fictional example above and do not endorse Accuralytix.
Found an error or a missing qualification? Send an editorial correction.
Check my data readiness.
Use a practical tool to turn this idea into a clearer starting point.
Check my data readiness