Start with the decision a respondent needs to make
A survey introduction should give people enough information to decide whether to take part before they answer. Begin with the survey’s purpose, who is conducting it, approximately how long it may take, and what participation involves. Use familiar language: “We’re asking about your experience with our delivery service so we can identify what to improve” is easier to understand than a broad promise to “generate customer insights.”
Explain whether participation is voluntary, whether respondents can skip questions, and what happens if they stop partway through. These details should match the survey’s actual settings. If every question is required, do not say people can skip any question. If partially completed responses are saved, say so when that matters to the respondent’s choice. Place this information before the first substantive question rather than hiding it at the end.
Use “anonymous” only when you mean it
An anonymous survey does not collect information that allows the organizer to connect a response to a particular person. That is a stronger claim than saying names will not appear in a report. Email invitations with individual tracking links, account sign-ins, recorded contact details, or combinations of highly specific answers may make responses identifiable even when there is no question asking for a name.
Confidentiality describes how identifiable information is protected and shared; it does not mean the organizer cannot identify respondents. For example, a team might collect email addresses to send an incentive while limiting access to those addresses and removing them from the file used for analysis. That arrangement may be confidential, but it should not be described as fully anonymous without checking how the survey and incentive process work together.
Before writing an anonymity statement, review the full path of a response: invitation, survey platform settings, open-text questions, exports, and any follow-up. If you are unsure whether responses could be linked to individuals, describe the concrete protections you can provide instead of making an absolute promise.
Say what data you collect and why
A useful data-use explanation covers both the answers people enter and any other information collected through the survey process. Depending on the setup, that might include an email address, an invitation identifier, or technical information recorded by the survey tool. Explain the purpose of each category in everyday terms. Respondents should be able to tell which details are needed to analyze answers, which are needed to contact them, and which are optional.
Then describe how findings will be used. Will the team compare experiences across groups, improve a product, or inform a future interview guide? Will results be reported as summaries, and could written comments be quoted? If a comment might be shared, consider whether its wording could identify the writer even without a name. Avoid vague assurances such as “your data will be used responsibly” when you can state a specific practice instead.
Make sharing, storage, and withdrawal understandable
Tell respondents who can access individual responses and whether any outside service helps collect or process them. Distinguish sharing a summary of findings from sharing the underlying response file. If responses will be available to another team or organization, name its role in plain terms. Keep the explanation consistent with what actually happens after the survey closes.
It also helps to say how long identifiable information will be kept, or what determines when it will be deleted, if that has been decided. Explain how someone can ask a question or request removal of a response, and be honest about practical limits. In a genuinely anonymous survey, you may have no way to locate one person’s answers later. Once responses have been combined into a summary, it may also be difficult to remove an individual contribution from that summary. Do not promise withdrawal on terms your process cannot support.
Write the notice, then test it against the survey
A short notice can cover the essentials without becoming a wall of text: “This survey asks about your recent delivery experience and takes about five minutes. Taking part is optional, and you may stop at any time. We will use responses to identify service improvements and report results in summary form. Our research team can view individual responses. Please avoid including names or other personal details in written comments.” Add only statements that are accurate for your particular survey, along with any relevant details about contact information, sharing, or retention.
Finally, test the notice as carefully as you test the questions. Ask someone unfamiliar with the project to read it and explain, in their own words, what they are agreeing to. Check their understanding against the survey settings and the team’s planned workflow. If the reader expects anonymity but responses carry identifiers, or expects comments to stay private when they may be quoted, revise the notice or the process. Clear consent depends on both.
