Translation work is knowledge work conducted under time pressure, which creates a specific note-taking problem: the terminology decision made during an active translation session needs to be captured before the next term requires attention. The subject matter insight understood while researching a complex concept needs to be captured before the project deadline forces a return to active translation. The client feedback received after delivery needs to be captured before the next project request arrives.
Without structured note-taking, translation work generates knowledge that disappears. The terminology decision made in month three of a client relationship is available in month four only if it was captured somewhere retrievable — not because the translator happened to remember it. The subject matter expertise developed during a complex technical translation is available for the next project in the same domain only if it was captured systematically.
Four templates structure the note-taking contexts that most directly build retrievable translation professional intelligence: terminology research notes, project notes, subject matter research notes, and client and feedback notes.
Template 1: Terminology Research Notes
Terminology research notes capture the investigation of how to express a source language term in the target language — the research process, the sources consulted, the decision made, and the reasoning behind it.
TERMINOLOGY RESEARCH NOTES
Date: [Date of research]
Project: [What project triggered this research — or "general KB development"]
Source term: [Term being researched]
Source language: [Source language]
Target language: [Target language]
SUBJECT AREA:
Domain: [Legal / Medical / Technical / Financial / Other]
Subdomain: [More specific area]
THE RESEARCH QUESTION:
What I needed to find: [The specific question — not just "how to translate X" but "whether X in context Y maps to A or B in the target language"]
SOURCES CONSULTED:
Source 1: [Resource name]
Type: [ ] Official glossary [ ] Regulatory text [ ] Professional association
[ ] Bilingual dictionary [ ] Monolingual dictionary [ ] Other
URL + Archive URL: [If online]
Date published: [Source's own date]
Date accessed: [Today's date]
What it said: [Relevant finding]
Authority assessment: [How authoritative is this source for this term?]
Source 2: [...]
FINDINGS:
Primary target language term: [The authoritative equivalent]
Alternative terms found: [Other terms encountered, with sources]
Field-specific variants: [If term usage varies by professional context]
DECISION:
Term used: [What was chosen]
Why: [Reasoning — especially if not using the most common term]
Confidence: [ ] High (authoritative source + consistent usage) [ ] Medium [ ] Low
NOT TO USE:
Term: [An incorrect or outdated alternative found]
Source that used it: [Where the incorrect term appeared]
Why incorrect/outdated: [The specific problem]
KB UPDATE:
[ ] Terminology KB updated
[ ] Client terminology updated (if client-specific preference)
The "authority assessment" field is the professional judgment field that makes the note useful when the terminology decision is questioned. A term found in an official regulatory glossary has different authority than a term found in a user-generated wiki; documenting this assessment makes the reasoning for the decision reconstructable.
The "NOT TO USE" field is the error prevention documentation. The incorrect term or false cognate encountered during research — the tempting but wrong equivalent — should be explicitly documented so it doesn't get reconsidered in future research on the same term.
Template 2: Project Notes
Project notes capture the context, decisions, and knowledge generated during a translation project — the record that supports consistency within the project and knowledge transfer to future similar projects.
PROJECT NOTES
Project: [Client + document/project name]
Date started: [Date]
Date delivered: [When delivered]
Subject area: [Domain]
Language pair: [Source language] → [Target language]
PROJECT CONTEXT:
Document type: [What kind of document]
Purpose: [What the document is for, who the audience is]
Client-specific requirements: [Style, terminology, formatting, other requirements]
TERMINOLOGY DECISIONS MADE:
Decision: [A terminology choice made for this project]
Source term: [...]
Target term chosen: [...]
Reason: [Why this choice]
[ ] Added to terminology KB
STYLE AND REGISTER DECISIONS:
Decision: [A register or style choice made for this project]
Why: [Reasoning]
SUBJECT MATTER NOTES:
Concept requiring research: [What was unfamiliar]
Understanding developed: [What was learned]
Source: [Where the understanding came from]
[ ] Added to subject matter KB
QUERIES TO CLIENT:
Query: [Question sent to client]
Date sent: [When]
Response: [Client's answer]
[ ] Terminology KB updated if response has implications
LESSONS LEARNED:
Preparation gap: [What I wish I had in my KB before starting]
What I'd do differently: [Process improvement for next similar project]
What worked well: [What to repeat]
POST-DELIVERY:
[ ] New terminology added to KB
[ ] Client feedback received and captured
[ ] Subject matter insights captured
[ ] Reference sources discovered added to KB
The "preparation gap" field is the continuous improvement driver. Capturing what was missing from the KB before starting the project — the terminology that should have been there but wasn't, the subject matter background that required mid-project research — generates the specific KB development agenda that makes future similar projects more efficient.
Template 3: Subject Matter Research Notes
Subject matter research notes capture the understanding developed while researching the domain content of translation work — the comprehension of what the source text means, which is the prerequisite for translating it accurately.
SUBJECT MATTER RESEARCH NOTES
Date: [Date of research]
Topic: [What subject matter concept was investigated]
Project: [What translation project prompted this research]
Domain: [Subject area]
THE QUESTION:
What I needed to understand: [The specific conceptual question]
Why it matters for translation: [How this affects translation choices]
SOURCES CONSULTED:
Source: [Resource]
Type: [ ] Domain authority [ ] Academic [ ] Professional [ ] General
URL + Archive URL: [If online]
Date: [Publication date]
What it explained: [Relevant explanation]
Quality assessment: [How reliable is this source for this concept?]
WHAT I LEARNED:
Concept understanding: [What I now understand about this concept]
How it's expressed in the source language: [Source language usage]
How it's expressed in the target language: [Target language usage]
KEY DIFFERENCE BETWEEN LANGUAGE CONTEXTS (if applicable):
Source language concept: [How it works in source language professional context]
Target language concept: [How it works in target language professional context]
Difference: [What's different — conceptual scope, implications, usage]
HOW THIS AFFECTS TRANSLATION:
Vocabulary implications: [What this means for term choices]
Structural implications: [Whether source text structure translates directly]
RESIDUAL UNCERTAINTY:
What I'm still uncertain about: [If complete clarity wasn't achieved]
How I'm handling it: [Note to client / additional research / professional judgment]
KB UPDATE:
[ ] Subject matter KB updated
The "key difference between language contexts" is the most translation-critical field in subject matter research. The conceptual difference — where the source language concept and the target language concept don't map exactly — is the understanding that prevents the translation error of mapping one concept directly onto another when they actually work differently in their respective professional contexts.
Template 4: Client and Feedback Notes
Client and feedback notes capture the information received from clients — their stated preferences, their corrections, their feedback on delivered work — and the professional intelligence this generates for future work.
CLIENT AND FEEDBACK NOTES
Date: [Date of communication or feedback]
Client: [Client name]
Project: [Project this relates to]
Type: [ ] Initial briefing [ ] Project query response [ ] Post-delivery feedback
[ ] Correction [ ] Preference expressed [ ] New project briefing
WHAT THE CLIENT SAID:
Their communication: [What the client said — verbatim where possible for corrections]
WHAT IT MEANS FOR TRANSLATION:
Terminology implication: [If this affects terminology choices]
Style/register implication: [If this affects style choices]
Process implication: [If this affects how to handle future projects]
MY INTERPRETATION:
What I think they mean: [My understanding of their feedback]
What I'd do differently based on this: [Concrete change to my approach]
IF THIS IS A CORRECTION:
What I did: [Original translation choice]
What they want: [Client's preferred version]
Why (if stated): [Client's reasoning, if given]
Whether I agree: [My professional assessment]
KB UPDATE:
[ ] Client KB updated (style/register preference)
[ ] Terminology KB updated (if correction involves specific term)
The "whether I agree" field in the corrections section is the professional judgment field. Not every client correction reflects a translation error — sometimes clients have preferences that differ from standard professional usage, sometimes corrections reflect client style choices rather than translation mistakes. Documenting the professional assessment of corrections — and whether they indicate an error or a preference — is the self-awareness that builds accurate professional judgment over a career.
Key Takeaways
-
Terminology research notes capture the source, the reasoning, and the error prevention. The "NOT TO USE" field for incorrect alternatives encountered during research is as important as the correct term — it prevents the same error from being reconsidered next time.
-
Project notes end with a preparation gap list. What was missing from the KB before the project started — the terminology that should have been there, the subject matter background that required mid-project research — is the specific development agenda that makes future similar projects more efficient.
-
Subject matter research notes include the "key difference between language contexts" field. The conceptual false friend — where source and target language concepts don't map exactly — is the subject matter intelligence that prevents the most consequential translation errors.
-
Client feedback notes capture professional disagreement where it exists. Not every client correction reflects an error; some reflect preferences or stylistic choices. Documenting whether corrections represent errors or preferences builds accurate professional self-knowledge.
-
The KB update step on each template is what converts individual notes into system intelligence. A note that isn't routed to the KB when written may never be retrieved when needed; the on-trigger KB update is what makes captured knowledge accessible.
Conclusion
Four note-taking templates structure the professional knowledge contexts most important for translators: terminology research notes with source authority assessment, decision reasoning, and "NOT TO USE" error prevention; project notes with terminology and style decisions, query resolutions, and the preparation gap list that drives KB development; subject matter research notes with the "key difference between language contexts" field that captures conceptual false friends; and client and feedback notes with the "whether I agree" professional assessment that builds accurate self-knowledge. The KB update step on each template — the explicit prompt to route captured knowledge to the appropriate KB domain — is what converts note-taking from personal record-keeping into the institutional knowledge infrastructure that makes translation quality improve over a career.
Related reading: The Ultimate Guide to Web Clipping.