The document is a receipt, and the law treats it as one #
On international road movements the mechanism is explicit. Article 13 of the CMR Convention, in the schedule to the Carriage of Goods by Road Act 1965, states that after arrival of the goods at the place designated for delivery:
the consignee shall be entitled to require the carrier to deliver to him, against a receipt, the second copy of the consignment note and the goods
Article 9(1) makes the consignment note prima facie evidence of the making of the contract of carriage, its conditions, and the receipt of the goods by the carrier.
So the signed note is not an administrative courtesy. It is the evidence that the carrier performed. Article 5 requires three original copies, one handed to the sender, one to accompany the goods, one retained by the carrier, which is why the copy that matters to the office is travelling in a cab rather than sitting in a filing system.
Why the clock on a POD is shorter than people assume #
The reservation periods in Article 30 are short and they are specific:
| Situation | When a reservation must be made |
|---|---|
| Loss or damage that is apparent | At the time of delivery |
| Loss or damage that is not apparent | Within seven days of delivery, Sundays and public holidays excepted |
| Delay | In writing within twenty-one days from the time the goods were placed at the disposal of the consignee |
Article 32 then sets a period of limitation of one year for actions arising out of carriage under the Convention, extended to three years in the case of wilful misconduct. The practical consequence is that a POD which surfaces three weeks after a query is often too late to be useful in the conversation it was needed for, even though the underlying liability may still be live for a year.
Domestic work sits under whatever conditions of carriage the parties agreed rather than under the Convention, so the periods differ. The shape does not: a short window to raise a problem, a longer window in which it can be argued about, and a document that has to be produced on demand in both.
Why the document goes missing, specifically #
It is worth naming the actual failure points, because they are not the ones people blame.
-
The POD is created outside the business
It is signed at a consignee's gatehouse, on a forecourt or on a yard, by somebody who does not work for either party and has no interest in the copy.
-
Nothing downstream of delivery depends on it
The driver's next job starts whether or not the office has the paperwork. The consequence lands days later, on somebody else's desk.
-
The signature is often illegible or generic
A surname and a squiggle is a receipt, but it is a weak one when a consignee later says nothing arrived.
-
The office does not know what is missing until it looks
Absence is not an event. Nobody is notified that a POD did not arrive, so the gap is only found when somebody compares delivered jobs against held documents.
That last point is the one worth sitting with, because it is the difference between a job that is hard and a job that is merely invisible. Knowing which delivered loads have no proof of delivery against them is a set difference between two lists. It requires no transport knowledge at all. It just requires somebody to do it, on a day when the phones are busy, which is why it slips to Friday and then to next Friday.
What the missing document costs downstream #
Billing is the obvious one, and it is covered in detail on invoicing against PODs. The point to register here is that the delay compounds. GOV.UK states that where no payment date is agreed, payment is late 30 days after the customer gets the invoice or after the goods are delivered.
The less obvious cost is on the phone. A consignee ringing to ask whether something arrived is a question a complete POD file answers in seconds and an incomplete one turns into a chase, a callback and an apology. That conversation is the subject of where is my delivery calls.
Which parts of the POD cycle run on rules #
Runs on rules
- Knowing which delivered jobs have no POD against them, a set difference between two lists
- Knowing which of those are now blocking an invoice, the same list filtered by billing status
- Knowing which sit inside or outside a reservation period, which is date arithmetic against published periods
- Filing an arriving document against the right job, if the references are on it
- Retrieving a POD when a customer queries a delivery, which is a lookup
Needs a person
- Deciding whether a damage claim should be accepted, which is a liability question
- Deciding how hard to push a consignee who will not sign properly, which is a relationship question
- Deciding what to change about a route that keeps producing disputes, which is a management responsibility
The split is familiar from every other sector on this site. Detection and retrieval are mechanical. What to do about what was detected is not.
The which tasks run on rules checklist is a fast way to test your own POD process against that line, and the chasing payment calculator shows what the delay between delivery and invoice is worth in cash terms. For the compliance documents that travel with the same driver on the same day, see drivers' hours record keeping.