How to create an anonymous feedback form

To create an anonymous feedback form, start by removing questions that identify the respondent. Then review the less obvious ways an answer could reveal someone: a small department, an uploaded document, or a comment about a meeting only two people attended. The introduction should describe the privacy you can provide with that setup.

This takes more care than deleting the email question. A form can omit names while the service still processes technical data. Decide who will read the answers and what you will share with the wider group before asking people to write something candid.

Choose a specific subject for the feedback

A form asking for thoughts about everything at work is difficult to answer and difficult to act on. Choose a subject such as the recent onboarding process or the weekly planning meeting. A narrower request lets you explain what will happen after someone submits it.

For example, a team reviewing its planning meeting could ask:

1. How useful was this month's planning meeting for your work?
2. Which part helped you decide what to do next?
3. What would you change about the next meeting?
4. Is there anything else the facilitator should know?

Use a labeled choice scale for the first question and optional text fields for the others. Give people a way to say they did not attend. Someone without that experience should not have to invent a rating just to reach the comment box.

Remove identifying questions and unnecessary attachments

Leave out names, email addresses, employee numbers, and other direct identifiers. Review combinations too. Asking for department, job title, and tenure can identify the only person who fits all three answers. Keep a grouping question only if you need it for a specific decision.

Avoid requiring a screenshot or document. It may include a profile photo, account name, or details in the file itself. If evidence is needed, offer a separate contact route and explain who will receive it. An optional email field in the same response still connects that address with the feedback when somebody fills it in.

The Thunder Forms Customer Feedback template starts without a name or email question. Its satisfaction and recommendation questions are written for customers, so replace those labels if you are collecting feedback about a meeting. Our template walkthrough also explains the optional slider's starting value. Keep only the questions your review needs.

Write a privacy statement you can support

Explain whether names are requested, who reads individual responses, and whether comments will be quoted. If you plan to publish themes instead of raw comments, say so and follow that plan. Remove names and identifying incidents from examples before circulating them.

A possible introduction, if it matches your process, is: "We do not ask for your name or email address. The workshop facilitator will review the responses and share a summary of suggested changes. Please avoid including personal details in your comments."

Check the form provider's privacy information before promising complete anonymity. Thunder Forms' privacy policy describes server logs and analytics. Omitting identity questions does not mean that the service processes no technical information. If your purpose requires stronger anonymity guarantees, confirm that your chosen service and review process meet them before collecting answers.

Review access and test the shared link

Open the public link in a browser where you are not signed in to the builder. Submit a harmless example without entering contact details. Inspect the saved response and any spreadsheet destination as the person who will actually review the feedback.

If you use Google Forms, review email collection and the response summary setting. Google explains that enabling a results summary can make response text or charts visible to people who can respond. Its sharing and response settings guide is useful when checking that access. Signing in alone should not be described as proof that the owner sees a respondent's identity.

Agree on how the answers will be used

Assign someone to read the comments and record the changes you intend to make. If several people mention an unclear meeting agenda, share the revised agenda with the group. You can explain what changed without publishing the individual responses that prompted it.

For employee feedback, use the more detailed employee feedback form guide to plan questions and review access. Keep a separate, clearly named contact route for anyone who wants a personal reply, since a response without contact information cannot support that conversation.

Run a privacy review before sharing

• List the people who can read raw responses and remove everyone else.
• Check whether account, email, or identity fields are collected.
• Look for combinations such as role, location, and tenure that single someone out.
• Remove required uploads unless a file is necessary to act on the feedback.
• Decide how long answers are kept and where exported copies are stored.
• Tell respondents whether comments will be quoted, summarized, or shared.

Then test the published link using a fresh browser session. Submit one response with a comment and one without optional details. Check what the owner sees in the response record and any connected spreadsheet. If you cannot explain every field shown to the reviewer, revise the collection or the privacy statement before inviting people to answer.