Tracking and communication should help complete deliveries safely and accurately. They should not become a surveillance system that collects more location data than the operation needs. The design must serve dispatch, customer communication, driver safety and evidence during an exception.
Define the operational purposes
| Purpose | Minimum useful information |
|---|---|
| Assignment | Driver availability and approximate working location |
| Dispatch | Accepted job, collection point and destination |
| Customer update | Meaningful status or limited journey progress |
| Safety | Contact route and escalation when a driver is overdue |
| Incident review | Relevant timestamps and route evidence retained for a defined period |
Do not collect continuous location data merely because the software supports it. Define why each data point is needed, who can see it and when it is deleted.
Separate internal and customer views
The dispatcher may need more detail than the customer. Customer-facing tracking should not expose another person’s precise location unnecessarily or reveal private movement before or after the delivery. Use an order-specific view that ends when the service is complete.
Choose the communication hierarchy
- Structured in-app status for ordinary progress.
- Short operational message for a delay, access issue or reassignment.
- Voice call only when a real-time conversation is necessary and safe.
- Manager escalation for complaints, threats, accidents or uncertain payment/remedy decisions.
Drivers should not be expected to read or type messages while moving. The process must allow them to stop safely or use an approved hands-free method where lawful and appropriate.
Control personal-device use
If drivers use their own phones, document the required app, permissions, data use, battery impact, support and what happens when the device is unavailable. Avoid collecting unrelated device information. Provide an alternative where personal-device use would be unreasonable or insecure.
Plan the failure modes
- GPS position is stale or inaccurate.
- The driver has no mobile data.
- The driver app is logged out.
- The customer link fails.
- A job is reassigned but the first driver still sees it.
- The dispatcher loses access to the dashboard.
- Tracking continues after the shift.
Measure useful outcomes
Review assignment time, late contact, failed address, customer calls, tracking-link use, driver safety reports and complaints about privacy or inaccuracy. Do not use raw route data as a simple performance score without context such as traffic, access and safe driving.
Routes through this section
- Use How to Plan Driver Tracking for requirements, privacy and rollout.
- Use Driver Communication Systems for dispatch messaging and escalation.
- Use Live Order Tracking for Customers for customer-facing design.
Restrict access and review change
Dispatchers may need live access during service; payroll, marketing and general managers usually do not need unrestricted historical routes. Use role-based access and remove accounts promptly. Reassess the system if the business begins automated scoring, adds dashcams, expands customer tracking or starts using data for disciplinary decisions, because the privacy risk and required safeguards may change.
Practical next step: list every person who can see driver location, the exact purpose, the retention period and how tracking stops outside working time.
Official UK privacy guidance
- Information Commissioner’s Office: Monitoring workers
- Information Commissioner’s Office: Specific considerations for worker monitoring
Guidance checked: 24 July 2026. The ICO notes that monitoring guidance is under review following legislative change, so tracking arrangements should be rechecked before implementation or material expansion.
Related guides
- Delivery Management — the main guide for the wider topic.
- Driver Communication Systems — a detailed next step for putting this guidance into practice.
- How to Plan Driver Tracking — a detailed next step for putting this guidance into practice.
- Delivery Zones and Minimums — a closely related operational control to review alongside this page.
- Failed Deliveries and Problem Handling — a closely related operational control to review alongside this page.
- Data Protection for Restaurant Customer Data — a connected decision that can change the recommended approach.
