Proof of delivery that stands up when queries start

When delivery queries start, the difference between a quick answer and a drawn-out dispute is usually the quality of the POD. In UK haulage, a proof of delivery document is not just a signed bit of paper to satisfy admin. It is the record that shows what was presented, where it was handed over, when that happened, and whether the receiver accepted it cleanly or with exceptions.

That matters for both sides of the job. Shippers need a delivery record they can rely on for invoicing, customer service and claims handling. Hauliers need something strong enough to support payment, answer shortage or damage allegations, and stop traffic teams spending half the next day chasing signatures, timestamps and missing notes. At Haulier.AI, where we handle organised request and quote flow across urgent, awkward and routine UK haulage work, weak POD is one of the most common reasons a straightforward movement becomes an avoidable argument.

What a proof of delivery document is and what it proves

A POD is the delivery-side confirmation that the goods reached the stated delivery point and were handed over. In practical UK haulage terms, it usually links back to the collection reference, booking reference, consignment number, delivery note, purchase order or job number that identifies the movement.

A proper proof of delivery document normally proves five basic things:

1. The delivery location.
2. The date and time of delivery.
3. The goods or units presented for delivery.
4. The person or function receiving them.
5. Whether the delivery was accepted cleanly or with exceptions.

That last point is where many disputes are won or lost. A clean signature tends to support the position that the goods were delivered in apparent good order, at least so far as could reasonably be seen at handover. An exception note, such as "1 pallet wet", "outer wrap torn", "short by 2 cartons" or "received unchecked", records that the receiver did not accept the delivery without qualification.

Just as important are the limits. A POD does not usually prove that every item inside sealed packaging was correct, nor that the goods were free from hidden damage discovered later in production or unpacking. It does not replace a full stock check, quality inspection or installation sign-off. If the load was tipped at a warehouse gatehouse or left in a designated safe area under instruction, the POD may prove handover in line with those instructions, but not necessarily that the goods were later put away correctly by the receiver.

This distinction matters in claims. If a consignee signs "unchecked", that is not the same as signing cleanly after a full count. If a trailer arrives sealed and the seal is intact, the POD may support the position that the load was handed over as despatched, but it still may not settle a later internal shortage argument without supporting records. In container haulage, the delivery event can be even more specific. The record may show that a loaded box was grounded, live-unloaded or exchanged at the nominated site, but not that the cargo inside was counted item by item at that moment.

What should be on a POD

A POD only helps later if the details are usable. Too many delivery records have a signature and little else. That is enough until someone asks which pallet was short, what time the vehicle was tipped, or whether the site accepted damaged packaging under protest.

At minimum, we expect a usable POD to include:

• Delivery date
• Delivery time
• Full delivery address or recognisable site name
• Consignment number or job reference
• Vehicle registration, trailer number if relevant
• Customer reference, purchase order, booking or delivery note number
• Description of goods
• Quantity delivered, by pallets, cartons, units, lengths, reels or whatever measure the job uses
• Receiver name, printed if possible
• Receiver signature, or accepted digital equivalent
• Any exception notes
• Driver name or identifier

Depending on the work, more detail may be essential rather than optional. For example:

• For pallet network or palletised direct work, pallet count and pallet condition matter.
• For part-load, where several consignments are on one vehicle, the delivery note reference and exact quantity for that stop are critical.
• For full-load, seal numbers, bay number, waiting time notes and unloading completion time may matter more.
• For container haulage, container number, seal number, booking reference, VBS slot details if relevant, and whether the box was live-unloaded, tipped, or left mounted can all become important later.

Exception wording needs to be specific. "Damaged" is weak. "Top corner crushed on pallet 3", "2 cartons missing from 20", or "packaging wet on offside rear" is much stronger. If the receiver refuses to count, "signed unchecked" should be written clearly. If the site will not allow inspection before signature, note that too. If delivery is refused, the driver should record who refused it, the stated reason, the time, and what happened next.

Photos often help, but they should support the POD rather than replace it. A photo of goods on a bay floor with no visible location, timestamp or reference may not answer much. A photo sequence showing trailer doors opened, packaging condition, goods on site, and any visible damage is far more useful.

