Who should chase a POD after delivery in UK haulage?

If a POD is missing after delivery in UK haulage, the party that booked the movement should normally lead the chase. In direct customer work, that is usually the customer’s own traffic or transport team chasing the delivering haulier. In subcontracted work, the main contractor or transport desk should chase its subcontractor first, not send everyone straight to the delivering driver or delivery site.

That matters because a POD chase is really a chain of responsibility problem, not just a paperwork problem. If too many people start asking different parties for the same document, you get crossed messages, duplicate calls, and delays to invoicing. The quickest route is usually the contractual route, with one point of contact owning the follow-up and escalating only when the normal path has failed.

Who is normally responsible for getting the POD first - who should collect the POD at delivery and how that differs between direct customer work and subcontracted UK haulage

The first responsibility sits with the delivering driver. At the delivery point, the driver should obtain the POD before leaving site wherever the job type and site process allow it. In practical terms that usually means a signed delivery note, a stamped CMR where one is in use, a site-generated goods received note, a warehouse receipt, or an electronic signature captured on the delivery device.

In ordinary domestic UK haulage, the POD is often a signed delivery note or an electronic proof captured by the haulier’s app or telematics-linked workflow. For pallet, part-load and full-load work, the exact document varies by customer and site. Some RDCs issue their own receipt reference instead of signing the haulier’s paperwork. Some manufacturing sites sign the delivery note but add shortages, damage remarks or booking references. For container haulage, the evidence may also include terminal event timings, container number, seal check, and the consignee’s receipt or warehouse booking reference.

The next responsibility depends on who is contracting with whom.

In direct customer work, where the shipper or consignee books the delivering haulier directly, the customer’s operations team is usually the first office function responsible for making sure the POD comes back. The haulier collects it on site, then returns it to the customer under the agreed process, whether by portal upload, email, app workflow or weekly paperwork batch.

In subcontracted UK haulage, responsibility is different. If we place a load with a subcontract haulier through our AI-assisted, human-backed transport desk, the subcontract haulier still needs to collect the POD at delivery. But the first office party responsible for recovering it is us, because we are the contracting party to that haulier. Our customer should not have to work out which driver delivered, which depot planned the vehicle, or which subcontractor’s admin team holds the paperwork. We should do that.

That distinction is where many arguments start. A customer sees a missing POD and asks, reasonably, who can chase the POD after delivery in haulage. The practical answer is the party who placed the job with the next party down the chain. That keeps accountability aligned with the contract and avoids side conversations that undermine control.

There are exceptions. If a site refuses to sign, uses barrier camera evidence only, or issues PODs through a separate goods-in system days later, the delivering haulier may not physically leave with a signed paper document. In those cases, the responsibility is still the same, but the form of POD is different and the expected timing should be agreed in advance.

When chasing a POD becomes necessary after delivery - what situations lead to missing or delayed PODs and when operations teams should start following up

Not every missing POD is a problem at the moment of delivery. Some jobs are delivered at 08:00 and the paperwork is not scanned until the driver returns to depot that evening. Some container haulage jobs end with a box grounded at a warehouse and the receiving paperwork is issued later by the customer’s warehouse admin. The key is knowing what “late” means for that job.

Common reasons for delayed or missing PODs include:

• the driver forgot to get the document signed
• the site would not sign the haulier’s paperwork
• the site uses a receipt number system and the reference was not recorded
• the POD was signed but not scanned clearly
• the paperwork stayed in the cab or at the depot traffic desk
• the job was covered by another subcontractor and the paperwork path is unclear
• the delivery was out of hours and no goods-in clerk was available
• the load was refused, short delivered, damaged, or rebooked
• the consignee says the goods arrived but disputes quantity or condition
• for container haulage, the delivery evidence sits across terminal events, warehouse booking logs and driver notes rather than one simple signed note

For ports and container work, timing can be especially awkward. A movement linked to container haulage through major UK ports may involve collection near Felixstowe, London Gateway, Southampton, Tilbury, Liverpool, Teesport or Immingham, then delivery to a warehouse that has its own booking and receipt process. If there is a quay delay, VBS issue, customs hold, or post-Brexit document query, the final delivery paperwork can be slower to settle than a standard domestic pallet run.

When should the chase start? Operationally, we treat that by job type.

For same-day or next-day general haulage, if the POD is not visible by the end of the driver’s shift or by the following working morning, the transport desk should start checking. For urgent jobs, timed deliveries, event freight, or loads tied to immediate invoicing, we start sooner, often as soon as the driver has tipped and left site but the POD has not landed through the normal channel.

