How to Report Stakeholder Engagement Outcomes to Regulators

Most organisations know they need to engage their stakeholders, and yet, fewer know how to prove it.

Regulatory reporting is where that gap becomes expensive. Ofwat, Ofgem, and the Environment Agency do not want a summary of your good intentions. They want structured, traceable evidence that shows who you engaged, what you heard, and how it shaped your decisions. If you cannot produce that, your submission is weak regardless of how much actual engagement took place.This guide explains what regulators expect from stakeholder engagement reporting, how that expectation differs across the main UK frameworks, and how organisations that do it well structure the process from the start.

What does reporting stakeholder engagement outcomes to regulators actually mean?

Reporting stakeholder engagement outcomes to regulators means providing structured, evidenced documentation that demonstrates how an organisation identified and engaged relevant stakeholders, what feedback and issues were raised, and how that input influenced decisions, plans, or operations.

In regulated UK industries, this is not a discretionary communications exercise. It is a formal part of licence compliance, periodic review submissions, and planning consent processes. The report is scrutinised. Vague claims about community engagement or public consultation without supporting evidence are routinely challenged.

The key distinction regulators make is between activity and outcome. Sending emails, running events, and publishing consultations are activities. Demonstrating that community concerns about a particular route were logged, considered, and either acted on or formally responded to is an outcome. Regulators want the latter. They increasingly want it backed by a complete, time-stamped record.

What each regulator expects

Ofwat (water and wastewater companies)

Ofwat's Asset Management Period 8 (AMP8, 2025–2030) requires water companies to embed genuine stakeholder and customer engagement in their business plans and evidence it throughout delivery. This is a step change from previous periods. Companies must show not just that they consulted, but that engagement shaped their investment priorities.

The expectation covers three areas:

• First, breadth: who was engaged, including customer groups, environmental bodies, local authorities, and community representatives.

• Second, process: how engagement was structured, how responses were collected, and how different views were weighted.

• Third, impact: where stakeholder input directly altered a plan, investment decision, or operational approach.

A company that cannot produce granular interaction logs, issue tracking records, and a clear narrative of how feedback was incorporated is exposed at periodic review and at enforcement.

Ofgem (electricity and gas networks)

Ofgem's RIIO frameworks (RIIO-ED2 for electricity distribution, RIIO-T2 for transmission, RIIO-GT2 for gas transmission) require network operators to demonstrate ongoing stakeholder engagement as a condition of their licence. This is not a one-off submission. It is a continuous obligation.

Network operators must evidence how they have engaged consumer groups, communities, local authorities, and statutory consultees in investment decisions. They must show how stakeholder views informed their business plan and how they have responded to feedback over the course of the price control period.

Ofgem's approach has become more rigorous over successive price controls. Organisations that relied on high-level summaries of engagement activity in earlier periods found that RIIO-ED2 required a level of evidential detail they had not built systems to produce.

Planning and consenting frameworks (Development Consent Orders and EIAs)

For infrastructure projects subject to a Development Consent Order or Environmental Impact Assessment, stakeholder engagement reporting is part of the statutory consent process. The Planning Inspectorate and examining authorities review evidence of public consultation, statutory consultee engagement, and how representations were handled.

The expectation here is a complete audit trail: every consultation response categorised, every issue tracked, every statutory consultee contacted and their response recorded. Projects that cannot demonstrate a robust process face delays, further information requests, or rejection.

The Environment Agency and Natural England both require specific evidence of engagement where environmental impact is a consideration. Their input, and your response to it, must be documented and reportable.

Transport (Office of Rail and Road, Transport Scotland, National Highways)

Infrastructure projects across road, rail, and active travel face similar requirements. National Highways' Development Consent Order process requires evidence of community and statutory consultee engagement at multiple stages. The Office of Rail and Road expects regulated operators to evidence stakeholder engagement as part of their licence compliance and periodic review obligations.

What good regulatory reporting looks like in practice

The organisations that produce strong regulatory submissions share a common characteristic: they build the report as they go, not at the end.

A complete and consistent interaction record. Every meeting, site visit, phone call, email exchange, and consultation response is logged at the time it happens, against the relevant stakeholder record, with the team member, date, content, and any commitments or actions recorded. Reconstructing this retrospectively from calendar invites and email threads produces a record that is incomplete and unconvincing to a reviewer who has seen hundreds of them.

