You said, we did: how to close the loop after an employee survey

“You said, we did” is how HR teams report back after an employee survey: what people told you, and what changed as a result. This guide sets out what to say and when, how to make it believable, how to say no, examples by theme, and a template you can copy.

What it is, and why it matters.

A “you said, we did” is a short report back to everyone who was asked to take part in a survey. Each line pairs something people told you with what you have done about it. It might be an all-staff email, an intranet page, a poster in the canteen or a few minutes at a team briefing.

It matters because people judge a survey by what happens next. If nothing seems to change, or nobody says what did, the next survey looks like a box-ticking exercise, and people are less likely to answer it honestly, or at all. When people can see that their time was well spent and that they were listened to, they have a reason to speak up again.

Four colleagues smiling at a laptop together

When to say what.

Before it opens: set expectations

Tell people when they will hear about the results, and only promise what you will deliver. If you don't plan to share the findings, don't suggest that you will. We do advise reporting back after every survey, so people know their time was well spent and that they were listened to.

Plan the messages that follow the survey now, alongside the rest of your employee survey communication plan.

When it closes: say thank you

Within a day or so of the survey closing, thank everyone who took part, and say when they will hear the high-level findings: within two weeks is a good aim. If you watched the results come in while the survey ran, you may already have some ideas. If you have already decided on actions, share what you can. If you haven't, say when you will follow up.

Within two weeks: share what you heard

Share the high-level findings: the main themes, what is going well as well as what needs to improve, and how many people took part. Keep it to what people can take in at a glance, and say when they will hear what happens next. Managers can talk through their own team's results at a team meeting, as long as the group is big enough that nobody's answers can be picked out.

Next: say what you will do

Choose a small number of themes, often no more than three, and agree an action for each, with an owner and a date. Involve the people affected in deciding what to do: they often know what would help. Then publish the plan while the survey is still fresh in people's minds. At this stage it is a “you said, we will”. In Ten Space, the action planner suggests actions from your results, lets you give each one an owner and a due date, and keeps track of them for you. See action planning.

Until the next survey: show progress

Update people as actions move, not only when they are finished: what has changed, what is still under way, and anything that has slipped, with the reason and a new date. Before the next survey opens, publish a final “you said, we did”, so people go into it knowing the last one counted.

Make it believable.

Report themes, not comments. Sum up what many people said, in plain words. Leave out anything that could point to one person: a name, a role, a shift, a site or a turn of phrase colleagues would recognise. Don't report results for a group so small that people could work out who said what.
Pair every theme with an action, an owner and a date. “We will look into it” is not an action. “We will [action] by [date], led by [owner]” is.
Use people's words, not management's. If people said meetings waste their time, say that. Don't turn it into “colleagues identified opportunities to improve meeting effectiveness”.
Include what is going well. Say what people value, and that you will protect it.
Be honest about what you can't do. Say so, say why, and say what you can do instead.
Say “we're working on it”, with a date, rather than nothing. Silence reads as inaction. A dated promise that you keep builds trust.
Keep it short. A few themes, on one page or one screen, with a link to the full findings for anyone who wants more.
Say it more than once. Use the same channels you used to invite people to the survey, and ask managers to talk it through with their teams.

You said, we didn't.

Closing the loop doesn't mean fixing everything. Some of what people raise can't be changed, or not yet: the money isn't there, the decision sits somewhere else, or the change would cause a bigger problem elsewhere. Saying no, while showing that you heard what people asked for, is an essential part of the process.

People can accept a no. What they find hard to accept is silence. A theme left out of your report back looks ignored, and people read that as a sign the survey didn't matter. A clear no, with a reason, shows that the feedback was heard, weighed and taken seriously, and it makes your “we did” lines easier to believe.

How to say no well

Name it. Say what people raised, in their words, so they can see it was heard.
Give the real reason. Cost, safety, the law, a contract or a decision made elsewhere: say which, plainly.
Say what you can do instead. Even a small step shows that the feedback made a difference.
Say whether it could change. If the answer is “not now” rather than “never”, say what would need to change, and when you will look at it again.
Put it beside what you did. Your “we didn't” lines belong in the same update as your “we did” lines, not in a footnote.

Examples, by theme.

Each example shows the shape of a good one: what people said, in plain words, and what was done about it, by whom and by when. Swap in your own people's words, and your own numbers where you see [x].

Communication

You said: You often hear about changes that affect your work from colleagues before you hear about them from us.
We did: Started a monthly briefing from the leadership team, with a recording for anyone on shift or on leave. Team leaders now go through the key points at their next team meeting. Led by the head of internal communications; the first briefing was held within a month of the survey closing.

Workload

You said: There are too many meetings, and they leave too little time for the work itself.
We did: Made Wednesday afternoons free of internal meetings, and cut recurring meetings to 30 minutes unless their owner makes the case for longer. Every department head reviewed their team's meetings within six weeks.

Recognition

