How to Plan Driver Tracking

Driver tracking should begin with a documented operational need, not a map feature. This method helps a takeaway choose the minimum system needed for assignment, customer updates, safety and incident evidence while respecting worker privacy.

Step 1: define each purpose

• finding an available driver;
• confirming collection and departure;
• estimating arrival;
• supporting a driver during an incident;
• investigating a specific complaint;
• providing limited customer tracking.

Delete vague purposes such as “monitor performance” unless the business can explain the specific decision, necessity and safeguards.

Step 2: map the data flow

Record which device collects location, how frequently, where it is stored, which supplier processes it, who can access it, whether customers see it and how it is deleted. Identify transfers between the ordering platform, driver app, mapping service and customer interface.

Step 3: assess necessity and proportionality

Question	Example control
Can the purpose be met with less precise data?	Use status events rather than continuous coordinates
Is tracking needed outside an active job?	Disable or pause tracking off shift
Does the customer need an exact dot?	Use a time range or coarse progress where sufficient
Is long retention necessary?	Keep ordinary route data briefly and preserve specific incident evidence separately
Could automated scoring harm a driver unfairly?	Require human review with journey context

Step 4: select the device model

Compare a business-provided device, a personal phone with a dedicated app and vehicle-based tracking. Evaluate cost, permissions, off-shift controls, battery and data use, support, device loss and private use. Do not assume consent is the right lawful basis in an employment relationship merely because the app asks for it.

Step 5: write the worker notice and controls

Explain what is collected, the purposes, access, retention, customer visibility, automated use and how concerns can be raised. Restrict access by role and log sensitive access where practical. Make sure managers cannot casually browse historical movements.

Step 6: test operational exceptions

1. Driver denies or withdraws location permission.
2. Phone loses signal or battery.
3. GPS is inaccurate near flats or dense streets.
4. Job is cancelled or reassigned.
5. Driver finishes the shift.
6. Customer shares the tracking link.
7. A subject access request or complaint is received.

Step 7: run a limited pilot

Measure whether the tracking actually reduces assignment delay, failed contacts or customer calls. Collect driver feedback and privacy complaints. Expand only if the benefit is real and the controls work.

Questions for tracking suppliers

• Can tracking be limited to an active shift or job?
• What happens when the driver is offline?
• Can ordinary route data be deleted automatically?
• Can customer visibility be configured separately?
• Which sub-processors and mapping services receive the data?
• Can access and exports be audited?
• How are automated recommendations or scores produced?
• How is data returned or deleted when the contract ends?

Practical next step: complete a one-page tracking data map and necessity assessment before asking suppliers for demonstrations.

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 Tracking and Communication — the broader guide that frames this implementation.
• Driver Communication Systems — a closely related operational control to review alongside this page.
• Live Order Tracking for Customers — a closely related operational control to review alongside this page.