Translation Workflow Explained: From Source Files to Delivery
When a document goes out for translation, a lot happens between the moment you upload a file and the moment you receive a finished one — even if the client-facing part looks simple. Understanding that process helps you plan realistic timelines, prepare cleaner source files, and know what to ask a vendor before you commit to one (see our guide on questions to ask before hiring a translation company if you’re still evaluating vendors).
Here’s what actually happens at each stage of a professional translation workflow.
1. File Intake and Analysis
The workflow starts with the source file itself — a Word document, a website export, a subtitle file, a legal contract, or a technical manual. At this stage, a project manager checks the file for translatability: is it editable text or a scanned PDF that needs conversion first? Are there embedded images with text that also need translation? Ekitai’s translation services page lists the full range of supported formats, from standard Office files to CAT-tool-specific formats like .sdlxliff and .mqxliff.
Word count and file complexity are calculated here too, since both drive the quote and the timeline. If you want to understand how that quote is actually built, our translation pricing guide breaks down per-word, per-page, and per-hour pricing models.
2. Scoping and Quotation
Once the file is analyzed, the project manager scopes the job: source and target languages, subject-matter category (legal, medical, technical, financial, marketing), turnaround requirements, and whether certification is needed. Certification matters more than people expect — if you’re submitting a document to an embassy, court, or government agency, the difference between a certified, notarized, and sworn translation can determine whether your document is even accepted. Our certified vs. notarized vs. sworn translation guide explains which one you actually need.
3. Translator Assignment
This is where subject-matter matching happens. A legal contract goes to a translator with legal-domain experience; a clinical trial document goes to someone familiar with medical terminology. Ekitai maintains dedicated teams for legal translation, medical translation, financial translation, and technical translation, because generalist translators simply don’t carry the vocabulary these fields require.
4. Translation Memory and Terminology Setup
Before translation begins on any recurring or large-volume account, the project is checked against existing Translation Memory (TM) — a database of previously translated segments specific to that client. This step matters more than most people realize: it keeps terminology consistent across every project a client sends over time, and it can meaningfully lower cost on repeat work since previously translated segments don’t need to be translated from scratch. Our full breakdown of how Translation Memory works and saves money covers this in more depth.
5. Translation (Human or MTPE)
This is the core step — converting the source text into the target language. Depending on the project’s budget, timeline, and required quality bar, this happens one of two ways: full human translation, or Machine Translation Post-Editing (MTPE), where a machine-translated draft is edited by a human linguist. These aren’t interchangeable for every use case. Our guides on when to use MTPE instead of human translation and the broader MTPE business guide explain how to decide, and AI translation vs. professional human translation covers where machine translation alone still falls short.
6. Editing
Once translated, the content goes to a second linguist — the editor — who checks it against the source for accuracy, omissions, and consistency, independent of the original translator. This second set of eyes is what separates a genuinely reviewed translation from a single-pass one.
7. Proofreading
A third linguist reviews the edited translation for grammar, spelling, punctuation, and readability in the target language, this time reading it more as a standalone document than as a comparison against the source. Translation, Editing, and Proofreading together make up the TEP process — the industry-standard three-stage quality workflow.
8. Formatting and DTP (Desktop Publishing)
If the source file had specific formatting — a brochure layout, a slide deck, a legal document with numbered clauses — that formatting needs to be restored in the target language. This step matters more than it sounds: text length can change significantly between languages (German and Finnish text commonly run 20-35% longer than English), which can break layouts if it isn’t accounted for.
9. Final Quality Check
Before delivery, a final QA pass checks the completed file against the original request: correct file format, no missing sections, consistent terminology throughout, and formatting intact. For larger or multi-format projects — say, a video that needs both transcription and translation — this stage also confirms the two outputs line up correctly; our post on combined transcription-translation workflows for multilingual video covers how that specific process works.
10. Delivery and Client Feedback
The finished file is delivered in the requested format, along with any certification documents if required. Client feedback at this stage — terminology preferences, style notes — gets fed back into the Translation Memory and glossary for that account, so future projects start from an even stronger baseline.
Why This Process Matters
Skipping steps in this workflow is usually where translation quality problems come from — and problems don’t just cost a re-do. Mistranslated contracts, inaccurate medical documents, or unreviewed marketing copy can carry real legal and financial consequences. Our analysis on the true cost of poor translation walks through what’s actually at stake when a workflow gets rushed or a single-pass machine translation is used where a full TEP process was needed.
If you’re translating content for a website rather than a document, note that the workflow above is necessary but not sufficient — you’ll also want to think about SEO structure and hreflang setup, which our post on website translation vs. localization for SEO covers separately.
