What it means
Choose the exact physical custody point, such as depot gate, cross-dock or partner loading bay, because a departure manifest and later sort scan can frame the event but may not be the agreed handoff. Establish which partner must acknowledge the agreed unit, since a driver's load scan, depot gate record and receiving clerk's counted acceptance can have different meanings.
GS1 transport information guidance describes standardised logistics event identification and scans, but actual custody rights depend on contracts and carrier terms. Map pallet, carton and consignment IDs across both carriers before computing the interval, as a relabelled handling unit without a cross-reference can create a false missing case or attach proof to the wrong order.
Record the sending and receiving counts, so if the partner accepts only some cartons those units close while the remaining discrepancy stays open. For loads with mixed destinations, split quantities by onward partner, since one trailer signature may not mean every downstream carrier accepted every carton.
Use the physical event time and retain the delayed electronic upload time, because offline scanning or batch feeds can make a prompt transfer look late. Keep the two parties' conflicting timestamps without overwriting either, and let a supervisor reconcile them against gate records, scan logs and signed manifests.
Set a clear clock rule, since local time zones and delayed uploads confuse elapsed time. Distinguish clean receipt from receipt with damage or seal reservation, since both acknowledge custody but the condition dispute must remain visible.
Calling the handoff unconfirmed hides the transfer, while calling it clean hides the damage. A rejected shipment needs a documented reason and return movement, and for sensitive units check seal or temperature evidence where the agreement requires it.
Keep contractual risk transfer separate from this operational timestamp, because the contract, not a dashboard calculation, determines liability for a missing carton. Communicate only verified status, so do not tell the customer the local partner has the parcel before that partner confirms.
A quick handoff is not a final-mile delivery, and customer arrival estimates and proof of receipt sit outside this custody measure. Show open cases and the oldest transfer beside median lag, since a single high-value missing handling unit can matter more than many fast routine acknowledgments.
Review repeated gaps by site and shift, because slow device synchronisation, unclear sign-off roles and a real custody break need different remedies. Where a unit passes through several depots, report each agreed custody boundary separately and treat confirmation quality as distinct from speed.
In practice
Real-world examples.
Example
A line-haul driver delivers a trailer to a partner's cross-dock at 16:00. The partner counts and signs for 24 of 26 cartons at 16:40, so the 24 are closed with a 40-minute lag and the missing 2 stay open as a discrepancy.
Example
A regional grocery distributor hands over chilled pallets and the receiver notes a broken seal. The acknowledgment is recorded together with the condition exception so neither is hidden.
Example
A depot in a remote area uploads scans only when its device reaches a network at night. The team keeps the physical scan time and the upload time separately, so a slow connection is not mistaken for a slow handoff.
Formula
Calculation
Confirmation lag = Verified receiving-partner acknowledgment timestamp - defined physical tender timestamp. Show partial and unresolved transfers separately.
Worked example. A fictional line-haul carrier tenders three pallets to a local partner. The acknowledgments arrive 40 minutes, 2 hours and 22 hours after tender.
- Total lag = 40 + 120 + 1,320 = 1,480 minutes.
- Average lag = 1,480 / 3 = 493 minutes, or about 8 hours 13 minutes.
- Median lag = 120 minutes, so the 22-hour outlier is what the average is hiding, and that single pallet is investigated first.Case study
Seen in the real world.
This entirely fictional and illustrative case follows Kestrel Freight, an invented line-haul carrier. Its reports showed an average handoff confirmation lag of 3 hours, but customers kept asking where their parcels were. Reviewing the oldest open transfers showed that most of the delay sat in one partner depot where the evening shift had no one assigned to sign manifests.
Kestrel assigned a sign-off role to the evening shift and began reporting median lag, oldest open transfer and the share of confirmations with a condition note. Median lag fell from 95 minutes to 35 minutes, and the oldest open transfer dropped from 31 hours to under 6. The change also exposed that some quick acknowledgments omitted damage notes, which the team then required as part of a clean handoff.
Watch out
Common mistakes.
- Using an outbound scan as proof of receiving custody.
- Closing a partial transfer as fully accepted.
- Ignoring system-upload delay when interpreting timestamps.
Questions
People also ask.
Is this delivery time?
No. It measures the custody transfer between delivery partners.
What if cartons are missing?
Record partial receipt and investigate the missing units.
Who bears loss?
The contract and facts decide; the metric does not.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related