Before an employee survey, tell people why it is happening, what privacy protection actually applies, how long it takes and what leaders will do after it closes. Then repeat the essential privacy explanation at launch, use one proportionate reminder and share findings with named actions within a promised timeframe.
The four templates below are ready to adapt. Replace every bracketed field and remove any privacy claim your system cannot prove.
What must every survey message explain?
Employees should not have to infer the data flow from the word anonymous. A credible message answers:
- Why are we asking? Name the decisions or conditions the survey will examine.
- What will be collected? Explain identity, invitation, completion and answer data separately.
- Who can see what? State whether HR, managers, administrators or a service provider can access participant-linked answers.
- How will results be protected? Cover small groups, filters and written comments.
- What is expected? Give the time required, closing date and whether participation is voluntary.
- What happens next? Promise a realistic date for findings and the first action response.
Do not bury privacy details in a policy link while the email makes a broader claim. Put the plain-language boundary where employees will actually read it.
Which privacy wording should you use?
Choose the wording that describes the real system.
Strictly anonymous collection
Use only when no identity-to-answer connection is collected or retained:
The survey does not collect your name, email address, account identity or another identifier that can be connected to your answers. Results will be shown only for groups that meet our reporting minimum, and written feedback will be reviewed for identifying details before it is reported.
If the form requires sign-in, uses a unique employee invitation or stores IP addresses with answers, this wording is probably not accurate.
Confidential survey
Use when the system retains participant-linked answers but limits access:
This is a confidential survey. [Named authorised role or provider] can connect responses to participant records for [specific purpose]. Managers and general employer users will receive [aggregate results / approved reports] under reporting rules that hide groups below [accurate threshold or principle]. [Explain whether raw answers or comments can be accessed and by whom.]
Confidential is not a lesser word when it is the truthful one. A precise promise is more trustworthy than a larger promise undermined by the settings.
Responses completely anonymous to HR
Use when identity supports delivery and grouping but employer accounts cannot access participant-linked answers:
Your responses are completely anonymous to HR. The survey service uses your invitation details to deliver the survey, prevent duplicate responses, track completion and apply the correct reporting group, but HR cannot switch anonymity off, access participant-linked or raw responses, or recut results to identify how you answered. After the survey closes, results are privacy processed: unsafe small groups are withheld and written responses become supported themes rather than individual comments or quotations.
This describes Candora's employer boundary. It does not claim that the service has no operational identity data.
Template 1: advance survey announcement
Send this roughly three to seven working days before launch.
Subject: Employee survey opens [day, date]
On [date], we will open an employee survey about [leadership, workload, communication, belonging and growth / specific purpose]. We are asking because [name the decisions or conditions the results will inform].
The survey should take about [X] minutes and will close at [time] on [date]. You may complete it during working time. Participation is voluntary, and we want an honest picture rather than a particular response rate.
How your feedback is protected
[Insert one accurate privacy paragraph from the options above. Add any organisation-specific access or reporting detail employees need.]
Please avoid naming yourself or another person in written answers. [Explain whether written answers are withheld, reviewed, themed or released individually.]
We will share the main findings by [date] and confirm the first actions, owners and next update date. Questions about the process can go to [contact who can answer without pressuring participation].
Why this announcement works
It gives a reason before asking for effort, separates privacy from reassurance and commits the organisation to a result date. It also avoids language such as “we expect 100% participation”, which can make a voluntary survey feel compulsory.
Template 2: survey launch message
Keep the launch email shorter than the announcement, but repeat the privacy boundary.
Subject: The [Organisation] employee survey is now open
Our employee survey is open now and closes at [time] on [date]. It should take about [X] minutes.
Take the survey: [survey link or invitation instructions]
We want to understand [one-sentence purpose]. Please answer from your own experience; there is no preferred score.
[Insert a concise, accurate privacy explanation. Example: “Your responses are completely anonymous to HR. Candora uses invitation details for delivery, completion tracking and reporting-group attribution, but HR cannot switch anonymity off, access participant-linked or raw responses, or recut results to identify how you answered. Employer reporting uses privacy-safe results created after closure.”]
Please avoid identifying yourself or colleagues in written responses. We will share the main findings and first actions by [date]. For access problems, contact [support contact].
What should the survey landing page repeat?
The survey itself should restate:
- Purpose and expected completion time.
- Closing date.
- Whether participation is voluntary.
- What identity or invitation data is used.
- Who cannot and can access participant-linked answers.
- How small groups and written feedback are treated.
- A support route that does not expose responses.
An employee may open the link without having seen the earlier email. The privacy promise should still make sense on its own.
Template 3: one survey reminder
Send one reminder around the middle of the survey window. A second final-day reminder may be appropriate for dispersed or shift-based teams, but repeated messages can feel like surveillance.
Subject: Employee survey closes [day]
A reminder that the employee survey closes at [time] on [date]. If you have not completed it and would like to take part, use [survey link or invitation instructions].
[Insert one accurate privacy sentence. If reminders are targeted, explain: “The service records whether an invitation is complete so it can avoid reminding people who have finished. Completion status does not give your employer access to your answers.”]
Thank you to everyone who has already responded. We will share the main findings and first actions by [date]. If you have an access problem, contact [support contact].
What should managers say?
Give managers a short script so encouragement does not become pressure:
The survey is open until [date]. Please take part if you choose and use working time where possible. I cannot see who said what. I will not ask whether you completed it, and I will discuss the team-level findings only where they meet the reporting protections.
Managers should not ask employees to complete the survey during a watched meeting, request screenshots, circulate names of non-responders or compete publicly over team response rates.
Template 4: survey results and action message
Share a first update within two to four weeks where possible. If analysis will take longer, send a holding update before the promised date rather than going silent.
Subject: What we heard in the employee survey
Thank you to everyone who took part. [X of Y invited employees / X%] completed the survey. Participation tells us how much evidence we have; it is not a performance target.
What is working
The clearest strengths were [strength one] and [strength two]. We will protect these by [brief commitment].
What needs attention
The strongest areas for action were [priority one] and [priority two]. [Describe protected written-feedback themes without quoting or exposing individual comments.]
[If relevant: “Some team or question results are not shown because too few responses supported a privacy-safe result. We will not weaken that protection to fill a report.”]
What happens now
- [Action one], owned by [role], by [date].
- [Action two], owned by [role], by [date].
- Progress update on [date].
We cannot act on every suggestion at once. We chose these priorities because [short rationale]. The next survey or pulse will happen only when its answers can inform the next decision.
What if the results are uncomfortable?
Say so calmly. Do not challenge the validity of the survey simply because the message is difficult, and do not search comments for the person who “must have said it”.
A useful structure is:
- Acknowledge: “Trust in senior decision-making is lower than we expected.”
- Clarify: “The strongest pattern concerns decisions being announced without the reasons.”
- Own: “Leaders have not consistently explained the trade-offs behind changes.”
- Act: “From next month, each major change update will include the decision, evidence, alternatives and owner.”
- Return: “We will report progress in six weeks and test whether clarity has improved in the next focused pulse.”
Defensive language teaches employees to soften the next answer. Honest ownership gives them a reason to participate again.
What timeline should HR use?
| Timing | Communication | Purpose |
|---|---|---|
| 3–7 working days before launch | Advance announcement | Explain purpose, privacy and what follows |
| Launch day | Survey invitation | Give access, timing and the concise privacy boundary |
| Mid-window | One proportionate reminder | Restore access without pressure |
| Closing day | Optional short thank-you | Confirm closure and repeat the results date |
| Within 2–4 weeks | Findings and first actions | Close the first feedback loop |
| At the promised action date | Progress update | Show what changed, what did not and why |
The results email is not the end of communication. A later progress update is the evidence that the organisation meant what it said before launch.
What should you leave out?
Remove language that creates pressure or makes an unverifiable promise:
| Avoid | Why | Use instead |
|---|---|---|
| “No one can trace anything.” | Overstates the service-side operational data boundary | “Your responses are completely anonymous to HR,” followed by the precise delivery and reporting safeguards |
| “We need 100% participation.” | Can make a voluntary survey coercive | “Please take part if you choose; we want honest feedback.” |
| “Your manager will never know whether you responded.” | May be false if completion dashboards exist | Explain exactly who can see completion and that it is separated from answers |
| “Every comment will be heard.” | Suggests individual comments will be circulated or acted on | Explain how protected themes are formed and prioritised |
| “We will fix everything you raise.” | Impossible promise that invites later disappointment | Commit to publishing priorities, owners and dates |
How does Candora communicate the privacy boundary?
Candora responses are completely anonymous to HR. Candora uses identifiable participant data for invitation delivery, one-response enforcement, completion status and reporting-group attribution, but there is no HR-controlled anonymity setting and employer accounts cannot access participant-linked or raw responses or recut results to identify how someone answered.
After a survey closes, restricted processing creates privacy-safe results. Unsafe small groups are withheld, and written responses become supported thematic findings instead of employer-visible individual comments or quotations. Reports and exports use that protected layer.
That explanation is longer than “trust us”, but it gives employees something concrete to assess. Read the complete Candora privacy flow.
The short answer
Tell employees the purpose, the real data boundary and the date they will hear what happened next. Repeat the essentials at launch, remind without pressure, and return with a small number of owned actions.
The quality of a survey is partly determined before the first answer and after the last one. Clear communication makes the privacy promise understandable; visible follow-through makes the next survey worth answering.
Use the free 20-question survey template with these messages, or see how Candora manages the complete workflow.
quick answers
Frequently asked questions
What should employees be told before an engagement survey?
Explain why the survey is happening, how long it takes, what identity or completion data is collected, who can access answers, how small groups and comments are protected, when it closes and when employees will hear the findings and actions.
How far in advance should an employee survey be announced?
Three to seven working days is usually enough for a broad survey. The aim is to give employees time to understand the purpose and privacy model without creating a long campaign that feels pressured or overproduced.
Should employee survey participation be mandatory?
Honest feedback should be voluntary. Give employees reasonable working time and access, but avoid manager pressure, public completion lists or team participation competitions that can weaken trust and distort responses.
Can a reminder be sent without breaking anonymity?
A system may track whether an invitation has been completed without giving the employer access to the person's answers. The reminder should explain that distinction accurately; if completion and answers are linked for employer users, do not describe the process as anonymous.
When should employee survey results be shared?
Share a first results update within two to four weeks where possible, even if deeper work continues. Include what was heard, what cannot safely be reported, the first one or two actions, their owners and the date of the next progress update.
