Proof of delivery that settles disputes: photos, signatures and scans

Every courier knows the call. "The parcel never arrived." The driver remembers the street but not the door. The paper manifest has a scribble that could be anyone's initials. You credit the delivery to keep the customer, and the cost comes out of your margin.

The takeaway: proof of delivery is only useful if it answers the next question someone will ask. A signature answers "who took it?", a photo answers "where was it left?", a location answers "was the driver actually there?", and a scan answers "was it the right parcel?". Choose the proof for each kind of delivery based on the question you expect, then make it impossible to skip.

The four kinds of proof, and the question each one answers

Most disputes are settled by combining two of them. A photo plus a location stamp settles almost every "it was never delivered" claim for a safe drop. A signature plus a printed name settles most "nobody here signed for it" claims at a business.

Capture proof at pickup too

Disputes do not only happen at the delivery end. "You picked up two boxes, not three" and "it was damaged before you took it" are pickup questions. For B2B work, especially medical, legal and high-value goods, capture a signature and name at pickup, and a photo when condition matters. It costs the driver ten seconds and can save an argument.

Make proof a checklist, not a request

The weakest proof policy is a memo that says "always take a photo". Drivers are busy, it is raining, the phone is in a pocket. The policy that works is a checklist in the driver app that will not let the stop be completed until the required items are there, and a server that checks the same rules again, so nothing can be marked delivered around it.

Good rules are layered, from general to specific:

1. Company default. For example: photo optional, signature required for business deliveries, safe drop allowed with a photo.
2. Per service. An age-restricted service needs an ID check; a document service needs a signature.
3. Per customer. A pharmacy customer forbids safe drops; a retailer allows them.
4. Per address. A hospital campus gets a larger location radius.
5. Per order. A one-off "signature required" ticked by the customer.

The most specific rule wins. That way you set things once and only think about the exceptions.

Location checks without false alarms

A location check compares where the phone was with the delivery address. Set it too tight and drivers get blocked at large buildings; too loose and it proves nothing. Two settings make it practical:

• Warn rather than block for most addresses: outside the radius, the driver gives a reason ("loading dock at the back"), and the reason and the distance stay on the order.
• A larger radius per address for campuses, malls and industrial parks.

Block completely only where it really matters, and never block a driver from reporting a failed attempt.

Age and identity checks

For age-restricted goods, the rule is simple: the parcel cannot be left at the door, and the driver must check photo ID and confirm the recipient is old enough under the rules for that product in that province. A good app records that the check passed without storing the person's birth date. A delivery PIN, a short code the recipient reads from their tracking page, is a lighter alternative when you just need to be sure the right person received it.

Photos that hold up

A few habits make photos useful later:

• Show the parcel and something that identifies the place: the house number, the unit door, the reception desk sign.
• Take it after the parcel is placed, not before.
• For damage, photograph the label and the damage in one frame.
• Do not photograph people's faces or the inside of homes. You need to prove a location, not record a person.

When there is no signal

Drivers lose signal in underground parking, freight elevators and rural roads. Proof captured offline must queue on the phone and upload when the connection returns, with each action recorded exactly once. If your app loses a photo because the driver was in a basement, the proof policy has failed at the moment you needed it.

Using proof when a dispute arrives

When a customer says a parcel never arrived:

1. Open the order and check the timeline: picked up, out for delivery, delivered, with times.
2. Check the proof: photo, signature and name, location distance from the address.
3. Send the customer the evidence, politely and quickly. Most disputes end here, often with "oh, reception had it".
4. If the proof is weak, treat that as feedback on your rules for that customer or address, not just a lost parcel.

Proof also protects drivers. A driver with a clean record of photos and signatures is not the person blamed when something goes missing.

How NemiRoute handles proof

In the NemiRoute driver app, completing a stop is a live checklist: location, signature, recipient name, photo, barcode and cash collected when there is cash on delivery. You set signature, photo, recipient name, ID check and delivery PIN each to off, optional or required, separately for pickup and delivery, for the company, then per service, customer or order. Safe drops are allowed or not by the same rules and always need a photo. The location check can be off, warn with a reason, or block, with a radius from 25 m to 5 km that you can also set per service, customer or address. ID and minimum-age checks and a delivery PIN are available, and an ID check can never be left at the door. The server checks the rules again, so a stop cannot be completed around them; only an admin or operations manager can complete a stop without proof, with a written reason in the activity log. Actions and photos queue when there is no signal and are sent once.

Drivers can see the steps in the public guide Complete a delivery. For work where every handover matters, see how this applies to medical and lab couriers.

Next step

Write down the three disputes you had last quarter and the proof that would have ended each one. Then set those rules once: start free or book a demo. For the other half of the problem, read Ten ways to cut failed deliveries.