How do I set up a recurring employee survey programme?
Zuletzt aktualisiert 28 Juli 2026 |
Drucken
A recurring employee survey programme is useful when you want to measure employee feedback repeatedly over time, for example through an annual engagement survey, quarterly pulse surveys, follow-up surveys after action planning, or year-over-year employee survey waves.
This guide explains one common technical setup pattern for employee survey programmes. It should be read together with the generic guides on recurring Quest programmes, respondent data, Hidden Identity, subgroup reports and wave comparison.
Before you start decide how the programme should be structured:
- One ongoing Quest
- use this when you want to add new send-outs to the same Quest and separate periods with time filters. This setup can support timeline-style reporting when data is collected in the same Quest.
- One Quest per wave
- use this when each survey wave should have a clean separate dataset. You can copy the previous Quest and compare the different Quests later in Results.
- Pulse or follow-up Quest
- use this when a shorter survey follows an annual survey and focuses on selected topics or groups.
For meaningful comparison over time, keep question wording, answer scales, respondent data fields, languages and Hidden Identity settings as consistent as possible.
Recommended workflow:
- Plan the employee survey programme
- Define the cadence, for example annual, quarterly or pulse. Decide which employee groups will be invited, which languages are needed and which reporting levels are required.
- Prepare employee respondent data
- Prepare fields such as Country, Location, Department, Team, Manager Group, Role, Language or Employment Group. Keep field names and values stable across waves if you want to compare results over time.
- Set anonymity and reporting thresholds
- Before publishing, decide whether Hidden Identity or Advanced Hidden Identity is required.
- Build the first survey wave
- Create the questionnaire, translations, distribution method, respondent data and availability settings. Test the Quest before launch.
- Plan distribution for different employee groups
- Use email invitations where individual email addresses are available. For employees without individual email access, consider QR codes, links, Quest Login or password-based access where appropriate.
- Create a reporting master
- Build a report structure for the first wave, for example KPIs, topic summaries, top/bottom analysis, text analysis, filters, comparisons and LiveReports. Test the report before sharing it.
- Create subgroup reports
- Use respondent data and value filters to create subgroup views, for example by country, location, department, team or manager group. Decide whether to create one report per group or use filtered LiveReports.
- Reuse the reporting structure
- For later waves or time periods, copy the reporting master and apply the relevant time filter, value filter or Quest comparison. This helps keep manager and subgroup reporting consistent across cycles.
- Compare results over time
- If you use one ongoing Quest, compare periods with time filters. If you use one Quest per wave, compare the different Quests in Results. Use consistent questions, scales and respondent data to make comparisons reliable.
- Review after each wave
- Check response rate, respondent data quality, threshold issues, report access and whether any question or scale changes affect future comparison.
Important notes
If questions, scales or respondent data fields change between waves, comparisons may still be technically possible, but interpretation can become less reliable.
Timeline graphs are easiest when responses are collected in one ongoing Quest. If each wave is a separate Quest, results can be compared in Results, but may be shown side by side rather than as one continuous timeline.
Questback can support action planning through reports, exports, workshops or external processes, but this guide focuses on the technical setup inside Essentials, not on managing action plans inside the platform.
Related articles:
