What citizen engagement systems need to support long-term decision use
A good, purpose-built engagement system should be able to collect, analyse and store data in a way that allows the responses to be used for years to come. When this isn’t the case, or when inappropriate tools are used, it can lead to serious issues. The following article explores what a system that is designed for long-term use looks like.
Engagement is increasingly expected to inform decisions beyond its original scope
Historically, when an engagement activity was run - such as a stakeholder meeting, a town hall or a public consultation - it was typically to inform a single decision or project. For example, a public consultation on a new housing development would be used to inform the planning decision made by a public body or local council on that development alone. Once that decision was made, the consultation would be closed and the data archived.
This isn’t the case in 2026. The almost universal digitisation of consultation records means that engagement outputs aren’t put away in a filing cabinet. Instead, they are frequently revisited to inform policy development, support future consultations or respond to legal scrutiny down the line. A consultation on a Local Plan for example, may be referenced years later during planning applications, when creating new infrastructure or during a legal challenge from local residents.
In some ways, this can be very useful. By using engagement outputs taken over a longer period of time and in different contexts, decision-makers will have access to rich data that can support better policy-making. Regulators, elected representatives and the public increasingly expect organisations to demonstrate clear continuity in how they use evidence. There is also an expectation that resources should be used efficiently and in a cost-effective way. If data gathered in one engagement process can be used to support a fuller context in another, then why shouldn’t it be used?
However, as a result of this changing expectation around engagement data, there are new requirements around how this information should be stored, structured and explained. Unfortunately, not all organisations have kept pace with these requirements, which leads to the use of data that is missing important context.
Long-term decision use depends on preserved context, not just responses
When data is going to be used in a long-term way to inform multiple projects, it has to be treated differently. Organisations must be able to evidence:
- How an engagement activity was designed and delivered.
- The exact context participants were given.
- How responses were interpreted and used at the time.
Without this context, the value of the input degrades. Decisions will become harder to evidence as a result. That’s why when this data is revisited, it cannot be responses alone. It certainly can’t be - as is unfortunately common - summaries of responses alone.
Example: Let’s say that a local council ran a consultation in 2022 on the creation of a new play park in Area A, and only 30% of respondents were in favour of the proposal. In 2025, a play park is proposed in Area B and the council refuses it on the basis that “only 30% of residents want new play parks”.
When residents dig further into the data that informed this decision, they find that the consultation run in 2022 was about a park next to a busy road and that most objections arose out of concern about a lack of safe crossings. In contrast, the park proposed in Area B is in a residential area with a 20mph speed limit.
This is an example of data that has lost context, and is therefore being used in a way that is not only less useful, but actively misleading decision-makers about the views of residents.
For engagement to support long-term decision use, the tools used by public bodies must preserve both responses and the circumstances within which they were received. This ensures that future analysis can reflect not just what was said, but why.
Traceability supports both compliance and organisational accountability
Clearly then, it is vital for legal compliance and for accountability to stakeholders and the public that data is traceable. In this context, traceability means being able to follow a clear path from inputs, to how those inputs were analysed and finally to how decisions were then made. It also means preserving context in the form of:
- How questions were phrased and why.
- What supporting information participants were given.
- Any specific issues raised by participants that affected decision-making.
It is really useful to be able to use data in a way that can enrich future engagement activities, but without traceability, this data could be misrepresented and cause more harm than good. This is particularly a risk for more formal engagement activities such as statutory consultations, where misrepresented data could lead to serious legal challenges.
It is therefore important that anyone intending to reuse data does so only using tools and systems that support saving evidence in a way that can clearly demonstrate traceability of evidence even over long periods of time.
Interpretation changes over time and across decision-makers
It is an inherent part of having analysts and decision-makers that are human, that the way they interpret responses and the conclusions they come to will differ. That can be really helpful when thinking about a team, where different members will have different strengths and weaknesses that can be taken together to make decisions that are representative.
However, this can also cause issues. If an individual leading one team comes to a certain conclusion from a data set, but a different individual comes to a different conclusion from a similar set of circumstances elsewhere - this may lead to uneven decision-making where one group benefits more than another.
This is particularly a risk if different teams revisit the very same evidence, but draw different conclusions.
Example: A survey conducted with residents in a city centre has a variety of responses, but the biggest complaint is how slow the buses are despite many areas of the centre being bus lane only routes. Team A analyses these results and concludes that residents would like to see more regular bus services in the city centre. Team B analyses the same results and conclude residents want these bus only routes to be made accessible to motorists.
Neither of these interpretations are wrong, but they are very different despite using the same inputs. Over time, these conclusions may be used to draw up policies that are actively antagonistic to one another.
Changes in policy priorities can also affect interpretation. What was considered a minor concern at the time of the consultation may become more significant in light of new developments. Conversely, issues that were very important may become less relevant.
Engagement systems must ensure that insight remains intelligible over time. This includes preserving original analysis, documenting how conclusions were reached, and ensuring all current and future users have access to this information. Engagement systems must support reuse without distortion.
Long-term decision confidence relies on durable engagement systems
Confidence in public decision-making depends on the ability of a public body to show that engagement activities have been conducted well, and that the data from it has been used appropriately. If engagement data is going to be used again and again - as has become the norm - the necessitates confidence in the engagement platforms used to gather and store that data. So what should an organisation look for in these tools?
Firstly, the tools used to store and reuse data should be a purpose-built platform that has traceability embedded as part of the design. Using spreadsheets or tools not designed for long-term data storage of this kind is exactly how the loss of context discussed above happens.
That means that questions and supporting information is captured and stored alongside inputs, and stored in a way that they can easily be viewed together. Where summaries are used, it should be simple to see the original data the summaries were based on and there should be an easy way for users to leave notes on any relevant additional context.
There must be a consistent framework for capturing, storing and analysing input that reduces the chance of data being interpreted in contradictory ways over time, and allows easy data comparison even over long periods or across different areas.
Case Study: Police Scotland
Police Scotland make a great example of how engagement data can be used effectively over a long period of time when it is captured and managed within a purpose-built platform. Since adopting Citizen Space in 2019, the organisation has significantly expanded its ability to gather and use public input, increasing public participation by more than 500%.
Central to this approach is the annual Your Police Survey, which generates a consistent and repeatable dataset on public attitudes to policing across Scotland. As it is run through Citizen Space, responses are captured in a structured format year after year, allowing trends to be identified and compared over time. Data is stored alongside its context, ensuring the early inputs have retained their integrity even 7 years later.
Over time, the traceability and repeatability of these inputs has allowed Police Scotland to build a detailed and evolving picture of community priorities. Rather than relying on one-off engagement exercises, they are able to revisit and reuse data with confidence.
“Everybody who’s used Citizen Space within Police Scotland loves it.”
- Davina Fereday, Research and Insight Manager, Police Scotland
Citizen Space is the go-to govtech platform for engaging with citizens, managing large scale government consultations and simplifying statutory processes. If you’d like to learn more about how our software can be used to support long-term decision-making, book a free demo today.
Sign up for the Delib newsletter here to get relevant updates posted to your email inbox