Severn Trent and UK Power Networks, both Tractivity clients, run engagement programmes where dozens of interactions happen on a single day across multiple teams and geographies. The only way to maintain a coherent organisational record at that scale is through a system that captures interactions consistently as they occur.

Structured issue tracking. Regulators want to see that stakeholder concerns were not just received but managed. That means categorising issues, tracking them through to resolution or response, and being able to demonstrate that nothing was ignored or lost. A well-maintained issue log is one of the clearest signals to a regulator that engagement was genuine rather than performative.

Evidence of influence. The hardest part of regulatory reporting is demonstrating that engagement actually shaped decisions. This requires a deliberate process of linking stakeholder input to specific outcomes: a revised route, a changed construction schedule, an updated communication approach, a new community benefit. Where input was considered but not acted on, the reasons should be documented. Regulators understand that not every stakeholder concern can be accommodated. They do not accept the absence of any record that concerns were considered.

Consistent stakeholder records across a programme lifecycle. Infrastructure programmes run for years. Teams change. People leave. A stakeholder record that lives in someone's laptop or in the memory of a senior project manager is a liability. When a new team member picks up a relationship, they need to see the full history. When a regulatory submission is due, the team needs to pull structured data from across years of activity without a manual collation exercise.

SGN and Northern Gas Networks, both of which manage stakeholder engagement across multi-year gas infrastructure programmes covering thousands of kilometres of network, use Tractivity to maintain a centralised stakeholder database that every team member can access, updated in real time, and reportable on demand.

The most common reporting failures

Activity without outcome. The record shows that engagement took place but not what it produced. A log of emails sent and events attended is not a regulatory submission. It is a starting point.

Incomplete records reconstructed after the fact. Pulling together a submission from calendar invites, email archives, and individual team members' notes in the weeks before a regulatory deadline produces records that are visibly incomplete. Reviewers notice gaps. Reviewers also notice when a submission's level of detail is suspiciously consistent across all entries, suggesting it was written in one sitting.

No link between engagement and decision. A common failure in Ofwat and Ofgem submissions is a well-documented engagement process with no clear narrative of how that process influenced outcomes. The two sections sit alongside each other but do not connect.

Data held in systems not built for evidential reporting. A generic CRM, a project management tool, or a series of spreadsheets can store stakeholder data. None of them produces the structured, audit-ready reports that regulatory submissions require without significant manual work. That manual work introduces errors and takes time that could be spent on the engagement itself.

How to structure the reporting process

Start with the regulatory obligation, not the report format. Before any engagement activity begins, identify what the relevant regulatory framework requires you to demonstrate. For an Ofgem RIIO submission, that means engagement breadth, process rigour, and demonstrated influence on investment decisions. For a DCO consultation, it means complete response handling and statutory consultee records. The structure of your engagement and your record-keeping should be designed to meet that standard from day one.

Build the audit trail as you go. The engagement record that will sit behind your regulatory submission should be built in real time, interaction by interaction. If your system requires manual data entry at the end of a week or a project phase, the record will be incomplete.

Separate your stakeholder database from your project management system. Project management tools track tasks and milestones. They are not designed to maintain longitudinal stakeholder relationship records or produce regulatory reporting outputs. These are different requirements and need different systems.

Use structured reporting templates aligned to the regulatory framework. A report exported from a stakeholder management system should map directly onto the evidence requirements of the relevant regulator. If it requires significant reformatting or manual annotation to be usable, the system is not fit for purpose.

Document decisions and the reasoning behind them. For every point at which stakeholder input could have influenced a decision, record what the input was, what decision was made, and why. This is the part of regulatory reporting that most organisations leave too late and find hardest to reconstruct.

What this means for your organisation

Regulatory engagement reporting is not primarily a technology problem. It is a process problem that technology makes manageable.

The organisations that produce strong submissions have usually made two decisions early: they decided that engagement records would be maintained consistently in real time rather than reconstructed retrospectively, and they chose a system designed for the specific requirements of regulated stakeholder engagement rather than adapting a general-purpose tool.

Tractivity is used by water companies, energy networks, and infrastructure organisations across the UK to manage stakeholder engagement and produce the audit-ready reporting that regulatory frameworks require.

If your current process involves manual collation before a submission deadline, or if your records are distributed across multiple systems and individuals, it is worth understanding what a purpose-built system would change.