Feedback and survey design
Keeping a multilingual event survey equivalent
Your members answer in English, Bahasa Melayu or Chinese, and you need to know whether the three versions are really asking the same thing.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Language equivalence means every item and every scale label carries the same meaning in each version, so that answers can be pooled or compared. Translate from one master, have a second person review each item against the master, and test the wording with a few readers before it goes out.
Where an item cannot be made equivalent, change the item or report that language separately. Do not merge answers you have reason to think mean different things.
Why a direct translation is not enough
A literal translation can keep the words and lose the meaning. Common culprits are scale labels, polite phrasing and terms that sound natural in one language and formal or odd in another.
If the Malay version reads as more demanding than the English one, the scores may differ because of wording, not because of the event.
A five-step review sequence
- Fix one master version, usually the one the survey designer thinks in, after the feedback objectives and question selection are settled.
- Ask a competent translator to produce each other version from the master, not from another translation.
- Ask a second person who has not seen the master to review each version, then compare item by item with the master.
- Run a short read-through with two or three people per language who match your real respondents. Ask them to say each question back in their own words.
- Record every change in a log, update the master if a wording problem was found there, and freeze all versions together.
Where equivalence usually breaks
| Element | What can go wrong | What to check |
|---|---|---|
| Scale labels | Agree, mostly agree and satisfied sit at different distances in different languages. | Compare the labels as a set. See response scales. |
| Event terms | Words such as session, workshop or networking have more than one common rendering. | Use one agreed glossary term per concept. |
| Tone | A casual English prompt becomes very formal, or the reverse. | Ask readers if the question feels the same in effort and tone. |
| Negatives and double questions | One language handles them more clearly than another. | Keep one idea per item in every version. |
| Names and examples | An example familiar to one group means little to another. | Use neutral examples or the same example everywhere. |
What to do when an item will not match
- Reword the master so a simpler idea translates cleanly.
- Drop the item if it does not serve an objective in the first place.
- Keep the item but report that language separately and say why.
- Never average across versions when a reviewer has flagged a meaning difference.
Respondents who read more than one language
Some respondents will open two versions or answer in a language that is not their first. Give each person a clear way to choose a language and keep the language choice as a recorded field, so you can see differences later.
For a hybrid event, make sure the online version offers the same language options as the printed or on-site one.
Worked example · Fictional example
A three-language member survey for a logistics association
Fictional organisation and figures, written to show the review process.
Persatuan Fiktif Pengurus Logistik runs a one-day members' forum and plans a six-question survey in English, Bahasa Melayu and Chinese. The secretariat writes the English master, a translator produces the other two, and a second reviewer compares them.
The reviewer flags that the Malay and Chinese labels for the middle of the satisfaction scale read as mildly negative, while the English label reads as neutral. Three members per language read the questions aloud and confirm the problem. The secretariat replaces the labels with a set the readers agree is evenly spaced, and logs the change in the review table below.
| Item | Master wording | Reviewer finding | Action |
|---|---|---|---|
| Q3 overall usefulness | How useful was the forum for your work? | Equivalent in all three versions. | None |
| Q4 scale midpoint | Neither agree nor disagree | Malay and Chinese read as mildly negative. | Labels replaced after reader test |
| Q5 networking | How was the networking? | Two Chinese readers took it as food and drink time. | Reworded to ask about useful conversations |
Use this yourself
Survey language equivalence review table
Copy this into a spreadsheet, one row per item and scale label, and complete one block per language.
- Item number and master wording:
- Language and translator:
- Reviewer (not the translator) and date:
- Meaning matches the master? Yes / No / Unsure:
- Tone and effort match? Yes / No:
- Scale labels read as evenly spaced? Yes / No:
- Reader test done with how many people:
- Change made, and was the master also changed?
- Decision if not equivalent: reword / drop / report separately:
- Final version frozen on (date), all languages together:
Handle it in-house, or bring in help?
Your team can usually handle this when
- Your team has fluent speakers of each language who can act as independent reviewers.
- The survey is short and uses plain, single-idea questions.
- You only need to look at each language's results on its own.
Outside planning help earns its fee when
- You plan to combine or compare results across languages for a board paper.
- Nobody on the team can review one of the languages independently.
- The survey is long, uses specialist terms, or must be signed off by several committees before release.
Want the survey plan documented across languages?
If your team needs the language review, glossary and sign-off steps written into the working plan, an Event Blueprint can set out the survey scope, who reviews each version and when the versions are frozen. The questions themselves stay yours; the plan makes the process repeatable. You can also build the question set first with the feedback questionnaire builder.
Questions organisers ask
Is back-translation enough to prove equivalence?
It is a useful check, but it can hide problems when both translators make the same literal choices. Pair it with an independent reviewer and a short read-through with real respondents.
Can I use machine translation for the first draft?
You can use it to speed up the first draft, but a competent person should review every item and scale label against the master before release. Treat the draft as unreviewed until that is done.
Should I publish results separately by language?
If any item was flagged as not fully equivalent, report that item separately by language. With small numbers in one language, say so plainly rather than drawing conclusions from a handful of responses.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.