POD disputes: how haulage offices can protect delivery evidence
A practical guide to reducing POD disputes by capturing delivery status, signatures, photos, exception notes and customer communication in one job record.
POD disputes are rarely solved by the phrase "the driver says it was delivered". The office needs evidence: delivery status, time, location, recipient details where appropriate, photos or notes where useful, and a clear link to the job.
Electronic proof of delivery can help, but only if the workflow captures the right information and keeps it findable. This article focuses on practical evidence handling for haulage offices. It is not legal advice.
What a POD dispute usually needs
Customer disputes often ask one of four questions:
- Was the delivery made?
- Was it made to the right place?
- Was it complete?
- Was there damage, delay or exception?
The POD record should help answer those questions without sending the office through messages, paper files and driver memory.
Capture the basics every time
A good POD record should normally include:
- job reference
- customer and delivery point
- delivery date and time
- driver, vehicle or run reference
- delivery status
- recipient name or signature where used
- exception notes
- photos where safe, relevant and proportionate
- failed-delivery reason where applicable
The record should be attached to the job, not only saved as a loose file.
Handle photos carefully
Photos can be useful for pallet count, damage, location, seal, access issue or failed delivery evidence. They can also capture people, number plates, addresses or customer property. Follow data minimisation principles: capture what is needed, avoid unnecessary personal data and store it securely.
Drivers should know when a photo is useful and when it is not. A photo taken unsafely or without context can create more problems than it solves.
Record exceptions at the time
If there is a shortage, damage, refusal, waiting time, wrong address, unsafe unloading issue or customer instruction change, record it immediately. The note should say what happened, who was told and what decision was made.
Exception notes are especially important when they affect invoicing or credit control. A clean exception record helps the office explain why a job was delayed, partially completed or charged differently.
Link POD to invoicing
Many disputes surface when the invoice is raised. If the POD is missing, incomplete or hard to find, the office loses time and may delay billing.
A simple workflow is:
- Job completed by driver.
- POD and exception notes submitted.
- Office reviews missing or disputed evidence.
- Job is marked ready for invoicing.
- Invoice references the correct job and customer details.
This does not require a complex process. It requires the POD to be visible before the invoice is sent.
Create an exception review before billing
For higher-value or repeat-customer work, add a short review step before billing. The office should check whether the job was delivered as planned, whether any exception note exists, whether waiting time or failed delivery charges apply, and whether the POD evidence matches the invoice.
This reduces awkward follow-up after the invoice lands. It also gives the office a chance to resolve unclear notes while the driver still remembers the delivery.
Keep retention practical
There is no single POD retention period that fits every business and contract. Operators should keep records for as long as they are needed for operational, contractual, accounting or legal reasons, and remove or archive data when it is no longer needed. Where personal data is involved, follow data protection principles.
Train drivers on useful notes
A driver note should be short but specific. "Customer unhappy" is weak. "Customer refused two pallets due to visible corner damage; office called at 14:20; photos attached" gives the office something to work with.
Drivers should also know when not to write opinions. Keep the note factual: what happened, what was seen, who was told and what instruction was given. That makes the record more useful if a dispute reaches management or an insurer.
Make missing POD visible
The office should not discover missing POD only when a customer chases an invoice. Use a daily or weekly list of completed jobs with missing evidence. Sort it by customer, age and value so the office can chase the most urgent items first.
If a driver repeatedly submits incomplete POD, treat it as a training or process issue. If a customer repeatedly refuses to sign or changes requirements, update the site instructions before the next visit.
Frequently asked questions
Is a signature always required for proof of delivery?
Not always. It depends on the contract, customer process and type of work. Some jobs use signatures, some use photos, status updates or customer systems. The key is knowing what evidence is expected before dispatch.
Should a driver photograph every delivery?
Not unless the business has a clear reason. Photos should be relevant, safe and proportionate.
How can the office reduce POD disputes?
Use clear site instructions, capture the right evidence at delivery, record exceptions immediately and review missing POD before invoicing.
Final takeaway
POD disputes are easier to handle when evidence is captured once and stored with the job. Keep the record complete, proportionate and easy for the office to find before the customer asks.
Related pages
Sources & further reading
Manage checks, defects and records digitally
HauliK gives UK transport operators digital walkaround checks, defect tracking, job management and driver compliance — built around DVSA-aligned workflows.