How to explain who sees employee data and what it is used for

Summary
A communication professional has drafted a survey invitation that says "Your answers are confidential". A colleague asks why the link is personal, who sees the answers and what they are used for. This episode asks what to get confirmed, and by whom, before you explain who sees employee data and what it is used for, and which parts of an explanation can go out while others go back to the data owner.

The scenario in this episode is fictional. It does not describe a real organisation or case. The episode is background reading, not new research.

News
Texas State University, Office of Human Resources, "Employee Engagement Survey". Publication date not stated; survey window 21 September to 2 October 2026. The university says Gallup manages the survey and that it receives grouped results rather than individual responses. Its frequently asked questions say individual codes prevent repeat submissions and let Gallup group responses by workgroup. This is the university's own public explanation, not an audit; we have not tested it. The page promises confidentiality, which is not the same as anonymity.
https://www.hr.txst.edu/employee-engagement-survey.html

Context
Gallup, "Employee Data Use: One in Five Trust Leaders a Great Deal", by Andy Kemp and Ryan Pendell, published 24 September 2026. Gallup reports that employees who had discussed workplace data use with someone in their organisation were more likely to report a great deal of trust in leaders to use employee data responsibly, and also more likely to express concern. The article is about perceptions of data on work activity and content, not about engagement surveys. Gallup says perceptions may not match actual practice. Gallup is a commercial research and advisory provider. We use no figures and claim no cause.
https://www.gallup.com/workplace/714932/employee-data-one-five-trust-leaders-great-deal.aspx

Our reading
An explanation helps when an employee can follow the route their data takes: who collects it, who can see it individually, what the employer receives and what it is used for. A clear explanation does not repair a practice that is itself a problem. This is our synthesis, not a measured finding.

Your next move
Choose one existing application, such as a survey. Ask its owner to confirm five things: what is collected; who can see individual responses or data, and what the personal link or code is for; what the employer receives, and for which groups; what it is used for; and where employees can ask questions, and who answers. Record each answer as confirmed by a named person, or unknown with an owner and a date. Publish what is confirmed and send the rest back to the owner. Make the explanation reachable for people without a company device. An untested practical check, not evidence that trust improves.

To check it later: was the route confirmed before you published, and were the open questions given an owner? That is process evidence, not a measure of trust, participation or growth.

Keep in mind
- This is not legal or privacy advice. If the law requires a specific notice, your legal or data protection colleagues own that wording.
- A personal code on its own does not prove that answers can be traced, or that they cannot.
- The example is a scenario we made up, not a pattern in every organisation.
- The practice has not been tested with real users.

Sources checked
Texas State University page: no publication date on the page; survey window 21 September to 2 October 2026; checked on 27 and 28 October 2026 through web-fetch extracts.
Gallup article: published 24 September 2026 as shown on the page; checked on 27 and 28 October 2026 through web-fetch extracts.
Research cut-off for this edition: 27 October 2026, 01:30:45 Europe/Amsterdam.

We use AI to expand the context, sharpen the analysis and make your attention go further.
Sponsored by Springcast.