A proof of delivery app proves three different things.
A proof of delivery app is supposed to settle one question: did the shipment actually get where it was going? In practice that question splits into a signature, a photo, and a GPS geostamp, and they don't prove the same thing. Most field service apps bolt a capture step onto the last stop of a route without explaining which of the three it's actually giving you.
This page covers what each method actually proves, what USPS and UPS capture under those names today, where the ESIGN Act and the Carmack Amendment fit in, and where a proof-of-delivery step belongs if you're building the rest of the route app yourself.
The short version
Signature names a person. Photo and geostamp name a place.
A proof of delivery app can rely on a signature, a photo, a GPS geostamp, or all three together. A signature is the strongest single piece of evidence because it names a recipient, but it only works if someone is there to give it. A photo and a geostamp both work with no one home, but they prove where the device and the package were, not who took possession. Electronic signatures are legally valid under the ESIGN Act, and for freight moved by a motor carrier, the Carmack Amendment is what actually governs how a delivery dispute gets resolved. The rest of this page walks through each method, then where proof of delivery fits once it's part of a bigger route app.
The three methods
What actually counts as proof of delivery.
“Proof of delivery” isn't one fixed format. USPS defines its own Proof of Delivery service as an emailed record containing the delivery information, the recipient's name, the tracking number, and an image of the signature. See USPS's own definition. Most delivery apps built since then extend that same idea with a photo and a location stamp, so it helps to treat the three as separate tools rather than one interchangeable feature.
Signature capture
A signature is the only one of the three that names a specific person. USPS's Signature Confirmation service, for example, tells the sender the date and time an item was delivered or an attempt was made, tied to a signature at the door. Read USPS on Signature Confirmation. The obvious limitation is that it needs someone present to sign, which makes it the weakest option for the growing share of deliveries where nobody answers the door.
Photo capture
A photo proves the item was left somewhere, whether or not anyone was home to accept it. UPS now offers this directly as photo proof of delivery through UPS My Choice, viewable alongside the standard tracking history. See UPS Tracking Support. A photo's weakness is the mirror image of a signature's: it can show exactly where a package landed without saying anything about who, if anyone, ever picked it up.
GPS geostamp
A geostamp attaches a GPS coordinate and a timestamp to the delivery event itself, usually stored alongside a photo. It doesn't require the recipient to do anything, which makes it the one method that works even when nobody is reachable at all. The tradeoff is that it proves where the device was, not who received the package, so it's strongest paired with a photo of the item at that same location. Getting the accuracy right — GPS drift, location permissions, telling a stopped delivery from a driver stuck at a red light — is its own engineering problem, one we cover separately in GPS in delivery apps.
Where records actually fail
None of the three methods fail the same way.
A capture method can be technically present and still not hold up. These are the three gaps that actually show up in disputed deliveries.
No timestamp
A photo or signature with no time attached can't establish when the item actually arrived, only that it eventually did.
No location match
GPS coordinates that don't match the delivery address undercut a claim instead of strengthening it — a stop logged from the truck's last parking spot proves the driver was nearby, not that the package reached the door.
No exception note
“Left with neighbor” or a gate code that never got written down turns an ordinary delivery into an unexplained one the moment somebody asks about it.
Side by side
Signature vs. photo vs. geostamp, compared.
None of the three is strictly better — each answers a different question when a delivery gets disputed.
| Method | What it proves | Works with no one home | Strength in a dispute | What it needs |
|---|---|---|---|---|
| Signature capture | A specific person accepted the item | No | Strongest — names a recipient | Recipient present at the door |
| Photo capture | The item was left at a specific spot | Yes | Moderate — proves location, not recipient | A camera and a driver who frames the shot well |
| GPS geostamp | The device was at the address at a given time | Yes | Moderate — proves device location, not the item | Location permission and accurate GPS |
| Signature + photo + geostamp | Recipient, item location, and time together | Falls back to photo + geostamp | Strongest, and works whether or not someone answers | All three, wired into one capture flow |
Try it
Would your delivery record hold up in a dispute?
Check off what your current proof of delivery app actually captures on every stop, not just the ones that go smoothly.
0 of 6 · Thin. This would be hard to defend if a customer disputed it.
The full path
How a stop becomes a defensible record.
Four steps, and the second one is where most of the actual proof gets decided.
- 1
Arrive
The driver's app confirms the stop, usually because it's already sequenced into a route. This is the last moment the delivery location is unambiguous — everything captured after this point is evidence, everything before it is just a plan.
- 2
Capture
A signature, a photo, a GPS geostamp, or some combination gets attached to the stop, right there, not reconstructed later from memory. Which method runs depends on the shipment: signature-required packages prompt for a signature first and fall back to a photo if no one answers.
- 3
Attach
The order or tracking number, the timestamp, and any driver notes — a gate code, "left with neighbor," a damaged-box flag — get tied to the same record as the capture itself, not stored as a separate note somewhere else.
- 4
Resolve
If a customer or shipper later disputes the delivery, this record is what gets pulled up. A complete one settles the question in seconds; a partial one turns into a back-and-forth about what actually happened.
Pick your delivery
Not every stop needs the same capture.
The right method depends on what's being delivered and where, not on picking one method for every stop on the route.
Try it
Which proof do you actually need?
Pick the description closest to what you're actually delivering.
A timestamped photo at the door covers most of these
For a standard, non-signature package, a photo of the item at the drop point already matches what carriers like UPS offer as their default proof of delivery. A geostamp alongside it is a cheap way to make the record stronger without adding a step for the driver.
The legal side
Is an electronic signature legally valid?
Yes. The Electronic Signatures in Global and National Commerce Act, better known as the ESIGN Act, has said since 2000 that a signature, contract, or record “may not be denied legal effect, validity, or enforceability solely because it is in electronic form.” Read 15 U.S.C. § 7001. A finger-drawn signature on a driver's handheld device qualifies exactly the same way a signed paper delivery slip would. The law doesn't mandate any particular signature-capture technology; it just removes “it's electronic” as a reason to throw the record out.
What settles an actual dispute
For property moved by a motor carrier, the Carmack Amendment (49 U.S.C. § 14706) is the federal law that actually governs how a delivery dispute over loss or damage gets resolved, and it doesn't specify a required proof-of-delivery format at all — a carrier's liability isn't even voided by failing to issue a receipt. Read 49 U.S.C. § 14706. In practice that means whatever proof of delivery actually exists — signature, photo, geostamp, or scan history — is what a claim gets decided on, which is the real argument for capturing more than one method rather than betting on a single format being enough.
Where it lives
Proof of delivery is the last stop on a route, not a separate app.
Capture rarely stands alone in practice. A delivery route planning app already knows the stop order, the address, and the expected arrival window for every drop, so proof of delivery is just the last screen of that same stop, not a reason to open a second app.
A bolted-on signature capture app
- Captures a signature or photo at the door
- Lives outside the app for route planning, so it's a second login and a second place to check
- Every extra tap at the door is a chance to skip the record entirely
- Doesn't know your exception codes or client-specific instructions
Proof of delivery built into the route app
- Same signature, photo, or geostamp capture, one tap after the last stop is marked complete
- One login, one app, for route planning and proof of delivery together
- Exception codes and client instructions are fields you defined, not a vendor's fixed form
- Nothing to reconcile between a route planner and a separate capture tool
The best route planning app for a delivery business is the one where a driver never has to switch out of the app for route planning to a separate signature capture app just to close out a stop. This tends to compound with everything else a driver already does: a route only exists because someone decided which driver runs it, which is its own problem covered in crew scheduling app, and the same driver logging stops between deliveries is usually the one whose miles need to roll into an app for tracking business mileage for reimbursement. None of these are separate problems once they're all screens in the same app.
When to build your own
A proof of delivery step that fits your exceptions.
Off-the-shelf route software usually ships with one fixed capture flow — a signature field, maybe a photo — and no room for the exception codes, client-specific instructions, or multi-method fallback a real delivery operation actually needs. A team whose process doesn't fit that off-the-shelf tool tends to end up building its own, which is what Newly is for: describe the stop fields, the fallback rules between signature, photo, and geostamp, and whatever else the delivery needs to connect to, and it builds a real native app around them instead of around a vendor's fixed capture screen.
Sources
Where the specifics came from.
The definitions and legal rules on this page come straight from USPS, UPS, and federal law, not secondhand summaries:
FAQ
Proof of delivery, answered.
Proof of delivery is a record showing a shipment reached its destination. The exact contents vary by carrier, but USPS defines its own Proof of Delivery service as an emailed record containing the delivery information, the recipient's name, the tracking number, an image of the recipient's signature, and the printed name and address. Most delivery apps today extend that idea with a photo of the item at the drop point and a GPS-stamped location and time, on top of or instead of a signature.
Build proof of delivery into the route, not next to it.
Signature, photo, geostamp, or all three — the record only holds up if it's captured at the stop, not rebuilt afterward. Build it into the rest of your route app in Newly, starting at $25 a month.