1. PoFA Technical Breach – Relevant Period Starts the Day After the ContraventionPoFA Schedule 4, Paragraph 9(5) defines the “relevant period” for delivering a Notice to Keeper as (my emphasis):
"the period of 14 days beginning with the day after that on which the specified period of parking ended."
This is not optional or ambiguous — the Act says the 14-day countdown starts the day
after the contravention date, not on it.
Therefore, if an NtK is issued on the same date as the alleged contravention, then by definition:
• The operator has commenced the relevant period prematurely, in breach of the timing requirements under PoFA.
Even though the NtK was eventually delivered within 14 days,
the issue date being within the contravention date is legally incorrect, and it demonstrates non-compliance with the statutory framework the operator claims to follow.
2. Procedural Impossibility – DVLA Data Cannot Be Received the Same DayRegardless of PoFA, it's a fact that:
• DVLA KADOE data requests cannot return keeper information in real-time,
• Parking operators are only permitted to request keeper data after the contravention has occurred,
• Data requests are processed in overnight or scheduled batches, and responses are not immediate.
Therefore, if the NtK was dated and issued on 28/03/2025, the same date as the alleged breach:
• ParkingEye could not lawfully have obtained the DVLA data on that date,
• Which makes it impossible for them to have prepared and issued a compliant NtK that same day.
So, this isn't about whether the NtK was delivered within 14 days — it was.
It's about the fact that:
• PoFA requires the notice to be issued no earlier than the day after the contravention date.
• ParkingEye could not lawfully or practically issue a same-day NtK due to DVLA access restrictions.
This is both a technical breach of statute and a likely breach of DVLA contractual and data protection rules.