Delivered isn't documented: who owns the missing POD?

Key Takeaways

A load marked "delivered" isn't finished until the proof of delivery (POD) is on file. The POD is the signed document showing the consignee received the freight, and it's the evidence for billing, payment and claims.
A missing POD can hold up customer billing, carrier payment and damage or shortage claims, and it gets harder to find the longer a team waits.
Ownership comes down to 3 decisions set once: who requests the POD, how long to wait for it and who gets the escalation when it doesn't arrive.
Wilson, by Cartage, is an AI logistics agent that requests the POD after delivery, follows up until it's received and files it on the shipment. If it's still missing past the set window, Wilson escalates to the team.
Every request, follow-up and filing is recorded in the shipment's change history, so anyone can see where a POD stands.

Why do PODs go missing after delivery?

PODs go missing because delivery feels like the end of the job, and requesting the POD is a separate step that nobody is assigned to. The carrier marks the load delivered, the coordinator moves on to the next pickup, and the POD stays with the driver or the carrier's back office until someone needs it, usually during a dispute.

This affects manufacturers and distributors whose coordinators run dozens of loads by email and phone, where the POD request competes with every pickup and exception still open. It also reflects a wider gap: in a March 2025 survey of 240 supply chain leaders, BCI Global found only 35% reported end-to-end visibility. Without the POD, the last step of a shipment is the least visible.

One delivery, three weeks to prove it

Here's a distributor's LTL load (less-than-truckload, where several shippers share a trailer). Dates and times are for example.

Friday 3:40 p.m.: the load delivers. The carrier's website shows "delivered" by PRO number, the carrier's tracking number for the shipment.
Friday 4:00 p.m.: the coordinator sees the status, closes the load in the spreadsheet and turns to Monday's pickups. Nobody requests the POD.
Day 14: the customer's receiving team reports a short shipment, one pallet missing, and the customer short-pays the invoice.
Day 15, 9:10 a.m.: billing asks logistics for the signed POD to see whether the receiver noted the shortage at delivery.
Day 15, 10:00 a.m.: the coordinator emails the carrier's customer service. No reply.
Day 19: after two calls, the carrier dispatcher sends a scan. The receiver signed for the full count with no notation.
Day 22: billing finally goes back to the customer with the evidence, three weeks after delivery.

The POD existed the whole time. It just had no owner until a dispute created one.

Who should own the missing POD?

The person or system that runs the shipment should own the POD, with three decisions set once for every load: who requests it, how long to wait and who gets the escalation. Deciding this per load, under pressure, is how PODs get skipped.

Decision	What to set	Example
Who requests the POD	The owner of the shipment, not billing	Whoever booked and tracked the load
How long to wait	A window after delivery, set per carrier or mode	For example, 2 business days for LTL
Who gets the escalation	A named role, not a shared inbox	Logistics lead or account owner

The window depends on the carrier and mode. Some LTL carriers post signed PODs on their websites, while a truckload POD may need to come from the driver or dispatcher directly. A window that’s too long lets the trail go cold; one that’s too short floods the escalation owner with PODs that were about to arrive anyway.

Billing and AP shouldn’t own the request. By the time they need the POD, the window has usually passed, and they don’t have the carrier contacts the shipment owner already uses. For timing guidance, see when should the team chase a missing POD?

What does a missing POD block?

A missing POD can block customer billing, carrier payment and claims, and it leaves the shipment open in every report. The impact grows with each week it's missing.

Customer billing: some customers require the POD with the invoice, or short-pay without it.
Carrier payment: some teams pay only with a POD on file, so the carrier waits too and starts calling AP.
Claims: damage and shortage claims depend on the signed POD and any notes the receiver made at delivery.
Open shipments: loads without a POD stay open, which distorts on-time and carrier performance reports.

Common mistakes

Treating "delivered" as closed. The shipment drops off everyone's list before the POD arrives.
Requesting PODs only when a dispute starts. Weeks later, the carrier takes longer to find it, and the dispute stalls.
Sending POD requests from a shared inbox. Replies land where nobody is watching.
Setting no escalation owner. Missing PODs pile up without anyone deciding what to do.
Not tracking missing PODs by carrier. The carriers that are slow to send PODs never hear about it.

