Good community engagement on an infrastructure project means engaging the right people early, giving them something real to respond to, recording every interaction as you go, and being able to show a planning inspector exactly who you engaged, when, how, and what changed as a result. On a Nationally Significant Infrastructure Project (NSIP), that record is the difference between a consent that holds and one that's open to challenge.
Consultation reviews expose a consistent pattern in where teams come unstuck. It's rarely the engagement itself. It's the moment, months later, when someone asks 'can you evidence that?' and the answer lives in three spreadsheets, an inbox and someone's memory.
This guide sets out what good looks like in 2026 and how the teams getting it right are working.
What are best practices for community engagement in infrastructure projects?
The best practices are consistent across sectors: engage early and before decisions are fixed, map every affected community and interest group, make consultation materials genuinely accessible, respond to what you hear, and keep a single, date-stamped record of the whole programme. Get those five right, and both the relationship and the audit trail take care of themselves.
Breaking that down:
-
Engage before the design is locked. The Gunning Principles, the legal benchmark for fair consultation in the UK, require that consultation happens 'at a formative stage', that you give enough information for considered responses, that you allow adequate time, and that you conscientiously take responses into account. Engagement that starts after the decisions are made fails the first test, and it's the most common ground for challenge.
-
Map the whole community, not just the loudest voices. Affected residents, landowners, parish and community councils, MPs and councillors, statutory consultees, environmental and amenity groups, businesses, and seldom-heard groups all have standing. A stakeholder map that misses a group is a gap someone else will find for you.
-
Make it easy to take part. Accessible formats, plain-English materials, a mix of in-person and online channels, and Welsh language provision where it applies. The point is a representative response, not just a large one.
-
Close the loop. Show people what you heard and what you did with it. 'You said, we did' is not a slogan; it's evidence that you took responses into account, which is exactly what an inspector looks for.
-
Keep one record of everything. Every email, meeting, event, survey response and feedback comment logged against the stakeholder it relates to, as it happens. Reconstructing a consultation record after the fact is where projects lose weeks and expose gaps.
How should an organisation approach community engagement for a nationally significant project?
For an NSIP, treat the engagement record as evidence from day one. Development Consent Order (DCO) consultation is governed by the Planning Act 2008 and examined by the Planning Inspectorate, so every stage of pre-application consultation has to be planned, delivered and evidenced to a standard that will stand up at examination. The organisations that do this well build the audit trail into the daily work rather than assembling it at the end.
In practice, that means a few things beyond the general best practice above.
Run day-to-day and project-specific engagement in the same system. On a major programme, the same MP, councillor or community group turns up across multiple workstreams, often engaged by different teams. Anglian Water coordinates engagement with more than 13,000 stakeholders across day-to-day operations and major capital projects, including the Cambridge Wastewater Treatment Plant Relocation, an NSIP, from one platform. That shared view is what stops a stakeholder from receiving three uncoordinated approaches and stops a team from missing something a colleague already knew.
Keep political stakeholder data live. Positions shift, and so do the people holding office. Anglian Water keeps MP and councillor data current through a nightly Mapolitical feed inside Tractivity, so when a regulatory or political question lands, the engagement can go out the same day rather than waiting on a manual data refresh.
Build the evidence base so it's queryable in minutes. EDF's consultation programme for Hinkley Point C and Sizewell C logged and tagged around 30,000 stakeholder issues at a 100% response rate, with 650+ events evidenced. At that volume, the only way to answer 'show me every issue raised about traffic, and how we responded' at examination is a structured, tagged record built as you go.
Plan for handover. Consent isn't the end. The operations or business-as-usual team inherits the relationships and the record, and a clean hand-over depends on that record living somewhere durable, not in the outgoing project manager's files.
Why the engagement record matters more than the engagement
Here's the uncomfortable part. You can run a textbook consultation and still be exposed if you can't evidence it. Communication failure is one of the biggest risks on any major programme: PwC research has found that 57% of projects fail due to a breakdown in communications. And the fallback tool, the spreadsheet, quietly makes it worse: a University of Hawaii study found that 94% of spreadsheets contain errors, with a mistake in roughly one in every 20 cells. A consultation record that can be edited without trace is not a record an inspector, an FOI request or a judicial review will treat kindly.
This is why more infrastructure teams are moving off spreadsheets and general CRMs and onto purpose-built stakeholder relationship management. Tractivity, the UK stakeholder relationship management (SRM) platform, exists for exactly this job. A CRM tracks pipeline and revenue. An infrastructure consultation needs to track relationships, sentiment, issues and commitments, and prove it did so. Different job, different tool.
What good looks like across the sector
The pattern holds across infrastructure. National Grid runs a phased deployment with 430+ users, built around a shared stakeholder view rather than individual usage. The Midland Metro Alliance coordinates multiple alliance partners and local authorities through a single instance, so no partner works from a different version of the truth. Transport for the South East reports spending 'less than a quarter of the time' on stakeholder management compared with spreadsheets, and needed software that integrated with their county council's secure IT environment.
The common thread isn't a methodology. It's a single coordinated record that every team, consultant and partner works from and that holds up when scrutinised.
A practical checklist for infrastructure engagement
If you're setting up or reviewing a programme, work through these questions:
-
Have you engaged before the design is fixed, in line with the Gunning Principles?
-
Is your stakeholder map complete, including seldom-heard and statutory groups?
-
Are materials accessible, in plain English, and available in the formats and languages your community needs?
-
Is every interaction logged against the right stakeholder as it happens, not reconstructed later?
-
Can you produce a 'you said, we did' account of how responses shaped the scheme
-
Could you evidence the whole programme, filtered by issue or group, for examination tomorrow?
-
Is the record durable enough to survive staff turnover and hand over cleanly post-consent?
If the answer to the last three is 'not easily', the engagement isn't the problem. The system holding it is.
Make your engagement record examination-ready
Tractivity gives infrastructure teams one audit-ready record of every stakeholder, interaction and commitment, ready to be evidenced at examination.
Book a personalised demo with the team to see how it would work on your programme.
Frequently asked questions
