POD vs POC: why drivers should capture both (and where most teams skip one)

A customer rings on a Tuesday morning. Two of the eight pallets you delivered to their RDC on Monday have a corner crushed in. They've got photos. They want a credit note for £4,200 worth of damaged stock and they want the haulage fee refunded on top.

You open the job in your TMS. The POD is beautiful: timestamped photo of the load on the customer's bay, clear signature from the goods-in supervisor, GPS pin within five metres of the gate. Whoever drove it did their job.

Then you go looking for the POC and there's nothing. The driver collected from your own consolidation warehouse at 4am, signed it out on a paper run sheet, and rolled. No photo of the pallets on the trailer. No condition note. No second signature.

So now you have a POD photo showing damage and zero evidence the pallets weren't damaged when they left your yard. Your claim against your own warehouse insurance is weak. Your defence against the customer is weaker. You pay.

This is the post about why that happens, and how to stop it.

The definition refresher

Two pieces of paperwork, often confused, doing very different jobs.

Proof of collection (POC) is evidence that the consignment was handed to the carrier at the origin in a specific state, at a specific time. It records what was loaded, how many of it there were, what condition it was in, and who handed it over. It marks the moment chain of custody passes from the shipper (or your own warehouse) to the driver.

Proof of delivery (POD) is the mirror image. It's evidence that the consignment was handed to the consignee at the destination — same data points (what, how many, what condition, who received it), captured at the other end of the journey. It marks the moment chain of custody passes from the driver to the consignee.

Both exist for the same reason: when something goes wrong, somebody has to pay, and the side with the better paperwork wins. A POD without a POC is half a story. It tells you what arrived but not what left. If the two don't match — short count, damage, wrong product — the gap in the middle is where the disputes live, and without a POC the gap is yours to swallow.

Almost every TMS in the world treats POD as a first-class object and POC as a checkbox. That's the bug.

Why most teams skip POC

Three reasons, all of them understandable, none of them good enough.

The origin is "our warehouse," so it feels redundant. If the goods are coming out of your own consolidation centre, the instinct is "we know what we sent — we picked it." Except the people who picked it aren't the people who loaded it, and the people who loaded it aren't the driver. Three handovers, no paperwork.

There's no customer at the origin to sign anything. POD has a built-in counterparty: the consignee. They want to sign because they want a record that they received it. POC at your own warehouse has no counterparty in that sense. The yard manager isn't motivated to sign because they're not the one being held responsible later. So nobody asks them to.

Drivers see it as extra paperwork before they've even started driving. They've done a four-hour run from home, they're cold, they want to get on the road. Asking them to walk the trailer with their phone and tap through a six-screen form feels like punishment for showing up.

All three are real. None of them survive contact with the first damage dispute you lose.

The six scenarios where missing POC costs you

This is the spine of the post. Six specific situations where the POC is the difference between paying and not paying. If your operation does more than ten loads a week, you'll recognise at least four of them.

1. Damage at delivery

The one from the opening. Customer reports damage on arrival, you've got POD evidence of damage and no POC evidence of condition at collection. The dispute logic is brutal: if you can't prove it left undamaged, the carrier-side assumption is it didn't. Insurers default the same way. A 30-second photo at the yard gate before the trailer rolls would have closed this. Without it, you eat the claim or you spend three weeks arguing about it and eat half.

2. Short shipment

Driver was supposed to collect 12 pallets and collected 11. Maybe one was held back by warehouse for a quality check and nobody told dispatch. Maybe the driver miscounted in the dark. Maybe one fell off the forks and got put back in the racking. Without a POC pallet count, you don't find out until the consignee signs for 11 and your TMS lights up with a discrepancy at 3pm. Now you're calling the warehouse, calling the driver, trying to reconstruct what happened eight hours ago. A POC count at the gate would have caught it before the truck left.

3. Wrong load

Less common but spectacular when it happens. Driver hooks the wrong trailer or loads the wrong stack of pallets — same customer, different consignment, or worse, different customer entirely. A POC photo that the driver actually looks at while taking it ("are these the right pallets for job number X?") catches it 90% of the time. Without it, the wrong load arrives at the wrong RDC, gets rejected, and the cost of the recovery run plus the missed delivery window comes out of your margin.

4. Mis-labelled pallets

The pallets are physically right but the labels are wrong — somebody printed the wrong customer reference, or the consignee SSCC barcode is from yesterday's run, or a single pallet in the stack belongs to a different customer entirely. A POC photo of the labels (not just the pallets) is the moment to catch it. It also catches the inverse: right labels on the wrong pallets, which is the kind of error that, when it reaches a retail RDC, gets your account suspended.

5. Driver swap mid-route

Long-distance work, especially anything over six hours, often involves a swap. Driver A collects from origin and drops to a relay point. Driver B picks up from the relay point and delivers. Without a POC at origin and a second POC-style handover at the relay, you have no chain of custody. If damage shows up at delivery, you can't tell whether it happened on Driver A's leg, in the relay yard, or on Driver B's leg. Neither driver wants to take the hit and your operations manager has to play detective. POC plus a relay handover photo means you can point at the moment the damage appeared.

6. Customs and cross-border

