[Home] [Databases] [World Law] [Multidatabase Search] [Help] [Feedback] | ||
England and Wales High Court (Administrative Court) Decisions |
||
You are here: BAILII >> Databases >> England and Wales High Court (Administrative Court) Decisions >> Braithwaite & Anor, R (On the Application Of) v East Suffolk Council [2022] EWHC 691 (Admin) (28 March 2022) URL: http://www.bailii.org/ew/cases/EWHC/Admin/2022/691.html Cite as: [2022] EWHC 691 (Admin) |
[New search] [Printable PDF version] [Help]
QUEEN'S BENCH DIVISION
PLANNING COURT
Strand, London, WC2A 2LL |
||
B e f o r e :
____________________
THE QUEEN on the application of (1) GEORGE BRAITHWAITE (2) MELTON MEADOWS PROPERTIES LIMITED |
Claimants |
|
- and - |
||
EAST SUFFOLK COUNCIL |
Defendant |
____________________
Harriet Townsend (instructed by legal and Democratic Services) for the Defendant
Hearing date: 17 March 2022
____________________
Crown Copyright ©
Mrs Justice Lang :
"The grounds for the claim first arose when the 2020 liability notice was issued and served. This claim is therefore late and no proper grounds have been given for the delay.
If I had been of the view that the grounds first arose in September 2021, I would not have refused permission on this basis.
The remaining points raised in the amended SGD need not be considered at this stage."
Facts
"2…in the recent High Court Judgement of Trent v Hertsmere BC [sic] it was ruled that it is of fundamental importance that the recipient of the LN be addressed by name on the LN for it to be valid. In this case, the name on the LN is Melton Meadows Properties Ltd. The fact that the appellant is a director of that company, does not satisfy the service requirement as he specifically needed to be named on the LN as the 'relevant person'. The appellant having knowledge of the LN by other means, does not act as a substitute for it actually being served on him.
3. The Council point out that a LN was served on Melton Meadows Properties Ltd as nobody had assumed liability, so liability defaulted to the registered landowners in accordance with Regulation 33. However, while it was correct for a LN to be served on Melton Meadows Properties Ltd as the registered landowners, a LN was still required to be served on the appellant as the 'relevant person' in accordance with Regulation 65(3)(a).
4. With regards to the appellants [sic] assertion concerning the timing of the issue of the LN, as mentioned above, Regulation 65(1) explains that the Council must issue a LN as soon as practicable after the day on which planning permission first permits. In this case, a LN was not submitted for some 16 months after planning permission was granted. The Council explain that the reason for this delay was due to trying to establish when work had commenced, and on which planning permission, as they had not received a Commencement Notice (CN). However, a LN is required to be served before the recipient is required to submit a CN. As the appellant points out, the LN acts as the trigger for this to happen. It is also not possible to submit a valid CN before service of a LN as the CN requires the LN to be identified. The Council argue that the appellant would have been aware of the need to submit a CN from a previous LN and Assumption of Liability Notice in relation to original planning permission DC/17/1884/FUL. Again, the appellant having knowledge by other means does not act as a substitute for the required notice.
5. I consider that 16 months cannot reasonably be interpreted as meeting the requirement of Regulation 65(1). As the Council withdrew the instalment plan and imposed the late payment surcharge as a result of the appellant's failure to submit a CN, it follows that this was not appropriate in the circumstances of this case.
6. In view of the above, I conclude that a LN was not correctly served and consequently the alleged breach that led to the surcharge did not occur. Therefore, I have no option but to allow the appeal…."
Grounds of challenge
Submissions
"Where a collecting authority issues a liability notice any earlier liability notice issued by it in respect of the same chargeable development ceases to have effect."
R(Trent) v Hertsmere BC
"(a) A decision or action is in general to be treated as valid until struck down by a court of competent jurisdiction….
(b) Statutory words requiring things to be done as a condition of making a decision, especially when the form of words requires that something "shall" be done, raise an inference that the requirement is "mandatory" or "imperative" and therefore that failure to do the required act renders the decision unlawful.
(c) The above inference does not arise when the statutory context indicates that the failure to do the required act is of insufficient importance, in the circumstances of the particular decision, to render the decision unlawful.
(d) The courts, in appropriate cases and on accepted grounds may, in their discretion refuse to strike down a decision or action or to award any other remedy…."
"Delay
89. The Council submitted that it was too late for the Claimant to challenge the lawfulness of the 2019 liability notice, as the claim for judicial review was filed on 2 June 2020, long after the 3 month time period for bringing a claim for judicial review had expired. I do not accept this submission. Upon receiving the liability notice, on 3 September 2019, the Claimant acted properly in pursuing her alternative statutory remedies by appealing to the Secretary of State for Housing, Communities and Local Government. When the Inspector issued his appeal decision on 12 March 2020, she reasonably assumed that the Council would accept the wider implications of the Inspector's decision that the 2017 and 2019 liability notices were invalid, and not pursue its application for CIL. So she was understandably shocked to receive the 2020 demand notice, dated 21 April 2020. She acted properly in trying to resolve the matter with the Council in pre-action correspondence before filing her claim on 2 June 2020, which was well within 3 months of the date of the 2020 demand notice.
The effect of the Inspector's decision
90. The Claimant submitted that, following the Inspector's decision in the regulation 117 appeal that no valid liability notice had been issued and served on her, it was not open to the Council to issue and serve the 2020 demand notice. Alternatively it was improper and/or irrational and/or unfair and unreasonable to do so.
91. The Council submitted that the Inspector's decision on the liability notices was limited to the surcharge appeal under regulation 117(1)(a) and (b), and therefore his finding that no valid liability notice had been served on the Claimant had no wider effect. Under regulation 117, the Inspector had no power to quash the 2019 liability notice, and he did not purport to do so. In the appeal under regulation 118, where he exercised his power to quash the 2019 demand notice, he said "[i]f the Council are to continue to pursue the CIL they must now issue a revised Demand Notice" (DL5) which indicated that he did not consider that his findings under the regulation 117 appeal precluded issue of a further demand notice. So, despite the Inspector's findings, the 2019 liability notice remained in force and could be relied upon by the Council in order to issue and serve the 2020 demand notice.
92. I agree that the Inspector's jurisdiction was limited to the surcharge appeals under the terms of regulation 117. However, I would expect a responsible authority to have regard to the Inspector's findings when deciding upon its next steps. The Inspector had no power to quash the 2019 liability notice and he did not purport to do so. Applying the well-known principle in Smith v East Elloe DC [1956] AC 736 (which was applied to enforcement notices in Koumis v Secretary of State for Communities and Local Government 2014] EWCA Civ 1723, per Sullivan LJ at [87]), the 2019 liability notice was to be treated as valid until quashed, and so a valid liability notice was in existence when the 2020 demand notice was issued. However, in this claim for judicial review, the Court has exercised its jurisdiction to declare that the 2019 liability notice was invalid from the date of issue, and should be quashed, with the effect that there was no valid liability notice in existence when the 2020 demand notice was issued.
93. The Inspector exercised his powers under regulation 118(6) to quash the demand notice, and in doing so, he said that, if the Council intended to pursue the CIL, a revised demand notice would have to be issued (DL5). On my reading of the decision, the Inspector was doing no more than stating, in the standard words used in successful regulation 118 appeals (probably from a template), that the Council would need to issue a fresh demand notice if it wished to claim CIL from the Claimant. I do not consider that he was advising the Council to take that course, as was suggested in oral submissions by the Council. Nor was the Inspector addressing his mind to any potential wider implications of his findings in respect of the liability notices – that was not his task, and it would have been outside the scope of his jurisdiction."
Conclusions