What Is Proof of Delivery — And Why a WhatsApp Photo Isn't Enough

A customer calls. "We never got our delivery." You know your driver dropped it — you watched them leave with it. But "I'm pretty sure we delivered it" isn't an argument you can win. So you check with the driver, the driver says they left it by the side door, and forty minutes later you're issuing a refund for something that absolutely got delivered.

Every delivery operation has lived this. The fix is proof of delivery, and most small fleets think they already have it because their drivers snap a photo and send it over WhatsApp. That photo is better than nothing. But in an actual dispute, it usually isn't enough. This post explains what proof of delivery really is, what evidence holds up, and where proof of delivery software earns its keep.

What "proof of delivery" actually means

Proof of delivery (POD) is the evidence that a specific item reached a specific place at a specific time. Traditionally that was a signed paper slip. The customer signed, you kept the carbon copy, and if they ever complained you produced the signature.

A signature on its own has gotten weaker over the years, partly because so many deliveries are now contactless. "Left at door" is the norm for a lot of drops, and there's no one to sign. So modern POD has shifted toward a bundle of evidence rather than a single signature:

• When the delivery happened, to the minute.
• Where it happened, by GPS, not by the address you meant to deliver to.
• What was delivered and what condition it was in, by photo.
• Who received it, by signature or ID when that matters.

The strength of your proof is how many of those four you can produce, and how hard they are to fake or misremember.

Why the WhatsApp photo falls short

A photo your driver texts you is a real piece of evidence. But look at what it's actually missing when a dispute gets serious.

No trustworthy timestamp. WhatsApp shows when the message was sent, not when the photo was taken, and the customer knows it. A driver can snap ten photos in the morning and send them throughout the day. The timing is unverifiable, which means in a real argument it proves nothing.

No location. The photo shows a door. Is it the right door? A WhatsApp image strips most location data, and even when it doesn't, nobody's checking. "That's not my house" is a hard claim to rebut with a photo that could be anywhere.

It's unstructured and unsearchable. Six weeks later, when the chargeback comes in, you're scrolling through hundreds of chat images trying to find one drop at one address on one Tuesday. Good luck. The evidence might exist, but if you can't find it in 30 seconds when the customer's on the phone, it might as well not.

It lives on a phone you don't control. The driver who took it has left. Their phone was wiped. The chat history is gone. Your business records shouldn't depend on an ex-employee's photo roll.

No caption or context. A photo of a porch doesn't say "three crates, left beside the planter, clear of the rain." When the dispute is about condition or quantity, a bare image often doesn't settle it.

What real proof of delivery software captures

Proof of delivery software exists to turn that loose photo into a record that actually holds up. Here's the difference, side by side.

With RunSheet, the driver marks a stop delivered and snaps the photo in the same tap. The record captures the timestamp and the GPS location automatically. An AI caption describes the photo in plain language — something like "Boxes left beside the front door, under the awning, clear of weather" — so the record is meaningful even to someone who wasn't there. It all lands in your dashboard, searchable by client, date, or driver, and stored indefinitely. When you need it for a dispute or an insurance claim, you export it to PDF.

The 30-second dispute

Here's the whole point in one scene. The customer calls saying the delivery never arrived. Instead of "let me check with my driver," you search their name in the dashboard, pull up yesterday's record, and read it back: delivered 2:14pm, photo of the package at their loading dock, GPS pin on their address. You can send them the photo while they're still on the line.

Most disputes don't even reach a second call. The ones that do, you win, because you're holding evidence and they're holding a memory.

When proof of delivery is worth paying for

You don't need POD software for every operation. If you do a handful of deliveries a week and have never had a dispute, a photo text is fine. The math changes when:

• Disputes cost you real money. Every "it never arrived" that ends in a refund or a chargeback is a direct loss. A few of those a month and the software is already cheaper than the problem.
• You deliver high-value or perishable goods. Condition disputes ("it arrived damaged," "it was warm") need a captioned, timestamped photo, not a chat image.
• You have staff turnover. Drivers come and go. Your delivery records shouldn't leave with them.
• You need records for insurance or compliance. A clean, exportable, timestamped trail is the difference between a paid claim and a denied one.

Where it fits in RunSheet

Proof of delivery is part of the driver flow on RunSheet's Growth plan and above. The same link your driver uses to see their route and navigate is the one they use to mark stops delivered and capture the photo — one tool, one tap, no separate app. If you also need a signature, the driver collects it on the phone screen. If you deliver age-restricted goods, the Age Verification add-on requires an ID photo before a stop can be closed, with a full audit trail.

The Growth plan is $149/mo and includes POD photos with AI captions, or you can add POD Photos to a Starter plan for $19/mo if that's the main thing you need.