Professional translation produces a primary output — the translated document — and a secondary output that most translators don't systematically create: the documented knowledge generated during the translation process. The terminology decisions, the subject matter insights, the client usage discoveries, and the reference source findings that emerge during a translation project are the raw material of professional expertise. Captured systematically, they compound; left uncaptured, they disappear.
The research-to-output workflow for translators organizes around four research processes: project preparation research (before translation begins), terminology research and documentation (during translation), subject matter verification (when accuracy is uncertain), and post-translation knowledge capture (after delivery). Each process has outputs that serve both the immediate translation project and the long-term development of professional knowledge.
Research Process 1: Project Preparation Research
Project preparation research happens before translation begins: understanding the source text, the target audience, the client's terminology preferences, and the subject matter context for the project.
The pre-translation preparation structure:
PROJECT PREPARATION
Project: [Client + project description]
Date: [Start date]
SOURCE TEXT ANALYSIS:
Document type: [What kind of document — contract, technical manual, article, etc.]
Subject area: [Primary domain(s)]
Apparent complexity level: [How specialized is the content?]
Unfamiliar terminology: [Terms in the source text that will require research]
Unfamiliar concepts: [Subject matter areas that will require preparation]
CLIENT CONTEXT:
Terminology preferences found in KB: [Relevant existing client terminology]
Prior work in this subject area: [Reference documents from prior projects]
Style requirements: [Voice, register, formatting]
PREPARATION NEEDED:
Terminology to research: [List of terms to research before beginning]
Subject matter areas to review: [Domain knowledge to refresh or acquire]
Reference sources to identify: [Authoritative sources to locate before beginning]
TIMELINE:
Preparation phase: [How long allocated to preparation]
Translation deadline: [When delivered]
The unfamiliar terminology list generated during source text analysis is the research agenda for the preparation phase. Identifying unfamiliar terms before beginning translation — rather than stopping to research each one as it's encountered — allows preparation research to be more systematic and less disruptive to translation concentration.
Research Process 2: Terminology Research and Documentation
Terminology research is the investigation conducted to determine the accurate target language equivalent for source language terms. This research produces the most immediately critical output in translation: the terminology decisions that determine whether the translation is accurate and consistent.
The terminology research documentation structure:
TERMINOLOGY RESEARCH RECORD
Date: [Date of research session]
Project: [What project triggered this research]
Source term: [The term being researched]
RESEARCH PROCESS:
Sources consulted: [In order of consultation]
Source 1: [Resource name + URL + Archive URL]
Date of source: [When published / last updated]
What it said: [Relevant finding]
Assessment: [Reliable / Partially reliable / Unreliable for this term]
Source 2: [...]
FINDINGS:
Standard target language equivalent: [The authoritative term]
Alternative terms found: [Other terms encountered + where]
Field-specific usage: [If the standard term differs by professional context]
Client-specific usage: [If the client uses a different term]
DECISION:
Term used in this translation: [The term chosen]
Why: [The reasoning — especially if not using the most common term]
Confidence: [High / Medium / Low]
WHAT NOT TO USE:
Incorrect alternatives encountered: [Terms found that should not be used + why]
KB UPDATE:
[ ] Terminology KB updated
[ ] Client terminology KB updated if applicable
The "assessment" field on each source is the source evaluation discipline that professional translators apply but often don't document. A terminology database from a professional association is a different authority level than a user-generated glossary; a regulatory document is a different authority level than an industry blog. Documenting source assessment at the time of research makes the reasoning behind the terminology decision visible when it's questioned.
The "what NOT to use" field captures the errors encountered during research — the false cognate, the outdated term, the mistranslation that appears in poor-quality sources — so they don't get reconsidered in future work on the same terminology.
Research Process 3: Subject Matter Verification
Subject matter verification is the research conducted to confirm accuracy for translation of technically complex content — where the translator has a tentative translation but needs to verify that the meaning in the target language matches the intended meaning in the source language.
The subject matter verification structure:
SUBJECT MATTER VERIFICATION
Date: [Date of verification]
Project: [What project prompted this]
Question: [What needed to be verified]
VERIFICATION APPROACH:
What I was uncertain about: [The specific accuracy concern]
How I approached verification: [Search strategy, sources consulted]
VERIFICATION SOURCES:
Source: [Resource + date + archive URL]
Finding: [What the source said about this question]
CONCLUSION:
Verified?: [ ] Yes, my translation is accurate [ ] No, correction needed
Correction made: [If applicable]
Residual uncertainty: [If verification was incomplete]
SUBJECT MATTER INSIGHT:
What I learned: [Subject matter understanding gained from verification]
KB UPDATE:
[ ] Subject matter KB updated with verified concept
The "residual uncertainty" field is the intellectual honesty field. Sometimes verification resolves uncertainty completely; sometimes it reduces uncertainty but doesn't eliminate it. The translation delivered with residual uncertainty should be transparent about that uncertainty — a translator's note or a query to the client — rather than presented with false confidence.
Research Process 4: Post-Translation Knowledge Capture
Post-translation knowledge capture is the systematic harvest of professional knowledge generated during a completed project. This is the research-to-output process that most translators skip — and it's the process that converts professional work into compounding professional expertise.
The post-translation knowledge capture structure:
POST-TRANSLATION CAPTURE
Project: [Client + document]
Date: [Date of capture — should be immediately after delivery]
Subject area: [Domain]
TERMINOLOGY DECISIONS MADE:
[ ] All new terms added to terminology KB
[ ] Client-specific terminology confirmed in client KB
[ ] Any corrections from client feedback captured
SUBJECT MATTER INSIGHTS:
New concept understood: [Any domain concept that was learned during the project]
Where it should be captured: [Subject matter KB domain]
SOURCE DISCOVERIES:
Useful reference sources found: [Sources discovered during project research + why useful]
ERRORS OR NEAR-MISSES:
What could have been wrong: [Any terminology or accuracy risk that was caught during translation]
How it was caught: [What revealed the potential error]
Prevention learning: [What this suggests about preparation or verification]
WHAT WOULD HAVE MADE THIS PROJECT SMOOTHER:
Terminology preparation gap: [Terms that should have been in the KB but weren't]
Subject matter preparation gap: [Domain knowledge that required on-the-job research]
Reference source gap: [Resources that would have been useful to have identified before starting]
The "what would have made this project smoother" field is the continuous improvement driver. Each project reveals gaps in the preparation knowledge — terms that weren't in the glossary, subject matter concepts that required mid-translation research, reference sources that would have been useful to have identified in advance. Capturing these gaps generates the specific, project-grounded KB update agenda that makes future similar projects more efficient.
The Full Research-to-Output Cycle
The complete research-to-output cycle for a translation project:
- Pre-project: check the KB (terminology, client, subject matter, reference) — 10-15 minutes
- Preparation research: investigate unfamiliar terminology and subject matter before beginning — research agenda from source text analysis
- Active translation with documentation: capture terminology decisions and subject matter insights in real time or immediately after the session
- Subject matter verification: verify technically complex or uncertain translations against authoritative sources
- Post-project capture: systematic knowledge harvest from the completed project — 20-30 minutes immediately after delivery
This cycle produces both the translation (the primary output) and the professional knowledge capture (the secondary output that compounds professional expertise). The post-project capture step is the most commonly skipped and most professionally impactful.
Key Takeaways
-
Source text analysis before translation begins generates the research agenda. Identifying unfamiliar terms and concepts before beginning — rather than researching each when encountered — makes preparation more systematic and protects translation concentration.
-
Terminology research documentation includes source assessment. The professional association glossary and the user-generated wiki are different authority levels; documenting this assessment makes terminology decisions defensible.
-
The "what NOT to use" field is as important as the correct term. The false cognate, the outdated term, the common mistranslation — documented during terminology research, they don't get reconsidered in future work.
-
Subject matter verification should acknowledge residual uncertainty. A translator's note or client query is more professional than a translation delivered with false confidence when the subject matter accuracy isn't fully verifiable.
-
Post-translation knowledge capture is the most commonly skipped and most professionally impactful step. The 20-30 minutes of systematic KB updates after delivery is what converts professional project work into compounding professional knowledge.
Conclusion
The research-to-output workflow for translators covers four processes with documentation disciplines that make translation work both accurate and professionally compounding: project preparation research (source text analysis generates the research agenda; pre-translation KB check finds existing terminology and client knowledge); terminology research with documentation (source assessment and "what NOT to use" fields make decisions defensible and prevent re-researching errors); subject matter verification with residual uncertainty acknowledgment (intellectual honesty about verification completeness); and post-translation knowledge capture (systematic KB update immediately after delivery — the step that converts professional work into compounding expertise). The post-translation capture step — 20-30 minutes after every significant project — is the professional practice investment that has the highest long-term return on translation quality and professional efficiency.
To go deeper, check out Clip Articles for Later Reading.