When To Use Multilingual Surveys
Multilingual research surveys are useful when participants should answer in different languages, when a study spans countries or communities, or when translation is required for ethical and accessible participation. Treat each translation as a full research instrument, not as a cosmetic copy of the source survey.
Plan how participants reach the right language, how translated variables map back to the same analysis columns, and how reviewers will test every language path before launch.
Plan Translation Before Building
Step 1: Finalize the source instrument. Write clear source prompts, answer labels, instructions, validation messages, and end screens before translation begins.
Step 1: Finalize the source instrument
Step 2: Decide the language paths. Identify which languages participants need and whether they will choose a language, receive a language-specific link, or be routed by a panel variable.
Step 2: Decide the language paths
Step 3: Build translated blocks. In Block Builder, translate prompts, options, row labels, column labels, validation text, button-adjacent instructions, and end screens.
Step 3: Build translated blocks
Step 4: Check Flow. If language controls routing, open Flow and confirm each language path reaches the correct blocks.
Step 4: Check Flow
Step 5: Pilot with fluent reviewers. Use Preview to test every language path with reviewers who can spot meaning shifts.
Step 5: Pilot with fluent reviewers
Step 6: Export test responses. Confirm respondent language and equivalent variable names appear as expected in Export.
Step 6: Export test responses
Question Type Considerations
Translated answer labels should preserve the same meaning and coding across languages. Pay special attention to Grid Matrix scales, Multiple Choice categories, Conjoint levels, and Short Answer validation rules.
- Scales: keep direction consistent so high recodes mean the same construct in every language.
- Dropdowns: sort choices in a way that makes sense for the translated labels, then confirm the stored values still match analysis needs.
- Short answers: avoid validation rules that assume one alphabet, decimal convention, or date format unless that is intentional.
- Conjoint levels: document any translation that changes level length, tone, or cultural meaning.
- End screens: translate ineligible, quota-full, completion, and debriefing messages, not just the main questionnaire.
Block Builder: Question Type
Export And Analysis Notes
Review exports before launch so your analysis code can identify respondent language and compare equivalent variables across translations. Document source wording, translator notes, back-translation decisions, and any language-specific Flow branches in the codebook for reproducibility.
Export: Data Output