Proof of delivery: what it is and how to set it up

What proof of delivery is and why it settles disputes

Proof of delivery, often shortened to POD, is the documented confirmation that a courier completed the job: the goods were handed over, the service was performed, the recipient accepted the result. It is the last step of the order cycle and the only one that turns a promise into a fact you can show to a customer, an accountant or a court.

Three groups of people rely on that record every day, and each of them needs it for a different reason:

• The dispatcher needs to know an order is genuinely closed, not just marked as closed, so the shift can be balanced and the next job assigned.
• The finance team needs a basis for invoicing and for courier payouts — a job that was never confirmed should not be paid twice or billed twice.
• The customer needs an answer to the only question that matters when something goes wrong: who received the parcel, when, and what condition it was in.

The value of POD shows up precisely in the awkward cases. A recipient claims nothing arrived. A shop insists the box was damaged. A client disputes an invoice for a job nobody remembers. Without a record, every one of these turns into one person's word against another's, and the company usually pays to end the argument. With a record, the conversation is over in a minute.

Paper signatures versus electronic proof of delivery

The traditional scheme is familiar: the courier carries a stack of waybills, the recipient signs, the paper travels back to the office and is filed somewhere. It works, in the sense that it eventually produces evidence — but the cost of that evidence is high and the evidence arrives late.

The weak points of paper are structural rather than accidental:

• The delay. The office learns what happened only when the courier returns, so during the shift the dispatcher is blind and answers customer calls with guesses.
• Losses. Sheets get crumpled, soaked, left in a car or simply never handed in, and a missing sheet means a job with no evidence at all.
• A signature proves very little. An illegible scrawl says nothing about who signed, at what time, or in what condition the goods were.
• Manual re-entry. Somebody types the paper back into a spreadsheet, which costs hours and quietly introduces errors.

Electronic proof of delivery, or ePOD, removes the trip back to the office. The courier records the result at the doorstep, and the record appears in the system immediately, attached to the order rather than to a piece of paper. The dispatcher sees a closed job in real time, the customer sees a status, and nothing has to be typed in twice. Paper does not disappear entirely — some clients still require a stamped document — but it stops being the primary channel of truth.

What a complete POD record should contain

Confirmation is only useful if it answers the questions that come up later. A bare status flipped to done answers none of them. A record worth keeping combines several elements, each closing a different kind of doubt:

• A photo. The single most convincing element: the parcel at the door, the goods in the recipient's hands, the installed equipment, the completed work. A photo shows condition, not just fact.
• A checklist. A short list of what had to be done or checked at the stop, marked by the courier — this is what makes different couriers close jobs the same way.
• A status with a timestamp. Accepted, in transit, delivered, rescheduled, refused — the sequence of statuses reconstructs the whole story of the order.
• The result of the visit. Not every stop ends in a handover, and the record must be able to say so explicitly.

The important part is that all four live on the order itself, in one system, and are available the moment they are captured. In itlogist that is part of the standard cycle: Courier management covers order intake and dispatch, live routes on a map, the mobile app with photo reports and checklists, the customer portal with statuses, and on-site confirmation that the work was completed — so the evidence lands in the same place where the order was created.

How the courier captures proof in the field

Whatever the dispatcher screen looks like, the record is created by a person standing at a door, often in the rain, holding a box. If capturing it takes too long or demands too many taps, it will be skipped — and a system full of empty confirmations is worse than honest paper, because it looks reliable while telling you nothing.

So the field side deserves the closest scrutiny when you evaluate any POD tool:

• Barrier to entry. In itlogist the field employee works through a mobile web interface, with no mandatory app install from a store — the courier opens a link and sees their orders and route. That matters most for temporary staff and subcontractors, who would otherwise need an install, an account and a training session before the first shift.
• Photos and checklists at the stop. Capture happens where the job happens, in a couple of taps, not in a report written afterwards from memory.
• Statuses changed as the work goes. The courier updates the state of each order and the dispatcher sees it in real time, which removes the endless where-are-you calls.
• The route in the same place. The sequence of stops sits next to the confirmation step, so the courier does not juggle apps between one address and the next.

A useful test during a pilot: hand the tool to your least patient courier for one shift. If the records come back complete without anyone chasing them, the process will survive contact with a busy Friday.

Exceptions: proof matters most when nothing was handed over

Teams usually design confirmation around the happy path and then discover that the expensive cases are the other ones. Nobody was home. The recipient refused the goods. The address turned out to be wrong. The client asked to come back tomorrow. These stops produce no handover, yet the courier still spent an hour of a shift and still owes an explanation.

An exception should be recorded with the same discipline as a successful drop-off:

• A named reason chosen from a fixed list, so that reschedules can be counted and compared instead of being described in free text nobody reads.
• Evidence of the attempt — a photo at the address and a timestamp showing the courier was there.
• The next step — reschedule, return, or a second attempt — recorded on the same order rather than agreed verbally.

Two things follow from this. First, disputes about failed visits stop being unwinnable: you can show that a courier was at the address at a specific time. Second, you get statistics. When every failure carries a reason code, the pattern becomes visible after a month — one district generating most of the reschedules, one client whose addresses are habitually wrong, one time slot when nobody is ever home. Those numbers are what let you fix the causes rather than argue about the symptoms.

Rolling out electronic confirmation: a short checklist

Moving from paper to an electronic record is less a technical project than an agreement about how a job is closed. The technology is the easy half; the discipline is the part that decides the outcome. A practical order of steps looks like this:

• Define what closes a job. Write down, for each type of order, what must be captured — which photo, which checklist items, which final status. Vague rules produce vague evidence.
• Keep the courier's part short. Every extra required field is a field somebody will fake at the end of a long shift. Ask for what you will genuinely use.
• Connect the order sources. Confirmation is only worth as much as the order it hangs on: itlogist exchanges data with 1C, AmoCRM, Bitrix24 and Excel, so orders arrive from the systems you already run and statuses go back the same way.
• Open the status to the customer. A customer portal with statuses turns most support calls into a page the client checks themselves.
• Start small and fast. itlogist is built for a launch in 7 days and works without long-term contracts, and it fits teams of 5 to 100 field employees — enough room to pilot on one group of couriers before rolling out to everyone.
• Review the records weekly. For the first month, look at a sample of closed orders. Missing photos and identical checklists are early signs that the process is being worked around.

Done this way, confirmation stops being extra paperwork imposed on couriers and becomes the natural end of the job — the moment the order closes itself, the customer sees the result, and nobody has to reconstruct the day from memory.