Industry Playbooks
Research workflows for translators are the structured processes for pre-project subject research, terminology research, target-language usage research, and reference source verification — enabling consistent, accurate translations that reflect how professionals in each field actually write.
A translator renders a pharmaceutical clinical trial protocol accurately — every term technically correct, every sentence grammatically sound. The client rejects it. The issue: the translation reads like a bilingual dictionary produced the text, not like a document that pharmaceutical regulatory affairs professionals in the target country would write. Correct terms in wrong registers, accurate content in a style that signals the author is not a native practitioner in this field.
The translation problem isn't usually getting the words right. It's getting the register, the conventions, and the terminology preferences of the target language's professional community right. That requires research — not just "what does this term mean" research, but "how do practitioners in this field in this country write about this subject" research.
Research workflows for translators are the structured processes that produce translations that don't just read correctly — they read as if written by someone who thinks in the target language's professional conventions, not just its grammar.
Pre-project domain research: Before translating a document in an unfamiliar subject area, the translator needs to understand the domain well enough to recognize when a translation choice produces something that real practitioners in that field would recognize as correct. This requires reading authentic target-language documents in the subject area.
Terminology research: For domain-specific terms — especially regulatory vocabulary, technical terminology, and newly coined terms — there may be an established translation that departs from what a direct translation would produce. Research identifies established conventions before the translator commits to a choice.
Register research: Different fields, audiences, and document types require different registers. A regulatory submission for a pharmaceutical company requires different formality, syntax patterns, and vocabulary than a patient information leaflet for the same drug. Research into authentic target-language documents in each register establishes the conventions.
Source verification: Is the source document using authoritative terminology, or has the client's internal usage drifted from the official standards? For regulatory documents especially, verifying that the source terminology aligns with official standards helps the translator produce a target document that also aligns with official standards.
Before beginning translation:
Review the full document first: Skim the entire document before translating. Identify:
Domain orientation (for unfamiliar subject areas): Read authentic target-language documents in the same domain and document type:
This orientation research is most critical when entering a new subject area. After translating 20 pharmaceutical protocols, the orientation is already built — the research becomes more targeted rather than general.
For domain-specific terms without obvious established translations:
Terminology research hierarchy:
For each researched term, document:
False friends and false cognates: Terms that look like obvious translations but are misleading in the target language need particular attention. Document these separately — they're the errors that reviewers catch and clients notice, and they recur across projects in the same subject area.
Terminology is necessary but not sufficient. Authentic-sounding professional translation requires matching register:
Find authentic target-language parallel texts: Parallel texts — documents of the same type and subject area in the target language, produced by native practitioners — are the reference for register and convention:
Register analysis questions:
For regulated domains, verify that the source document's terminology aligns with official standards:
Regulatory document verification: Check that the source document's key terminology aligns with the regulatory framework:
Source inconsistencies with regulatory standards may need to be flagged to the client — translating an inconsistency produces a translation that inherits the inconsistency.
| Stage | Tool | Notes |
|---|---|---|
| Domain orientation | Authentic target-language documents + Wikipedia (for overview) | Never use Wikipedia for terminology decisions |
| Terminology research | Client glossary + IATE (EU) + specialised dictionaries + Linguee | Hierarchy matters |
| Corpus research | Linguee + context-rich corpora + parallel text files | How terms appear in authentic context |
| Regulatory terminology | EU Official Journal + FDA publications + ISO vocabulary | Authoritative regulatory sources |
| Web reference capture | WebSnips | Clip authoritative sources with date |
WebSnips for translation research: Translation research requires gathering and evaluating multiple web-based sources — regulatory body terminology pages, industry association publications, authentic target-language documents, parallel texts. WebSnips captures specific pages with date and source URL, organized by subject area or project. For terminology decisions that may be challenged by the client, a dated clip of the authoritative source (the EU Official Journal translation, the FDA terminology guidance, the ISO standards vocabulary) provides verifiable evidence for the translation choice. For parallel text research, clips of authentic target-language documents from authoritative sources — with dates — support claims about current professional conventions.
A legal translator, Christina Park, translates a German commercial lease agreement into English for a property company's international investor documentation:
Stage 1 — Scoping:
Christina reads through the full 45-page lease before translating. She identifies:
Stage 2 — Terminology research:
Nettokaltmiete / Bruttowarmmiete:
Schönheitsreparaturen:
Stage 3 — Register research:
Christina reviews 3 English-language commercial lease agreements from similar German properties filed with the German Commercial Register (publicly accessible) and 2 JLL Germany investor reports with sample lease terms.
Findings: International commercial property English in Germany uses British English conventions; formal sentence structure; passive voice is common for legal obligations ("the tenant shall be obligated" rather than "the tenant must"); longer sentence structures than US commercial prose.
Confidentiality of source materials: Research using source document content — searching for translation precedents using phrases from a confidential client document — requires care. Using proprietary client terminology in online translation tools or bilingual dictionaries that may log query terms may be a confidentiality concern. Review applicable client agreements.
Official terminology sources and copyright: Many official regulatory and standards terminology sources are publicly accessible and may be cited freely. Some standards vocabulary (ISO) may be copyright-protected — know the terms of use before reproducing standards terminology in client documentation.
Data residency for research tools: Online research tools that process document content may have data residency implications for clients in regulated industries (healthcare, financial services) with data localization requirements. Know where your research tools process and store data.
Mistake 1: Terminology research without checking client preference first. The best translation for a term in general practice may not be what the client uses or prefers. Check the client glossary before researching the general convention — then research the general convention only if the client glossary doesn't address the term.
Mistake 2: Using online machine translation outputs as reference for terminology decisions. Machine translation provides a starting point, not a source of truth. Using MT output as the primary reference for terminology decisions means deriving decisions from AI systems whose training data includes both accurate and inaccurate translations. Authoritative monolingual sources in the target language and official terminology databases are the right reference sources.
Mistake 3: Register research only for unfamiliar domains. Every specialized domain has register conventions — even domains the translator has worked in before. Register conventions shift over time, and different document types within the same domain have different register expectations. A medical researcher's grant proposal and a patient information leaflet are in the same domain but require entirely different register.
Mistake 4: Research without documentation. A terminology research process that produces a decision without documenting the sources consulted, alternatives considered, and rationale chosen is research that can't be defended if the client challenges the choice. Documentation is the evidence that the decision was informed, not arbitrary.
A research workflow for translators is what converts language proficiency into professional translation. Knowing both languages is the prerequisite; knowing how practitioners in the target language's professional community think about and write about the subject matter is what makes translation read as professional writing rather than competent language transfer. The research — domain orientation, terminology hierarchy, authentic parallel texts, source verification — is not overhead. It's the discipline that produces translations that clients don't need to explain to their colleagues.
More WebSnips articles that pair well with this topic.
AI knowledge work for translators is transforming terminology research, pre-translation research, post-editing workflows, and glossary building — while raising fundamental questions about professional judgment, quality thresholds, and the human expertise that remains essential for high-stakes translation.
Knowledge management for translators is the practice of organizing terminology databases, translation memories, client glossaries, style guides, reference materials, and subject-area research — enabling consistent, high-quality translations and building expertise that accelerates every project in a subject area.
A note-taking system for translators must capture terminology decisions with rationale, client preferences, subject-area register observations, project notes, and research findings — building the documented record that makes translations more consistent, research more efficient, and professional expertise more transferable across projects.