1
Civil penalty charge notices (Councils, TFL and so on) / Re: Wandsworth - code 12 parked in residents bay - Ravenna Road SW15
« on: Today at 01:33:41 pm »
Brilliant catch on the GSV history, thank you. I went and checked the historical imagery myself and here is what I found:
• 2020: post bore a "Permit Holders" restriction sign (compliant signage).
• 2025: sign gone, post bare.
• Now (2026): RingGo notice placed on the same post.
• Close-up of the RingGo notice showing the Wandsworth Borough Council logo.
So the post is one that previously formed part of the council's regulatory signage scheme for this bay. The restriction sign was removed or lost between 2020 and 2025 and was never replaced. A RingGo notice was subsequently placed on the same post.
Below is a stripped-down draft of the formal representation. Grateful for any further comments before I submit on 18 July.
Ground: A — The contravention did not occur
Box K (Details):
I am the registered keeper of vehicle PN63XYD. I am making formal representations on the statutory ground that the contravention did not occur.
On 19 May 2026, the vehicle was being driven by my husband, XXX, who parked on Ravenna Road, SW15, alongside a lamp post bearing a RingGo notice (location code 11751), paid for parking via the RingGo app, and left the vehicle.
1. The lamp post adjacent to the bay is part of the Council's regulatory signage scheme
Historical Google Street View imagery of the lamp post immediately adjacent to the parking position (approximately one car length in front of the vehicle, near the T-junction at the end of the street) shows the following:
• 2020: the post bore a compliant "Permit Holders" traffic sign.
• 2025: the sign had been removed or lost. The post was bare.
• At the date of the alleged contravention: the post bore a RingGo notice displaying location code 11751.
Screenshots and photographs of each stage are attached as evidence.
The post is therefore one which the Council itself has historically used as part of the regulatory signage scheme for this bay.
2. The RingGo notice was indistinguishable from official Council signage
The RingGo notice was affixed to a Council-owned lamp post identical in form to those used for traffic signs, was professionally produced, neatly placed, and displayed the Wandsworth Borough Council logo. A close-up photograph is attached showing the Wandsworth logo on the notice.
A reasonable motorist would conclude that the notice was the operative sign for the adjacent bay and that paid parking via the RingGo app was authorised.
3. The Council failed to maintain compliant signage
The Council removed or lost the original "Permit Holders" sign and failed to replace it for several years. It subsequently authorised or condoned the placement of a RingGo notice on the same post. A post which historically communicated a restriction now communicates an apparent authorisation of paid parking.
4. Conclusion
I respectfully submit that the contravention did not occur. The post immediately adjacent to the parking bay historically formed part of the Council's regulatory signage scheme. The Council failed to maintain the original restriction sign for several years and subsequently authorised or condoned the placement of a RingGo notice on the same post. To a reasonable motorist, this notice represented the operative parking arrangement for the adjacent bay.
I request that the Penalty Charge Notice be cancelled.
A couple of questions before I submit:
1. Does the draft above read OK, or is there anything you would change?
2. Is it worth including the point that the boundary sign relied on by the Council is approximately three to four car lengths behind the parking position, not "approximately 1 car length to the rear" as the rejection letter states (and as the Council's own enforcement photograph contradicts)? Or is that better left out at this stage and held back for tribunal if it gets that far?
Thanks again.
• 2020: post bore a "Permit Holders" restriction sign (compliant signage).

• 2025: sign gone, post bare.

• Now (2026): RingGo notice placed on the same post.

• Close-up of the RingGo notice showing the Wandsworth Borough Council logo.

So the post is one that previously formed part of the council's regulatory signage scheme for this bay. The restriction sign was removed or lost between 2020 and 2025 and was never replaced. A RingGo notice was subsequently placed on the same post.
Below is a stripped-down draft of the formal representation. Grateful for any further comments before I submit on 18 July.
Ground: A — The contravention did not occur
Box K (Details):
I am the registered keeper of vehicle PN63XYD. I am making formal representations on the statutory ground that the contravention did not occur.
On 19 May 2026, the vehicle was being driven by my husband, XXX, who parked on Ravenna Road, SW15, alongside a lamp post bearing a RingGo notice (location code 11751), paid for parking via the RingGo app, and left the vehicle.
1. The lamp post adjacent to the bay is part of the Council's regulatory signage scheme
Historical Google Street View imagery of the lamp post immediately adjacent to the parking position (approximately one car length in front of the vehicle, near the T-junction at the end of the street) shows the following:
• 2020: the post bore a compliant "Permit Holders" traffic sign.
• 2025: the sign had been removed or lost. The post was bare.
• At the date of the alleged contravention: the post bore a RingGo notice displaying location code 11751.
Screenshots and photographs of each stage are attached as evidence.
The post is therefore one which the Council itself has historically used as part of the regulatory signage scheme for this bay.
2. The RingGo notice was indistinguishable from official Council signage
The RingGo notice was affixed to a Council-owned lamp post identical in form to those used for traffic signs, was professionally produced, neatly placed, and displayed the Wandsworth Borough Council logo. A close-up photograph is attached showing the Wandsworth logo on the notice.
A reasonable motorist would conclude that the notice was the operative sign for the adjacent bay and that paid parking via the RingGo app was authorised.
3. The Council failed to maintain compliant signage
The Council removed or lost the original "Permit Holders" sign and failed to replace it for several years. It subsequently authorised or condoned the placement of a RingGo notice on the same post. A post which historically communicated a restriction now communicates an apparent authorisation of paid parking.
4. Conclusion
I respectfully submit that the contravention did not occur. The post immediately adjacent to the parking bay historically formed part of the Council's regulatory signage scheme. The Council failed to maintain the original restriction sign for several years and subsequently authorised or condoned the placement of a RingGo notice on the same post. To a reasonable motorist, this notice represented the operative parking arrangement for the adjacent bay.
I request that the Penalty Charge Notice be cancelled.
A couple of questions before I submit:
1. Does the draft above read OK, or is there anything you would change?
2. Is it worth including the point that the boundary sign relied on by the Council is approximately three to four car lengths behind the parking position, not "approximately 1 car length to the rear" as the rejection letter states (and as the Council's own enforcement photograph contradicts)? Or is that better left out at this stage and held back for tribunal if it gets that far?
Thanks again.







