What a proof of delivery is
A proof of delivery (POD) is a record that cargo was handed over at a place and time, to a named person, in a stated condition. It supports the carrier’s statement that delivery happened and the receiver’s statement of what was received. It is a handover record. It is not proof that an invoice has been paid, and it does not settle on its own whether a claim is valid.
The simplest PODs record only a signature. A useful POD also records what the signature refers to.
What to record
| Field | Why it matters |
|---|---|
| Receiver’s name and role | Shows who accepted, and whether they were entitled to |
| Date and time of handover | Fixes the moment responsibility changed hands |
| Place of handover | Matches the delivery instruction |
| Reference of the delivery | Links the POD to the order, delivery note or transport document |
| Quantity received against quantity expected | Makes a shortage or surplus visible at once |
| Condition of the packages | Records visible damage, wetness, opened or resealed packages |
| Exceptions, in words | States the specific difference, not a general remark |
| Photographs | Show packages, labels and any exception as they were |
| Signature or other acknowledgement | Shows the receiver’s acceptance of the record |
Handling exceptions
The value of a POD is greatest when something is not as expected. A clean signature next to a damaged carton hurts everyone. A specific note helps everyone, including the carrier.
- Record the exact count: "received 11 of 12 cartons; carton 7 not delivered".
- Record the condition in observable terms: "carton 4 crushed at the corner, contents not inspected".
- Photograph the exception before moving the packages.
- If the receiver refuses part of the delivery, record what was refused and the reason given.
- If the receiver signs "subject to inspection", record that, so the later inspection has a starting point.
A sanitized fictional example
Fictional example, invented to show the fields. No real person or delivery is described.
"Delivery reference DN-0001. Delivered to the receiving clerk at the stated dock at 10:42. Expected 8 pallets; received 8. Pallet 5 stretch film torn, two cartons visibly wet, photographed. Receiver signed with the note 'wet cartons, contents to be checked'."
The fields in the example are the ones from the table; a reader can see at a glance what was received, in what state and what remains open.
Location, photographs and personal data
A POD can carry a signature, photographs and sometimes a location reading. Each is personal or potentially identifying data about the receiver or the site. Collect what you need to document the handover and no more, tell the receiver what is being recorded, and keep it only as long as the purpose requires. If location is recorded, say why and let the receiver see it. Photographs should focus on the cargo and its packaging, not on people.
A QR code is a pointer, not a legal conclusion
Many delivery documents carry a QR code so that the record can be found and checked. It identifies a record. It does not by itself make a signature legally valid or the record conclusive. Whether an electronic acknowledgement has legal effect depends on applicable law and on the parties’ agreement. The GS1 Logistic Label Guideline and the GS1 Traceability Standard describe identifiers and events for tracking logistic units; they do not decide questions of legal validity.
Designing the form for the person holding the phone
A proof of delivery is often completed on a phone, at a dock, in a hurry. Keep the form short, put the exception fields where they cannot be skipped, and make the quantity a number the receiver can confirm or correct instead of a free-text box. Offer a way to continue if the signal drops and to resend if the upload fails. A form that loses data at the dock produces exactly the records nobody can rely on later.
What the receiver should be told
Before asking for a signature, tell the receiver what it confirms. A short sentence such as "this records that you received the packages listed, in the condition noted" is enough. It reduces disputes about what was agreed and shows that the receiver was given the chance to note exceptions.
After the handover
A POD is useful only if it reaches the people who need it. Decide who receives a copy, how fast, and where it is stored. Link it to the delivery note and, later, to the invoice, so that a billing question can be answered by following references instead of searching mailboxes. Keep a retention period that matches the purpose, and delete what you no longer need.
Reviewing exceptions in aggregate
Individual exceptions are claims to handle. Taken together they are information. If the same sort of damage appears at the same receiver, the same route or the same time of day, the cause is probably upstream of the person who signed, and the corrective action belongs there. A monthly look at the exceptions column is one of the cheapest quality reviews available.
Review the form itself every few months, with the people who use it at the dock. If they skip a field or work around it, the field is probably in the wrong place or asks the wrong question.
Limits of this guide
This is general guidance on content and handling. It is not legal advice and does not address the legal status of any signature or the specific privacy obligations that apply to your operation, which need a separate current review. The example is sanitized and fictional.