What is a longitudinal survey?
A longitudinal survey collects information over time to investigate change or continuity. In a panel survey, the same units are followed across waves, allowing their responses to be connected. Other repeated survey designs track a defined population using different samples and support population trends rather than matched individual change.
The units may be people, member organizations, customer accounts or sites. Define which you intend to follow. If an organization's representative changes between years, you may still have an organizational series, but not a series of answers from the same person.
This guide focuses on planning and fielding repeated surveys: questions, timing, invitations, linkage, response coverage and the report-back process. For wider research choices, see longitudinal studies.
Choose panel, cohort or repeated population sampling deliberately
Scroll horizontally to see all columns →
| Term | What it describes | What to specify |
|---|---|---|
| Panel survey | Repeated responses from the same selected units | How units are linked, followed and retained |
| Cohort survey | A survey concerning a group sharing a characteristic or starting event | Whether the same units or different samples of the cohort are surveyed |
| Repeated cross-sectional or trend survey | Repeated samples from a defined population | How sampling and measurement remain comparable |
A cohort can be followed as a panel; the terms are not mutually exclusive. A panel can examine individual change, while a repeated cross-section can examine population trends. Do not select a design merely because one sounds more rigorous.
An employee-listening program may prioritize anonymous population feedback. A participant follow-up study may need linked observations. Both can be useful if the collection and the claims match.
Begin with a question that needs another wave
Ask what will be learned from contacting people again. Examples include whether a skill is being used, whether a customer issue remains unresolved or how a member organization's activity changes year to year.
Choose timing based on that question. A follow-up should allow the relevant experience to occur. A survey about applying a new skill is premature if people have not had an opportunity to use it; a service check-in may need a shorter interval.
Two observations can show a difference. Additional waves can reveal more of a trajectory, but each adds burden and administration. More waves are not automatically better, and even several observations do not by themselves prove causation.
Document the intended schedule, acceptable response window and actual dates. Irregular timing can be analyzed when properly recorded and modeled; it is not automatically fatal to the study.
A practical survey plan for a member network
This fictional example follows member organizations across annual reporting periods. The network wants to understand service use and whether members can obtain useful support. The reporting unit is the organization; the person completing the return may change.
Scroll horizontally to see all columns →
| Part | Example collection | How it is maintained |
|---|---|---|
| Registration context | Organization key, region and authorized contact route | Collect once where appropriate; update changed details |
| Shared annual core | Defined service use, usefulness rating and reporting period | Use agreed wording, scale and denominator rules |
| Local questions | Topics relevant to a chapter or member type | Keep separate unless their meanings support comparison |
| Open context | What helped or prevented access to the service? | Retain original responses and review the analysis |
| Follow-through | What clarification is needed and what summary returns to members? | Assign an owner and a report-back date |
The shared core should be as small as the comparison requires. Local contributors do not need an identical form for every purpose. A data dictionary explains which fields can be combined and which describe different concepts.
A change in representative is recorded because it may affect the account of service experience. The network should not silently describe an organizational rating change as a change in one individual's opinion.
Design stable questions and useful follow-ups
Separate recurring measures from questions that are specific to a wave. For example, a stable item may ask about a defined service during the reporting period, while a rotating item asks about a newly introduced process.
Keep the scale and reference period clear. “How useful was the service you used during April–June?” has a different population from a question sent to every registered member, including people who did not use it. Provide a suitable route for non-users rather than forcing a rating.
An open question can add context: “What made the service easier or harder to use during this period?” It should not assume a problem or require people to explain a change they may not recognize.
Pilot wording, routing and collection modes. If a question must change, record the version and assess comparability. Do not preserve a demonstrably poor question forever merely to avoid change, but do not hide the break in a trend either.
Link responses appropriately and test exceptions
For a panel, use a stable unit key independent of contact details where possible. A changed email should not automatically create a new organization or participant. Maintain the correct contact route separately.
Test returning contributors, corrected submissions, shared devices, forwarded invitations and repeated responses. The appropriate controls depend on the collection context. A link that is convenient to use still needs to connect the response to the intended unit.
Do not assume that every unmatched record is a dropout. It might reflect a wrong identifier, an import issue, a duplicate registration or a genuinely different unit. Review uncertain links rather than forcing a match to improve the completion figure.
For anonymous repeated surveys, be explicit about what can and cannot be linked. Never promise anonymity while secretly using identifiers for individual tracking.
Track invitations, responses and usable matches separately
In this fictional annual panel, 100 organizations are invited. Eighty submit a response. Seventy-five responses are confidently linked to the intended organization and period; five need reconciliation. Seventy contain valid answers to the recurring usefulness item in both years.
The response rate among the invited organizations is 80%. There are 75 confirmed linked returns and 70 valid item pairs. These are different measures of coverage. Calling all 80 responses a complete matched dataset would hide the remaining work.
Keep reminders proportionate and accessible. Explain the value of participating and return something useful to contributors. Record known reasons for nonresponse when appropriate, while respecting decisions not to continue.
Attrition may be selective, but its direction is not known from the count alone. Do not assume that everyone who stopped answering had a worse experience or that the remaining sample necessarily exaggerates improvement.
Compare waves with the population visible
For an individual or organizational change question, describe the valid matched set and its coverage. For a population-trend question, use the appropriate repeated-sample design and analysis. Do not insist that only complete pairs can ever be analyzed; methods for incomplete panels exist under assumptions.
Report the relevant wave totals and comparison population. A difference between all-response means and matched means can indicate a composition issue, but it does not directly measure the full bias from missing data. The unobserved outcomes are still unknown.
Check question versions, respondent roles, collection modes and timing before interpreting the change. A clearer question or different sample can move a score even when the underlying experience has not changed in the same way.
Use longitudinal data analysis for method selection and a worked example. For the record layout, see long and wide data formats.
Review incoming evidence without overstating early results
Monitoring collection can reveal a broken invitation, confusing wording or a group that has not yet responded. Addressing those issues during the fieldwork period can reduce avoidable rework.
Early summaries are provisional. The first responses may come from a different mix of people or organizations than the eventual sample. Separate a specific request that needs attention from a population conclusion that requires more evidence.
If changing the collection process mid-wave, record the change and consider its analytical effect. Improvements should make the process more usable without erasing the history of how the data was obtained.
AI can help organize open text, but it can also misread context or generate an unsupported explanation. Review suggested themes, preserve original wording and keep important decisions with the responsible team.
Evaluate the complete repeated-survey workflow
A platform demonstration should include more than sending a second form. Test a returning unit, a changed contact, a missing wave, a corrected record, a local question and a restricted source. Inspect the calculations and the report a contributor or reviewer receives.
Sopact's relevant fit is helping operational teams connect collection, analysis and governance across recurring evidence. Confirm how definitions, permissions and exceptions are maintained and which steps require configuration or integration.
Evaluate ongoing work: preparing waves, supporting contributors, reviewing matches, checking analysis and returning results. Do not rely on a promise that one identifier eliminates all matching errors or that analysis happens without review.
For reporting, use the impact report guide and report examples. Include coverage and limitations alongside the trend.
Watch: repeated surveys and connected records
This companion video introduces longitudinal survey evidence. Use the collection checks above to test the approach against your own unit, schedule and privacy commitments.
Frequently asked questions
How many waves does a longitudinal survey need?
It needs repeated observations, with at least two time points for a basic comparison. Additional waves should serve a clear question and allow for contributor burden, timing and analysis requirements.
Can a cohort survey follow the same people?
Yes. Cohort describes the group's defining characteristic or starting event; a cohort can be followed as a panel. Explain the actual sampling and linkage rather than treating the labels as mutually exclusive.
Must every wave use identical questions?
Keep intended recurring measures comparable, but allow justified changes and wave-specific questions. Record versions and disclose breaks or uncertainty in comparison.
Does the gap between matched and unmatched averages measure attrition bias?
No. It can reveal a composition difference in observed data, but it does not establish what missing units would have reported. Assess missingness and assumptions explicitly.
Do all local teams need the same survey?
No. A limited shared core with agreed definitions can support comparison while local forms address different needs. Combine only fields whose meanings and coverage justify it.
What should be reported for each wave?
Report the eligible and invited population where known, responses, usable observations, valid matches for the analysis, timing, measure versions and important limitations.
Choose your next step
ASME
Explore how a membership organization uses stakeholder evidence. The annual panel example above is fictional.
Read the customer story →