DVLA Data, Weeded Records, and the Case for a Trusted Data Pipe

In 2025 alone, at least 20,000 reported stolen vehicles in England and Wales never made it onto DVLA's records, according to research by loss adjusters QuestGates. Not because anyone hid them - because of a police process called "weeding," where an unconfirmed theft marker on the Police National Computer is automatically wiped after six weeks if it isn't formally confirmed, and never passed on to DVLA. The result: a genuinely stolen vehicle can come back "clear" on a standard check.

It's a striking number on its own. But it's also a useful example of a bigger, less visible problem: data that exists, technically, somewhere in the system - but doesn't reliably move to where it's needed, when it's needed.

Why this is a structural problem, not a one-off stat

Vehicle and driver data passes through several separate systems and organisations before it reaches the person who actually needs it: a police force, the Police National Computer, DVLA, and finally the insurer, solicitor or investigator making a decision. Each handoff is a point where data can be delayed, lost, or - as with weeding - quietly dropped altogether. There is rarely a single audit trail spanning that whole chain, which makes it hard for anyone at the end of it to know how current or reliable the information they're relying on actually is.

This is also the exact problem the Home Office is grappling with in its current consultation on police and law enforcement access to DVLA driver data (closing 8 September 2026). The proposals lean heavily on governance rather than just access: a new statutory Code of Practice, mandatory training and vetting, tamper-proof audit logs, and annual reporting to Parliament, regardless of how broad the final access rules end up being. We submitted our own response to the consultation, focused on exactly these governance and audit questions. The consultation is asking the right question: not "should there be more access," but "can the plumbing actually be made to work, safely and auditably."

NetWatch's role: a trusted pipe, not a data owner

We don't hold DVLA data ourselves. What NetWatch does, through Rapid, is give clients direct API access to DVLA's KADOE service, so insurers, solicitors and investigators can bring vehicle keeper information straight into their casework rather than requesting it through slower, manual channels.

Every request made this way has to follow DVLA's permitted purposes, and every one is logged and auditable - so organisations can demonstrate not just that data was accessed, but exactly why. That's the role we think NetWatch should play in this chain: not the organisation that owns sensitive data, but the trusted, secure pipe between the organisations that hold it and the organisations that need it - built so that speed and control aren't in tension.

"Sometimes data protection gets in the way of critical data getting where it needs to be, and being seen by the people it's legally fine to see it. Public bodies like the police and DVLA need systems they can trust to manage disclosures lawfully, and that are easy to use. That's why we've built Rapid: an easy to use, reliable disclosure platform for police forces, one we keep extending with more public data."

David Purcell, COO, NetWatch

What this means for you

If you're an insurer or claims team: verifying a vehicle's registered keeper at the date of an incident is often a critical, time-sensitive step in a claim. Doing it through an auditable platform means you can show your basis for a decision, not just the decision itself.

If you're a solicitor or law firm: the same applies to personal injury and collision matters where establishing the registered keeper is part of building a case - speed matters, but so does being able to evidence how and why the data was obtained.

If you're a police force: NetWatch's disclosure management offering for forces is already built, and a number of forces are now moving through onboarding. It's designed on the same principle as our approach to DVLA data - free to the force, but secure and auditable by default, not as an afterthought.

Sources: