Your Project Will Not Be Killed by Engineering. It Will Be Killed by the Community.

Your Project Will Not Be Killed by Engineering. It Will Be Killed by the Community.

Large capital projects are scrutinised to an extraordinary degree on the dimensions that are easy to model. Grid connection, water availability, planning envelope, cost of capital, construction sequencing: all of it gets a spreadsheet, a sensitivity analysis and a risk register entry with an owner.

Then the project is stopped by a petition, a council vote, a moratorium or a judicial review, and the post-mortem discovers that the thing which actually killed it had no owner, no score and no line in the register. Community acceptance is treated as a communications activity that begins after the decision, rather than a risk that could have been assessed before it.

Why This Risk Is Getting Worse

Three things have changed for energy, data-centre and heavy infrastructure development in Europe and beyond.

Opposition organises faster than approval does. A local group can reach several thousand signatures in a fortnight using tools that cost nothing, while the corresponding permitting process moves on a timescale of quarters. The asymmetry in tempo is new, and it is structural rather than cyclical.

Resource visibility has increased. Water consumption and grid draw that were once technical annexes are now front-page local issues, and a project's demand figures are routinely compared with the host municipality's entire consumption. That comparison is easy to make, hard to rebut, and extremely effective.

Precedent travels. A community facing a proposal now arrives at the first public meeting already briefed on how a comparable project was fought elsewhere, including which arguments worked. Developers, by contrast, often arrive without having systematically studied the same precedents.

What Gets Measured Instead

Ask most development teams to characterise community risk on a site and the answer comes back as an adjective. Local opposition is moderate. Sentiment is mixed. The council is broadly supportive.

These statements cannot be acted on, compared between sites or falsified. "Moderate" is not a finding; it is a placeholder for the absence of one. Compare it with a statement that carries an actual claim: a petition passing several thousand signatures inside a month, a council with a documented record of refusing comparable proposals, a projected water draw that exceeds what the host municipality itself consumes at peak. Each of those can be checked, argued with and mitigated. The adjective cannot.

Two Disciplines That Make an Assessment Usable

Assessment systems that survive contact with a sceptical development committee share two properties. Both sound pedantic and both are the reason the output gets used rather than filed.

Where the Model Belongs, and Where Arithmetic Does

The same division of labour that makes executive decision tooling credible applies here, for the same reason: the output is going to be used to argue against a large capital commitment, so it has to withstand a hostile read.

Language models are well suited to reading messy local reality: municipal minutes in three languages, regional press, planning documents, campaign material, transcripts of public meetings. That is genuine unstructured-text work and it is where the leverage is.

Aggregation is not a model task. Once sub-indicators are scored against anchored definitions, combining them into a dimension score and a headline number should be deterministic arithmetic. If a model performs the aggregation, two things follow: the number is not reproducible, and it cannot be calibrated against outcomes you already know. Both are fatal in a procurement conversation.

The scoring anchors matter as much as the arithmetic. A "seven on water" has to mean the same thing on every site, which means the scale needs to be defined against real reference cases rather than left to interpretation. This is the same argument we make about deterministic detectors in what AI-native actually changes in your operating model: put the model where judgement about text is needed, and keep it away from anything that produces a number someone will quote in a board paper.

The Score Is Not the Product

A risk score by itself changes nothing. It tells a development team that a site is difficult, which the local team frequently knew already, and provides no route forward. Used badly it becomes a reason to abandon sites rather than a means of derisking them.

The useful version pairs the assessment with the work that moves it: which commitments actually reduce which dimensions, by how much, and under what conditions. A global corporate pledge applied to a specific municipality should not count for the same as a locally audited commitment, because communities do not treat those as equivalent and neither should the model.

That produces a defensible sequence: this is where you stand today, this is where the commitments you have already made take you, this is where a structured engagement programme could take you. The gap between the first and the last is the actual business case, and it is a far stronger internal argument than a number on its own.

Why This Cannot Be Bought Off the Shelf

Every element of this is specific. The regulatory environment is national. The pattern of local opposition is regional. The reference cases that anchor the scoring are sector-specific, and the weighting between dimensions depends on the technology being deployed and where.

More practically, the people who hold the necessary judgement are usually development and permitting staff who have never worked on a data model and have no interest in doing so. Extracting what they know and encoding it into something mechanical is not a requirements-gathering exercise that can be conducted over three workshops. It requires someone sitting with the team, building against real sites, being wrong in the first iterations and correcting.

The practical test of whether the resulting system is any good is whether the domain experts can change it without engineering involvement. If updating a weight or an anchor requires a development ticket, the model has become an implementation detail and it will decay. If the scoring model is a configuration file that the permitting lead can revise directly, it stays alive. That is a design decision made early by someone embedded closely enough to know it matters, which is the point we make more generally in how to buy AI delivery that actually ships.

Where to Start

Frequently Asked Questions

Isn't this just sentiment analysis?

No, and the distinction is the whole point. Sentiment analysis produces a mood reading from text volume. What is described here is a scored assessment against defined dimensions, where each score traces to specific evidence and each piece of evidence carries a confidence grade. Sentiment tells you the temperature; this tells you which specific factors are driving it and which commitments move them.

Our development team already knows the local situation. What does this add?

Comparability and durability, mainly. Individual site knowledge is usually good and rarely transferable, which means it cannot be used to rank a pipeline, does not survive staff turnover, and is difficult to present to an investment committee. A consistent scale lets you compare fifteen sites on the same basis and defend the ranking.

What if the assessment says a site is high risk and the business wants to proceed anyway?

Then it has done its job. The purpose is not to veto sites but to price them accurately and to identify what would have to be true to proceed safely. A project that goes ahead with an explicit understanding of its exposure and a funded engagement programme is in a substantially better position than one that proceeds without either.

How current does this need to be?

Current enough to reflect events. A public meeting, a disclosure or a council vote can move the position materially, so the assessment should be re-run against events rather than on a fixed quarterly cycle. A risk picture that is six months stale on a live opposition campaign is worse than none, because it carries unearned authority.

Does this apply outside data centres and energy?

The pattern applies wherever a project needs local consent that is not guaranteed by a permit: waste and water infrastructure, transmission, mining, large logistics, and increasingly industrial siting generally. The dimensions and weights change considerably by sector. The discipline of evidence-backed claims and graded confidence does not.

Sources & References