Collecting employee feedback with names masked
Feedback schemes die at the second round. Nothing visible happened after the first, so people conclude the box is decorative and stop filling it.
A company wants to hear things people will not say in a meeting. Two obstacles stand in the way.
The first is fear of attribution. The second is the suspicion that nothing will happen either way.
PeopleMuster answers both. Every submission lands in the admin list with the name masked, and a lifecycle of received, reviewed, addressed and closed shows whether anything moved.
Masking is a permission, and you decide who holds it. A reviewer reads the substance first; the name appears only when someone with the reveal permission opens that one item. Keep that list to one or two people and say so when you launch the scheme. Survey vendors run the same model; in September 2026 Culture Amp described its own surveys as confidential rather than anonymous.
Why one record instead of two
Feedback is the one flow that runs from the team back towards the company. One route covers both obstacles. A submission carries a category and an attachment if needed, the name stays masked until someone with permission reveals that single item, and a visible lifecycle shows what happened next.
What is switched on
- Feedback
- Feedback in categories such as suggestion, concern, praise and general, with attachments.
- Feedback
- A four-stage lifecycle with thirty-day counts, plus filters by category, label, user and department.
- Feedback
- Identity masking by default, with a deliberate reveal action rather than open names.
- Roles and permissions
- Who may reveal an identity is a permission, and it should be a short list.
- Notifications
- Closing the loop publicly is what keeps the second round alive.
What the week looks like
Any time
An employee submits feedback in a category, with attachments if needed. The name is masked the moment it reaches the admin list.
On arrival
The reviewer reads the substance with the name hidden, then filters by category and department to see whether it's one voice or a pattern.
Weekly
Whoever reviews works the received queue and moves items to reviewed.
As things happen
Items become addressed and then closed, which is the only part employees judge.
Monthly
Thirty-day counts by category show themes rather than individual complaints.
Rarely
Reveal an identity only when there is a specific reason. The default is masked for a reason.
Questions people ask
Is employee feedback anonymous in PeopleMuster?
Submitter names are masked by default on every item, and only a person you give the reveal permission can show one, item by item. Tell the team exactly that when you launch: names hidden, a short list of who can reveal, and a lifecycle they can watch.
Who can reveal a submitter's name?
Anyone holding the reveal permission, and nobody else. Reveal is a permission in roles, works on one item or the whole list, and the sensible list is one or two people.
How do we show that feedback led to something?
The lifecycle is the mechanism: received, reviewed, addressed and closed. Publishing what moved to addressed is what keeps a second round of feedback coming.