POFA 2012 Schedule 4: The Law That Makes Most Private Parking Charges Unenforceable Against You

Before 2012, private parking operators had a significant problem. They could issue charges to whoever was parked on their land. But if the driver was not the registered keeper, they had no reliable way to identify them. The registered keeper knew who was driving. The operator did not.

The Protection of Freedoms Act 2012 created a solution: a legal mechanism allowing the operator to hold the registered keeper liable — regardless of whether they were the driver — provided the operator followed a precisely defined process. That process is Schedule 4 of the Act.

The same Act that gave operators this power also defined its limits. Every requirement in Schedule 4 is mandatory. There is no discretion to overlook a missed step. Where the process is not followed exactly, keeper liability does not arise.

What Schedule 4 actually does

Before POFA 2012, private parking enforcement relied on the common law of contract. The operator could only sue the driver — the person who actually parked the vehicle and (in the operator's argument) accepted the parking terms. If the driver was not the registered keeper, the operator had no clear route to the person who owned the car.

Schedule 4 created a new statutory route. It allows the operator to recover unpaid parking charges from the registered keeper of the vehicle, even if the keeper was not driving, provided:

1. The underlying charge is a valid contractual claim
2. The operator has followed the Schedule 4 notice procedure precisely
3. The keeper has not paid or provided the driver's details within the required period

This mechanism is the entire basis on which camera-only enforcement operates. No windscreen ticket. No way to identify the driver at the time. Just the registered keeper — whom the operator obtained from the DVLA via a KADOE (Keeper at Date of Event) request.

Without Schedule 4 compliance, that route to the keeper does not exist.

The two Notice routes under Schedule 4

Schedule 4 creates two separate routes depending on whether the operator gave the driver a Notice to Driver (a windscreen ticket) at the time of the alleged contravention.

Route 1: No Notice to Driver was given

Camera-only enforcement — ANPR, CCTV — where the driver was not confronted and no windscreen ticket was attached. In this case the operator must serve the Notice to Keeper between 14 and 56 days after the date of the alleged contravention.

The 14-day minimum exists so the keeper has had a reasonable opportunity to receive and respond to any Notice to Driver that might have been sent. The 56-day maximum is a hard deadline. A Notice to Keeper served on day 57 or later means keeper liability never arises.

Route 2: A Notice to Driver was given

A windscreen ticket was placed on the vehicle or handed to the driver. In this case, the operator has longer: the Notice to Keeper must be served within 56 days of the end of the parking period.

The 56-day window is the same, but the start point is different — it runs from the end of the parking period, not from when the windscreen ticket was given.

What the Notice to Keeper must contain

Even where the Notice to Keeper is served within the correct window, Schedule 4 paragraph 9(2) sets out a list of prescribed content that must appear in the notice. Every item is required. Missing any one of them is a compliance failure that prevents keeper liability from arising.

The required content includes:

• Identification of the vehicle (registration mark)
• The period of parking to which the charge relates — not just the date, but the specific parking period from entry to exit
• The amount of the unpaid parking charge
• The name and address of the creditor (the operator seeking payment)
• A statement that the creditor does not know both the name and current address of the driver
• A statement that the creditor is unable to pursue the driver for the charge without that information
• An invitation to the keeper to either pay the charge or provide the driver's name and current address
• A warning of the consequences of failing to do either — specifically, that the keeper may be held liable
• The period within which payment or driver identification must be provided (at least 28 days from the date of the notice)

Operators who use template notices sometimes omit prescribed statements — particularly the specific wording around liability transfer and the invitation to identify the driver. Where the wording is vague, incomplete, or absent, the notice fails the Schedule 4 test.

The keeper's response options under Schedule 4

Once a valid Notice to Keeper has been served, Schedule 4 gives the keeper a defined response period — at least 28 days from the date of the notice. Within that period, the keeper can:

• Pay the charge — which ends the matter (and the right to challenge it)
• Provide the driver's name and current address — which transfers the operator's claim to the driver and removes keeper liability, provided the information is accurate
• Neither — after which keeper liability may arise, but only if the Schedule 4 process was followed correctly in the first place

The keeper is not legally required to identify the driver under Schedule 4. The invitation to do so is a mechanism that, if accepted, removes keeper liability. Refusing to identify the driver is not an admission of anything — it simply means the operator's claim against the keeper depends entirely on their Schedule 4 compliance.

Where compliance is defective, the operator has no legal route to the keeper regardless of whether the driver is identified.

The landowner authority link

There is a frequently overlooked connection between POFA 2012 and landowner authority. The DVLA KADOE contract — the agreement under which the DVLA provides keeper details to parking operators — requires the operator to have a "reasonable cause" for the data request.

If the underlying parking charge is invalid — because the operator had no valid landowner authority, the signage was non-compliant, or the charge was issued in error — then there was no reasonable cause for the DVLA data request. That means the keeper's personal data was obtained and processed unlawfully under UK GDPR Article 6.

This is the angle that connects a data protection challenge to a private parking appeal. It does not cancel the charge by itself, but it raises a separate ground that can support a POPLA appeal and, if appropriate, an ICO complaint.

Why operators fail Schedule 4 so often

Private parking operators issue millions of charges per year. The process is largely automated. Notices are generated and posted by system rather than reviewed individually.

That automation creates systematic failures:

• System delays between the contravention date and the Notice to Keeper issue date — a system that processes notices in batches may routinely generate notices on day 57 or 58 rather than within 56 days
• Template notices missing prescribed statements — a notice template not updated since before certain case law clarified the requirements
• Incorrect contravention dates on the Notice to Keeper — where the system records the ANPR read time rather than the actual start of the parking period
• Notices that describe the period of parking in vague terms rather than specifying the precise entry and exit times
• Failure to distinguish between the date the notice was generated and the date it was served — the 56-day window runs from contravention to service, not to generation

These are not rare edge cases. They appear repeatedly at POPLA, in county court defences, and in complaints to the BPA and IPC. Operators know they occur. Many rely on the fact that most motorists do not check.

How POFA arguments are assessed at POPLA and IAS

Both POPLA and IAS adjudicators are familiar with POFA 2012 Schedule 4. A POFA compliance argument that is clearly stated, supported by the dates and the notice itself, and identifies the specific requirement that has not been met is taken seriously.

What does not work is a generic assertion that "the operator has not complied with POFA 2012." An adjudicator reviewing that statement has nothing specific to assess. The argument must identify:

• The specific requirement that was not met (timing, content, or both)
• The evidence supporting the failure (the dates, or the absence of prescribed wording)
• The paragraph of Schedule 4 that has been breached

A precise, evidenced POFA challenge is among the strongest grounds available at the independent appeal stage. It does not require the adjudicator to make a judgment call about signage adequacy or commercial justification. Either the dates comply or they do not. Either the prescribed statements are present or they are not.

What Schedule 4 tells you about your position

Schedule 4 to the Protection of Freedoms Act 2012 is a public document. The requirements it sets out — the timing windows, the prescribed content, the consequence of non-compliance — are all there in the legislation.

What the legislation does not tell you is how to use those requirements to construct an argument that succeeds. Which element of non-compliance carries the most weight in your specific notice. How to frame a timing argument when the gap is narrow. What to say when the operator's notice appears to contain most — but not all — of the prescribed statements in paragraph 9(2). How to respond when the operator claims Schedule 4 does not apply to their enforcement model.

Knowing the law is the starting point. Successfully arguing it at initial appeal, at POPLA, or at the IAS is a different exercise — one that depends on how the argument is constructed, in what order, and with what evidence attached.

The POFA Schedule 4 challenge is the strongest ground available against a keeper liability claim. It is also the ground most often lost through imprecise drafting. The template letters cite the specific paragraph that applies to your notice, frame the timing argument correctly, and request the evidence that puts the operator's compliance under scrutiny.