Employee feedback form: questions and privacy settings

An employee feedback form needs a clear subject and a clear reader. Staff should know whether they are commenting on workload, a recent change, or the support they receive from a manager. They should also know who will read the answers before they submit them.

Begin with a decision you can make. If the next planning meeting can change how work is assigned, ask about priorities and capacity. If the team is reviewing a new tool, ask about access and the tasks it should support. Keep unrelated performance-review questions in a separate process.

Questions for a team workload review

The following examples use the past two weeks as a shared time window. Change that period to match your team's review cycle, then keep it consistent when comparing later rounds.

• How clear were your priorities during the past two weeks?
• How manageable was the amount of work assigned to you?
• How often did you have the tools or access needed to do that work?
• Which handoff caused the most avoidable delay, if any?
• What should we change before the next planning cycle?

Use labeled choices for the first questions and optional text for examples. Keep clarity and workload separate. A person can understand every priority and still have more work than they can finish. A single question about whether work is "clear and manageable" hides that difference.

Questions about manager support

If manager support is the topic, ask about observable experiences. "How often could you get a decision when work was blocked?" points to something the manager can investigate. "Is your manager a good leader?" leaves people to interpret a broad judgment in different ways.

Other useful prompts include "What would make our one-to-one meetings more useful?" and "Which decisions need a clearer owner?" If the manager named in the feedback will read the raw comments, tell staff that before they answer. If someone else will summarize them first, describe that process instead.

Choose between named replies and feedback without names

Named responses let a reviewer ask for more detail. Feedback without contact details can still suggest a team-wide change, but it may leave a specific problem unresolved when nobody can ask a follow-up question. Choose the collection method for the work you intend to do with the answers.

Removing a name field does not settle every privacy question. A department and job title might identify the only person in that role. The wording of a comment can identify a meeting or incident too. The anonymous feedback form guide covers those collection choices and the limits of an anonymity promise.

Account access and recording names are also separate settings in some tools. Microsoft documents a Record name setting for organization surveys in its guide to collecting responses without recorded names. Inspect the saved responses and provider information instead of assuming that a sign-in screen tells you everything the owner receives.

Write the invitation before building the form

State the subject, review date, and people who will read individual responses. Explain whether the wider team will receive a summary. If you cannot write that introduction clearly, resolve the review process before sending the survey.

For example: "We are reviewing how work was assigned during this planning cycle. The operations lead will read the responses and share proposed changes at Friday's meeting. Contact details are optional and will be used only if you ask for a reply." Use this wording only if it describes what your team will actually do.

Build the questions and check reviewer access

In Thunder Forms, start with a blank form or adapt the Customer Feedback template. Replace its customer wording and remove questions that do not belong in an employee review. Use an explicit choice field when you need staff to select a rating instead of accepting a preselected value.

Submit a sample response through the public link and inspect it from the reviewer's account. Check any linked spreadsheet separately. Exporting answers or syncing them to a shared location creates another place where people may read them. Keep the access list consistent with what you told employees.

Report what will change

Separate the response count from the number of people invited. Record what the respondents raised and choose the changes your team can make. If several comments mention conflicting priorities, identify who will resolve those conflicts during the next cycle.

Share the accepted actions, their owners, and when staff can expect an update. If you keep a question for the next survey, retain its wording and answer scale so the comparison has a consistent basis. Remove questions whose answers have not led to a useful review.

Turn the results into a bounded action plan

Suppose several answers say priorities changed without warning. The first response need not be another survey. A manager could publish a weekly priority list, name who approves urgent changes, and review the process after the next planning cycle. Record the owner and review date beside the action so staff know when they can expect an update.

Separate issues that need a private conversation from themes that can be addressed across the team. An anonymous response cannot be followed up with its author, and a named response should not be shared with more people than the stated review process requires. If a comment describes an immediate safety concern or a specific allegation, use the organization's established reporting channel rather than treating a general feedback form as a case-management system.

Keep repeat surveys comparable

When you repeat a workload question, keep its timeframe and answer labels stable. If the question changes from "past two weeks" to "usually," mark that change in your notes instead of placing both results on one uninterrupted trend. Keep the invitation and review process consistent too, or differences may reflect who felt safe or able to respond.

For question banks by goal, from product testing to employee pulses, see the survey questions guide.