This one isn't optional. For any cross-border move — Northern Ireland, Republic of Ireland, the rest of Europe — the POC is part of the customs paperwork. Tax authorities want evidence that goods were loaded at a specific origin, in a specific quantity, at a specific time, before they can clear them through. If you're running international and your POC is "the driver said it was all on there," you're going to fail an audit. The fine isn't the worst part — the worst part is the load sitting at a border post for two days.

What good POC actually looks like

If you're going to fix this, fix it with the right components. Skipping POC is bad. Capturing a POC that's just "driver tapped a button" is almost as bad — it gives you false confidence without any evidentiary weight.

The components that matter:

• A GPS-stamped photo of the loaded trailer or the pallets on the floor. The GPS is what makes it defensible later. A photo on a phone with no location proves the photo exists; a photo with lat/long and a timestamp proves the photo was taken at the origin yard, on the day of collection, at the time of collection. That's the version that survives a dispute.
• A pallet count entered against the booking. Not derived from the driver's memory, not assumed from the manifest — actually entered as a number on the device, with the manifest expected count visible alongside it. If the two don't match, the app asks "are you sure?" before letting the driver close out.
• A signature from the warehouse handover person. Not the driver's own signature — that's worth nothing in a dispute, because the driver is the one being held responsible. A signature from the yard supervisor, gateman, or pick-team lead. Someone whose name the operations team can find on Monday morning.
• Optional: a temperature reading. If you're moving cold chain, the trailer reefer temperature at the moment of departure is a POC component. It's the baseline you need if the consignee rejects the load for being out of spec at delivery. Without an origin reading, you can't tell whether the breach happened on your watch or theirs.

Four items, none of them difficult, all of them missing from most operators' workflows.

How to enforce POC without making drivers hate you

This is where most rollouts die. You add four new mandatory steps to the start of every job, drivers hate it, compliance drops to 40% within a fortnight, and the project gets quietly buried.

Three rules for getting POC adopted without a mutiny:

Make it a tap-and-photo flow, not a form. The job arrives on the driver's phone. They open it. The screen says "Take a photo of the loaded trailer" with a big camera button. They tap, take the photo, hit confirm. Same for the pallet count: a single number field with the expected count pre-filled, so the driver either confirms or amends. Same for the signature: hand the phone to the yard supervisor, they sign, hand it back. The whole flow should take under 90 seconds. If it takes longer, drivers will route around it.

Block "start driving to delivery" only when origin requires it. Not every collection needs the same paperwork. A pickup from your own warehouse with your own staff probably doesn't need a third-party signature. A pickup from a customer's RDC absolutely does. Customs work absolutely does. The job configuration should know which is which and only enforce the components that matter. Drivers learn fast that the system isn't being arbitrary — when it asks for a signature, there's a reason.

Don't require third-party signatures for own-warehouse collections. Your own yard supervisor signing your own POC adds friction without adding evidentiary value. They're not a third party; they're your employee. A photo and a count from the driver, against a manifest, is enough for own-warehouse work. Reserve the signature requirement for shipper-origin collections (where the shipper genuinely is a separate counterparty whose signature you'd want in a dispute).

Get those three right and you'll see compliance settle around 85–90% within the first month. The drivers who push back hardest are the ones who've never lost a damage dispute themselves — and they tend to come around the first time the POC photo they took saves a claim they'd otherwise have been blamed for.

The damage dispute that POC saved

Last year, a small mixed-pallet operator I work with delivered a load of seasonal stock to a high-street retailer's DC. The retailer raised a damage claim two days later: three pallets, around £6,000 of stock, all with crushed corners on the bottom layer. The retailer wanted a full credit.

The driver had captured a POC photo at collection — wide shot of the loaded trailer from the rear, GPS-tagged, taken six minutes before the trailer left the yard. The photo showed all eight pallets stacked clean, no visible damage on the bottom layer of any of them.

The operator sent the POC photo to the retailer alongside the POD photo (which clearly showed the damage on arrival). The gap between the two was the journey itself and the unload — three hours and a forklift. The retailer's own forklift, in their own DC.

The credit note got rewritten as a forklift-handling internal note on the retailer's side. The operator paid nothing. The whole dispute took 48 hours instead of three weeks.

The POC photo took the driver about 20 seconds to capture. Twenty seconds of work saved six thousand pounds. That's the trade.

Where to start

If you're capturing POD religiously and POC sporadically right now, two things to do this week:

1. Audit your last month of damage disputes. How many would have been winnable with a POC photo at origin? In every operation I've looked at, the answer is more than half.
2. Pick one origin — your busiest consolidation yard, probably — and add a mandatory tap-and-photo POC flow for every collection out of it. Just photo and pallet count to start, no signatures. See how drivers respond. See what your dispute rate does over the next 90 days.

You don't need to roll it across the whole fleet at once. You need one yard, one workflow, one month of data showing the disputes that didn't happen. Then the rest of the business will ask to be next.

POD answers "did it arrive?" POC answers "did it leave in the state we said it did?" Both matter. Most operations only answer one of them and pay for the other in claims.

If you're rebuilding your driver workflow, delivery tracking is where POC and POD live as first-class objects rather than checkboxes — same data model, same audit trail, same chain-of-custody story end to end. Worth a look if you're tired of losing damage disputes you should have won.