How Operators Get Keeper Details From the DVLA

Understanding the KADOE Electronic Service

DVLA runs two routes: the paper V888 forms set out on the main GOV.UK overview, and the electronic KADOE service for organisations enquiring at volume. The overview page concentrates on the forms, so an operator comparing options from it alone can miss the electronic service, even though DVLA publishes it separately through its own guidance and developer portal.

GOV.UK's main overview page sets out four forms. V888 is for individuals. V888/2A gives a company a keeper's name and address on a specific date. V888/2B covers other vehicle record details. V888/3 is for companies issuing parking or trespass charge notices. That overview concentrates on the application forms and carries no fee figures or response times, so a reader who stops there would reasonably conclude that a paper form, one plate at a time, is the whole system.

A second route runs alongside the forms. DVLA provides an electronic service, the Keeper at Date of Event service known as KADOE, for eligible organisations needing frequent access, with its own developer portal, and the V888/2A form itself points frequent applicants towards it. The published version of the KADOE contract sets a fee of £2.50 per valid request transaction, collected by Direct Debit by the third working day following the week of account, so an active site is billed weekly instead of per form. DVLA's separate guidance on releasing register information describes the secure electronic link for organisations enquiring at volume. The forms overview and the electronic service are two different front doors, and an operator comparing options from the forms page alone will not see the second.

The two routes are not interchangeable once volume enters the picture. A team working notices by the hundred cannot complete a manual form per registration and wait on a postal reply.

New customers do not begin on the electronic link at all. DVLA's published contract defines a mandatory probationary period of 26 weeks, during which a new applicant has to make a minimum of 300 valid manual requests before the electronic KADOE service commences. If fewer than 300 are made inside that window, the probation runs on until the total is reached, and the period only starts once the applicant has made its first valid manual request after confirming it intends to join. DVLA notifies a commencement date for the electronic service only once the applicant has completed that probation to DVLA's satisfaction, and DVLA's own guidance for new customers states the same 6 month probationary period. The practical effect runs against treating electronic access as available from day one: the manual route comes first, the earliest requests are the most closely watched an operator will make, and the sensible step is to confirm the current onboarding requirements with DVLA before planning around a fixed timetable.

What Evidence an Operator Must Hold Before Enquiring

DVLA's contract puts reasonable cause in the past tense. The customer must have gathered the evidence proving it before the enquiry is made, and must be able to produce that evidence long afterwards, which turns a question about paperwork into a question about what the site captures automatically every time.

DVLA's published contract puts the obligation on the customer's side before a request ever reaches DVLA. Clause B2.3 requires gathering evidence demonstrating reasonable cause ahead of the enquiry, and clause B2.2 restricts any data received to the reasonable cause and the specific date, event and purpose requested. Reasonable cause is not ticked off at the moment of asking. It describes a state the operator has to already be in, with documents to prove it, before the form is submitted.

DVLA's guidance for private parking operators spells this out, and it is more specific than most sites treat it. The evidence of reasonable cause is expected to be in hand before the enquiry: the case reference, the registration, the make and model, the date and location of the incident, photographic evidence with the date and time displayed on the images themselves, images of the site signage showing the terms and conditions, and a landowner agreement authorising the scheme and any action to recover a charge. Where the contravention was ticketed on site, a notice to driver sits in that set too. The one item that cannot is a completed notice to keeper, because an operator needs the keeper's name and address from DVLA before it can produce one, so that notice belongs to the stage after the enquiry, not before it. Not every item is universally mandatory in the same way; what has to exist before the request is the evidence that justifies it.

That list is a site specification in disguise. A camera must produce a legible, accurate timestamp, a matter of ANPR accuracy as much as DVLA compliance. Signage must exist, be photographed, and match what the notice claims the driver agreed to, covered by what ANPR cameras do and the signage on the ground. A landowner agreement must exist in writing before the first charge notice goes out, with the authority to recover written into it.

