top of page

Translation Project Management: A Practical Workflow Guide

Writer: Umar Usman
Umar Usman
Nov 15
10 min read

Translator reviewing a translation project

Translation project management is the work of getting multilingual content from request to delivery on time, at the right quality and on budget: scoping the job, preparing files, assigning the linguist, agreeing terminology, reviewing, and delivering. The fewer people and handoffs between your source file and your final file, the fewer places a project can slip. That is why we run Hungarian-English work through one experienced translator who uses CAT tools (software that stores and reuses approved translations) and a built-in quality check, rather than a chain of coordinators.

 

This guide is for teams that buy translation: product companies localizing software, medical and legal professionals who need precise documents, game studios, and anyone with a deadline. It covers the stages, the briefing that prevents most delays, how to talk to a vendor, and how to keep quality and confidentiality under control.



TL;DR

 

  • A translation project has four core stages: translation, editing, proofreading and maintenance. Each stage you add is a handoff, and each handoff is a possible delay.

  • Most delays come from incomplete source files, unclear deadlines, slow internal reviews and unapproved terminology, not from the translation itself.

  • Write the brief once: audience, tone, glossary, file formats, deadline with time zone, and who approves what.

  • Agree deadlines and changes in writing, and give feedback with both corrections and what worked.

  • For Hungarian projects, we work as one subject-specialist translator with after-hours availability, so the person who translates is the person you talk to.

 

Table of Contents

 

 

What translation project management actually covers

 

The Institute of Translation and Interpreting (ITI) describes the role as handling the lifecycle of a multilingual project from the request through quality control and delivery. That includes understanding the client’s requirements, matching them to suitable translators, estimating how long tasks take, negotiating deadlines and rates, and reassessing goals when circumstances change.

 

In practice, someone on your side or the vendor’s side does these jobs:

 

  • Scope: what is being translated, into which languages, for whom.

  • Preparation: collecting final source files, reference material and previous translations.

  • Assignment: choosing a linguist who knows the subject.

  • Coordination: answering questions, relaying decisions, tracking dates.

  • Quality control: review against the brief and fixing issues.

  • Delivery and maintenance: handing back files and keeping approved terms for next time.

 

When a project is small or recurring, one person can do all of it. When it spans many languages and departments, it needs a dedicated coordinator. Either way, the same tasks have to be done by someone.

 

The stages of a translation workflow

 

The COMET guide to translation project management, an academic training resource, splits the process into translation, editing and revising, proofreading, and maintenance. It notes that professional translators typically perform the first three steps themselves, after which an editor or reviewer repeats the second and third.


Four translation workflow stages with reviewer loop

Here is what each stage means for you as the buyer.

 

1. Translation

 

The linguist produces the target text. Quality here depends mostly on what you gave them: final source text, context (screenshots, product descriptions, who reads it) and a glossary. Translating from a draft that still changes is the most common way to pay twice.

 

2. Editing and revising

 

A second pass compares the translation against the source for accuracy, omissions and terminology. In a CAT tool, the translator also checks matches reused from earlier approved work.

 

3. Proofreading

 

The last read looks at the final layout and the language itself: spelling, punctuation, number formats, consistency. This is also the moment to check how the text fits in the design, because Hungarian words are often longer than English ones.

 

4. Maintenance

 

Approved terms and sentences are stored so the next project starts from them. This is where recurring clients save the most: repeated content is not translated from scratch.

 

Where translation projects get delayed

 

In a June 2023 MultiLingual interview, Loy Searle, formerly head of Google’s Global Production and Language Services, argues that faster delivery comes from flexible, lean processes rather than pressure. His suggestions include eliminating unnecessary steps, setting timeboxes for subject-matter review, establishing vendor turnaround times, setting precise delivery times for handoffs and making sure assets are complete.

 

Turn that into a delay checklist:

 

Cause of delay

What it looks like

Prevention

Incomplete or changing source

New text arrives after work started

Freeze the source or send changes as a clearly marked update

Slow internal review

The translation waits days for an approver

Name the approver and give a review window in the brief

Unclear terminology

Questions pile up mid-project

