Yes, if you do it properly. The Information Commission’s Office (ICO), the UK’s data protection regulator, asks in its guidance on monitoring workers whether employers can monitor work vehicles, and its answer begins with the word “Yes”. The condition is that you comply with data protection law, and that changes what you can do when a vehicle is also used privately.
The obligations attach to how you track, not to whether you track. Most of them are straightforward to meet before installation and much harder to put right after a grievance.
This is general guidance, not legal advice. Vision Telematics does not offer legal advice, and nothing here should be relied on as a substitute for it. Data protection duties depend on your own circumstances and can change, so you should take independent legal advice before making decisions about monitoring your drivers.
You need a lawful basis, and it is probably not consent
Every organization handling personal information needs a lawful basis, and the ICO says you must decide on it and record it before you start. Tracking is covered: the ICO says telematics data that records what drivers do is personal information.
The UK GDPR has seven lawful bases. The ICO says none is better or more important than the others, and that the right one depends on your purpose and your relationship with the person.
The instinctive answer, “we’ll get the drivers to sign something”, is usually the wrong one. The ICO says consent is not usually appropriate in employment, because workers are likely to feel they have no choice. Consent must also be open to withdrawal without detriment, so one driver changing their mind could leave you tracking everyone except them. A clause in the employment contract does not solve this either: the ICO says the contract basis is unlikely to suit monitoring.
For a private employer the basis most likely to fit is legitimate interests. It has three tests: there is a legitimate interest behind the tracking, the tracking is necessary for it, and the driver’s interests, rights and freedoms do not override it. The ICO says you should assess each test before you start and record the outcome in a legitimate interests assessment. It also warns that this basis may not be the most appropriate if you are monitoring in ways workers would not reasonably expect, or if some would be likely to object once it was explained to them.
Three other bases can apply:
- Legal obligation. Where the law requires the monitoring, this basis can apply. The ICO’s example is tachographs and the rules on drivers’ working hours. It does not extend to obligations you have only under a contract.
- Public task. Public authorities cannot use legitimate interests for their official tasks, and much of what they do falls here. A private operator delivering a public authority’s legal function under contract may be able to use it too, but the task needs a clear basis in law.
- Recognised legitimate interest. The seventh basis, in force since 5 February 2026. It covers a short list of pre-approved purposes, including preventing and investigating crime, and needs no balancing test, although the processing must still be necessary. It may be relevant where tracking data is needed to investigate a theft. Routine fleet management is not on the list.
A customer’s requirement does not settle the question. The ICO says you cannot justify monitoring solely because a customer makes it a condition of business, and that the decision rests with you.
Note the distinction: you do not need drivers’ consent, but you should ask for their views. The ICO says you should seek and document the views of workers or their representatives, such as trade unions, unless there is a good reason not to, and record the decision if you do not. That is not a veto. The ICO says it can avoid complaints later and helps to build trust. How to handle that conversation is set out in how to introduce cameras without losing your drivers.
You must tell people, properly, before you start
Transparency is not a sticker on the dashboard. Apart from very exceptional cases, the ICO says you must inform workers about any monitoring, in a way that is accessible and easy to understand, and before it begins. You must also inform passengers of any vehicle monitoring. The ICO’s reason is plain: monitoring conducted without transparency is unfair.
In practice that means a plain-language privacy notice, issued and explained before the system goes live. The UK GDPR and the ICO set what it must cover:
- Who is responsible for the data and how to contact them, including any data protection officer.
- What you are collecting, why, and the lawful basis you rely on. If that is legitimate interests, say what those interests are.
- Who receives it, and any transfers outside the UK.
- How long it is kept.
- Drivers’ rights, including access to their data and the right to object.
- Their right to complain to you and to the ICO.
- Any automated decisions that need safeguards, and what they mean for the driver.
Add one item the law does not list: what the data will never be used for. Drivers will ask.
Complaints are a new duty. Since 19 June 2026, people have had the right to complain directly to an organization about how it uses their personal information, and the ICO says there are no exemptions. You must give drivers a way to complain, acknowledge a complaint within 30 days, respond without undue delay and tell them the outcome. A complaint can arrive by any route, including through a transport manager, so the ICO says staff should be able to recognize one.
Tracking a driver without telling them is a different matter. The ICO says covert monitoring is unlikely to be justified in most usual circumstances. It may be justified in exceptional cases, for example where it is necessary to prevent or detect suspected criminal activity or gross misconduct and telling the worker would prejudice that. Even then, the ICO says it should be authorized by senior management, strictly targeted and limited to the shortest time possible, and you must carry out a DPIA.
Some monitoring requires a formal impact assessment
A Data Protection Impact Assessment, or DPIA, is a written analysis of the privacy risks and how you will reduce them. For higher-risk monitoring it is a legal requirement, not good practice.
The ICO says you must carry one out if you monitor driver behavior or driving style, use cameras or audio, or use any tool that applies analytics to make inferences, predictions or decisions about drivers. That describes most driver scoring.
Basic location tracking of a vehicle used solely for work is the lower-risk case, but it should not be assumed to be exempt. Screen it and write the answer down, and if you are in any doubt the ICO strongly recommends doing a DPIA.
Beyond compliance, it is a useful document for handling workforce concerns, because it forces you to write down exactly what you will and will not do. What a data protection impact assessment should contain is set out in the guide to DPIAs for driver monitoring.
A summary of the law and ICO guidance, not a substitute for them. Read them against what your own system does.
Be careful when a score makes the decision
The rules on automated decisions changed on 5 February 2026. Where a significant decision about a driver is taken with no meaningful human involvement, you must now have safeguards in place. You must tell the driver about the decision and let them make representations, obtain human intervention and contest it. A significant decision is one with a legal or similarly significant effect. The ICO’s examples include changing a worker’s pay and dismissing them.
The ICO’s guidance includes a useful contrast. A courier firm used vehicle tracking data to check deliveries, and issued a warning only after an HR manager had reviewed the data and discussed it with the worker. A person took that decision, so the automated-decision rules did not apply. That review has to be real: the ICO says it cannot be a token gesture.
Whichever applies, the ICO says workers should be able to see and, where necessary, explain or challenge the results of any monitoring. It also warns that analytics tools can make incorrect inferences about workers. A score should open a conversation, not end one.
Private use is where organizations get caught
Where drivers may use a vehicle privately, the ICO says you will rarely be able to justify monitoring during that private use. Its own example is a company car tracked during working hours, on a system the driver can disable so that it does not monitor them when they are not working.
In practice that means a privacy mode the driver can switch on, which stops detailed location recording outside working hours. If you also want stolen-vehicle protection out of hours, ask how the system provides it without recording private journeys, and cover it in your assessment and your privacy notice.
If a system cannot do this and your drivers take vehicles home, treat that as a compliance problem rather than a missing feature. It is worth confirming during evaluation rather than after installation.
Cameras raise the bar
Everything above applies, with additions. A DPIA is required rather than advisable. Any audio capability should be switched off by default and used only in exceptional circumstances: the ICO says audio, particularly when continuous, is more intrusive than video and needs a much greater justification. Where a vehicle is also used privately, it says continuous recording during that use is likely to be considered excessive, and that drivers should have the option to deactivate it.
Outward-facing cameras capture other motorists and pedestrians. The ICO says you must make anyone else caught by the monitoring aware of it and why, and expects signage within the vehicle saying when recording may happen and who to contact. For people outside the vehicle, a notice on the vehicle pointing to a fuller privacy notice is the practical answer.
Access to footage should be limited to those who need it, and they should be trained to handle it. Name the roles, log every viewing and be able to say why it happened. “Anyone in the office can look at any camera at any time” is not a defensible position. Drivers and others who are recorded can also ask for footage of themselves, so you may need to be able to redact other people from it. If you have not yet decided whether to fit driver-facing cameras at all, start with the case for and against driver-facing cameras.
Keep it for a stated period, then delete it
The UK GDPR does not set retention periods, but the ICO says you must not keep monitoring data for longer than necessary, must have a retention schedule and must delete in line with it. You should not keep information just in case. Set a period, write down the reason, take account of any legal obligations, automate the deletion, and have an exception process for material relating to an open claim or investigation.
Purpose limitation: the trap that catches good employers
Data collected for one stated purpose should not be quietly repurposed for another. The ICO says you must be clear about your purpose and should not monitor workers “just in case”. You can generally only use the data for a new purpose if it is compatible with the original one, and you must tell drivers before you do.
If you told drivers the system exists for safety and efficiency, using it to time break lengths is a different purpose. That is a compliance problem, and it is also a quick way to lose workforce trust. One manager phoning a driver about a nine-minute break can undo eighteen months of credibility.
The ICO calls this function creep and says it can happen gradually, so review your use of the data regularly. Decide in advance what the data will and will not be used for, write it down, tell people, and hold managers to it.
Two things that are easy to forget
Your supplier. In most cases you are the controller and your tracking supplier is a processor. The ICO says you must have a written contract in place, should not assume a product is compliant, and stay responsible for how the data is handled. If the supplier is based outside the UK, the rules on international transfers apply.
Other laws. The ICO points out that data protection is not the only law that applies to monitoring. Others include the Human Rights Act 1998, equalities legislation and investigatory powers regulations. What happens if a driver refuses or breaks a policy will also depend on your contracts and procedures, so take advice before treating it as a disciplinary matter.
The short checklist
- Lawful basis identified and recorded, with a legitimate interests assessment if that is the basis
- Privacy notice issued to drivers before monitoring begins
- DPIA completed for behavior monitoring, analytics and cameras, and a recorded decision for anything else
- Private use addressed, with a way for drivers to stop monitoring outside work
- Complaints route in place and named in the privacy notice
- Significant decisions checked for meaningful human involvement
- Retention period set, justified and automated
- Access restricted to named roles and logged
- Purposes defined in writing, including what the data will never be used for
- Drivers or their representatives consulted before the decision was final
- Signs in vehicles with cameras, and a notice for people outside them
- Supplier’s role as processor set out in a written contract, including where data is stored
Sources: UK GDPR, Articles 5, 6, 8A, 13, 21, 22A to 22D, 28 and 35, and the Data Protection Act 2018, section 164A, as published on legislation.gov.uk. Information Commission’s Office (ICO): A guide to lawful basis, Recognised legitimate interest and How to deal with data protection complaints; Employment practices and data protection: monitoring workers, and Surveillance in vehicles, which carry the ICO’s notice that they are under review following the Data (Use and Access) Act. Where the monitoring guidance predates that Act, as on the number of lawful bases and on automated decisions, this article follows the current law. All read on 3 November 2026. General guidance, not legal advice.