How does Wilson, by Cartage, handle missing PODs?

Wilson requests the POD after delivery, follows up until it’s received, files it on the shipment and escalates if it’s still missing past the set window. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

The POD step is part of the same shipment Wilson booked and tracked. Wilson replaces the TMS as the system of record, so the POD is filed on the shipment rather than in an inbox, and it connects to the company’s ERP.

Step	Trigger	What Wilson does	When a person steps in
1. Confirm delivery	The carrier, tracking source or driver reports delivery	Updates the shipment status	Not required
2. Request	The load is delivered	Requests the POD from the carrier	Not required
3. Follow up	No POD received	Follows up by email, text or phone, at the frequency the SOP sets	Not required
4. File	POD received	Files it on the shipment	Not required
5. Notify	POD filed	Notifies the team, carrier, shipper and consignee as configured	Not required
6. Escalate	Still missing past the set window	Escalates to the team	Deciding next steps

Approval rules and escalation. Wilson starts with assisted execution, and the company decides which actions need a person and who is notified about what. The company also sets the POD window, the follow-up frequency and the channels. When the window passes without a POD, Wilson escalates to the team rather than guessing at next steps.

Change history. Every request, follow-up and filing is recorded in the shipment’s change history, and call transcripts are saved on the order. Anyone in billing or customer service can see whether the POD was requested, when the carrier was last contacted and when it was filed.

What Wilson doesn’t do. Wilson collects and files the POD, but decisions on damage or shortage claims stay with the team. It works only with the company’s approved carriers. For the wider workflow, see POD collection automation.

How do teams make PODs routine?

Teams make PODs routine by treating the POD as the last step of every shipment, not a document to find when someone asks. The rules are simple; the discipline is applying them to every load.

Request every POD, not only the ones billing asks for.
Set a window per carrier or mode and an escalation owner by role.
Close the shipment only when the POD is filed.
Track missing PODs by carrier and raise them in carrier reviews.

What to ask a vendor to show in a demo

Mark one of your recent loads delivered and show the POD request go to the carrier.
Let the carrier stay silent and show each follow-up, its channel and its timing.
Show where the POD is filed and who gets notified.
Let the window pass and show who receives the escalation.
Show the change history from delivery to filing.

To measure results, compare the lanes Wilson runs with how they ran before, including POD collection time and manual touches per load.

FAQs

Who is responsible for getting the POD? Whoever runs the shipment, with the request, the wait window and the escalation owner set once. Wilson, by Cartage, requests the POD after delivery, follows up until it's received and files it.
What happens if a POD is missing? It can hold up customer billing, carrier payment and damage or shortage claims, and the shipment stays open.
How long should we wait before chasing a POD? Set a window per carrier or mode, and escalate when it passes. The right window balances fast follow-up against PODs that were about to arrive.
Does Wilson collect PODs? Yes. Wilson requests the POD after delivery, follows up until it's received and files it on the shipment.
What if the carrier doesn't send the POD? Wilson keeps following up, and if the POD is still missing past the set window, it escalates to the team.
Does Wilson call carriers about PODs? Wilson follows up by email, text and phone, with channels and frequency configured per customer, and saves call transcripts on the order.
Who gets notified when a POD is filed? Each company chooses who's notified and how. The team, carrier, shipper and consignee can all receive the POD-filed update.
How is Wilson priced? There's no subscription fee. The company preloads a wallet, Wilson pays carriers from it once invoices are audited and reconciled, and pricing is a percentage of those payments, covering the full lifecycle.

Conclusion

Delivered and documented aren’t the same thing. Without the POD, billing waits, claims stall and the shipment stays open until a dispute forces someone to chase it. Set the owner, the window and the escalation once, and request every POD as the last step of every load. For how an agent runs the whole shipment, see what is an AI logistics agent?

Wilson, by Cartage, requests, follows up on and files every POD, and escalates the ones that don’t arrive. Bring one load whose POD your team chased last month and watch Wilson run the POD follow-up in a demo at cartage.ai.

Sources

BCI Global, March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
Cartage, Wilson product FAQ, October 2026: https://cartage.ai