Send a glossary and past translations upfront

Awkward file formats

Time lost extracting text from images or layouts

Send editable files (see our InDesign file guide)

Vague deadline

“ASAP” with no date or time zone

State date, hour and time zone

Too many handoffs

Questions travel through several people

Give the linguist one point of contact

The last row is the one most teams underestimate. Every person between the requester and the translator adds a message that can be misread or wait in an inbox.

 

A worked example

 

Say a medical device maker needs a 12,000-word instruction manual in Hungarian by the end of next week. The source is a PDF exported from a layout file, the product name has three variants, and a regulatory reviewer must approve the Hungarian text.

 

The delays are predictable: the PDF needs text extraction, the variants need a decision, and the reviewer is traveling. The fix costs one hour before the project starts: send the editable file, a list of approved product names, and ask the reviewer for a two-day window on a named date. The translator can then work in parallel while the review slot is reserved.


A worked example

Write the brief once, and write it well

 

A good brief is the cheapest project management tool there is. Include:

 

  1. Purpose and audience: who reads the text and what they do with it.

  2. Tone: formal or informal address, brand voice, regulatory register.

  3. Languages and variants: for Hungarian work, say whether the text is for consumers or specialists.

  4. Reference material: previous translations, glossaries, style guides, screenshots.

  5. File formats: the editable originals, not only PDFs.

  6. Deadline: date, hour, time zone, and whether a partial delivery helps.

  7. Approvers: who signs off and how quickly they respond.

  8. Confidentiality: what is sensitive and how files should be sent.

 

Our own guide on how to choose and brief Hungarian translation services goes through this list for Hungarian projects specifically.

 

Terminology and quality control

 

Searle’s position is blunt: style guides, standards and terminology are what make consistent results possible. A glossary does more for quality than any amount of end-stage checking, because it settles the question before it is asked. We cover how to build and maintain one in our terminology management guide.

 

On quality assurance, a 2017 MultiLingual article by Vassilis Korkas argues that QA should cover three phases: pre-translation (clean, well-prepared source content), in-translation (tools that help the translator resolve terminology and locale issues as they appear) and post-translation review. It adds that many large projects only do the last phase because of time and cost, which makes it quality control rather than true assurance.

 

A practical way to apply this:

 

  • Before: send final files and the glossary.

  • During: let the translator ask questions and answer them within a day.

  • After: review a meaningful sample, not two sentences, and send corrections along with what worked.

 

Quality standards are also moving toward objective measurement. MultiLingual reported that the forthcoming ISO 5060 was meant to give a framework for evaluating translation output against requirements defined in the project specification. The takeaway for buyers is simple: the clearer your specification, the more objectively quality can be judged.

 

When the audience changes the translator

 

A 2024 Localization Institute case study on Johnson Health Tech by Christa Walter shows that tone matters as much as accuracy when content moves from a business audience to consumers, and that technical documents almost always need a different translator than consumer-facing material. So match the specialist to the text type: a clinical protocol, a user manual and a game’s dialogue are three different jobs.

 

For clinical documents specifically, see our guide to clinical trial translation; for engineering content, our technical document translation guide.

 

Communicating with your translation vendor

 

Most vendor problems are communication problems with a delay attached. A workable routine:

 

  • Confirm scope in writing. The ITI recommends agreeing deadlines in writing as part of clear communication, one of the core skills it lists for translation project managers.

  • Name one contact on each side. Questions should not pass through three inboxes.

  • Answer queries fast. A translator waiting on one answer can often continue with other sections, but not forever.

  • Send changes as changes. Mark what is new instead of resending the whole file.

  • Give balanced feedback. Searle recommends feedback with both corrections and kudos, and regular calls with linguists and vendors for continuous improvement.

  • Act on suggestions. He also says a vendor-client relationship is a partnership and that clients should act on improvements the vendor proposes.

 

The principle of treating communication as an ongoing partnership applies well beyond translation. A multilingual AI assistant guide for restaurants, for example, shows how written policies and clear escalation rules keep multilingual guest messages consistent, the same idea as a written brief and approval path for translators.

 

Keeping clients informed

 

