What is survey data collection?
Survey data collection is the process of gathering answers from a defined group using a planned set of questions. It includes deciding who should respond, how they will be reached, what context each response needs, and how the answers will be checked and used. A questionnaire is one part of that process.
Good collection makes the next decision easier to answer. Before sending a survey, identify the result you need: understand a service problem, compare experiences across locations, review a training program or follow a group over time. That purpose determines what you ask and which records can legitimately be compared.
A completed form is not automatically reliable evidence. People may interpret a question differently, some groups may not respond, and a repeated survey may reach a different mix of people. Collection design and ongoing review matter even when the platform validates fields.
Choose a collection method your respondents can use
Choose the method around access, language, sensitivity and the kind of answer needed. Convenience for the organization is only one factor. If the intended population cannot participate comfortably, the resulting dataset may omit the people whose experience matters most.
| Method | Useful when… | Plan for… |
|---|---|---|
| Online self-completion | Respondents have suitable access and can answer independently | Mobile usability, accessibility, invitation reach and duplicate submissions |
| Telephone or interviewer-led | Respondents need support or the collection needs clarification | Consistent interviewer guidance and possible effects of answering to another person |
| Paper or offline capture | Connectivity or device access is limited | Transcription or synchronization checks, batch identification and safe handling |
| Mixed-mode collection | One channel would exclude part of the intended group | Comparable wording, mode labels and checks before combining results |
For example, an association might offer an online annual survey and a supported telephone option. Keep a record of the collection mode so the analyst can investigate differences. Do not assume responses are directly comparable simply because they appear in one spreadsheet.
See quantitative data collection methods for a broader methods discussion.
Define who should answer before writing the questions
Write down the population of interest and how the invited group will be selected. “Our customers” is rarely precise enough. Does the survey include active customers, recent cancellations, people who used a particular service or everyone who registered during a period?
A public link shared through social media produces a different group from a survey sent to a defined list. Both can provide useful feedback, but they support different claims. Document the invitation route and eligibility rules so the report can explain whose views are represented.
- Who is eligible? State the service, membership or participation condition and relevant dates.
- Who can be reached? Check contact coverage and alternatives for people without a usable address or device.
- Who actually responded? Track responses and nonresponse by meaningful groups where appropriate.
- What can be claimed? Distinguish feedback from respondents from a conclusion about the entire population.
A large response count does not, by itself, remove selection bias. More answers from the same easily reached group may still leave a blind spot.
Write questions that support the decision
Ask about one idea at a time and use a clear period. “Was our service helpful and easy to access?” combines two issues: someone may find it helpful but difficult to access. Separate those questions if the distinction matters to the action.
Pair a structured measure with a relevant open question when explanation would help. For example, after asking about access during the last month, ask what made access easier or harder. Avoid asking for a long narrative unless the team has a plan to review and use it.
Decide how missing, not applicable and prefer-not-to-answer responses will be represented. These are not interchangeable with a low score or a zero. Requiring every question can create inaccurate answers when respondents do not have a meaningful response.
Test the questionnaire with people similar to the intended respondents before fielding it. Ask what they understood, how they chose an answer and where the process was difficult. AAPOR recommends pretesting as part of survey research practice. AAPOR best practices.
Choose anonymous or identified collection deliberately
Anonymous collection can be appropriate when candid group feedback is the goal and individual follow-up is unnecessary. Identified collection may be needed when the question concerns a person’s change over time or a service follow-up. Explain the actual arrangement clearly to respondents.
Do not label a survey anonymous if response links, contact fields or other stored information allow the organization to connect answers to individuals. Conversely, do not attempt to identify respondents after promising anonymity. The analysis design must respect the collection agreement.
Three records with different jobs
- Registration record: the person or organization, with stable facts and controlled updates.
- Response record: the dated answers for a particular survey or period.
- Contributor context: whether the answers came from the participant, a representative, a coach or another observer.
Keep these relationships explicit. A parent’s observation and a participant’s self-report can concern the same person while remaining different evidence.
A stable identifier supports planned linkage, but it does not eliminate duplicate, missing or incorrect records. Test matching and correction rules. Where anonymity is required, use group-level trends without implying individual change.
Allow local questions while protecting shared comparisons
A network of chapters, partner organizations or schools may need different questions locally. Imposing a single long survey can reduce relevance and discourage participation. Start with the small set of shared fields needed to answer agreed central questions.
Define those fields in a data dictionary: meaning, response options, reporting period, unit, source and aggregation rule. Record which local questions remain separate. Two sites can ask about their own activities while sharing compatible measures for selected comparisons.
Collect stable registration details once where appropriate, and provide a way to update changing facts such as role or location. Attach later responses to the relevant period. Do not overwrite history when a change matters to interpreting earlier answers.
The member and network evidence course works through collection, shared definitions, analysis and governance as a connected plan.
Prepare the launch and monitor collection
A launch checklist should cover the invitation, questionnaire, record structure and review responsibilities—not only whether the submit button works.
- Check the invitation. Explain purpose, expected effort, how answers will be used and whom to contact.
- Test the experience. Try the survey on the devices and languages respondents will use, including accessibility needs.
- Test the records. Submit representative answers and inspect the stored fields, identifiers, dates and missing-value handling.
- Assign an owner. Identify who monitors collection problems and who approves changes.
- Plan follow-up. Set a proportionate reminder process and a route for questions or corrections.
- Record changes. If wording or logic changes during collection, preserve the version and assess the effect on comparability.
During collection, monitor completion patterns and common points of confusion. Investigate sudden changes in missing answers, unexpectedly repeated submissions or a group that has not responded. Resolve the cause without silently changing the meaning of the dataset.
Validate at entry, then review after collection
Entry checks can prevent avoidable errors, such as an impossible date or a missing required identifier. They cannot tell whether a respondent understood the question, gave a thoughtful answer or described the right reporting period. Validation reduces some cleanup work; it does not make later review unnecessary.
- Duplicates: distinguish an accidental repeat from a legitimate second response or correction.
- Missing values: keep unanswered, not applicable and excluded records distinguishable.
- Unexpected answers: investigate before deleting; an outlier may be a real experience.
- Corrections: retain the reason and original value when needed to reconstruct the result.
- Coverage: compare who responded with the intended group, using the information legitimately available.
Keep a short decision log for exclusions and corrections. A cleaned dataset should remain explainable to someone who did not perform the cleaning.
Connect the analysis plan to the collection design
Before calculating a percentage, specify the denominator. A fictional survey has 200 eligible invitees, 120 respondents and 90 answers to a particular question. If 45 of those 90 answers report an access problem, the result is 50% of people who answered that question—not 50% of invitees and not automatically 50% of all customers.
For repeated surveys, distinguish the full respondent groups at each time from the matched group that answered both. A change in the mix of respondents can affect a comparison. State the matching rules and missing follow-up count beside the result.
For open-ended answers, define the themes, review ambiguous cases and retain supporting text. Keep themes with the relevant structured records where permitted, so the team can ask what people with a low score said without rebuilding a separate join. A theme count and a person count may differ if people can mention several themes.
See qualitative and quantitative analysis for a worked example, and survey data analysis for the next stage.
What to test in survey collection software
Many survey tools support identifiers, validation, integrations and analysis. Avoid choosing on an assumption that every tool produces anonymous, disconnected rows. Test the configuration needed for your own collection and the ongoing work around it.
Sopact’s approach connects collection, record context, reviewed analysis and governance. The practical benefit to test is whether the operational team can maintain recurring surveys and answer questions across records with less repeated preparation. That still requires clear definitions, permissions, data checks and human review.
Use one complete cycle in the evaluation: create the collection, submit a correction, add a later response, change a definition and produce a reviewed result. Include the staff time needed for setup, reconciliation and reporting. A fast first form does not establish a low-maintenance recurring workflow.
Report how the evidence was collected
Readers should be able to understand who was invited, who responded, when collection occurred, how the questions were delivered and what limitations affect interpretation. Keep the question wording, response options and relevant versions available with the analysis record.
AAPOR’s disclosure guidance identifies collection methods, population and sampling information among the details that support transparency. Use that principle to make your own report understandable, even when it is an internal operational survey rather than a public poll. AAPOR disclosure standards.
Frequently asked questions
What is the difference between a questionnaire and survey data collection?
The questionnaire contains the questions. Collection also includes selecting and contacting respondents, handling responses, checking quality and documenting how the evidence was obtained.
Should every survey identify the respondent?
No. Choose identification only when it serves the purpose and is consistent with what respondents are told. Anonymous group feedback and identified longitudinal collection answer different questions.
Does field validation remove the need for cleaning?
No. It can prevent certain entry errors, but duplicate records, misunderstood questions, missing data and comparability still need review.
Can different sites use different surveys?
Yes. Agree a shared core for the comparisons the organization needs, preserve useful local questions and document which measures can be combined.
Can a later survey attach to an existing participant?
Yes, with an appropriate identifier, consent and access arrangements, and tested matching rules. A stable ID helps linkage but does not guarantee that every source record is correct.
What should we do before sending the survey?
Define the decision and population, test the questions with relevant respondents, validate the technical flow, confirm the analysis plan and assign responsibility for collection and corrections.
