POD and tracking answer different customer questions
A map position may help explain progress, but it cannot confirm who accepted the goods or whether an item was refused. A signed record may explain the handover, but it does not help a customer follow an earlier journey.
The useful combination is a consistent job reference linking the booking, progress and completion evidence. Drive It supports that workflow for your own entered jobs and eligible connected work.
| Software area | Main purpose | What to review |
|---|---|---|
| Tracking | Where is the delivery in its journey? | Recorded progress and available location information |
| Electronic POD | What happened at the handover? | Outcome, recipient details, photos and signature |
| Combined workflow | Which booking do these records belong to? | A consistent job reference and the correct collection or delivery stop |
One practical example: a furniture collection and delivery
Suppose you collect an item from a retailer and deliver it to a customer. Keep the retailer’s reference, goods and access instructions with the booking, and distinguish the collection stop from the delivery stop.
While the job is being worked, use the supported customer tracking view to explain progress. At the destination, record the actual outcome and requested evidence. If access prevents completion, record an unsuccessful attempt and the reason instead of treating arrival as delivery.
Benefits for the next customer enquiry
When a customer asks where their order is, start from the job record. When they ask who received it, review the outcome and evidence. Keeping these records associated with the booking gives you a clearer starting point than an isolated photo or a message with no reference.
This can support a consistent follow-up process, but accurate input still matters. Check incomplete or contradictory records and investigate before answering. Software alone cannot establish what happened when the evidence has not been captured.
What a useful combined system should let you assess
Evaluate the whole chain using a normal working day. Include a successful stop, an address query and an unsuccessful attempt so the demonstration covers exceptions as well as an ideal delivery.
Make the customer view part of the test. Check the information visible to the intended recipient and how you retrieve evidence later. Confirm any specialist barcode, custom form, offline or integration requirement with the supplier.
- Recognisable booking and customer reference.
- Correct collection and delivery legs.
- Route instructions visible to the driver.
- Supported customer tracking for the relevant job.
- Accurate outcome and readable delivery evidence.
- A clear way to find the record for a later enquiry.
Keep connectivity and evidence completion visible
Live reporting depends on permissions, app setup and a usable connection. A stale location and an unuploaded photograph create different gaps; check the actual job record before assuming either has reached the office or customer.
Use the phone setup guide and test the places where your routes have weak coverage. Drive It’s iPhone and Android apps are in beta. Do not assume an uninterrupted signal or automatic success for every upload.
Choose an owner-driver membership or scope a wider operation
Drive It is worth assessing when you want your own customer bookings, routes, tracking and POD together with eligible Deliverate opportunities. Current availability is UK only, including Northern Ireland.
If you need a dispatch team, several merchant accounts, a warehouse connection or a particular evidence document, ask Nexus to confirm the right setup. Compare complete quotes and use the individual supplier guides to understand differences in account scope.