For work influenced by customs and port processes since Brexit, references matter even more. A delivery record may need to tie back to customs release status, container release, or site-specific booking instructions, especially on traffic moving through Felixstowe, London Gateway, Southampton, Tilbury, Liverpool, Teesport or Immingham. The POD is still about delivery, but if its references do not match the movement paperwork, admin teams can lose time proving that the delivered load is the one invoiced.

Who signs it and when it should be completed

The POD should be completed at the point of handover, not an hour later in the cab and not the next morning from memory. If there is a signature, it should be obtained when the goods are transferred to the receiver’s control, whether that is at the warehouse bay, goods-in desk, site office or other agreed handover point.

Who can sign depends on the site process. In most UK haulage work, the acceptable signer is the person authorised by the delivery site to receive goods. That may be:

• A goods-in operative
• A warehouse supervisor
• A stores person
• A site manager
• A gatehouse operative, if that is the site’s formal intake process
• A named contact on the booking, if they are the person taking receipt

The named contact does not have to be the one who signs, provided the signer is clearly acting for the delivery site. Problems start when the signature is unreadable and there is no printed name, no role, and no delivery timestamp.

If the named contact is unavailable, the driver should not simply leave with a scribble from whoever is nearest. The right process is to ask who is authorised to receive the goods, note that person’s name and role, and, if necessary, call the traffic office while on site. If the site insists on its own intake stamp, barcode scan or handheld receipt process instead of signing the driver’s paperwork, the driver should still capture what the site provides and note the handover details.

For unattended deliveries, out-of-hours drops or leave-in-safe-place instructions, the instruction itself needs to be documented before delivery where possible. Then the driver should record:

• Who gave the authority
• When it was given
• Exactly where the goods were left
• Photos showing placement and condition
• Any site access limits or inability to obtain a signature

That is not as strong as a normal signed POD, but it is far better than "left on site" with no evidence.

If the receiver refuses to sign, the driver should not argue on the bay. Record the refusal, the reason given, the time, and notify the office immediately. In many cases, a quick call between traffic and the delivery site resolves it while the vehicle is still there.

Why POD problems turn into payment and claims problems

A missing or weak POD creates two immediate risks. First, the customer may delay payment because the delivery cannot be evidenced cleanly. Second, any later complaint becomes harder to challenge.

On the invoicing side, many finance teams will not release payment without a valid proof of delivery document, especially for one-off jobs, urgent cover, subcontracted legs, or customers with strict purchase-to-pay controls. If the job was booked against a PO, the POD often needs to match that PO reference. If the delivery date on the POD does not match the invoiced date, or the quantity signed for is unclear, the invoice can go into query status.

That affects everyone in the chain. The shipper may not be able to bill its own customer. The main contractor may hold the subcontractor invoice. A haulier may end up chasing payment for work that was physically completed days or weeks earlier.

Claims are where poor POD really bites. Common examples include:

• Alleged shortages
• Visible damage
• Wet loads
• Wrong delivery point
• Late delivery disputes
• Refused goods
• Temperature or handling allegations on relevant work

If the POD is clean and detailed, the discussion starts from a solid record. If it is missing, unsigned, illegible or inconsistent with the job sheet, the dispute becomes harder and more expensive to handle.

This is especially true on awkward jobs. A last-minute part-load inserted into a busy route, a redelivery after a failed first attempt, a site with restricted booking windows, or a multi-drop run through controlled urban areas can all create pressure on drivers and traffic teams. That is exactly when process slips happen. We see the same pattern repeatedly, the transport leg is done, but admin proof is weak, so the work still has to be defended afterwards.

If London access restrictions or booking windows affect arrival timing, the delivery record should show the actual arrival and unload times. That can be important where a customer later says the vehicle missed slot or caused a failed delivery. For related planning issues, we have covered how delivery planning is affected by London controls.

There is also a VAT angle in some businesses, not because a POD is a VAT invoice, but because supporting transport records form part of the wider audit trail behind supply, billing and cross-checking of transactions. The cleaner the chain of records, the less time accounts teams spend reconciling what happened.

Paper, photo and digital POD in day-to-day UK haulage

In live operations, paper, photo and digital POD all still exist side by side.

Paper POD remains common because it is simple, familiar and accepted almost everywhere. A stamped delivery note with a clear signature can still be perfectly workable. The weakness is retrieval. Paper gets lost in cabs, mixed across jobs, or returned days later in poor condition.

