Here's my assessment of the RCP Parking Ltd Landowner Agreement (as provided in the redacted copy) in the context of PoFA 2012 and the Private Parking Single Code of Practice (PPSCoP) v1.1 (17 February 2025) compliance, particularly regarding proof of authority to issue parking charges.
1. Purpose and Scope
The agreement purports to grant RCP Parking Ltd authority to “install, control, and operate” parking enforcement systems at Rochdale Road, Manchester, M9 6AJ. It refers to RCP Parking as the “Operator” and the other party as the “Landowner” (name redacted).
However, under PoFA 2012 Schedule 4, Paragraph 2(1) and PPSCoP Section 7.1, the operator must have written authorisation from the landowner confirming its right to:
• Issue parking charges in its own name, and
• Pursue them through the courts if necessary.
The copy provided does not clearly demonstrate these rights beyond generic management powers.
2. Landowner Identity and Legal Standing
The Landowner’s name and company details are redacted, which makes it impossible to verify:
• Whether the signatory is the actual landholder or a tenant/agent;
• Whether they have the legal interest or delegated authority to enter into the contract.
Under PPSCoP 7.2, evidence must identify the landholder and confirm their capacity to authorise enforcement. A redacted or anonymised signature prevents verification and fails to meet this evidential requirement. POPLA should reject redacted agreements on this basis, just as any court would.
3. Signatory Validity
The RCP representative signed as “Contracts Manager – Declan and Sam King”. This is not a personal signature, but two names handwritten in a way that suggests ambiguity as to who actually signed. The document lacks:
• A printed name of the RCP signatory,
• Any witness or counter-signature validation, and
• A company seal or letterhead confirmation that the individual is authorised to bind RCP Parking Ltd.
These omissions undermine the agreement’s evidential weight.
4. Term and Duration
The document refers to the start date but the commencement and expiry dates are not visible. Without a defined duration, it cannot be established whether the contract was in force at the date of the alleged parking event. This breaches PPSCoP 7.3(a), which requires a “clearly defined start and end date”.
5. Extent of Authority
The operative clause gives RCP Parking permission to:
“Install and operate a parking management system to control and enforce parking on the Site.”
However, it does not expressly state that RCP Parking:
• May issue Parking Charge Notices in its own name, or
• Take legal action in its own name against motorists.
This is crucial. Under PoFA 2012 Schedule 4, Paragraph 4(1), only the “creditor” may recover unpaid charges. If RCP is merely acting as an agent for the landholder, it cannot lawfully claim or litigate in its own name. The absence of a clause expressly granting those rights renders the agreement insufficient to establish RCP as the “creditor”.
6. Annex A – Site Plan and Facilities
The annex identifies the site and lists features such as “Tariff machines”, “Lighting”, “Signage” and “CCTV”, but these are purely descriptive. There is no clause cross-referencing Annex A as a schedule of rights or indicating it forms part of a legally binding contract. The plan also lacks date validation, which is relevant where signage has changed over time.
7. Photographic Evidence
The attached photographs show:
• RCP-branded signage with tariffs and contact details.
• However, there are no clear terms or notice of the charge for breaching any terms.
Photographs alone cannot prove contemporaneous authority; they may merely show operational presence rather than ownership or control.
8. Overall Assessment
The provided agreement does not satisfy the requirements of:
• PoFA 2012 Schedule 4 (Paragraphs 2(1) and 4(1)), or
• PPSCoP Sections 7.1 to 7.3, which require transparent evidence of landowner authority.
Specifically, it fails on:
• Redacted landowner identity (cannot be verified);
• No explicit right to issue or pursue PCNs in RCP’s name;
• No proof the contract was in force at the material date;
• Ambiguous signatures and lack of execution details.
9. Suggested Conclusion for a POPLA
The operator’s redacted “Landowner Agreement” fails to meet the evidential requirements under the Protection of Freedoms Act 2012 and Section 7 of the Private Parking Single Code of Practice. The document does not identify the landholder, does not demonstrate that the signatory had authority to grant enforcement rights, and does not confer any express right upon RCP Parking Ltd to issue or pursue Parking Charge Notices in its own name. As such, RCP Parking Ltd has failed to establish itself as the creditor and has no locus standi to pursue this charge.
Great—POPLA code secured and TRACE recalled. Next step: file a tight POPLA appeal focused on (1) no keeper liability due to a defective PoFA warning, and (2) rebutted delivery/service. Submit within 33 days of the rejection letter date (the letter is dated 10/10/2025, so don’t miss the deadline).
Below is a ready-to-paste POPLA appeal text. Use it as your whole appeal.
POPLA Appeal: PCN [ref], VRM [vrm], Site: RCP Rochdale Road, Event date: 20/06/2025
1. Operator has not shown that I (the keeper) was the driver; keeper liability not established – Notice to Keeper fails PoFA 2012 Sch 4 para 9(2)(f).
The Notice to Keeper (NtK) dated 26/06/2025 contains contradictory statutory warnings. One paragraph states that the creditor “will have the right to recover from you, so much of that Parking Charge as remains unpaid” (addressed to the keeper), but the very next paragraph states that the creditor has the right “to recover the Parking Charge amount that remains unpaid from the driver of the vehicle”.
PoFA 2012 Sch 4 para 9(2)(f) requires a single, clear warning that if the creditor does not know the name and a current address for service for the driver by the end of 28 days, the creditor will have the right to recover the unpaid charge from the keeper. A notice which equivocates between recovery from “you” (keeper) and “from the driver” does not strictly comply with para 9(2)(f). Because strict compliance is mandatory for keeper liability, no keeper liability can arise and the appeal must be allowed.
I am the registered keeper and I will not be naming the driver.
2. No delivery of the original NtK – PoFA presumption of delivery rebutted; the NtK was not “given” within 14 days as required by para 9(4)(b).
PoFA Sch 4 para 9(4)(b) requires the NtK to be delivered (given) to the keeper within 14 days beginning with the day after the parking event. I attest that no NtK was received at my address in June/July 2025. The first correspondence I found on returning home mid-August was an overdue letter dated 24/07/2025, followed by 11/08/2025. The operator’s portal could not locate the PCN, preventing an in-time appeal.
After a formal complaint to the operator, a copy of the missing NtK was provided. However, the operator relies on an internal “Unity5 hybrid mail” certificate referring to a “2–3 day delivery” service as their 'evidence' of posting. That document is not independent proof of posting or delivery, does not evidence handover to a postal operator, and on its face indicates a service inconsistent with two-day delivery.
PoFA 9(6) says a Notice to Keeper sent by post is presumed to be delivered two working days after posting—unless the contrary is proved. That phrase is crucial. It means the presumption of delivery is not automatic or absolute. It can be overturned.
To rely on the presumption, the operator must first prove that the notice was actually posted. That means showing independent evidence of:
• the date of posting,
• correct addressing,
• and handover to a postal operator.
If they can’t prove that, the presumption doesn’t apply. And if the motorist provides credible evidence of non-receipt, or shows that the operator’s evidence is weak or inconsistent (e.g. a hybrid mail certificate with no proof of handover or a “2–3 day” service), then the “contrary is proved”.
In this case, the operator’s Unity5 certificate is not proof of posting. It’s a self-generated internal record that shows the notice was queued for hybrid mail—not that it was posted or handed to Royal Mail. It even refers to a “2–3 day” service, which contradicts PoFA’s two-working-day presumption.
Therefore, the presumption of delivery is rebutted. The notice was not “given” as required by PoFA, and keeper liability does not apply.
3. Landowner authority – the operator is put to strict proof.
Strict proof of a valid, contemporaneous contract or lease flowing from the landowner that authorises the operator to manage parking, issue PCNs, and pursue legal action in its own name. I refer the operator and the POPLA assessor to Section 14 of the PPSCoP (Relationship with Landowner), which clearly sets out mandatory minimum requirements that must be evidenced before any parking charge may be issued on controlled land.
In particular, Section 14.1(a)–(j) requires the operator to have in place written confirmation from the landowner which includes:
• the identity of the landowner,
• a boundary map of the land to be managed,
• applicable byelaws,
• the duration and scope of authority granted,
• detailed parking terms and conditions including any specific permissions or exemptions,
• the means of issuing PCNs,
• responsibility for obtaining planning and advertising consents,
• and the operator’s obligations and appeal procedure under the Code.
These requirements are not optional. They are a condition precedent to issuing a PCN and bringing any associated action. Accordingly, I put the operator to strict proof of compliance with the entirety of Section 14 of the PPSCoP. Any document that contains redactions must not obscure the above conditions. The document must also be dated and signed by identifiable persons, with evidence of their authority to act on behalf of the parties to the agreement. The operator must provide an agreement showing clear authorisation (standing) from the landowner for this specific site.
4. Inadequate signage and terms.
From the operator’s own images, the terms are presented in dense, minuscule text with the charge amount buried within a block of wording. The signage fails the requirements of clarity, prominence and legibility that are necessary for a driver to be bound by contract terms, especially for an onerous £100 charge. The operator is put to strict proof of clear entrance signage, legible terms at the point of parking/payment, and contemporaneous photos showing how the signs appeared on 20/06/2025.
Conclusion
For the reasons above, the operator has failed to establish keeper liability and has not proven a valid contract was formed and breached. I request that POPLA allow the appeal.
Respond with the following:
Subject: Formal complaint & appeal – PCN [ref], VRM [VRM]
For the personal attention of the Appeals Manager
Dear RCP Parking Ltd,
Your email is noted. You appear to be under the misapprehension that I am obliged to justify my personal circumstances or enter into a discussion about the driver or payment. Allow me to clarify your position.
I am the registered keeper, not the driver. My correspondence is a formal complaint, which under PPSCoP §11.2 must be treated as an appeal. You are legally required to either cancel the charge or issue a POPLA verification code if you disagree. You are not entitled to interrogate me about matters that are irrelevant to keeper liability under the Protection of Freedoms Act 2012 (Schedule 4).
The question of why or when I contacted you is none of your concern. What matters is that:
1. No Notice to Keeper was ever delivered.
•Your “Unity5 hybrid mail” printout does not prove posting, delivery, or even correct addressing. It refers to a 2–3 day service, inconsistent with first-class post and therefore insufficient to rely on PoFA’s presumption of delivery. •The statutory 14-day delivery requirement in para 9(4)(b) was not met, so keeper liability fails at the first hurdle.
2. Your NtK is not PoFA-compliant anyway.
It contains contradictory warnings — one line referring to recovery from “you”, another referring to recovery “from the driver”. That is not the wording required by para 9(2)(f), which demands a clear warning that recovery will be from the keeper. Non-compliance is fatal.
3. Your debt collector’s involvement is wholly improper.
While this complaint/appeal remains unresolved, continued processing or pursuit by TRACE constitutes a breach of both the PPSCoP and the UK GDPR. The account must be placed on hold immediately.
So, here are your only two options:
1. Cancel the charge forthwith; or
2. Issue a POPLA verification code and confirm the matter is on hold for the statutory 28 days.
Anything else will be treated as a breach of the PPSCoP and reported to the BPA AOS Investigations Team and the DVLA Data Sharing Policy Group.
Yours faithfully
,
[Keeper’s full name]
Registered Keeper of [VRM]
You can send the following formal complaint to RCP at rcp@rcpparking.com and CC yourself:
Subject: Formal complaint – PCN [ref], VRM [VRM], RCP Rochdale Road (20/06/2025)
Dear Sir/Madam,
I am the registered keeper. This is a formal complaint, which the Private Parking Single Code of Practice (PPSCoP) §11.2 requires you to also treat as an appeal. Please place the matter on hold.
1) No delivery of the original NtK – PoFA presumption rebutted (fatal to keeper liability)
Under PoFA 2012 Sch 4 para 9(4)(b) a Notice to Keeper (NtK) must be delivered to the keeper within 14 days of the alleged event. Para 9(5) defines “given” as delivered, and para 9(6) provides a rebuttable presumption that postal delivery occurs on the second working day after posting.
I formally attest that no original NtK was ever received at my address in June/July 2025. The first correspondence found on returning home mid-August was an “overdue” letter dated 24/07/2025, followed by 11/08/2025. Your portal could not locate the PCN, denying any timely appeal.
The “Unity5 hybrid mail certificate” you later supplied is not independent proof of posting or delivery. It merely shows an internal instruction for a “2–3 day” service and does not evidence handover to a postal operator or actual delivery. The “2–3 day” service description itself supports late/failed delivery and therefore assists rebuttal of the para 9(6) presumption.
Accordingly, the statutory requirement that the NtK be delivered within 14 days is not satisfied. Keeper liability cannot arise.
2) Mandatory keeper warning misstated – PoFA 9(2)(f) non-compliance (independent fatality)
Your NtK (dated 26/06/2025) contains conflicting warnings: one paragraph says you may recover “from you”, but another says you may recover “from the driver”. PoFA para 9(2)(f) requires a clear warning that—if the driver is not named—the creditor will have the right to recover the unpaid charge from the keeper. This contradiction is not strict compliance and is independently fatal to keeper liability. I am under no legal obligation to name the driver and I decline to do so.
Outcome required
• Cancel the PCN and confirm in writing; or
• If you disagree, issue a POPLA verification code within 7 days. Under PPSCoP §11.2, this complaint must be treated as an appeal and, if rejected, a POPLA code must be provided.
Please also:
• Recall TRACE and suspend all collection while this complaint/appeal is determined;
• Confirm the case is on hold for at least 28 days;
• If you elect to pursue the driver only, confirm that keeper liability is not asserted and erase my data under UK GDPR Art. 17.
Yours faithfully,
[Keeper’s name]
[Postal address]
[Email]
That hybrid mail receipt is not proof of posting. The “Unity5 Certificate of Postage” is a self-generated record showing that a document was queued for hybrid mail on 26/06/2025 with a 2–3 day service. It is not independent proof that:
• the NtK was actually handed to Royal Mail (or any postal operator) that day;
• the correct full keeper address was used; or
• the item entered a class of post that engages PoFA’s presumption that it was “given” two working days after posting (PoFA Sch 4 para 9(6)).
Courts generally expect something more than a system printout—e.g. a Royal Mail certificate of posting, franking/manifest records, a hybrid-mail audit log evidencing handover to the postal operator (batch ID, acceptance scan), or a witness statement from the mail house exhibiting those business records.
So, this certificate is some evidence of “intended posting”, but it is weak and rebuttable by credible evidence of non-receipt and by pointing out the absence of proof of actual handover and address accuracy.
Can you elaborate on: "I have a couple speculations about what might have happened, but not sure that's helpful or matters."?
Where is the original Notice to Keeper (NtK). Anything but the original is irrelevant and useless for providing advice.
Where is the original NtK? What you have shown us are simply reminders for the original NtK for an alleged contravention on 20/06/2025.
As for Trace or any other useless debt recovery letters, you can safely ignore them. Debt collectors are powerless to do anything except to try and intimidate the low-hanging fruit on the gullible tree to pay up out of ignorance and fear.
For now you can email RCP with the following:
Subject: Request for Copy of Original Notice to Keeper and Proof of Posting
PCN Ref. No.: [PCN reference No.]
VRM: [car reg no.]
Dear Sir/Madam,
I am the registered keeper of vehicle [registration number]. I have recently received correspondence dated 24 July and 11 August 2025 regarding an alleged parking charge, followed by a debt collection letter from TRACE.
I did not receive any original Notice to Keeper for this matter. Please therefore provide me with:
1. A copy of the original Notice to Keeper you allege was issued in respect of this charge.
2. Documentary evidence of the date and method of posting, such as a copy of the Royal Mail certificate of posting or proof of bulk mail posting.
Unless you can provide satisfactory proof of posting, I will deny the presumption of delivery.
For the avoidance of doubt, I will not enter into any discussion with debt recovery agents, who are not a party to any alleged contract. Please ensure all future correspondence is addressed directly to me.
I look forward to your prompt response.
Yours faithfully,
[Full name]
Registered Keeper