Start with the intended use—not the file itself
The same paragraph may require a different approach in a contract, mobile interface, or voice-over script. Before work begins, explain who will read the content, where it will appear, and what the audience should understand or do next.
Context enables the language team to make informed decisions about terminology, tone, formality, sentence length, and cultural references before those choices become review queries.
Resolve ambiguity in the source content
Resolve tracked changes, label tables and images clearly, and identify any text that should remain untranslated. If several files repeat the same product names, legal terms, or technical expressions, provide the approved wording with the complete file set.
- Provide editable source files where possible
- Explain abbreviations and internal names
- Mark non-editable or reference-only text
- Include previous approved translations
Assign clear ownership of terminology
A concise list of approved terms is more valuable than a large, unreviewed spreadsheet. Identify who can approve new terminology and whether those decisions should apply only to the current project or become part of the organisation’s long-term language assets.
Plan the review process before translation begins
Choose reviewers who understand both the subject matter and the target audience. Give them the same brief as the translation team and consolidate their comments in one place. Clear, contextual feedback protects consistency and strengthens future projects.