Proof of delivery exists to answer one question at a later date: did we deliver what we said, when we said, to the right place, in the right condition? Systems that capture a signature and nothing else answer barely half of it.
What good ePOD captures
| Element | Why |
|---|---|
| Timestamp | From the device clock, ideally corroborated by network time |
| GPS position at capture | Confirms the location of the delivery, not the depot |
| Recipient name | Typed or captured, not just a scribble |
| Signature | Still expected in many trades, weak evidence on its own |
| Photograph | The strongest single element |
| Item-level confirmation | What was actually accepted, especially with partial deliveries |
| Exceptions and reasons | Damaged, short, refused, wrong item |
| Temperature reading | Where relevant to the product |
| Driver identity | Who performed the delivery |
| Device identity | Useful in disputes and investigations |
The combination of photograph, position and timestamp is what makes a delivery record hard to challenge. A signature alone is easily disputed and frequently illegible.
In most delivery operations the photograph resolves more disputes and prevents more credits than every other feature combined.
Photo standards
A photo requirement without a standard produces useless images — a blurred close-up of a wall, a shot of the driver's boot.
Define and train:
- What to include: the goods, in place, with a recognisable element of the location (door number, dock, shelf).
- When: after placement, before departure.
- How many: one for a standard delivery, more for exceptions and damage.
- Damage photos: the damage itself plus a wider shot showing the item's condition and packaging.
- Safe place deliveries: a wide shot showing where it was left and that it is not visible from the street.
Enforce with a quality sample: review a random selection weekly and feed back. Photo quality decays quietly without it.
Legal and contractual weight
Electronic records are admissible in most jurisdictions, and their weight depends on demonstrable integrity:
- Tamper evidence. Records should be immutable after capture, with any subsequent amendment recorded as a separate, attributed event.
- Complete audit trail. Who captured, when, on what device, and every access thereafter.
- Time integrity. Device clocks drift and can be changed; corroboration with server time strengthens the record.
- Retention. Long enough to cover your dispute window and any statutory period — commonly several years for commercial deliveries.
- Retrievability. Evidence you cannot produce within the dispute timeframe is not evidence. Test retrieval, including after a platform change.
Contractual points worth agreeing with customers: what constitutes proof, who may sign, what happens when nobody is available, and the time limit for raising a claim.
Exception handling
Most of ePOD's value is in the exceptions, and most systems handle them worst.
Design a short, specific exception vocabulary:
| Exception | Required capture |
|---|---|
| Short delivered | Quantity, reason, photo |
| Damaged | Photo, description, disposition |
| Refused | Reason, who refused, photo |
| Wrong item | Photo of the item and the label |
| Access failed | Photo of the obstruction, attempted contact |
| Nobody present | Photo of the premises, calling card left |
| Left in safe place | Photo, authorisation reference |
Each exception should trigger a downstream action automatically: a credit request, a redelivery, a customer notification, an investigation. An exception recorded that triggers nothing teaches drivers not to bother.
Integration into the business
ePOD data is operational evidence, but its value multiplies when connected:
- Billing. Invoice on confirmed delivery rather than on despatch, and attach the POD to the invoice. This alone removes a large share of payment disputes.
- Customer portal. Let customers retrieve their own PODs. Every self-served retrieval is a customer service call avoided.
- Claims. Automatic attachment of evidence to claims reduces both handling time and rejected claims.
- Route analytics. Delivery timestamps feed service time models.
- Quality. Damage photos aggregated by product, route and depot reveal packaging and handling problems.
Common weaknesses
- Signature capture on a slippery screen with a finger, producing a mark that proves nothing.
- No item-level detail, making partial deliveries impossible to reconcile.
- Photos stored but never retrievable by anyone outside IT.
- Exceptions recorded in free text, defeating analysis.
- No linkage between the POD and the invoice, so disputes require manual matching.
- Retention shorter than the dispute window, discovered during a dispute.
Frequently asked questions
Is a photograph better than a signature?
Generally yes. A photograph shows what was delivered and where; a signature shows that somebody made a mark. Best practice in most operations is both where a person is present, and a photograph always.
How long should we keep proof of delivery records?
At least as long as your customers' claim window and any statutory limitation period that applies — several years is common for commercial deliveries. Confirm the period with your legal adviser and ensure the records remain retrievable throughout, including after a system change.
What if nobody is available to sign?
Have a defined policy: authorised safe place with photograph, neighbour delivery with record, or return to depot. The policy must be agreed with the customer in advance, and the evidence standard for each option written down.
Can customers dispute an electronic POD?
They can dispute anything. What matters is the strength of the record: timestamp, position, photograph and item detail together are difficult to overcome. Weak records — signature only, no position — are disputed successfully far more often.
Should PODs be sent automatically to customers?
For most operations, yes. Automatic delivery confirmation with the POD attached reduces inbound queries substantially and shortens payment cycles. Make it a configurable preference per customer, since some large accounts prefer batch or EDI delivery.
