Industry Playbooks
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.
A translator specializing in EU regulatory documents has translated the words "Verordnung des Europäischen Parlaments und des Rates" dozens of times. She knows the correct translation is "Regulation of the European Parliament and of the Council" — not "law," not "act," not "ordinance." She knows this so well she doesn't think about it anymore.
A new translator at her firm gets her first EU regulatory assignment. She googles. The first five results are inconsistent. She makes a decision, makes it again differently three pages later. A reviewer catches both inconsistencies. The client gets a revision round that costs everyone time.
This is the simplest case of translator note-taking failure: institutional knowledge in one person's head, inaccessible to another person who needed it, producing inconsistency that looks like carelessness.
A note-taking system for translators is the organized practice of capturing the decisions, conventions, research findings, and client knowledge that accumulates through translation work — in forms accessible enough to be used, not just archived.
Terminology decisions with rationale: Not just "Verordnung = Regulation" but why — EU official translation practice, the distinction from Richtlinie (Directive), and the client convention for this client's specific document types. The rationale is what makes the decision reusable when a similar but not identical term appears.
Client voice and preference notes: Each client has a voice — a preferred register, specific vocabulary preferences, conventions they consider correct even when they differ from general usage. Notes that capture these preferences don't require the translator to re-learn them from project to project.
Subject-area convention notes: How practitioners in the target language actually write about this subject — the sentence structures, the vocabulary preferences, the register signals that mark insider vs. outsider writing. These observations accumulate through research and exposure; organized, they accelerate every project in the subject area.
Research-in-progress notes: During a project, capturing the terminology decisions made and the sources consulted creates both a record and a working glossary for the project — which becomes a reference for future projects and the source for updating the terminology database after the project closes.
During translation, maintain a working project glossary:
During project: Capture as you work:
This working glossary is the raw material for:
For each client, maintain a record that grows with each project:
Client record format:
Updating the client record: After each project, update the record with:
A client record that's updated after every project means the 10th project starts with the accumulated knowledge of the prior 9, not just the prior project's memory.
For each domain worked in, maintain observation notes about the target language's professional conventions:
What to capture:
The "false friend" note: A term that looks like an obvious translation but misleads in the target language is worth capturing the first time it's identified — and reviewing whenever working in that subject area. False friends accumulate as expertise builds; organized, they prevent recurrence.
Example: Subject area: Financial reporting (German→English)
Convention notes:
For reference sources discovered and used during projects:
Research source note format:
The "dated verification" discipline: Regulatory terminology sources change. A source that was authoritative and accurate for EU financial regulation in 2022 may reflect superseded regulatory frameworks. Dating each source note and periodically re-verifying currency prevents citing outdated sources as current authoritative references.
| Context | Tool | Notes |
|---|---|---|
| Project glossary (during project) | CAT tool termbases (SDL MultiTerm, memoQ) | Integrated with translation workflow |
| Post-project terminology database | Excel/Airtable or dedicated terminology tool | Organized by subject area and language pair |
| Client records | Notion / Airtable | One record per client; updated after each project |
| Subject area convention notes | Notion | Organized by subject area |
| Research source notes | Notion + WebSnips | Source notes with dated clips |
WebSnips for translator note-taking: Research source notes are most useful when linked to the actual current state of the source. A note that says "EU Official Journal translations use 'Regulation' for Verordnung" is less verifiable than a note linked to a WebSnips clip of the EU Official Journal's translation of a specific Regulation, dated the month it was consulted. When a client challenges a terminology decision, a dated clip of the authoritative source is evidence; a note in your own record without a verifiable source is your recollection. For subject-area convention research, clips of authentic target-language documents from professional practitioners — with dates — provide evidence for claims about professional writing conventions.
A medical translator, Aiko Tanaka, maintains a systematic note-taking practice for her Japanese→English pharmaceutical work:
Project glossary snapshot (during translation of clinical study report):
| Japanese (source) | English (chosen) | Notes | Source |
|---|---|---|---|
| 有害事象 (Yuugai Jishou) | Adverse Event | ICH E2A standard term; not "side effect" (side effect implies causal relationship) | ICH E2A Guideline (FDA website); WebSnips clip saved |
| 治験薬 (Chikenyaku) | Investigational Product | ICH E6(R2) GCP standard; "investigational drug" is also acceptable per FDA; "IP" abbreviation after first use | ICH E6(R2) (EMA website); WebSnips clip saved |
| 来院 (Raiin) | Visit (clinic visit) | "Clinic visit" more explicit; "visit" acceptable in context where clinical setting is established | Client style guide + CONSORT reporting standards |
Subject-area convention note:
Subject area: Clinical research (Japanese → English)
Register note: Japanese clinical study reports use extensive passive structures and honorific language conventions. English ICH-format clinical study reports are also formal and somewhat passive but considerably more direct than literal translation would produce. Avoid literal translation of Japanese passive constructions; convert to active where English regulatory style permits.
False friend: 安全性 (Anzensei) = "safety" (noun, characteristic) in pharmaceutical context; often tempted to translate as "safety profile" but ICH terminology uses plain "safety" in most contexts (e.g., "safety and efficacy," not "safety profile and efficacy"). Reserve "safety profile" for contexts where the full profile is being described.
Key regulatory terminology note: ICH (International Council for Harmonisation) terminology governs. When ICH guidelines use a specific English term, that term is the default regardless of alternative translations that might read more naturally. ICH E8, E6(R2), E2A are the primary style references.
Updated: October 2026
Research source note:
Source: ICH Guideline E6(R2) — Good Clinical Practice (GCP)
Location: ICH.org → Guidelines → Efficacy → E6
Relevance: Authoritative terminology source for clinical trial documentation
Why authoritative: ICH guidelines are adopted by regulatory bodies in US (FDA), EU (EMA), and Japan (PMDA); terminology that appears in ICH guidelines is the standard for regulatory submissions
Useful for: Any clinical trial documentation terminology; GCP standards vocabulary; clinical study report structure
Date last verified: October 2026
WebSnips clip: ICH E6(R2) main page, October 2026
Confidentiality of project materials in notes: Project glossaries and notes will inevitably contain terminology from client documents. Client agreements often include confidentiality clauses that extend to project materials. Know the applicable confidentiality terms for your project notes, and ensure that notes containing client-specific terminology are stored in appropriately secured systems.
Notes in shared systems: If note-taking systems (Notion, shared drives) are shared with colleagues, consider what client-specific information is appropriate to share vs. what should remain in individual project files. General subject-area convention notes are generally shareable; client-specific terminology decisions from confidential projects may not be.
Personal data in translation memories: Translation memories built from projects involving personal data (medical records, legal proceedings) may contain fragments of personal information. Some data protection frameworks may consider TM content with personal data fragments to have data protection implications. Know the applicable rules for your jurisdiction and industry.
Mistake 1: Project glossary that doesn't survive the project. A glossary maintained during a project and then archived in the project folder is functionally inaccessible for future projects. Transfer key decisions from every project glossary to a searchable terminology database organized by subject area. The project folder is the archive; the terminology database is the knowledge asset.
Mistake 2: Client notes not updated after projects. A client record that was created at the start of the client relationship and never updated doesn't reflect the accumulated decisions and preferences developed across multiple projects. Update after every project: terminology decisions, style feedback received, any new instructions.
Mistake 3: Convention notes that don't capture why. "Don't use X; use Y" is less useful than "Don't use X; use Y because Z (regulatory convention, false friend, register mismatch)." The rationale is what makes the note applicable to similar-but-not-identical situations.
Mistake 4: Research source notes without dates or verification records. "EU Official Journal is the source for this terminology" — which year? Which regulation? Regulatory terminology that was official in 2021 may have been superseded. Source notes need dates and periodic verification to remain trustworthy references.
A note-taking system for translators is what converts translation work from a series of separate projects into a cumulative professional development track. The translator who captures terminology decisions with rationale, updates client records after every project, documents subject-area conventions, and maintains dated research source notes is building expertise that makes each project start further ahead than the last. The translator who finishes each project and moves immediately to the next without capturing what was learned is doing the same research repeatedly — and making the same mistakes when memory fades.
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.
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.