A translation can be grammatically elegant and still change the decision a reader makes. An interpretation can sound fluent and still leave out the sentence that matters. The Gold Standard of Translation and Interpretation Services is therefore not simply a promise of bilingual ability. It is a managed process that preserves meaning, purpose, dignity and accountability when information moves across languages.
Consider a fictional school preparing a permission form for an outdoor activity. The source says parents may decline one optional segment while permitting the rest. A translated form makes the segment sound compulsory. Everyone receives a beautifully formatted document, yet the consent decision has changed. That is the kind of failure a high-standard service must catch before distribution, not apologise for afterward.
Translation generally concerns rendering written content into another language; interpreting conveys spoken or signed communication in real time or near real time. Both require skill, but they involve different workflows and types of risk. ISO 17100:2015 addresses translation-service processes; ISO 18841:2018 addresses general interpreting services. They are useful reference points, not evidence that any named provider is automatically certified.
The language-service chapter index
Follow the complete journey from an ambiguous source to the words that a reader or listener can genuinely use.
1. Ask what the message must let someone do
A menu, a research abstract, a medical appointment explanation, a school consent form and a marketing campaign do not share the same success criteria. Start with who will use the message, which decisions depend on it, which language variety is appropriate and which words cannot be altered without review. ‘Make it sound natural’ is not a complete brief when legal rights, money, dates or personal safety are involved.
Before quoting, identify target languages, audience, document purpose, format, delivery channel and permitted adaptations. A website may need accessible navigation and culturally suitable labels, while an examination notice may need strict fidelity to eligibility rules. Good scoping protects the client from ordering the wrong service.
Back to chapters · Next chapter
2. Distinguish translation, localisation and interpreting
Translation transfers written meaning. Localisation adapts content for a particular market or audience, sometimes including formats, conventions, imagery and interface design. Interpreting enables conversation between people using different spoken or signed languages. These services overlap in language knowledge, but a skilled translator is not automatically qualified to interpret a live consultation.
Tell the client whether they need a written document, consecutive interpreting, simultaneous interpreting, remote interpreting or specialist review. Do not promise that a text-only workflow can cover the pressures of fast dialogue, tone, turn-taking, confidentiality and speakers interrupting one another.
Back to chapters · Next chapter
3. Build the source-of-truth before the first word is translated
Many translation problems begin in the source. A document may contain undefined abbreviations, inconsistent product names, contradictory dates or a passage that has not yet been approved. Translators should have a route to query ambiguities and record the answer. A definitive, version-controlled source protects everyone.
For example, if one version says the excursion ends at 3:30 p.m. and another at 4:30 p.m., the translator should not guess which is correct. The accountable content owner must resolve the conflict. That source correction should flow into every target language instead of leaving the linguists to make inconsistent independent judgments.
Back to chapters · Next chapter
4. Assign people by subject and language direction
Language fluency is necessary but not sufficient. A scientific report needs technical comprehension; a literary text requires attention to voice; a public information notice calls for clarity and careful definitions. The right qualifications depend on service type, language pair, domain, risk and client specification.
Map roles explicitly: project manager, translator, reviser, subject reviewer and final approver where appropriate. In interpreting, consider suitability for the setting, technical vocabulary, impartiality, preparation material and working conditions. A bilingual staff member can sometimes help informally, but should not quietly become the sole authority for a high-stakes specialist message.
Back to chapters · Next chapter
5. Decide what must remain identical and what may change
Names, figures, dates, units, eligibility conditions and contractual distinctions often require exact control. Idioms, sentence structures and cultural references may need careful adaptation to preserve their intended effect. Good work balances fidelity with usability instead of choosing between literal awkwardness and free invention.
Prepare a glossary and a decision log for terminology with multiple plausible translations. When ‘school level’, ‘grade’ or ‘stream’ carries a precise local meaning, explain the concept rather than choosing a superficially similar foreign term. Record approved translations of recurring programme names so readers do not encounter a different label each month.
Back to chapters · Next chapter
6. Use a real revision stage
A translation that has been checked only by its own author may retain blind spots. For work using the core processes of ISO 17100, revision is an important distinct function; the exact service agreement should specify what quality stages are included. A second competent reviewer can compare source and target for omissions, changed modality, inconsistent terminology and numerical errors.
Review must be purposeful. One person checks meaning and accuracy; another may validate domain-specific consequences or layout. Calling a spelling check ‘independent review’ is misleading. Conversely, do not impose expensive specialist review on a low-risk task without explaining the purpose and obtaining an appropriate brief.
Back to chapters · Next chapter
7. Treat numbers, negation and consent as high-risk
Small marks can carry large consequences. ‘Not required’ versus ‘required’, ‘before’ versus ‘after’, ‘per day’ versus ‘per week’, decimal separators and time-zone references need explicit verification. Wording that changes permission from opt-in to compulsory is not a stylistic disagreement. It can change what a person agrees to do.
Set a high-risk review pass for money, dosage instructions, dates, times, ages, thresholds, rights and safety warnings. Mark any unresolved source ambiguity. A critical discrepancy should stop release until the content owner decides the intended meaning; the deadline must not silently override the meaning.
Back to chapters · Next chapter
8. Prepare interpreters before the meeting
Interpreting happens under time pressure. Provide the purpose, agenda, names, specialist terminology, language varieties, expected duration, technical setup and any conflicts of interest in advance. If the meeting concerns a sensitive or specialist topic, book appropriately trained interpreters and plan how participants can ask for clarification.
Speakers should use manageable turns, avoid jargon where possible and allow the interpreter to preserve complete statements. Establish whether interpretation is consecutive or simultaneous and how confidential discussions are handled. If someone says ‘I did not understand the question’, the system should make space to repeat or rephrase it.
Back to chapters · Next chapter
9. Protect impartiality, privacy and trust
Interpreters and translators may encounter personal, commercial, medical, academic or legal information. Access should be limited to the work needed; agreements should identify confidentiality expectations, storage, retention and secure transfer. A translation memory or AI tool can become an unintended disclosure route if text is uploaded without authorisation.
Interpreters should convey what was said without making undisclosed decisions for participants. They may flag ambiguity, request clarification or explain a culturally relevant misunderstanding through an agreed process. They should not secretly become the negotiator or adviser. Conflict-of-interest and role boundaries deserve explicit attention.
Back to chapters · Next chapter
10. Use machine translation under accountable controls
Machine tools can help with drafts, terminology searching and high-volume routine material. They also invent meanings, flatten distinctions, mishandle rare language pairs and reproduce errors with great fluency. The right question is not whether AI was used, but who decided it was suitable, whether confidential content was protected and how a competent human verified the result.
Do not describe raw machine output as if it had followed ISO 17100’s translation workflow. The standard’s published scope distinguishes its core translation processes from raw machine translation plus post-editing. Specify a separate, truthful workflow if machine output or post-editing is involved, and increase checks for consequential content.
Back to chapters · Next chapter
11. Design the layout so the meaning survives publication
A perfect target-language sentence is still unusable when text overflows the page, a button is cut off, a date reverses direction or a PDF does not support the script. Test the final file, not only the editable translation. Consider fonts, reading direction, line breaks, alt text, subtitles, form labels and compatibility with devices actually used by the audience.
For public-facing sites and online forms, accessibility matters alongside language accuracy. The W3C Web Content Accessibility Guidelines provide a recognised framework for digital accessibility. A multilingual service should test whether people can navigate and complete the task in their language, not merely see a translated heading.
Back to chapters · Next chapter
12. Control versions across every language
Suppose a school changes the return time after a form is translated into four languages. Which four files are now obsolete? A dependable translation service maintains a source version, target version, approval status, publication date and change log. A changed sentence should trigger an impact check across all affected languages and formats.
Beware the apparently small last-minute edit. Moving a deadline, changing a fee or adding a new condition is substantial even if only six words were changed. Establish a release gate: the owner signs off the source, language reviewer signs off the target, and publication staff confirm that the approved file is the one actually used.
Back to chapters · Next chapter
13. Give readers a correction route they can understand
People may notice a mistranslation after publication, especially in a community language or a specialised domain. Provide a visible way to report the exact passage and its effect. Classify corrections by risk. A confusing heading is different from a wrong safety instruction, deadline or consent term.
When a consequential translation is wrong, correct the document and notify affected users through appropriate channels. Do not silently replace the file and assume the earlier readers will discover the change. Record the decision, affected versions, distribution route and verification that the corrected message arrived.
Back to chapters · Next chapter
14. Measure comprehension, not just words delivered
Word count, turnaround time and per-language budget are useful production measures. They say little about whether the final reader understood the instructions or whether a live participant had a fair opportunity to speak. Measure meaningful errors, queries unresolved at release, revision rework, comprehension testing and corrected copies reaching people.
Test a sensitive form with representative users where practical. Ask what action they believe the text permits or requires. If readers consistently misunderstand a key condition, that is evidence about the communication even when linguists agree the grammar is technically defensible.
Back to chapters · Next chapter
15. Use a fictional release exercise to test the whole chain
Return to the school excursion form. The source writer confirms that one activity is optional. The project manager marks consent as high risk, the translator drafts the text, a qualified reviser catches the changed meaning, the school approves the corrected language and staff test the actual PDF with its checkboxes. When the English source is updated, all target versions receive an explicit update request.
The exercise demonstrates why translation quality is a system. The correct decision emerges from source ownership, professional language work, independent checking, publication control and a correction path. No single person is expected to rescue a broken process by being unusually brilliant.
Back to chapters · Next chapter
16. Make multilingual access a continuing service
Language needs change as communities, products and rules change. Revisit glossaries, reviewer competence, vendor performance, accessibility feedback and records of significant corrections. Document what should happen when a linguist is unavailable, a live event runs long or a source document arrives late.
The gold standard is a person understanding the same essential promise, choice, risk or instruction regardless of the language route they used. Excellent language services make that result normal through disciplined collaboration rather than declaring that fluent-sounding output must be correct.
The meaning-preservation test
Use this release table when a message will affect rights, decisions, health, learning or eligibility.
| Potential failure | Control that detects it | Release evidence |
|---|---|---|
| Optional activity becomes compulsory | Source-to-target comparison of consent wording | Both versions allow the same decision |
| Return time changes across languages | Numerical and date check with version control | All language versions show the approved time |
| Unqualified interpreter faces a specialist discussion | Domain and language-direction matching, preparation | Appropriate interpreter and session conditions confirmed |
| AI output alters a warning | Human review proportionate to risk | Critical warning verified against approved source |
| Correct PDF is not the published file | Final-layout and release-version check | Approved file is the file distributed |
Questions readers and service buyers often ask
Is a literal translation always the safest? No. Literal wording can mislead when an idiom, concept or local term has no exact equivalent. The correct target is faithful meaning under the agreed purpose, with high-risk details tightly controlled.
Is interpreting just translation spoken aloud? No. Interpreting is a live interaction requiring turn management, listening, delivery and often specialist preparation. Written translation allows different editing and review stages.
Can AI take responsibility for a wrong translation? Accountability still belongs with the organisations and professionals specifying, reviewing and releasing the work. A clear contract should say how technology and human checks are used.
References and eduKate reading routes
Standards and accessibility references: ISO 17100:2015 Translation services; ISO 18841:2018 Interpreting services; W3C Web Content Accessibility Guidelines. Standards describe applicable processes; they do not imply that any particular vendor is certified.
Connected eduKate guides: Gold Standard Case Study 28: the translated permission form; multilingual communication and translation literacy; public-sector multilingual services.