A customer calls 45 days after delivery saying the goods never arrived. You check your paperwork. The driver said it went fine. You think there’s a signed form in the truck somewhere.
That’s not a proof of delivery. That’s a dispute you’re going to lose.
Proof of delivery — POD — is the document that confirms a shipment was received at the destination. For a carrier, it’s the paper trail between a completed delivery and a paid invoice. Without a defensible POD, you have no leverage when a customer disputes a delivery, files a damage claim, or simply refuses to pay.
What a Complete POD Captures
A POD that holds up under scrutiny has six elements:
The receiver’s name. Not a squiggle. The name of the person who physically accepted the shipment — printed or clearly legible. “Left at dock” is not a signature.
Date and time. Date alone isn’t enough for time-sensitive freight or anything with an appointment window. The timestamp matters.
Piece count and condition. Number of units or pallets received. Any visible damage noted at time of delivery. If the receiver notes damage on the POD, that notation is part of the record — which protects you from claims filed weeks later for damage that may have happened after delivery.
Signature. A handwritten signature on paper or a captured digital signature on a device. A driver’s verbal account of how the delivery went is not documentation.
Reference numbers. The BOL number, your order reference, and the customer’s PO number if applicable. These tie the POD to the specific shipment so it can be matched to the invoice without question.
Photos. For any load where damage is a realistic concern — temperature-sensitive freight, high-value goods, fragile items — photos at delivery are increasingly the standard. A photo of the load at the dock, showing condition and timestamp, closes most disputes before they start.
Why Paper POD Fails
The failure scenario plays out the same way every time:
Driver gets a signature at delivery. Paper POD goes in the cab. Driver returns to the yard, POD goes in a folder or a box or somewhere in the office. Forty-five days later, a customer disputes the delivery or questions the condition of goods.
Now you’re searching through paper. You find the form — maybe — and it’s smudged, or faded, or the signature is illegible, or it was filed under the customer name spelled three different ways. You scan it at 400% zoom and email a blurry image.
The customer says the signature doesn’t match their receiving manager. You have no metadata, no timestamp, no photo.
The paper POD’s fundamental problem: the document exists separately from the trip record. There’s no automatic connection between the delivery event and the file. That gap is where disputes live.
Digital POD Closes the Gap
When a driver captures POD on a mobile device, several things happen automatically that paper can’t replicate:
The timestamp is embedded at capture — tied to the device clock at the moment the signature is drawn, not filled in manually afterward. The photos are attached to the same record. The GPS coordinates of where the capture happened are logged. All of it is associated with the specific trip and visible to the dispatcher the moment it uploads.
When a customer disputes a delivery made six weeks ago, you pull up the order, open the POD, and send the link. The signature, the timestamp, the photos, and the delivery location are all there. The dispute is typically resolved in the same conversation.
What Makes a POD Legally Defensible
A POD is a business record. If a dispute goes to collections or small claims court, it needs to:
- Identify the receiver by name
- Show when delivery occurred with a timestamp
- Be clearly linked to the specific shipment by reference number
- Not have been altered after the fact
Digital PODs with embedded metadata — device timestamp, GPS coordinates, driver ID — are harder to challenge than paper. The metadata isn’t something you can retrospectively fill in.
One practical note on damage claims: a signed POD is not a complete shield against liability for concealed damage (damage that wasn’t visible at delivery). But a clear POD showing the load’s condition at the time of delivery shifts the burden of proof significantly.
How CyVeR Handles POD
CyVeR’s CyVeRDriver Android app handles POD capture at delivery. When a driver marks a delivery complete, they capture photos of the load and the receiver’s signature on-screen. Both are uploaded to the order record and immediately visible to dispatchers.
The POD record is tied to the trip with the delivery timestamp. Dispatchers can send the POD to the customer manually from the order view when needed. If the driver’s device has no connectivity at delivery, the POD queues and uploads when signal returns.
POD capture is included on all CyVeR plans.