Photo-supported POD is now standard good practice on many movements, even where the main record is still paper. Drivers photograph signed paperwork, goods on delivery, damage, seals, and site conditions. This helps if the original note goes missing or if someone later disputes the condition of the load at handover. But photos need discipline. Without the right sequence and references, they create volume rather than clarity.

Digital POD is often the strongest format operationally, especially where it captures timestamp, geolocation, signature, exception notes and images in one place. It also makes chasing easier. Traffic, customer service and accounts can access the record without waiting for paperwork to come back. For busy transport desks handling mixed full-load, part-load and container haulage, that speed matters.

Still, digital is only better if the process is better. A blank signature box completed on a handheld device without a name, quantity or exception note is no more useful than a poor paper slip. The content matters more than the format.

In practice, the best UK haulage operations use a layered approach:

• The job record holds the booking and references.
• The driver captures a signed or otherwise evidenced delivery event.
• Photos support any exceptions or unusual circumstances.
• The office can retrieve the record quickly by job number, customer reference, vehicle or date.

That accessibility is what stops routine queries becoming a half-day search. We have looked at the admin benefit in more detail in our guide to reducing chasing and disputes with better delivery proof, and also in who should be chasing a POD after delivery.

How to tighten the process across awkward and last-minute work

The fastest way to improve POD quality is not to tell drivers to "get a signature" more often. It is to build the requirement into the job setup, handover and exception process.

For shippers and booking teams, the starting point is clean instruction. Every job should state:

• Delivery address and postcode
• Delivery contact and phone number
• Booking reference or PO
• Required delivery note reference
• Quantity and packaging type
• Any site-specific POD requirement
• Whether photos are required
• What to do if the site signs unchecked or refuses to sign

For traffic teams, the key is making the handover point explicit before the vehicle arrives. If the load is going to a site where the gatehouse signs but goods-in checks later, say so. If the customer insists on a barcode receipt instead of signing paperwork, brief that in advance. If the site has awkward booking windows, limited waiting time, or a history of refusing exception notes, tell the driver before departure.

For hauliers and subcontractors, a short POD standard helps a lot. We work best when everyone knows the non-negotiables:

• No departure from delivery point without delivery evidence, unless the office agrees the exception
• Printed name or role with signature where possible
• Time of delivery recorded
• Specific exception notes, not vague ones
• Immediate escalation of refusal, shortage allegation or visible damage
• Photos for exceptions, unattended deliveries and unusual site instructions

On urgent and changing work, references often break down first. A job booked in a rush may start with one reference and finish with another. That is where organised request handling matters. At Haulier.AI, our AI-assisted, human-backed desk is designed to keep the request, quote and movement trail structured so the operator and customer are not reconstructing the basics afterwards. That is particularly useful where loads change late, extra drops are added, or delivery instructions move while the vehicle is already running.

Multi-drop work needs extra discipline because one weak stop can contaminate the whole day’s paperwork. Drivers should separate each stop clearly, whether on paper or digitally, and traffic teams should not accept one blanket signature for multiple deliveries unless the site process genuinely supports it and the quantities are itemised.

For container haulage, the same rule applies in a different form. A movement through our container haulage support might involve port collection, timed slotting, customs release dependencies and site delivery constraints. The delivery proof still needs to show the handover properly, even when the operational pressure is around slots, quay timings and turnround rather than carton counts.

The aim is simple. When the query comes in, we should be able to answer it with one coherent record, not a chain of guesses, screenshots and phone calls. A good proof of delivery document does not prevent every dispute, but it gives us and our operators something solid to work from when the easy assumptions stop and the real questions begin.

Is a POD the same as an invoice?

No. A POD records delivery. An invoice requests payment. The POD may support the invoice, but it is not the same document and does not replace commercial terms.

Does a signature on a POD prove the goods were undamaged?

Not always. A signature usually confirms receipt at the delivery point. If damage is hidden or not checked at the time, the dispute may still continue.

Can a POD be digital?

Yes. Many operators use digital signatures, timestamped photos or app-based records. The key point is that the record is clear, retrievable and linked to the correct movement.

What if nobody will sign for the delivery?

The driver should follow the delivery instruction and report the issue straight away. Notes, photos, time records and contact attempts may all matter if the delivery is later queried.

How long should a POD be kept?

Retention depends on contract, customer requirements and internal policy. In practice, operators should keep POD records long enough to deal with invoice queries, claims and audit needs.