For container haulage, especially port-related work through deliveries linked to Felixstowe container movements or similar gateways, we allow for the fact that delivery evidence may not be a single signed note in the first hour after tipping. Even so, if by the next working day we do not have either the POD itself or a clear delivery confirmation with time, location and receiving contact, follow-up should already be underway.

The main mistake is waiting until invoicing day. By then, the driver may be on leave, the paper may be buried in the cab, and the receiving clerk may no longer remember the delivery. POD chasing works best while the movement is still fresh.

Who should chase whom in a subcontract chain - how POD chasing works between shipper, transport desk, main contractor and delivering haulier without creating confusion

In a clean subcontract chain, each party chases the party it instructed.

If the shipper gave the job to us, we chase the delivering haulier or the subcontract chain beneath us. If we gave it to a subcontractor, that subcontractor chases its own driver, depot, or any further subcontractor it used with permission. The shipper should deal with us. The delivering driver should not be fielding separate POD requests from the end customer, the main contractor and a warehouse supervisor all at once.

That is the best answer to the question people often ask in search form, about whether someone can chase the POD after delivery in haulage. Yes, but not everyone should. One owner in the chain should coordinate it.

A practical subcontract chain often looks like this:

• shipper or importer
• our transport desk
• main contracted haulier
• delivering haulier or owner-driver
• consignee or delivery site

The POD chase should normally run upward and downward through those links only.

So if our customer asks for the POD, we confirm delivery status from our records first. If the POD is not already in our system, we contact the contracted haulier. That haulier checks with its traffic office, then with the delivering driver if needed. If the driver says the site signed but the document is not scanned, the haulier arranges a copy. If the site refused to sign and gave a receipt reference only, that detail comes back up the chain with supporting notes.

What should be avoided?

• the customer calling the delivery site directly before the haulier has checked its own records
• multiple parties emailing the same warehouse asking for “proof”
• bypassing the main contractor and asking the subcontractor for documents on a job where commercial control matters
• accusing non-delivery before checking whether the site uses delayed receipt processing
• treating a disputed POD as if it were just an admin delay

Commercially, this is important for Haulier.AI because our model is built around organised handling, human oversight and preserving hauliers’ control, not pushing work into an unmanaged auction process. If a haulier covers a job for us, we keep the communication chain tidy. That protects the customer experience and the haulier relationship at the same time.

There is also a document control point here. If the POD contains signatures, names, timestamps, references and sometimes personal data, it should be stored and shared only with the parties entitled to receive it. The UK position is not identical to broad EU assumptions after Brexit, because businesses still need to think in terms of UK data handling requirements and their own retention practices, even where customer groups use wider European processes.

What a workable POD chasing process looks like - the practical steps, timings and records needed to recover PODs quickly and keep invoicing moving

A workable process is simple, timed, and recorded. It does not depend on memory.

Our preferred sequence is:

1. Confirm the job details
2. Confirm whether delivery actually took place
3. Check whether the POD is already held somewhere in the chain
4. Chase the contracted party, not everyone at once
5. Escalate by age and invoice risk
6. Record every contact and outcome

Step one is basic but often skipped. Before chasing, check the movement reference, date, vehicle, trailer or container number, delivery postcode, booking slot and consignee name. Many failed POD chases start with the wrong load reference.

Step two is delivery confirmation. If telematics, driver call, site booking system, terminal event or warehouse unload note already confirms delivery, record that immediately. A missing POD is then an admin recovery issue, not a live service failure.

Step three is checking the obvious places. Has the document already been emailed by the driver? Uploaded to the portal? Sent to a generic inbox? Attached to the job in the TMS? Sitting with night trunk paperwork? In container haulage, has the warehouse sent a goods received confirmation under a separate thread?

Step four is the actual chase. We recommend a timed ladder:

• On day 0, after delivery, request POD return under the normal process
• On day 1, if still missing, contact the contracted haulier’s traffic desk
• On day 2, escalate to the haulier’s admin or depot manager if no response
• On day 3, if invoice-critical or dispute-linked, request driver statement, site contact confirmation, and any substitute evidence
• After that, escalate commercially according to the subcontract terms

Substitute evidence can matter. A clean POD is best, but where that is genuinely unavailable, useful supporting records may include:

• driver arrival and departure times
• site booking confirmation
• unloading bay reference
• warehouse receipt number
• signed gate pass
• geofencing record
• terminal out-turn or handover event for container work
• email from consignee confirming receipt
• photo of signed paperwork if the original scan is delayed

