Industries/ Logistics/ Driver and proof-of-delivery apps
Electronic proof of delivery that works with no signal, at every drop
The day's drops, scanning at load and delivery, and photo, signature and location captured at the door, on the phone your drivers already carry. Everything saves to the device first, so a dead zone in a loading bay never costs you a delivery record.

- Used by
- Drivers, subcontracted hauliers, traffic office and depot staff
- Takes the place of
- Paper manifests, signed POD sheets and calls about failed drops
- Connects to
- Your transport system, accounts software and customer tracking
- Built with
- Our staff & field apps service
Where it hurts today
A normal week, before it exists
The day starts with a printed manifest on a clipboard and a stack of delivery notes in the cab. At each drop the driver gets a signature on the customer's copy and moves on. By the time the van is back at the depot those sheets have been rained on, folded into a door pocket, signed 'unchecked' by someone at goods-in, or left on a pallet at the last drop. The office cannot invoice until it has them.
Failed deliveries are worse. The driver rings the traffic office to say the site was closed, or goods-in refused the load without a booking, or nobody answered at the house. Someone writes it on a pad, or does not. A week later the customer says the driver never turned up, and the only evidence is two people's memory of a phone call. The redelivery gets charged, disputed and often written off, because nobody can show what happened at the gate.
Many firms have tried an app already. Often it came bundled with the transport system, needed signal to save anything, had buttons too small for gloved hands, and asked for six taps between arriving and finishing a drop. Drivers worked out quickly that paper was faster. So the app gets opened at the end of the shift, if at all, and the office goes back to chasing sheets.
What it does
Driver and proof-of-delivery apps, feature by feature
What the app does at each stage of a run, from loading in the yard to the last drop of the day.
- 01
The driver's manifest, in drop order
Each driver opens the app to today's run: drops in the order the planner set, with address, delivery window, booking reference, a contact number and site notes such as 'tail lift needed' or 'rear entrance only'. When the planner changes the run, the driver sees the change with a clear prompt, not a silent reshuffle.
- 02
Barcode scanning at load and drop
Every pallet, cage or parcel label is scanned onto the vehicle in the yard, so a missing item shows up before the van leaves rather than at the customer's door. Scanning again at the drop confirms the right goods went to the right place, and flags anything short or over straight away.
- 03
Photo and signature capture at the door
The driver photographs the goods in place, takes a signature on the screen with the signer's printed name, and the app adds the time and location. If the receiver signs for goods unchecked or notes damage, that remark is recorded word for word against the consignment.
- 04
Failed delivery reason codes
When a delivery cannot be made, the driver picks a reason from your own list: closed, refused, no booking, access problem, nobody home, damaged in transit. A photo is required for the reasons where you want evidence, and the traffic office sees the failure as soon as the phone has signal, ready to rebook.
- 05
Built for the cab and the loading bay
Large buttons that work with gloves on, screens readable in bright sunlight, and as few taps as possible between arriving and finishing a drop. Common actions work one-handed. Nothing depends on remembering a sequence, because nobody does that at their fourteenth drop in the rain.
- 06
Walkaround checks and end of shift
The daily walkaround check can live in the same app, with a photo of any defect sent to whoever arranges repairs. At the end of the shift the driver records returns, pallets brought back and any notes, so nothing waits in the cab overnight.
A day with it
How the day runs instead
A normal day for a multi-drop driver and the traffic office, once the app is in use.
- 5.45amDriver
The driver signs in at the depot and the run is already on the phone. They do the vehicle check in the app, then scan each pallet onto the trailer. The app shows one pallet still unscanned, so they find it on the bay before the doors close.
- 9.40amDriver
At the third drop goods-in refuses the delivery because there is no booking. The driver picks 'refused, no booking', photographs the closed bay door and moves on. There is no signal in the yard, so the record waits safely on the device.
- 9.52amTraffic clerk
The van comes out of the dead zone and everything syncs. The traffic clerk sees the failed drop with its reason and photo, rings the customer to book a new slot, and adds the consignment to tomorrow's plan without calling the driver.
- 2.15pmAccount manager
A customer emails to say a pallet arrived damaged. The account manager opens the consignment and finds the signature, the remark 'one pallet wrapping torn' written at the door, and the photo taken at 11.08am. She replies with all three attached.
- 4.30pmDriver and finance
The driver scans returned pallets back into the yard and closes the shift in the app. In the office, every completed drop already has its proof attached, so finance raises the day's invoices without waiting for a single sheet of paper.
What it connects to
Works with what you already run
The app is where the work is captured. The records it creates have to land in the systems you already run.
Transport management system
Runs, drops and delivery windows come in from your transport system each morning, and statuses, proof and failure reasons go back. Where it offers an API we use it, and where it only exports files we work with those.
Accounts software
Completed drops with proof attached are passed on for invoicing, for example to QuickBooks or Microsoft Dynamics 365 where they offer an API, so finance bills from a confirmed record rather than a chased sheet.
Customer tracking and messages
Each status change can update a tracking page and send the customer a text or email: out for delivery, arriving soon, delivered with proof, or failed with the reason and a link to rebook.
Device management
Company phones are set up and controlled through your device management, so a new driver is working on their first morning, and a lost phone can be locked and wiped the same day.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- A simple list of today's drops on the phone, fed from your transport system
- Photo, signature, printed name, time and location captured at every drop
- Failed-delivery reasons from your own list, with a photo where you want one
- Everything saved on the device first and synced when signal returns
- Proof of delivery sent straight to the office and attached to the consignment
Once it is in use
- Barcode scanning at load and drop, checked against the day's manifest
- Daily walkaround checks with defect photos sent to whoever arranges repairs
- Pallet and cage returns recorded at each drop and back in the yard
- A version for subcontracted hauliers who use their own phones
Buyer's guide
Before you commission one
Four decisions worth making before you commission a driver app, whoever ends up building it.
- 01
Off-the-shelf ePOD or a custom app
Standalone ePOD apps, and the driver apps bundled with many transport systems, cover photo, signature and offline capture for a monthly fee per driver. If your drops look like everyone else's, buy one. A custom app earns its place when your runs carry steps those products handle badly: pallet exchange, timed bookings, site-specific checks, or a flow subcontractors must follow too.
- 02
What to gather first
Collect a week of real paperwork: manifests, signed delivery notes, failed-delivery notes and walkaround check sheets. Write down your failure reasons the way drivers actually describe them. List the phones and scanners in use, and find out what your transport system can export or accept. Those four things settle most design questions before the first workshop.
- 03
Who should own it
Usually the transport or operations manager, with a senior driver as the day-to-day voice of the cab. Finance should say what proof they need before invoicing, and whoever handles disputes should agree what a good record looks like. An app owned only by IT can drift a long way from how drivers really work.
- 04
How you will know it is working
Watch whether proof reaches the office the same day, whether invoices go out sooner, and whether disputes are settled from the record rather than written off. Check the sync log for devices that have not checked in, and ask drivers where they still reach for paper. Fewer calls from the cab to the traffic office is the plainest sign of all.
Terms worth knowing
The words you will meet
- Electronic proof of delivery (ePOD)
- The digital record that a delivery happened: who signed, when, where, and what the goods looked like, usually a photo and signature captured on a phone. It replaces the signed paper sheet, and it is what lets you invoice promptly and answer a disputed drop.
- Offline-first
- An app that saves everything on the phone first and treats a connection as a bonus, syncing when signal returns. Some apps that claim offline support only cache a few screens. Ask any supplier, including us, to show a full run completed in flight mode.
- Reason codes
- A fixed list of reasons a delivery failed, such as closed, refused or no booking, chosen by the driver rather than typed. Because every failure is recorded the same way, you can count them, rebook quickly and show a customer which of their sites cause the most redeliveries.
Handled with care
The details that matter here
A driver app is used at speed, outdoors, by people who did not ask for it. These are the details we handle with particular care.
Offline as the normal case
Every scan, photo and signature is written to the phone before anything else happens. We agree with you how long a device may go without syncing and what happens if two people change the same drop, and we test in basements, tunnels and steel-framed sheds rather than on office wifi.
Location only while on shift
Location is personal data about your drivers. We agree with your data protection lead when the app records it, usually only while a shift is open, how long it is kept and who can see it, and we help you tell drivers plainly what is collected and why.
Drivers in the design
We ride along on real runs before designing anything, and a small group of your drivers try each version before the rest of the fleet sees it. If they find a step slower than paper, we change the app, not the drivers.
Subcontractors on their own phones
Subcontracted hauliers may use personal phones and work for other firms too. We limit what they see to the jobs you give them, end their access centrally when the work ends, and keep your customers' details off devices you do not control wherever we can.
Guides
Worth reading first
Questions
What buyers ask first
Can a driver app work with our existing TMS?
Usually. A custom app can sit in front of the transport system you already run, reading runs from it and writing proof and failure reasons back, so planners keep the system they know. How easily depends on what your TMS offers: an API is simplest, and file exports work with more care. If the app bundled with your TMS already suits your drivers, we would rather improve its setup than build a rival.
What if drivers will not use the app?
Then it is the app's fault, and we treat it that way. We ride along before designing, follow the paperwork drivers already know, and pilot with a few drivers on real runs. We watch where they hesitate, skip steps or go back to paper, and fix those screens before the next group starts. Paper can run alongside for a while, so nobody is forced onto it on a Monday morning.
Can drivers use their own phones for proof of delivery?
Yes, though company phones are simpler to secure and support. On personal phones the app and its data can be kept apart from the driver's own things and removed remotely, but you have less control over the device itself. For subcontractors on their own handsets we limit what is stored on the phone and end access centrally when the work ends. We talk through the trade-off with you before you choose.
Does electronic proof of delivery stand up in a dispute?
It gives you far better evidence than a paper sheet: a photo of the goods in place, a signature with a printed name, any remark made at the door, and the time and location the phone recorded. Whether that settles a particular dispute depends on your terms and on the customer, so we agree with you what each record needs to show before it is built.
Does a proof of delivery app work without signal?
It should, and ours are built that way. Every scan, photo and signature is saved on the phone first and synced when the van comes out of the dead zone, with the sync designed so records are neither duplicated nor lost. A driver can finish a whole run with no connection. The office sees those drops a little later, and the app shows plainly which records are still waiting to send.
Show us the sheet your drivers still carry
Send us a manifest and a delivery note from a real run. We will reply within 48 hours with how the same drop would work on a phone with no signal.
More for logistics
What else we build for logistics
Customer tracking and booking
A portal where customers book collections, follow their consignments live, download proof of delivery and invoices, and see their own history, so the questions they used to phone about are answered before they think to ask.
Paperwork read automatically
Delivery notes, consignment notes, customs paperwork and supplier invoices read as they arrive, with reference numbers, signatures and handwritten notes about damage pulled out and matched to the right job, and anything unclear flagged for a person.
Operations and fleet dashboards
Drops completed, late and failed, vehicle utilisation and on-time performance by customer, route and depot, on a wallboard in the office and a phone in the yard, so problems show up during the shift rather than at month end.
Dispatch and planning tools
Internal screens for your planners: jobs allocated to vehicles and drivers, capacity and delivery windows visible at a glance, and changes pushed straight to the driver's app, replacing the whiteboard and the spreadsheet only one person can read.
Systems that talk together
Orders from customers' systems flowing into your transport software, completed jobs flowing on to your accounts, and every scheduled transfer watched, so a silent failure becomes an alert the same day rather than a month-end surprise.
Everything we build for logistics
The same idea, in other sectors
