In this article

Decide what the record must establish

A delivery photograph can show a package at a location without establishing who accepted it or whether a discrepancy was recorded. A signature can confirm receipt while leaving condition or quantity unresolved. Before choosing a proof method, identify the question the handover record is meant to answer. Different movements may require different evidence.

For a 3PL and fulfilment arrangement, map the points where goods move between parties. Specify the shipment reference, package or unit count, receiving role and relevant condition check. Agree what the receiver is confirming, and keep any commercial acceptance or payment decision separate where it has a different owner. One status should not silently stand in for several decisions.

Make exceptions visible at the moment of transfer

Describe how a shortage, damaged package, broken seal or refused delivery should be recorded. The process needs a responsible contact and an instruction for the goods while a decision is pending. An exception should not disappear because a Captain must close a task in an app or because the normal receipt screen has no suitable option.

Use terms that all participating teams understand. “Received with a discrepancy” conveys a different state from “accepted in full.” Where a system cannot represent the required distinction, agree a controlled supporting record and connect it to the shipment reference. The aim is a traceable account that the sender, transporter and receiver can reconcile without reconstructing the entire journey from separate messages.

Collect enough evidence, with clear boundaries

Choose evidence proportionate to the handover. A package label, count or authorised receipt may resolve the operational question without capturing a person’s face or a private interior. Explain who can see the record, where it is stored and how a correction is made. Avoid collecting identity documents simply because a camera is available.

The UN system’s privacy principles provide a reference for clear purpose, proportionate data collection and limited retention. These principles govern the UN context; they are useful design prompts here rather than a statement of local legal requirements. Agree the applicable privacy obligations and operational needs with the organisations responsible for the actual delivery arrangement.

Connect the record to resolution

A handover record has value when someone uses it to resolve an outstanding issue. Assign an owner, connect follow-up actions to the original reference and preserve the initial observation when a later decision is added. That helps distinguish what was seen at delivery from what was established after investigation.

Review recurring discrepancies with the relevant operating partners. Repeated count differences may require a loading change; recurring receipt disputes may require clearer confirmation language. Do not assume every problem originates with the last person who handled the goods. A useful proof process supports an understandable chain of custody, a fair review of exceptions and a specific improvement to the next handover.