Skip to main content

Translation Workflow

Step-by-step process for translating your surveys

Updated today

This guide walks through the complete workflow for translating your survey from one language to multiple languages.

Overview

The translation workflow has four main phases:

  1. Prepare - Finalize primary language content

  2. Translate - Add language versions

  3. Review - Verify accuracy and quality

  4. Validate - Test translated surveys

Phase 1: Prepare

Finalize Primary Content

Before starting translations:

  • Complete all questions

  • Finalize answer options

  • Add all screening logic

  • Configure conditional rules

  • Include AI follow-up instructions

  • Add stimulus materials

  • Test the primary version thoroughly

Why This Matters

Changes to the primary survey after translation require:

  • Re-translating affected content

  • Re-testing translated versions

  • Potential consistency issues

Take time to finalize before translating.

Review for Translatability

Check your content for translation-friendliness:

Issue

Example

Better Alternative

Idioms

"The ball is in your court"

"It's your decision"

Cultural references

"Super Bowl ads"

"Major sporting event ads"

Ambiguous words

"Right" (correct? direction?)

"Correct" or "Right side"

Slang

"Cool product"

"Appealing product"

Phase 2: Translate

Adding a Language

  1. Navigate to the Translations section of your study

  2. Click Add Language

  3. Select the target language

  4. Choose your translation method:

    • Auto-translate (AI-assisted)

    • Manual translation

    • Import from file

Auto-Translation

Auto-translation provides a starting point:

  1. Click Auto-Translate for the selected language

  2. Wait for translation to complete

  3. Review all translated content

  4. Edit as needed for accuracy

💡 Tip: Auto-translation is a starting point, not a final product. Always review with native speakers.

Manual Translation

For complete control:

  1. Open the translation editor

  2. View primary text alongside translation field

  3. Enter translations for each element

  4. Mark items as complete

  5. Track progress with the completion indicator

Import/Export Workflow

For professional translation services:

Export:

  1. Click Export for Translation

  2. Select format (XLIFF, CSV, or JSON)

  3. Send the file to translators

Import:

  1. Receive completed translations

  2. Click Import Translations

  3. Upload the file

  4. Review imported content

Phase 3: Review

Translation Review Checklist

For each translated element:

  • Accurate - Meaning matches the original

  • Natural - Sounds like a native speaker wrote it

  • Complete - Nothing was missed or cut short

  • Appropriate - Tone matches the survey context

  • Consistent - Same terms used throughout

Common Issues to Check

Length Issues:

  • Options that are too long for buttons

  • Questions that wrap awkwardly

  • Mobile display problems

Meaning Shifts:

  • False friends (words that look similar but mean different things)

  • Subtle meaning changes

  • Lost nuances

Cultural Mismatches:

  • References that don't apply

  • Scales that don't translate (e.g., school grades)

  • Assumptions about local knowledge

Review Process

  1. Self-review - Read through all translations

  2. Native speaker review - Have a native speaker check

  3. Back-translation (optional) - Translate back to original to verify meaning

  4. Side-by-side comparison - View original and translation together

Phase 4: Validate

Testing Translated Surveys

For each translated version:

  1. Generate test link for that language

  2. Complete the survey as a participant would

  3. Check all paths:

    • Conditional logic branches

    • Screening question outcomes

    • Error messages

  4. Verify display:

    • Text fits properly

    • Mobile view works

    • All elements visible

What to Look For

Element

Check For

Questions

Readable, complete, properly formatted

Options

Fit in buttons/fields, no cut-off text

Matrix

Rows and columns display correctly

Validation

Error messages appear in correct language

Progress

Indicators work properly

Documenting Issues

When you find problems:

  1. Note the question/element affected

  2. Describe the issue

  3. Suggest a fix

  4. Mark for re-translation if needed

Maintaining Translations

When Primary Content Changes

If you modify the primary survey:

  1. Added questions - Translate new content

  2. Changed wording - Update translations

  3. Deleted questions - Remove from translations

  4. Logic changes - Verify translations still work

Sync Process

When the primary version changes:

  1. The system flags affected translations

  2. Review flagged items

  3. Update translations as needed

  4. Re-test affected paths

Version Tracking

Keep track of:

  • When translations were completed

  • Who reviewed them

  • What changes were made post-translation

  • Any known issues or limitations

Quality Assurance Checklist

Before Launch

For each translated language:

  • All content is translated

  • Native speaker has reviewed

  • Survey has been tested end-to-end

  • Conditional logic works correctly

  • Screening questions function properly

  • Mobile display is acceptable

  • Error messages appear in correct language

  • Completion page is translated

Launch Readiness

Criterion

Status

Primary version finalized

All languages added

All content translated

All languages reviewed

All languages tested

Stakeholder approval

Tips for Efficiency

Speed Up Translation

  • Use auto-translation as a starting point

  • Create a glossary of key terms

  • Translate similar surveys together

  • Reuse translations from previous studies

Reduce Rework

  • Finalize primary content before translating

  • Test thoroughly at each stage

  • Document translation decisions

  • Keep primary and translations in sync

Quality Without Delays

  • Prioritize high-impact content

  • Use native speakers for review (not just translation)

  • Test real survey paths, not just text

  • Build in buffer time for revisions

Did this answer your question?