The ITI points out that clients cannot always see the work going into a project while it is still in development, so updates are part of the job. For a long project, ask for a mid-point check: a short note on progress, open questions and any date risk.

 

Managing multilingual content at scale

 

When content flows into several languages, the work shifts from single projects to a system. The Johnson Health Tech case study describes a standard procedure in which the agency returns estimates within 48 hours on average, uses translation memory so previously translated strings are not charged again, routes materials to in-region approvers with glossaries and style guides, and updates the memory before delivery. Global marketing sends translations through its main agency first so regional teams can review the text in the target language and tone.

 

The lessons that transfer to any size of team:

 

  1. Reuse approved text. Translation memory means repeated content costs less and reads the same everywhere.

  2. Put reviewers in the market. Someone who lives with the audience’s language catches what a central team cannot.

  3. Give reviewers reference material. Glossaries and style guides turn opinions into decisions.

  4. Close the loop. Update the memory with review changes before the next project starts.

 

Translation management systems (TMS) hold these pieces together. MultiLingual’s December 2023 overview calls them the cornerstone of translation technology, combining translation memory, terminology, machine translation, QA and project management. A TMS suits teams with many contributors; a small team with a single trusted translator can reach the same result with a shared glossary and a well-kept translation memory.

 

Machine translation in the workflow

 

If you use machine translation first, the human step is post-editing, and the level you choose changes cost and time. Searle recommends process gating for this, deciding upfront which content goes through machine translation with post-editing and which goes through full translation, editing and proofreading. Our guide to machine translation post-editing levels, workflow and pricing explains the choice.

 

Urgent projects

 

Rush work does not need a different process, it needs a tighter one: complete files, a ready glossary, a named approver and a realistic delivery time. Two pages cover this in detail: rush translation and same-day translation. For software and training content, see also our e-learning localization guide.

 

Perspective: fewer handoffs, clearer ownership

 

We have translated for more than 15 years, and the pattern is consistent: projects go wrong at the seams. A file is exported badly, a question waits for an answer, a term is decided twice.   That is why we work as a single translator. The person who reads your brief is the person who translates, so subject knowledge in technical, medical, legal, automotive, financial, marketing, software and game content stays with the text from start to finish.   Our workflow combines advanced CAT tools with quality assurance measures, which lets us handle high-volume projects without losing consistency. We are also reachable after regular business hours, which matters when your deadline falls in a different time zone or arrives with no warning.   We give deadlines we can keep, and we treat every document as confidential. If you want the quickest route to a reliable Hungarian text, send the brief to us directly.   Bernadett

 

Work with us on your Hungarian project

 

We translate into Hungarian from €0.05 per word, and into English, German or French from €0.07 per word. Machine translation post-editing starts at €0.04 per word for full post-editing and €0.03 per word for light post-editing. Localization, including website, software and video game content, is quoted per project. Our German-Hungarian and French-Hungarian work follows the same workflow as Hungarian-English.


Wordsbyme

Send us your files, your deadline and your reference material through wordsbyme.hu, and we will start from your brief.

 

FAQ

 

What does a translation project manager do?

 

A translation project manager oversees a project from the request to delivery. That includes clarifying requirements, matching the job to a suitable translator, planning the schedule, coordinating resources, and handling quality questions. They also keep the client informed and adjust plans when something changes.

 

How do I prevent translation delays?

 

Most delays can be avoided before work starts. Send final, editable source files, a glossary and a clear deadline with the time zone. Name who approves the translation and when they are available. Fewer handoffs between you and the translator also means fewer questions waiting for answers.

 

What are the stages of a translation workflow?

 

The basic stages are translation, editing or revising, proofreading, and maintenance of approved terms and memory. Larger or high-stakes projects add a second reviewer or an in-market approval step. Each added step improves control but adds time, so match the workflow to the risk of the text.

 

How should I give feedback to a translator?

 

Be specific and send it in one consolidated list. Mark corrections and also note what worked, so the translator knows what to repeat. Where a change reflects a company preference, add it to the glossary or style guide so it applies to the next project.

 

Sources

 

Recommended

 

 
 
 

Comments


bottom of page