Proof of Delivery Workflow: Matching PODs and Handling Exceptions

A proof of delivery workflow captures a signed POD or photo for every drop, matches it to the right load, chases anything missing after an agreed time and only releases the load for invoicing once the evidence is complete. Exceptions, such as damage, shortages, refusals and failed attempts, get their own record at the moment they happen, so claims start from evidence instead of memory.

For carriers, couriers and freight forwarders, PODs are where operations and cash meet. Without a POD, many customers won't pay the invoice. Without good exception records, a damage claim that arrives weeks later becomes an argument about what the driver remembers. And the work of chasing paper receipts and phone photos lands on an office team that has plenty else to do.

This guide sets out a workflow from capture to invoice release, with the exception and claims path alongside. It builds on our broader look at logistics automation and goes deeper into this one process.

The POD workflow at a glance

Stage 1: Capture the POD at the drop

The easiest POD to manage is one captured digitally at the moment of delivery. Options, from simplest to most integrated:

• An upload link. Drivers and partner carriers photograph the signed delivery note and upload it through a simple web link tied to the load. Printing a QR code on the delivery note, made with a QR code generator, takes the driver straight to the right upload page.
• A driver app or ePOD. Captures the signature, name, time, GPS location and photos of the goods in one step, often inside a transport management system.
• Paper, scanned later. Still common with subcontractors. The workflow should accept scans and photos in any format; iPhone photos often arrive as HEIC files, which a HEIC to JPG converter makes readable everywhere.

Whatever the method, capture happens when the vehicle is stopped. Drivers should never be asked to respond to messages or upload documents while driving. In the US, FMCSA rules prohibit hand-held mobile phone use by commercial drivers while driving and bar carriers from requiring it, and the UK has similar rules for all drivers.

Stage 2: Read and match to the load

Each POD is read for the load or job number, customer reference, delivery date, consignee name and whether it's signed. Matching it to the load in your TMS or job list is usually straightforward when the reference is clear, and that's where most PODs end up: filed automatically against the right job.

Stage 3: Validate and flag

Some PODs need a person to look:

1. Unsigned or illegible signatures.
2. Mismatched references or a date that doesn't fit the planned delivery.
3. Annotations such as "2 cartons damaged", "short 1 pallet" or "signed unchecked".
4. Wrong document, such as a collection note uploaded instead of a delivery note.

Annotations matter most. A note on the POD is often the first sign of a claim, so any annotated POD should automatically open an exception record (Stage 5) as well as being flagged.

Stage 4: Chase missing PODs

After an agreed period, for example the end of the delivery day for your own drivers or a set number of days for partner carriers, loads without a POD are listed. The workflow sends a reminder to the driver at the end of their shift or to the carrier's office, then escalates to the traffic office if it's still missing.

This turns the billing team's daily phone round into a short list of genuine problems.

Stage 5: The exception path

Exceptions should be recorded when they happen, not reconstructed when a claim arrives. Common types:

The driver reports the exception through the app with photos and a short description. A record is created against the load with time, location and the POD. Related emails and documents are attached as they arrive. For recurring problems, such as damage at one depot or shortages on one lane, these records become your best source of patterns.

Stage 6: Notify the customer

Customer service is alerted and a draft notification is prepared: what happened, what evidence exists and what happens next. A person reviews and sends it. Wording matters here, because an exception message should report facts without admitting or denying liability.

Stage 7: Release the load for invoicing

When the POD is matched and validated, and any exception is recorded, the load is released to billing with the POD attached. Customers who want PODs with invoices get them automatically; combining several PODs and the invoice into one file with a PDF merge tool, or converting photos with an image to PDF converter, keeps the pack tidy.

Extras such as waiting time, redelivery or tail-lift charges are added for billing to review, not applied silently.

Stage 8: When a claim arrives

When a customer or their insurer raises a claim, the workflow assembles an evidence pack from the exception record: POD, photos, timeline, driver notes, communications and relevant terms. A summary goes to the person handling the claim.

From there it's entirely a human matter. Customer service and management decide liability, settlements and whether to notify insurers. Automation keeps the record together; it never accepts or rejects a claim. That boundary is central to how Make It Flow approaches automation for logistics companies.

Claim and notice deadlines: check the rules for each load

Different regimes set different notice and claim periods, and your own terms and conditions add more. Examples:

• United States (interstate motor carriage): under the Carmack Amendment, a carrier can't set a period shorter than nine months for filing a claim or two years for bringing a lawsuit, measured from when it disallows the claim. Bills of lading and tariffs set the actual terms within those limits.
• International road transport (CMR Convention): under Article 30, reservations about apparent loss or damage are due at delivery, non-apparent damage needs written reservations within seven days excluding Sundays and public holidays, and delay compensation needs a written reservation within 21 days. The UK text is in the Carriage of Goods by Road Act 1965.
• Domestic carriage elsewhere: often governed by contract terms, such as trade association conditions in the UK, or national law in EU countries, Canada and Australia.

Because these periods start from delivery, your exception records and timestamps can decide whether a claim is in time. Check the rules and terms that apply to each customer and route, and take advice on anything disputed.

Driver data in POD photos, GPS records and app logs is personal data under laws such as GDPR, so only use services you've assessed, and keep retention in line with your policy.

FAQ

What is a proof of delivery?

A proof of delivery, or POD, is the record that goods reached the consignee: usually a signed delivery note or an electronic signature, with the date, time, recipient name and often photos and GPS location. It supports invoicing, resolves "where's my delivery" questions and is key evidence if damage or shortage is claimed.

What is the difference between a POD and an ePOD?

A POD is the proof itself; an ePOD is a POD captured electronically, usually through a driver app that records a signature, time, location and photos at the drop. ePODs are faster to match and harder to lose than paper, but subcontractors may still send paper or photos, so the workflow should handle both.

How do you handle a missing proof of delivery?

List loads without a POD after an agreed period, remind the driver or partner carrier automatically, then escalate to the traffic office if it's still missing. Check whether the driver app captured partial evidence such as GPS and time. If no POD can be found, customer service decides how to resolve it with the customer.

What should a driver do if goods are damaged at delivery?

Stop safely, photograph the goods and packaging, note the damage on the delivery note with the consignee, and report it through the app or to the office before leaving. The consignee's signature with a clear annotation, plus photos, gives the best evidence. The driver shouldn't admit or deny liability on the spot.

How long does a customer have to make a freight claim?

It depends on the regime and contract. In US interstate trucking, carriers can't set a claim period shorter than nine months under the Carmack Amendment. Under the CMR Convention, notice periods for reservations are much shorter, measured in days. Your own terms may add further conditions, so check them for each customer.

Can automation decide freight claims?

No. Automation can assemble the evidence pack, summarize the timeline and flag deadlines, but liability, settlement amounts and insurance notifications are decisions for customer service, management and your insurers. Keeping that line clear protects both your customers and your business.