The consultation closes, consent is granted, and the engagement team gets smaller. That's the pattern on a lot of major schemes, and it's usually the wrong way round. The consultation lasted 18 months. The build will last 10 years, and almost everything you promised during the consultation has to be delivered, evidenced and defended during it.
The phase before this one gets most of the attention, and we've written separately about stakeholder engagement on UK infrastructure projects in the run-up to consent. Here's what happens after the consultation closes, and what the teams who handle it well do differently.
Engagement after consent, in short
Once consent is granted, engagement moves from persuasion to delivery. The job becomes discharging the commitments made during consultation, running community liaison through construction, handling complaints as the main inbound channel, and keeping a continuous record that can be produced years later for the regulator, the local planning authority or a court. The audience barely changes. The obligations get sharper.
What changes the day consent is granted
Three things change at once.
The legal footing changes. During consultation you're making a case. After consent you're operating under conditions. On a Development Consent Order those conditions are called requirements, and they're discharged by the relevant local planning authority, often over several years and in phases. Miss one, or fail to evidence that you met it, and you're renegotiating with a regulator instead of building.
The audience changes shape rather than membership. The parish council that objected to your route is now the parish council fielding calls about 6am HGV movements. The MP who wrote to you about visual impact is now writing to you about a resident whose access has been blocked. Same people, different question.
The clock changes. Consultation runs to a published timetable. Delivery runs for as long as the build does, which on a Nationally Significant Infrastructure Project is routinely 10 to 15 years. Over that period, your engagement team turns over two or three times. The record is the only thing that doesn't.
The commitments you now have to discharge
Every consultation generates promises. Some are formal, in the DCO requirements, a section 106 agreement or a code of construction practice. Many are informal, made in a village hall by someone who no longer works for you: we'll keep the footpath open, we'll give you 48 hours' notice before piling, we'll fund the noise survey.
Both kinds get remembered by the community. Only one kind is usually written down properly.
This is the single most common failure we see on long-running schemes. The consultation report records what people said. It rarely records, in a way anyone can query three years later, what was committed in response, who owns it, and whether it's been done.
On the two projects where EDF runs engagement through Tractivity, Hinkley Point C and Sizewell C, close to 30,000 issues and comments have been logged and tagged, with a 100% response rate on stakeholder issues, across 130,000+ engagements and 650+ events. That's not a reporting statistic. It's the reason a query about what was promised to a particular household in a particular year takes minutes rather than an archaeology project.
What to do about it: turn every commitment into a tracked record with an owner, a due date and a status, at the moment it's made, not at the moment someone asks for it.
Community liaison through a 10 to 15 year build
Construction-phase engagement is mostly unglamorous and highly repetitive: liaison group meetings, newsletters to a defined radius, advance notice of works, school visits, road closure notifications, community fund panels.
The difficulty isn't any single activity. It's continuity across a decade of them, usually across multiple contractors and joint venture partners who each hold a piece of the relationship.
The Midland Metro Alliance is a useful example. It's an alliance, not a single organisation: Egis, Tony Gee, Pell Frischmann, Colas Rail, Barhale, Bouygues UK and Auctus, working alongside several local authorities on live tram construction through built-up areas, which is transport engagement at its most exposed. More than 2,500 stakeholder engagements run through one shared system, so a partner joining in year six inherits the history rather than starting a fresh spreadsheet.
That's the actual test of a delivery-phase set-up: can a new contractor, a new comms lead or a new local authority officer see what's already been said to this community, by whom, and what came of it?
Complaints become the main inbound channel
During consultation, feedback arrives because you asked for it. During construction, it arrives because something happened.
Noise, dust, traffic, HGV routing, working hours, vibration, light spill, damage to a wall, a blocked driveway. Complaints are the dominant engagement channel of the delivery phase, and they're the one most often handled outside the engagement system entirely, in a site office inbox or a contractor's own log.
Splitting complaints away from the engagement record causes three problems. You lose the pattern, so 40 separate noise complaints from one street never add up to a visible issue. You lose the person, so a resident who complained twice and attended a liaison meeting looks like three unrelated records. And you lose the evidence, which is the one you'll miss most when the local authority asks you to demonstrate how you responded.
What to do about it: log complaints where the rest of the engagement lives, categorised by issue, phase, source and sentiment, so a cluster shows up as a trend rather than as 40 emails.
Workforce and supply-chain impact is engagement too
Large builds import people. Worker accommodation, park-and-ride sites, shift changes, HGV movements, temporary road layouts and local labour commitments all land on the same communities you consulted, and they generate a distinct engagement workload that rarely appears in the consultation strategy.
It's worth planning for explicitly. The communities most affected by construction logistics are often not the ones most vocal during consultation, because at consultation stage the impact was abstract.
Geographic targeting matters here more than anywhere. Being able to draw a boundary on a map and communicate with everyone inside it, rather than everyone on the project list, is the difference between useful notice and notification fatigue.
The record has to survive scrutiny, and staff turnover
Two audiences will read your engagement record years after it was created.
The first is regulatory. Requirements get discharged in phases, and the evidence you supply for phase four may need to reference engagement carried out in phase one. Ofgem, Ofwat, the Planning Inspectorate and local planning authorities all work this way, which is why energy and utilities teams treat the record as a regulatory asset rather than an archive.
The second is legal. A challenge to a Development Consent Order is brought by judicial review, and under section 118 of the Planning Act 2008 it has to be brought within six weeks of the decision being published. That's the window for challenging the consent itself. What it doesn't cover is everything that follows: decisions taken during delivery, the discharge of requirements, and the handling of consultation commitments, all of which can be challenged on their own terms and all of which rest on the record you kept at the time.
Anglian Water's team works to the same principle across a £10 billion investment programme, coordinating more than 13,000 stakeholders across day-to-day operations and three major programmes including the Cambridge Wastewater Treatment Plant Relocation, an NSIP. Evidence for the regulator is assembled from the live record in minutes, not reconstructed after the request arrives.
A record built for scrutiny has four properties: it's continuous, it's attributed, it's date-stamped, and it doesn't live in anyone's personal inbox.
What a delivery-phase engagement set-up needs to do
Consultation tools are built for a campaign with an end date. Delivery needs something built for a decade, closer to continuous stakeholder tracking than to a consultation platform. In practice, that means:
- One stakeholder record that spans phases and partners, so the same household, business or councillor is one entity from consultation through to handover, whichever organisation is engaging them this year.
- Commitments and issues tracked to closure, with an owner, status and sentiment, not filed as free text in a consultation report.
- Complaints handled as engagement records, categorised and reportable, so patterns surface early.
- Geographic targeting, so notice of works reaches the affected radius rather than the full list.
- A complete communications trail, with emails, meetings, calls, survey responses and event attendance logged against the stakeholder automatically, rather than depending on someone remembering to copy them in.
- Reporting that can be produced on demand, filtered by phase, issue, location or stakeholder group, for the liaison group, the board or the regulator.
Tractivity, the UK stakeholder relationship management platform, is built around exactly this shape of work: a shared stakeholder record that survives project phases and staff changes, issue and commitment tracking with sentiment, enquiry handling for complaints and Freedom of Information requests, and 150+ pre-built reports for the moment somebody asks you to prove it. It's hosted on Microsoft Azure with UK data residency, and carries ISO 27001:2022, Cyber Essentials Plus, NHS DSPT and G-Cloud.
Where teams get caught out
Five patterns come up repeatedly on schemes that hit trouble in delivery:
- The consultation team disbands and the engagement record goes with it, into a shared drive nobody maintains.
- Commitments live in the consultation report rather than in a tracked list, so nobody owns them.
- Complaints sit in a contractor's system, invisible to the client until they escalate.
- Each new phase or partner starts a fresh spreadsheet, and stakeholder history fragments.
- Nobody's responsible for the record itself, only for the activities, so it degrades quietly until it's needed.
None of these are exotic failures. They're all versions of the same one: treating consent as the finish line rather than the halfway point.
The short version
Consultation is where you earn permission. Delivery is where you keep it. The engagement obligations after consent are longer, more operational and more legally exposed than the ones before it, and they run for years after the people who made the promises have moved on. The teams who handle it well aren't doing anything clever. They're keeping one continuous, attributed, queryable record from the first exhibition to the final handover.
If you'd like to see how that works in practice, book a demonstration and we'll walk through it with your own project shape.
FAQ
It doesn't end at consent. Engagement continues through the construction phase and often into operation, covering the discharge of consultation commitments, community liaison, complaints handling and evidence for regulators. On a Nationally Significant Infrastructure Project, that phase routinely runs 10 to 15 years, considerably longer than the consultation that preceded it.
Consultation engagement is about gathering views to shape a proposal, and runs to a published timetable. Construction-phase engagement is about delivering what was promised: advance notice of works, liaison groups, complaints resolution and evidence that commitments have been met. The audience is largely the same, but the obligations become operational and the timescale is far longer.
By tracking each commitment as a record with an owner, a due date and a status from the moment it's made, and linking it to the stakeholder or community it was made to. A consultation report captures what people said. It rarely captures what was promised in response, which is what you'll be asked to evidence during requirement discharge.
Yes. Keeping complaints in a separate site-office log breaks the pattern, the person and the evidence. Logged alongside the rest of the engagement record and categorised by issue, phase, source and sentiment, complaints show up as trends early enough to act on, and the response is already evidenced when a regulator or local authority asks.
Long enough to cover the discharge of every requirement and any challenge to decisions taken during delivery, which in practice means the life of the build and beyond. Requirements are discharged in phases, and evidence for a later phase often needs to reference engagement from a much earlier one, so the record needs to stay continuous and queryable rather than archived per phase.
