When you ask staff to share their experience of work, plan the response as carefully as the questions. Someone who has taken time to explain a concern should be able to find out what happened to it after the survey closed.

The CIPD describes employee voice as having a say in matters at work and being able to influence them. That gives leaders a useful test: can people see how their feedback entered the decision, even when the outcome differs from what they requested? [1]

Share what you heard

Begin with a clear account of the themes. Acknowledge what people value as well as what they want to change. Give enough context to make the findings understandable, including whose views the survey reached and where participation was limited.

Be careful with broad statements such as everyone agrees. A strong theme among respondents is not necessarily a view shared across the whole organisation. Where experiences differ between groups, recognise that difference without turning a small number of responses into a confident conclusion.

Handle comments according to the privacy arrangements explained to participants. Removing a name does not necessarily make a detailed account unrecognisable. Share themes at an appropriate level, check quotations carefully and avoid exposing a person through a distinctive role, incident or combination of details.

Explain the decision and its limits

Imagine that staff in an operational team say late changes to schedules make it difficult to plan their work. Some ask for every schedule to be fixed a month ahead. The organisation still needs to respond to urgent requests, so it cannot promise that.

A useful response would acknowledge the disruption, explain the constraint and identify what can change. For example, the team could trial a weekly planning cut-off, name the person authorised to approve later changes and explain how staff will be informed when an exception is needed.

This gives people something specific to consider. They may disagree with the decision, but they can understand its reasoning and challenge whether the proposed response addresses their concern. Avoid presenting a smaller change as though the original request has been fully met.

If no change is planned, say so plainly. Explain whether the obstacle is a resource limit, conflicting needs or a decision to retain the current approach. If more information is needed, describe how it will be gathered and when staff can expect an answer.

Make the next step visible

For each priority, publish a short update that people can find again. It should make the practical commitments clear:

• What we heard and what decision we made.

• Why we chose this response, including what we cannot currently do.

• Who is responsible for the next step and when progress will be reviewed.

Choose a small enough number of commitments to follow through properly. Check that named owners have the time and authority to act. Give managers the information they need to discuss the response consistently, and provide a route for staff to ask questions.

Return to the original concern

At the agreed review point, explain what has happened. If work has slipped, give the reason and a revised plan. If something has been completed, ask whether it has addressed the experience that prompted the feedback.

In the schedule example, introducing a planning cut-off is only part of the review. Staff also need an opportunity to say whether late disruption has become more manageable and whether exceptions are being handled as agreed.

Keep that response available alongside later updates. Before sending the next survey, make it easy for a colleague to answer one question: what did the organisation do with the views we shared last time?

Source [1] CIPD Employee voice factsheet (2026-04-06)

Talk to us about connecting staff feedback with useful follow-through.

Related insight: Why live reporting matters more than ever