Three Friar Park Approvals. Three Warning Signs. One Planning Culture Problem.
Let’s get one thing straight from the start.
Friar Park Urban Village (FPUV) has not yet had its main planning application submitted.
So this article is not about attacking an application that does not yet formally exist.
It is about something arguably more important:
👉 the pattern already visible in three separate approved applications in the same Friar Park area:
- DC/25/70154
- DC/24/69650
- DC/23/68742
Taken together, these approvals raise serious questions about:
- planning standards
- evidence gaps
- governance
- policy compliance
- transparency
- and whether the council is drifting into habits that bear the hallmarks of maladministration
Not proven maladministration, no.
But enough red flags to justify asking the question loudly.
And repeatedly.
This is not one bad application. It is a pattern.
Any one planning application can be messy.
Any one officer report can be debatable.
Any one set of conditions can be argued over.
But when you start seeing the same defects across multiple applications in the same area, the issue stops being “an error” and starts becoming a culture.
That is where Friar Park now sits.
Across these three applications, the same themes keep appearing:
- incomplete evidence at determination stage
- major issues kicked into planning conditions
- weak or missing cumulative assessment
- strange absence of recorded internal debate
- “NIL” FOI responses that do not sit comfortably with the documents actually disclosed
- and repeated signs that difficult matters are being parked for later rather than resolved before permission is granted
In other words:
approve first, sort it later, and record as little as possible.
DC/25/70154 — approved with gaps still live
This application is one of the clearest examples of the problem.
The council’s own disclosed material shows that noise concerns were still being actively queried before determination.
Calculations were challenged.
Clarification was requested.
Further information was sought.
An extension of time was needed to resolve outstanding issues.
That is not a clean, settled evidence base. That is an application with live technical uncertainty.
The biodiversity position was no better.
The ecology side effectively accepted that proper Biodiversity Net Gain detail was not in place at the point it should have been, and that key matters could simply be dealt with later through standard post-permission conditions.
So let’s be honest about what that means.
It means permission was being advanced while important ecological detail was still incomplete.
And yet when asked through FOI for records about:
- unresolved issues,
- concerns,
- risk,
- or the appropriateness of relying on conditions,
the council’s answer was largely:
NIL.
Apparently nobody was worried.
Nobody debated anything.
Nobody recorded any reservations.
Except the disclosed emails show that they clearly did.
That is not a minor inconsistency.
That is a governance problem.
DC/24/69650 — where the documents start telling a very different story
If 70154 is troubling, 69650 is positively instructive.
Because here the disclosed material begins to show how the sausage is made.
There were active discussions with the developer.
There were highways concerns.
There were layout issues.
There were SuDS constraints.
There were clear tensions between technical acceptability and maximising housing numbers.
In one strand, drainage choices were plainly being influenced by the desire not to lose plots.
In another, highways raised concerns over access standards, layout and future connectivity.
There were even internal comments suggesting that what was being counted toward biodiversity gain looked less like a thoughtful ecological solution and more like a left-over bit of land likely to become scrub and ASB territory.
That is not a model of robust planning.
That is a model of squeezing a scheme through.
And once again, when FOI requests asked for the internal risk thinking, balancing exercises, and recorded reasoning behind accepting these compromises?
The answer came back neat, sanitised and suspiciously empty.
NIL. NIL. NIL.
Only this time, the disclosed documents themselves show that is at best incomplete and at worst deeply misleading.
DC/23/68742 — the incredible vanishing paper trail
Then we come to 68742, the application where the council’s response was so devoid of internal record that it almost made the case on its own.
Planning? Nil.
Public Health? Nil.
Highways? Nil.
Environmental Protection? Nil.
Flood Risk? Nil.
Balancing exercise? Nil.
Why conditions instead of refusal? Nil.
For a development in this location, with this context, those responses are simply not credible.
And yet, in the same breath, the council still pointed to technical assessments and consultation responses that had evidently been received and considered.
So which is it?
Were there no internal records of any kind?
Or were the searches inadequate, the interpretation narrow, or the disclosure incomplete?
Because both positions cannot be true at once.
You cannot claim there was effectively no internal decision trail while also relying on technical consultation responses to justify the decision.
That is the kind of contradiction that should make every councillor, auditor and monitoring officer sit bolt upright.
The real issue: planning by condition, not by evidence
The most consistent theme across all three applications is not contamination alone, or noise alone, or BNG alone.
It is this:
key issues are not being fully resolved before approval.
Instead, there is repeated reliance on conditions to:
- investigate later,
- mitigate later,
- clarify later,
- submit proper detail later,
- and somehow clean up the evidential mess later.
Conditions are not unlawful. Of course they are not.
But they are not supposed to become a substitute for proper front-loaded planning judgment.
A planning authority should be able to explain:
- why the issue was safe to defer,
- why refusal was not justified,
- why the remaining uncertainty was acceptable,
- and how the decision still complied with policy despite those gaps.
That is exactly the kind of reasoning your FOIs have gone looking for.
And again and again, the answer has been a bureaucratic shrug.
No logs.
No drafts.
No concerns.
No debate.
No rationale.
For three separate applications.
At some point the absence of records becomes a record in itself.
Where are the cumulative assessments?
Another huge red flag is the lack of meaningful cumulative thinking.
These applications sit in the same broad Friar Park area.
They are not isolated islands.
They interact with the same strained transport corridors, the same air quality pressures, the same broader growth context, the same school-place problem, and the same nearby communities.
Yet the evidence trail for cumulative assessment appears painfully weak.
That matters because planning is not just about asking:
“Can this one scheme scrape through on paper?”
It is also about asking:
“What happens when these schemes are layered on top of each other in the real world?”
That question seems to have gone missing far too often.
Why this starts to look like maladministration
Let’s use careful language.
I am not saying maladministration has been formally proven.
That is for the appropriate body to determine.
But I am saying this:
These applications display traits consistent with possible maladministration, including:
- inadequate record-keeping
- inconsistent FOI responses
- failure to disclose obvious internal reasoning
- repeated reliance on conditions without visible justification
- fragmented rather than integrated assessment
- weak evidence of cumulative consideration
- and a planning culture that appears more focused on getting to “yes” than on evidencing why “yes” was safe, lawful and rational
That is not a throwaway criticism.
That is a serious governance warning.
And this matters before the FPUV application arrives
This is why these three applications matter so much.
Because the main FPUV application has not yet been submitted.
These applications are, in effect, the warning lights on the dashboard before the main engine failure.
If this is how smaller or linked applications in the same area are being handled now, what confidence should anyone have that the big one will suddenly be treated with immaculate rigour, pristine transparency and saintly caution?
Exactly.
Final word
The lesson from DC/25/70154, DC/24/69650 and DC/23/68742 is not simply that residents disagree with development.
It is that there is now a serious, evidence-backed basis for questioning how Sandwell is making planning decisions in the Friar Park area at all.
Three approvals.
Three sets of red flags.
Three signs of the same deeper problem.
And if nobody addresses that problem before the main FPUV application lands, then whatever comes next will not just be a planning application.
It will be the next chapter in a governance failure that everybody could already see coming.
#FriarPark #Sandwell #Planning #FOI #Governance #DC2570154 #DC2469650 #DC2368742 #ContaminatedLand #BNG #Noise #Highways #Wednesbury #LocalGovernment #Transparency
