Data centre development: building dialogue with local communities

Start with local questions

Before choosing a slogan, identify the public concerned and their questions: residents, elected officials, competent services, network operators, neighbouring companies and associations. Their expectations are not limited to being informed of a decision already finalised.

The method of portfolio company must correspond to the stage of the project and the applicable obligations. The CNDP resources provide methodological benchmarks; they do not mean that any project is automatically subject to the same procedure. The framework must be checked with the relevant functions.

Explain energy use with precise indicators

The proposed power, annual consumption, load profile and connection conditions answer different questions. Comparisons must specify their units, assumptions and horizon. A supply commitment alone does not describe all local effects.

The IEA's Energy and AI report places the energy challenges of data centres on a global scale. It cannot be used as a direct proof of the performance of a particular project. Local data should be documented separately and updated at the pace of studies.

Address water, employment and local impacts

Water needs depend in particular on design, cooling and operating conditions; construction jobs, permanent jobs and indirect effects should not be added without distinction; noise, traffic and land also deserve concrete answers.

A fact sheet of evidence must indicate for each data its source, scope, degree of maturity and the person responsible for its validation. When a study is in progress, tell what it needs to shed light on and when an update is expected, without prematurely announcing its findings.

Make room for dialogue that informs the project

Specify what is decided, what remains open for discussion and how contributions will be processed. Exchanges can involve meetings, drop-in sessions, visits, accessible documents and digital channels. An exclusively online process may leave a part of the audience out.

Restitution is essential: what questions have been asked, what answers have been made, what choices have changed and why have some requests not been accepted? Dialogue does not promise consensus; it makes decisions more explicable and disagreements more precise.

Prepare project leaders and local teams

The project leaders must share the same set of facts. Spokespersons must be able to recognise a technical limit or an unanswered question. Dialogue teams need a reliable circuit to get information, not just an argumentary.

National communication can present an industrial ambition; local communication must respond to the consequences of implantation. Both must remain compatible, including when a calendar, power or technical option changes.

An illustrative scenario and deliverables

A project leader prepares a file distinguishing estimated needs, firm commitments and ongoing studies. A public register of questions documents the answers and changes in version. This scenario does not describe a project accompanied by Belief System.

Useful deliverables include a mapping of stakeholders, a verifiable data sheet, a decision note, a dialogue mechanism and a registry of commitments. The follow-up focuses on the quality of responses, unresolved questions and project developments, rather than an abstract promise of acceptability.

Frequently asked questions