DVLA did not invent any of these burdens. They are the evidence a well run enforcement operation should already hold for its own reasons, to defend a charge at appeal and to satisfy a landowner.

The practical question is whether a site's systems capture the items DVLA names automatically, on every enforcement action. A site that timestamps every contravention, files signage evidence once and holds a signed landowner agreement before enforcement starts has done the work. A site relying on someone remembering where last year's signage photo lives has not, and will not find out until an enquiry or audit asks.

How DVLA Audits Work

DVLA does not treat a granted enquiry as closed. Its guidance describes two levels of audit over customers using its keeper data service, one checking a sample of individual requests and one checking the premises and processes behind them, and both look for the same evidence described above.

The first level, which DVLA's guidance calls a tier 2 audit, is a sampling exercise and not a response to suspicion. DVLA selects a sample of an operator's enquiries and asks for the reasoning behind them. The guidance describes a window of 10 working days to respond, though an operator should treat the exact scope, frequency and deadline as set by the audit procedure DVLA applies to its own arrangement. An operator unable to produce the case reference, the photographs, the notice and the landowner agreement inside that window risks having future requests refused.

The second level is a tier 3 audit, which the guidance describes as carried out by the Government Internal Audit Agency, on site at the premises where the operator stores DVLA's data. Auditors verify a full audit trail behind each request and compare the submitted date of incident with the date the contravention actually took place, which catches enquiries made too long after the event to relate to the cause claimed.

The two tiers test different things. A tier 2 sample tests whether an operator can explain one decision. A tier 3 visit tests whether the organisation behind that decision is built to hold personal data at all, which is why it takes in the premises, the security arrangements and the data protection registration alongside the enquiry trail.

Both tiers ask something an operator cannot answer retrospectively. A date of incident submitted months ago either matches the contravention or it does not. A photograph either carried a legible time when it was taken or it never will. By the point DVLA asks, the evidence has already been created or already been lost, which puts audit readiness at the moment of capture and nowhere else.

How an Operator Loses DVLA Access

DVLA's guidance lists several grounds on which it can withdraw access, and fraud is only one. Failing to answer a tier 2 audit, or making enquiries for spot checks, intelligence gathering, marketing or administration, are among them. Missed Protection of Freedoms Act timeframes primarily affect the right to recover from the keeper, a separate consequence from DVLA's access decision.

Operators picture access loss as punishment for something dramatic: a fabricated case, a request for a vehicle never on site. DVLA's guidance describes something more mundane. An unanswered audit sample can end access. So, the guidance indicates, can enquiries made for spot checks, intelligence gathering, marketing or administration. Where an audit turns up significant issues, the decision passes to DVLA's Senior Information Risk Owner.

Two different consequences are easy to run together here, and they should be kept apart. Missing the notice timeframes set by the 2012 Protection of Freedoms Act, at Schedule 4, goes to keeper liability: an operator who serves a notice to keeper late can lose the right to recover the charge from the registered keeper, under a framework that applies to relevant land in England and Wales, with Scotland and Northern Ireland not on the same terms. DVLA's decision to continue or withdraw data access is governed separately, by its own contract and audit guidance. Both can bite in the same case, but one is about whether the keeper is liable and the other is about whether DVLA keeps supplying names, and a careful operator does not assume a rule about one settles the other.

The cost of losing access is not a fine. That same framework gives an operator a conditional right to recover an unpaid charge from the registered keeper, but only where its conditions are met and, as a keeper liability regime, only in England and Wales. Exercising it takes a name and an address. An operator without keeper access still issues notices, still runs cameras, still pays the staff who do both, and can still pursue the recovery routes that do not depend on tracing the keeper, such as a charge paid at the time or pursued against a driver whose identity is already known. What changes is that reaching the registered keeper gets much harder, so administrative costs rise, cases take longer to close and the share that ever converts falls. The enforcement book keeps growing while less and less of it turns into recovery.

