A box of delivery notes and a customer who says it never arrived
Drivers come back at the end of the day with a clipboard of signed delivery notes, some damp, some illegible. They go in a tray. Someone scans or files them when there is time. Weeks later a customer disputes a delivery or a short shipment, and the office spends an hour searching for the note. Sometimes it is found. Sometimes the signature is a scribble with no name and the customer still says it was not them.
Invoices wait for the paperwork too, because finance will not bill until POD is confirmed. So cash flow slows down because paper moves slowly.
Why paper POD keeps failing
- The note travels with the driver all day and returns to the office late.
- Signatures are unreadable and names are not printed.
- There is no photo of where or how the goods were left.
- Time and location are whatever the driver wrote down.
- Filing depends on someone having time to scan and match notes to orders.
- Customers get no copy at the time, so disputes arise later from memory.
What it costs
Disputed deliveries you cannot evidence become credit notes. Finance waits for paperwork before invoicing. Office staff lose hours hunting and filing. And customers who receive no confirmation call to ask whether their goods arrived, which adds to the phone load.
| Evidence | Paper note | Digital POD |
|---|---|---|
| Signature | Often illegible | Captured on screen with printed name |
| Photo of goods | None | One or more photos at the drop |
| Location | Handwritten address | GPS coordinates recorded |
| Time | Driver's estimate | Device timestamp |
| Available to office | When the driver returns | As soon as it is captured |
How we build digital proof of delivery
- A driver app or mobile web flow showing the day's drops, pulled from your order system, TMS or spreadsheet.
- At each drop, the driver captures the recipient's signature and printed name, photos of the goods and where they were left, with GPS and time recorded automatically.
- Exceptions are recorded with a reason: refused, damaged, short, nobody home, left in safe place. Each exception needs a photo.
- The app works offline and syncs when signal returns, because drops in basements and rural areas have no coverage.
- The customer receives a POD email or text straight away, with the photo and a link to the signed record.
- The POD links to the order in your system and triggers the invoice in Xero, QuickBooks or Sage when a delivery is complete and clean.
- Exceptions create a task for the office to resolve with the customer, rather than being discovered at month end.
Where drivers still carry paper for some customers, a photo of the signed note is captured and read by an extraction step, then checked by a person, so the record is still digital.
We keep the driver's screen simple. Big buttons, a clear list of drops, and no more than a few taps per delivery on a normal day. Drivers are working in the rain with gloves on and a queue behind them, and a flow that slows them down will be worked around.
The office afterwards
When a customer queries a delivery, the office searches by order and finds the signature, name, photos, time and location on one screen. Invoices go out when deliveries complete rather than when paper comes back. Drivers stop carrying clipboards around, and short or damaged deliveries are dealt with the same day.
Finance sees a cleaner month end, because invoices and PODs match up automatically and the exceptions are already listed. Managers can see failed and refused deliveries by customer and by route, which often points to a specific address with access problems or a customer who regularly refuses short-dated stock.
Signs you need this
- Signed delivery notes come back to the office at the end of the day or later.
- You have lost a dispute because the POD could not be found or read.
- Invoicing waits for paperwork.
- Customers ring to ask whether their delivery arrived.
- Damaged or short deliveries are discovered days after the event.