Proof of delivery: what the photo actually needs to show

The test a photo has to pass

A delivery photo has exactly one job: three weeks from now, a party says they never received something, and you need to end that conversation in under two minutes without anybody driving anywhere.

That gives you two separate requirements, and most operations only solve the first one.

• The photo has to prove something. A blurry picture of a stack of cartons on an unidentifiable floor proves that cartons exist.
• You have to be able to find it. This is the part that actually fails. The photo was taken. It is simply not retrievable.

What the photo needs to contain

01Something that identifies the place

A shop board, a shutter, a doorway, a counter — anything that a human being would recognise as that party's premises. A picture of goods against a blank wall could have been taken in your own godown.

This is the single most common gap. Field staff naturally point the camera down at the goods, because the goods are what they are thinking about.

02The goods, countable

Not artistic. Cartons stacked so the number can be counted, or the crates visible as separate objects. If a delivery is eight cases, the photo should let somebody count to eight.

03The signed paper, if paper exists

Where a signed challan or delivery copy is still part of the process — and in most of this trade it is — a photograph of the signed copy is worth more than a photograph of the goods. It carries the party's own acknowledgement.

If it is legible in a separate photo, take a separate photo. Do not try to fit the paper and the goods in one frame; you get neither.

04Who, where and when — attached, not written

This is the part a phone can do and paper cannot. The time, the GPS location and the identity of the person who took it should be recorded by the system at the moment of capture, not typed in afterwards by anyone.

The distinction matters exactly once — in the argument — and that is the only time it needs to matter.

What to stop capturing

Two pieces of unsolicited advice, both learned the expensive way.

Stop photographing the customer. People object, and rightly. You need the premises and the goods, not a person's face. It also raises a consent question you do not want and do not need.

Stop taking five photos per delivery. More photos feel safer and make the archive useless — nobody scrolls through 400 images looking for the right one. Two good photos with metadata attached beat five without.

The filing problem, which is the real problem

Here is the honest sequence in most distribution businesses, ours included, for years:

1. Delivery boy photographs the goods.
2. Sends it to the office WhatsApp group.
3. It scrolls away under the day's other two hundred messages.

Three weeks later a bill is disputed. The photo exists somewhere above four hundred forwarded messages, on a phone that may have been replaced, belonging to a person who may have left, in a group that may have been cleared to free up storage.

A photo is only proof if it is attached to the delivery record. Not to a date, not to a person, not to a chat — to the specific delivery line, so that opening that delivery shows the photo and opening the photo tells you the delivery. Everything else is hoping.

What we do

Delivery confirmed on the phone at the door, one or two photos captured inside the app rather than in the camera roll, time and GPS and the staff member's identity attached automatically, and the whole thing written against the delivery line in the system. Retrieval is: open the delivery, look.

The reason it works is not the photograph. It is that the capture happens where the work happens, which is the same reason a spreadsheet in the office stops being a record of what actually took place.