That puts an operator's notice timetable and its evidence trail inside the same problem, whether or not the same team manages both. A team, council or private, that watches its deadlines closely while its evidence and data requests run on a separate unwatched timetable will eventually miss something that matters. What helps is a single view of enforcement timing, the kind a data dashboard is designed to hold, so a slipping deadline shows up while it can still be acted on, not after it has cost a recovery or drawn an auditor's eye.

Data Protection and Retention Requirements

DVLA's contract runs two retention clocks over the same case, not one. The keeper's personal details and the evidence justifying the request expire on different schedules, so what matters is that each type of information gets the right retention and deletion rule, instead of the whole case file running on a single timer.

DVLA's published contract treats the keeper's personal details and the evidence file as two separate obligations. Clauses D6.1 and D6.2 require data to be deleted once it is no longer needed for the purpose it was obtained for, which is not the same as deleting it the moment a case closes, because a continuing lawful purpose can keep it in play. Clause D6.3 requires retaining, for 2 years from the date of the request, the evidence relied on to show compliance. DVLA's guidance for operators puts the same split plainly: keep supporting evidence for a minimum of 2 years, and delete personal keeper details once they are genuinely no longer needed.

The trap is not storing the two together but applying a single blanket rule to the whole case. A system that deletes everything on closure, or keeps everything indefinitely because deleting feels risky, is applying one timer where the contract expects two. Deleting everything on closure removes evidence DVLA can still ask for up to 2 years later. Keeping personal keeper details indefinitely holds them longer than the contract permits once their purpose has ended, a breach in its own right. Keeper details and evidence can sit in the same system, provided each is governed by its own retention and deletion rule.

The practical requirement is to apply a distinct rule to each from the outset: case evidence on a 2 year schedule regardless of what happens to the case, and personal keeper data cleared once it is no longer needed for the purpose it was supplied for. Building that distinction into a site's own records is a different exercise from reading the contract after the fact.

It is also the easier thing to show an auditor. A system where the evidence file and the keeper record expire on their own schedules answers the retention question on one screen. A case run on one undifferentiated retention rule invites the auditor to go looking.

What Keeps a Site Ready for an Enquiry or Audit

A site that never struggles with a DVLA enquiry has usually stopped treating the evidence as paperwork and started treating it as something the site captures automatically: time stamped images, signage records, a landowner agreement and a notice trail that all exist before an enquiry, let alone an audit, ever asks for them.

The awkward part of all this is the lag. Evidence captured 18 months ago has to surface inside a short audit window, in a form somebody else defines, for a case the original team may no longer remember. That is an infrastructure question: cameras that record a usable, dated image every time, signage documented as it changes, and every notice logged against the date that triggered it.

Ask it about your own estate. How many of your sites could produce a dated signage photograph from 18 months ago by the end of next week?

This is the kind of infrastructure Parka is built around. Our ANPR cameras are designed to capture and timestamp a contravention at the point of the event instead of after it. Signage can be installed and documented as part of the initial setup, so a dated record of it exists from the outset instead of a photo someone hunts for later. A data dashboard can bring the notice timeline and the evidence trail into a single view, and the Ranger app gives enforcement staff a way to record activity on the ground. How much of this applies to a given site, and how retention schedules and any specific compliance step are handled, depends on how that site is set up and configured, so it is a conversation to have with us site by site, not a fixed feature list. None of it makes DVLA compliance or audit readiness automatic; what it does is put the evidence within reach for the moment an enquiry or an audit asks for it.

DVLA keeps its discretion either way. Regulation 27(1)(e) lets DVLA refuse in the exceptional cases its discretion covers, the audits run on DVLA's own schedule, and the tier 3 auditor decides what counts as satisfactory. What changes with good infrastructure is whether an operator is ready when the enquiry, or the audit, arrives: prepared before being asked, or assembling an answer under a short deadline that started the moment DVLA came looking. Only one of those positions keeps a site's access intact the next time it matters.