Planning narratives: committees see buildings, not compute

Ben Thompson’s Stratechery piece this week on data center opposition landed on a practical truth: the only workable solution is direct community payment. But before any payment structure gets designed, before any public consultation runs, there is a planning committee to win. And planning committees decide on what they can see. Data centers are commercial buildings first. The narrative work is identical to any contested scheme, and planning narratives sit at the center of that work.

What makes planning narratives for data centers different from other schemes?

They are not different. The compute inside the box matters far less to a committee than the jobs beside it, the grid connection behind it, the design facing the high street, and the construction traffic through the village. Planning narratives for data centers follow the same structure as narratives for logistics sheds, life sciences facilities, and car parks everyone hates: you describe the outcome the committee can approve, not the technology they cannot evaluate.

The error most teams make is leading with the infrastructure argument. Sovereign compute, AI workloads, national competitiveness. None of that survives contact with a councillor whose inbox is full of resident complaints about visual impact and road access. The narrative has to ground the scheme in local employment numbers, section 106 contributions, biodiversity net gain, and construction phasing. These are not vague commitments. They are costed, scheduled, and documented in the planning statement.

How do you structure planning narratives when the asset is contested?

Start with the planning policy framework. Identify which local plan policies the scheme complies with, and which require material considerations to outweigh. Most contested schemes fail because the narrative never addresses the conflict directly. If the site is designated employment land but the building height exceeds the local character study, the planning narrative must explain why the employment benefit outweighs the visual harm, with reference to comparable schemes the authority has approved.

Then layer in the specific mitigations. If the grid connection requires substation upgrades, show the infrastructure phasing and who pays for it. If HGV movements during construction exceed the threshold, provide the routing plan and the monitoring strategy. If the building is visible from a conservation area, show the verified views and the landscape buffer. These details belong in the planning statement, the design and access statement, and the committee report. The narrative holds them together.

The National Planning Policy Framework sets the baseline, but local authorities interpret it through their own development plans. A scheme that meets national policy can still fail if it conflicts with neighbourhood plan allocations or local design guides. The narrative bridges that gap.

What role does the digital platform play in a planning process?

For most schemes, the digital platform is a public-facing project page. It consolidates the consultation materials, the planning documents, and the committee timeline. It answers the questions residents and councillors ask before the meeting: what does it look like, how many jobs, when does construction start, where do I send comments. For larger schemes with phased approvals, a bespoke platform can track submissions across multiple applications, show updated visuals as the design evolves, and provide a single URL the planning case officer can reference.

I built a consultation platform last year for a stalled mixed-use scheme with a planning committee date already on the calendar. The client needed a place to host the revised design, the traffic assessment, and the economic impact study. The platform went live on a Monday. The committee met on the Thursday. The approval came through, and the platform became the project site during construction. That is the correct sequence: outcome first, then the tool that supports it.

When should you write planning narratives in-house versus bringing in a studio?

If the planning team has written successful narratives for contested schemes before, and the project is a straightforward allocation with policy compliance, write it in-house. If the scheme is outside policy, if the local opposition is organised, if the committee has refused similar applications recently, or if the decision timeline is tight, bring in someone who writes these narratives regularly. The cost of a refusal is always higher than the cost of the narrative work.

I write planning narratives for schemes where the committee calendar is live and the outcome is uncertain. For data centers, the brief is the same as any other commercial building that people would rather not have next door. The compute is invisible. The jobs, the rates, and the construction phase are not. That is what the narrative addresses.

Most of the work I do is for businesses in and around the built environment: developers, contractors, surveyors, planning consultants, engineers. From Yorkshire, but the planning work crosses authority boundaries. The structure of a planning narrative is the same whether the site is in Leeds, London, or a parish council area with three hundred residents.

If you have a planning submission due and the narrative is not landing yet, send a paragraph on the situation. I will write back, usually same day.