For port-related work, links between terminal, haulier and warehouse records are especially important. Jobs routed through London Gateway container delivery planning or other major ports often generate several operational timestamps that can support the delivery story even before the final POD copy is retrieved.

Keep a POD chase log. At minimum, record:

• job reference
• customer reference
• delivery date and time
• who delivered
• what POD was expected
• when each chase was made
• who was contacted
• what they said
• whether substitute evidence was received
• whether invoicing is on hold

That last point matters. Missing PODs slow cash flow on both sides. Customers often hold payment until POD is supplied. Hauliers often cannot invoice their contractor without it. If nobody owns the chase, everyone gets paid later.

For VAT purposes, the POD is not the only document behind an invoice, but it is often the practical document customers use to approve payment. So while a tax invoice may technically stand on its own if it contains the required information, commercial reality in UK haulage is that missing POD frequently means delayed approval.

How to reduce POD problems before the vehicle arrives - what booking, site instruction and communication checks help prevent POD disputes on part-load, full-load and container haulage jobs

The best POD chase is the one you never have to do. Most missing POD problems start before the truck arrives.

First, make the booking instruction precise. Every job should state:

• exact delivery address
• booking reference
• delivery contact
• opening hours
• whether signature, stamp, name print, or receipt number is required
• whether the site accepts electronic POD
• any rules for paper documents, seal checks or pallet exchange
• whether shortages or damage must be noted in a specific format

That matters even more on part-load work, where one driver may have several drops and several document sets in the cab. A vague instruction like “get signed POD” is not enough if the consignee only issues its own goods-in number.

For full-load work, especially factory or RDC deliveries, make sure the delivery booking and the commercial paperwork match. If the PO number, load reference or trailer ID on the booking does not match what the site expects, the driver may unload but leave without a useful POD.

For container haulage, check the whole chain before dispatch:

• correct container number
• seal number where relevant
• collection and delivery booking references
• terminal and warehouse slot details
• customs or release status
• whether the receiving warehouse signs haulier paperwork or only issues internal receipt references

That is particularly relevant on jobs through Southampton, Tilbury, Liverpool, Teesport and Immingham, where site-specific processes can differ sharply between depots, terminals and final receivers. A warehouse receiving imports after Brexit may have stricter release or reference checks than a standard domestic unload, and if those references are wrong the POD trail can become messy even when the physical delivery happens.

Second, brief the driver properly. The driver should know not just where to go, but what evidence to bring back. “Need signed note or site receipt number before leaving” is a useful instruction. “If refused signature, ring traffic from site” is even better.

Third, set the communication trigger points. We use simple rules:

• if running late, update ETA
• if site refuses unload, call immediately
• if site unloads but refuses to sign, call before departure
• if paperwork is left on site by mistake, report it the same day
• if an ePOD app fails, send photo backup

Fourth, separate service failure from document failure. A late vehicle, refused load or damage issue needs operational management, not just a POD chase. Treating every missing POD as a scanning delay is how real claims get missed.

Finally, keep the commercial chain clear. In subcontracted UK haulage, customers should know who owns the movement and where to ask for documents. Hauliers should know whether they are expected to upload paperwork directly or through the contractor. That clarity is one of the practical benefits of an AI-assisted, human-backed desk like ours. We organise the request, the placement, the follow-up and the records, without taking commercial control away from the haulier doing the work.

If you want fewer POD disputes, the answer is not more chasing after the event. It is better instructions, tighter handoffs, and one owner for the document chain from booking to invoice.

Can the customer chase the POD directly with the delivering haulier?

Yes, if that is the direct commercial relationship. In subcontracted work, it is usually better to follow the agreed chain first so responsibility stays clear and duplicate chasing is avoided.

How long should you wait before chasing a missing POD?

It depends on the job and agreement, but most teams should check the same day or next working day. Waiting too long can delay invoicing and make site-level recovery harder.

Is a signed POD always required for payment?

Not always, but it is often the main delivery record. Some jobs accept alternative evidence, though many customers and contractors still want a POD before approving invoices.

What if the delivery point refuses to sign a POD?

The driver should record names, time, reason and any unloading evidence straight away. That information should be passed back quickly so the operator can agree what proof will be accepted.

Does electronic POD remove the need for chasing?

No. Electronic POD usually helps, but it still depends on site process, driver compliance, signal, app use and whether the delivery record reaches the right party in the chain.