Om Academy
Finner du svaret på spørsmålet ditt? Under dokumentasjonen er det informative beskrivelser som hjelper deg å forstå og kunne bruke Essentials funksjonalitet. Gjennom innsiktsarbeid hever du kunnskapsnivået i hele organisasjonen.
How to prepare respondent data for routing and reporting
Respondent data should be prepared before distribution if you want to create different question paths, filter results or create subgroup reports.
Respondent data can include fields such as:
- department
- country
- location
- team
- manager group
- customer segment
- course type
- role
- language
- employment group or other internal categories
Recommended workflow:
- Decide what the data will be used for
- Common uses are routing, filtering, subgroup reporting and comparisons.
- Use clear field names
- Choose field names that are easy to understand and reuse, such as Country, Department, Location or Manager Group.
- Standardise values
- Keep values consistent. For example, use either “Germany” or “DE,” but not both.
- Avoid unnecessary detail
- Do not include fields that are not needed. Too much detail can make reports harder to manage.
- Check small groups
- If respondent data will be used for filtered reports, check whether some groups are too small to report safely.
- Test routing and filters
- Use test respondents to confirm that routing works correctly and that reports show the expected groups.
- Keep fields consistent across waves
- If you want to compare results over time, use the same respondent data fields and value structure in future waves.
Related articles:
- How to use Routing with Respondent Data for routing based on respondent fields
- How to use Hidden Identity for identity and threshold considerations
- How to use Respondent Data
- How to use Respondent Data Field Manager
- How to Validate your Respondent Data using Questions
- How to use Filters
- How to use Cross-Tabulation
- How to create a new Value Filter
