Twelve languages, five columns each
A market research client needs a questionnaire translated into twelve languages, with back translation to check that meaning has been kept. A life sciences client has patient-facing documents that need the same. For each language, your PM builds a spreadsheet: source, forward translation, back translation, comments, reconciled version. Forward and back translators must be different people, and the back translator must not see the source.
Comments go back and forth by email. Someone copies them into the spreadsheet. A reconciled version is agreed, then the client asks for a change, and the PM has to work out which language versions are affected. At the end, a report for each language is formatted by hand.
Why back translation projects are fiddly
- Every item has several versions, and they must stay aligned row by row.
- Independence rules, such as a back translator not seeing the source, are enforced by hand.
- Comments and decisions are made by email and copied in.
- Client changes after reconciliation affect every language, and tracking them is manual.
- Each client wants a different report format.
What it costs
PM time spent on spreadsheets rather than on the linguistic questions. Rows that drift out of alignment, so comments end up against the wrong item. Independence broken by accident, which undermines the whole point of the exercise. Late client changes missed in some languages. And reports that take days to format.
| Step | Spreadsheet approach | Workflow |
|---|---|---|
| Forward translation | Sent as a file | Assigned in the workflow |
| Back translation | Separate file, source removed by hand | Assigned to a different linguist, source hidden automatically |
| Comparison | Comments by email | Comments against each item |
| Reconciliation | Agreed by email, copied in | Recorded with the decision and reason |
| Report | Formatted by hand | Generated in the client's format |
How we build the back translation workflow
- The source questionnaire or document is loaded and split into items, and each item keeps an ID across all languages and versions.
- Forward translation is assigned to one linguist. Back translation is assigned to a different linguist, who sees only the forward translation, never the source, and the system prevents the same person from doing both.
- Back translations are shown next to the source for the reviewer or PM, item by item, and discrepancies are commented on against the item.
- The forward translator responds to comments, and the agreed reconciled version is recorded with the reason for any change.
- If the client changes a source item after reconciliation, every language version of that item is flagged for update.
- The final report is generated per language or across all languages, in the format the client or their protocol requires, including all versions and decisions.
What counts as a meaningful discrepancy, and how it is resolved, remains a linguistic judgement. The workflow keeps the versions, rules and decisions straight.
What changes
Cognitive debriefing and client sign-off can be added as further steps where a project needs them. Each step has its own assignee and deadline, and the item view shows exactly where every language has reached, so the PM can tell the client which languages are ready and which are waiting, without opening twelve spreadsheets to find out.
Every item's versions stay aligned in one place. Independence is enforced, not hoped for. Comments and decisions are recorded against the item, with reasons, so the report writes itself. Client changes are traced across all languages. And PMs can run more languages at once without drowning in spreadsheets.
For clients, the final report is clearer and more complete, which matters when it is part of the evidence for a study or a regulatory submission.
Does this sound like your back translation work?
- Each language has its own multi-column spreadsheet.
- Keeping the source hidden from back translators is done by hand.
- Comments are copied from emails into spreadsheets.
- Client changes after reconciliation are hard to trace across languages.
- Reports are formatted by hand for every project.