Published · Updated · GeoCliks Field Notes
what should photo proof of delivery include
A useful delivery photo records capture time and its source, GPS coordinates with reported accuracy, a readable address derived from those coordinates, the parcel and placement in context, and a photo identifier linked to an integrity record where available. Keep original files and other delivery records: an ordinary photo may still provide relevant evidence, and no photo format guarantees a successful claim or chargeback outcome. Checked time and a matching hash help evaluate the record; they do not independently prove the scene, exact location, customer receipt or who caused damage.
The five fields a delivery photo has to carry
A delivery photo is only ever read twice: once by nobody, and once by a person deciding whether to refund a customer. The second reader is the one it has to be built for. That reader asks when, where, what, and whether the file has been touched — so the photo has to answer all four on its face, without anyone having to trust the driver or the app.
| Field | Useful context | Limitation |
|---|---|---|
| Network-verified time | A capture-time reference to compare with the delivery window | Time checks do not prove the parcel was received; ordinary timestamps can still be relevant |
| GPS + accuracy radius | Reported device location and estimated accuracy | Location can be inaccurate or spoofed; the radius is not a guarantee |
| Reverse-geocoded address | A human reviewer can read the location without decoding coordinates | The address is derived from coordinates, not an independent location check |
| Parcel in context | The item, and the door or entryway it was left at | A close-up of a box could be any box, anywhere |
| Integrity seal (hash + signature) | Comparison with a trusted recorded hash helps detect changes to image bytes | A matching hash does not establish contents, recipient receipt or scene truth; a code on an edited copy does not check that copy's bytes |
What the stamp should actually look like
Burned into the image, not hidden in metadata, because the person adjudicating a dispute is looking at a screenshot pasted into a support ticket — not at an EXIF panel. GeoCliks writes it as three lines plus a code:
device 14:31:07 · network 14:31:09 · skew 2s · verified 43.65107° N 79.34015° W · ±4 m 112 Queen St W, Toronto, ON GC-8QF2-40XR-91KD
This is an illustrative record layout, not a promise that every watermark template prints every field. Check the capture's time source and status in its stored record. GeoCliks distinguishes capture time from server upload time and can mark stale or inconsistent clock checks unverified. Do not describe upload time as the time the shutter fired.
How to prepare delivery records for a dispute
- Capture at the permitted drop location, not at the van. Record visible site context; GPS alone cannot establish that a driver stood at a particular door.
- Frame the parcel and one fixed feature of the property — house number, door, gate, unit plate. The photo has to place itself.
- Let the stamp write itself. Anything a driver types by hand is a field a reviewer can discount.
- Capture offline if there is no signal, and let the app queue and sync. A dead zone should not turn into a missing proof.
- Send the verification link, not just the image. A reviewer who can re-check the code themselves does not have to trust either party.
- Keep original files, order details, delivery records and customer communications for the period required by your contracts and payment processor. Check the specific dispute deadline; there is no universal retention window.
Proof of delivery is not the same problem as route efficiency
Most delivery software sells minutes saved: stops sequenced, ETAs sent, drivers tracked. That is a real problem, and it is a separate one from evidence. A perfectly optimised route still ends in a photo that either holds up or does not. GeoCliks treats them as two modules for that reason — Delivery Routes is priced on its own as stops and drivers, while verified capture is the same engine the field-documentation plans use, verification included on every tier down to Free.
Follow-up questions
- Is a photo enough proof of delivery on its own?
- Not necessarily. A photo can support delivery records, including when it has no cryptographic seal, but it may not establish customer receipt or the condition of an item inside a package. Keep order records and customer communications. A time check or matching hash adds context without guaranteeing the dispute outcome.
- Can a delivery driver fake a proof-of-delivery photo?
- Yes. Device timestamps and EXIF can be manipulated, and a staged scene or spoofed location can precede hashing. Network-time consistency checks and comparison with a trusted original hash address particular discrepancies and later changes, not every form of false delivery evidence. Use supporting order and handoff records.
- How long should proof-of-delivery photos be kept?
- Follow the retention requirements in your customer contracts, applicable law and payment-processor guidance. Deadlines vary by dispute type and circumstances. Retain source files and associated records, and confirm access and deletion policies before cancelling a service.
- What does proof-of-delivery software cost?
- Routing and proof are usually billed differently. GeoCliks lists Delivery Routes as its own plan family priced on stops and drivers, while verified capture starts at $0 on Free — 300 captures a month, 1 seat — and $7 a month on Plus for unlimited captures and full PDF, Excel, ZIP and KMZ export. Compare per verified delivery rather than per seat; seat pricing hides the volume cost.
- Does proof of delivery work without cell signal?
- The mobile app can queue captures offline and sync later, but an offline capture is not yet a server-saved record. GeoCliks uses a recent clock check for its time-verification status; without a valid check the capture must remain unverified. Confirm location and sync status before sharing, and do not substitute the website for the mobile offline workflow.