Planning committees want outcomes, not engineering specs

Planning committees are blocking data centre conversions across the UK, not because the objections are irrational, but because the narrative arrives wrong. Technical specifications first, community outcomes nowhere. I see the same pattern when developers present projects that require local authority consent: rack specifications, cooling diagrams, megawatt capacity. Nothing about the GP surgery lease, the footpath lighting, or the apprenticeships starting in September. The planning committee presentation determines whether the project moves or stalls.

Why do planning committees reject data centre applications?

Most applications arrive built for engineers, not elected members weighing voter sentiment before Thursday’s vote. Ben Thompson’s recent Stratechery analysis on data centre opposition identifies the core tension: communities bear the visual and infrastructure load while the economic benefit disperses elsewhere. The planning committee presentation rarely addresses that imbalance, because the team preparing it optimised for technical compliance, not political consent.

The same dynamic appears in mixed-use redevelopment, office-to-residential conversion, and any project where the local authority holds veto power under the Town and Country Planning Act 1990. The developer commissions the technical reports, satisfies the policy tests, then watches the committee defer or refuse on grounds that never appeared in the brief. Residents packed the gallery. The ward councillor spoke for twelve minutes. The highways objection became the vehicle for a broader discomfort no one had thought to address in advance.

What should a planning committee presentation actually contain?

Outcomes the committee can defend to their constituents. Start with what changes for the people who live there: section 106 commitments quantified and staged, construction employment broken down by postcode, operational jobs with salary bands and local hiring requirements, grid capacity improvements that benefit surrounding industrial occupiers, and the site maintenance programme that removes the existing eyesore everyone has complained about since 2019.

Then explain the facility in terms a planning committee member can repeat at the weekend farmers’ market without sounding like a data sheet. Not server density per square metre. The facility that keeps the NHS booking system running when demand spikes, the infrastructure behind the supply chain software that employs 400 people at the business park two miles north, the reason the insurance company can keep its regional office here instead of consolidating to Birmingham.

The technical appendix still goes in. It satisfies the planning officer’s report and provides the defensibility the council’s legal team needs if the decision gets challenged. But the planning committee presentation itself should be built for elected members who will be asked about this decision at the school gate, at the pub, and at the next ward surgery.

How do you structure the narrative before the committee meets?

Pre-application engagement, properly done. Not the statutory minimum consultation required under the National Planning Policy Framework. Conversations with the ward members before the application lands, so they are not hearing about the project for the first time in a planning committee packet the night before the meeting. A public event where the concerns get surfaced and the design response gets documented, so the planning officer’s report can reference specific adjustments made in response to local feedback.

Most developers treat this as a compliance exercise, outsourced to the planning consultant who runs a poorly attended drop-in session at the community centre on a Tuesday afternoon. Then they are surprised when the committee refuses permission because 140 objection letters arrived and no one built a countervailing coalition. The developer who wins puts a senior person in the room, brings the architect who can sketch adjustments in real time, and builds relationships before the application goes live.

When does the digital platform come in?

After the narrative is right, when the stakeholder base is large enough that email threads and PDF updates stop working. I build platforms for project teams managing developments with planning risk: a timeline the council can check without ringing the project manager, a reporting layer that auto-generates the section 106 monitoring reports the legal agreement requires, a resident portal that answers the question about construction hours before it becomes a complaint to the ward councillor.

For developers with multiple projects at different planning stages, a CMS that the team can update when the committee date shifts, when the design changes, or when the landscaping contractor gets appointed. The operations associate who updates it does not need to know what a Git commit is. The platform serves the outcome, which is consent secured and relationships maintained through delivery.

If you have a project facing planning committee, a stalled application that needs reframing, or a portfolio where public consent sits on the critical path, send a paragraph to hello@goldspink.co and I will write back.