You said: Good work often goes unnoticed, especially on night shifts and at the smaller sites.
We did: Started monthly thank-you nominations that anyone can make, read out at team briefings on every shift. The operations director checks each quarter that every site and shift is included.

Career development

You said: You can't see how to progress here without leaving your team.
We're doing: From next month, every vacancy goes on the intranet before it is advertised outside. By the end of the quarter, every manager will have held a career conversation with each person in their team. HR will report on both in our next update.

Tools and equipment

You said: [x]% of warehouse colleagues said the handheld scanners fail too often, and it slows down every shift.
We're doing: Replacing the oldest scanners first. The first [x] arrive by the end of next month and the rest by the end of the quarter. Led by the operations manager, with an update in every monthly briefing until it's done.

Something we can't change

You said: There aren't enough parking spaces at [site], so people on early shifts struggle to find one.
We can't: Add more spaces. The car park is shared with other businesses, and the number of spaces isn't ours to change.
What we did instead: Set aside [x] spaces for people whose shift starts before 7am, and started a car-share scheme on the intranet.

A template to copy.

Use the first version for an all-staff email or an intranet post, and the short one for a poster or a screen. Replace everything in square brackets, and delete any line you don't need.

Email or intranet post

Subject: You said, we did: what has changed since our [survey name]

Hello everyone,

Thank you to everyone who answered our [survey name] in [month]: [x]% of you took part. Here is what you told us, and what we have done about it.

What's going well: you told us [theme]. We will protect it by [action].

You said: [theme]. We did: [action], led by [owner] and finished on [date].

You said: [theme]. We're doing: [action], led by [owner]. We will update you by [date].

You said: [theme]. We can't [what you can't do], because [reason]. What we are doing instead: [action], by [date].

What happens next: we will share our next update on [date], on [where you will post it]. Our next survey opens in [month].

If you would like to talk about any of this, speak to your manager or contact [name or team].

Thank you,

[name and role]

Poster

You said, we did

Thank you for taking part in our [survey name]. Here is what has changed.

You said: [theme]. We did: [action].

You said: [theme]. We're doing: [action], by [date].

Next update: [date]. Read the full update at [where].

Common mistakes, and how to avoid them.

Saying nothing. Silence after a survey tells people it didn't matter. If you need more time, say so, and say when you will be back.
Promising too much. A long list of actions that quietly stalls does more harm than three that get done.
Vague actions. “We will review communication” has no owner, no date and no way to tell whether it happened.
Answering back. “You said, but actually…” reads as an argument. Accept what people told you, even where you see it differently, and explain what you will do.
Passing off old plans as new. If a change was already planned, say so. Don't present it as a response to the survey.
Telling only the people at desks. If the report back goes only by email, people without a work email won't see it.
Stopping after the first update. The loop closes when people see the change, not when you announce it.

How Ten Space helps.

Watch the results come in while the survey runs, so you may have ideas formed by the time it closes.
Give every action an owner, a due date and a reminder by email or WhatsApp, and keep it linked to the result that prompted it.
Start from AI-suggested actions you can accept or ignore, and track progress as it happens.
With the ethics filter enabled (the most common setup), results are only shown for groups of six or more.

Every client has a dedicated client success manager: a named UK-based expert who works alongside your team. We help you understand your results, and how to find and share the insight you need. Expert help is always included.

See action planning in Ten Space.

A phone showing survey results in Ten Space

Questions people ask

How soon after an employee survey should we share the results?

Thank people within a day or so of the survey closing, and share the high-level findings within about two weeks. Results are available in real time in Ten Space, so you will likely have some ideas on themes before the survey even finishes! If it will take longer to agree actions, say when people will hear about them, and keep to that date.

What if we can't act on something people raised?

Say so, and say why. A “you said, we didn't” is just as important as saying what you did: it shows that the feedback was heard and weighed, not ignored. Give the real reason, say what you can do instead, even if it is small, and say if the answer could change later. Silence is the one answer that doesn't work, because people read it as not being listened to.

Should we share every result?

Share the main themes, including what is going well, and offer more detail to anyone who wants it. Never share anything that could identify a person, such as results for a very small group.

Should we quote people's comments?

Only with care. Summing up a theme in plain words is usually safer than quoting. If you do quote a comment, remove anything that could point to the person who wrote it, such as a name, a role, a site, a shift or a turn of phrase colleagues would recognise.

Who should share the “you said, we did”?

A senior leader for the message to the whole organisation, so people can see it is taken seriously, and each manager for their own team, where people can ask questions. HR can coordinate both, so the messages agree.

What is the difference between “you said, we will” and “you said, we did”?

Timing. “You said, we will” is the plan you share soon after the survey. “You said, we did” reports what has actually changed. Use both: share the plan, report each change as it happens, and publish a final “you said, we did” before the next survey opens.

See what your people would tell you.

Book a 30-minute demo See the platform

or call 0161 676 3443

Employee Engagement

Employee Retention

Team Performance

Blogs

eBooks & Guides