MULTILINGUAL PROJECT MANAGEMENT
How to manage a multilingual localization programme
A multilingual localization programme involves more than sending the same file to several translators. Languages, teams, deadlines, terminology, review and delivery all need to be coordinated across the same project.
The larger or more regular the workload becomes, the more important it is to set up a clear process that can be reused as new content arrives.
What is a multilingual localization programme?
A multilingual localization programme is an ongoing or large-scale project in which content is translated and localized across several target languages under one coordinated workflow.
It may involve websites, software, customer communications, technical documentation, marketing, legal content or several content types at the same time.
Some programmes run for a few weeks around a major launch. Others continue for years as new content is added regularly.
PRODUCT RELEASES
New interface strings, help content and customer communications are localized as the product changes.
MULTILINGUAL CONTENT OPERATIONS
Several languages receive new translation requests every week or every working day.
LARGE-VOLUME PROGRAMMES
Large batches of content are distributed across many language teams within a shared schedule.
Why does coordination become difficult?
As the number of languages grows, the number of moving parts increases quickly.
One source update may affect several target languages. A terminology decision made in one part of the project may need to be communicated to other teams. A delayed review in one language can affect a shared launch date.
The project therefore needs a central structure for files, instructions, queries, decisions and delivery.
Several languages
Each target language has its own linguistic team, questions and review status.
Different deadlines
Some languages or content types may follow different delivery schedules.
Several content types
Software, marketing, legal and technical content may need different workflows.
Reviewer feedback
Internal reviewers may make language-specific decisions that need to be recorded.
Source changes
Updated source content may arrive after translation has already started.
Ongoing requests
New work may continue arriving while previous batches are still in progress.
Start with the project structure
A multilingual programme is easier to manage when the main decisions are agreed before the first large batch arrives.
Which languages are included?
What types of content will be translated?
How often will new requests arrive?
What is the usual and peak volume?
Which review steps are required?
Who approves terminology and language decisions?
Which tools or client platforms will be used?
How will files, queries and deliveries be tracked?
These decisions do not need to make the workflow rigid. They provide a starting structure that can be adjusted when the volume or content changes.
Build language teams that can support continuity
Regular multilingual work benefits from having linguists who become familiar with the client’s content and project instructions.
Where possible, recurring translators and reviewers can remain on the same languages over time. This helps them understand the product, terminology and previous decisions.
Primary linguists
Regular translators become familiar with the project and content.
Reviewers
Independent reviewers apply the agreed quality process where required.
Additional capacity
Extra linguists can be added when volume increases or deadlines become tighter.
Specialist resources
Some content may require linguists with specific technical, medical, financial or other subject experience.
Use shared project instructions
Every language team should work from the same core project requirements where those requirements apply across the programme.
Instructions may cover tone, formatting, terminology, file handling, review stages and content-specific rules.
Style
Formal or informal language, spelling and writing preferences.
Formatting
Rules for dates, numbers, punctuation, tags and other structured content.
Terminology
Approved words, product names and do-not-translate terms.
Content-specific rules
Instructions that apply to software, marketing, legal or other content types.
Delivery requirements
File format, naming and other requirements for final delivery.
Translation memory and terminology support continuity
Multilingual programmes often contain repeated or updated content.
Translation memories make previous approved translations available when similar content appears again. Terminology resources record important words and phrases that should remain consistent.
Together, these resources help new requests build on previous work rather than starting from zero each time.
TRANSLATION MEMORY
Stores previously translated source and target segments.
Useful for:
- repeated content
- updated versions
- recurring sentences
- previous approved translations
TERMINOLOGY
Stores approved words, phrases and usage instructions.
Useful for:
- product names
- technical terms
- financial terminology
- feature names
- prohibited wording
- do-not-translate terms
Define the review process before the work starts
Different projects need different levels of review.
A professional translation workflow may include independent bilingual revision. Other projects may use proofreading, structured linguistic QA, client review or a combination of these.
The review process should be clear to every language team before work begins.
Bilingual revision
The translation is checked against the source.
Proofreading
The target-language text is checked for language and presentation.
Linguistic QA
Issues can be recorded by category, severity and comment where structured review is required.
Client review
Internal language reviewers may approve terminology or language choices.
Technical QA
Placeholders, tags, missing text and other file-related elements can be checked where applicable.
Manage queries centrally
Questions are normal in complex multilingual projects.
A translator may find an ambiguous source sentence, a reviewer may identify a terminology problem or several languages may raise the same issue.
Central query management helps prevent different teams from solving the same source problem in different ways.
Question raised
A linguistic or source-content question is identified.
Context added
The team provides enough information to explain the issue.
Decision made
The client, project manager or designated reviewer confirms the required solution where necessary.
Decision recorded
The answer is stored so that it remains available.
Teams updated
Relevant language teams receive the decision if it affects their work.
Plan for changing volume
Multilingual programmes rarely have exactly the same workload every week.
Some periods may contain only small updates. Others may include a product launch, campaign or large content batch.
The project structure should therefore allow team capacity to change without losing the core terminology, instructions and review process.
Regular volume
A stable team can handle the normal flow of content.
Peak periods
Additional capacity can be added when larger batches arrive.
Priority content
Urgent items can be identified separately from standard requests.
Longer planning windows
Known launches or campaigns can be prepared in advance where schedules are available.
Ongoing localization needs version control
When the same content changes repeatedly, teams need to know which source version is current and what has changed.
Previous translations can be useful reference material, but old wording should not automatically override a newer source or terminology decision.
Source versions
Teams should be able to identify the current source content.
Changed strings
Updated text should be distinguished from unchanged material.
Previous translations
Earlier approved versions can be used as reference.
Terminology updates
New terminology decisions should replace outdated wording.
Final delivery
The delivered version should match the agreed source and project status.
Working in the client’s localization environment
Many companies already have a CAT, TMS or localization platform in place.
VIAX can work in client-provided environments where access is available. This can keep the client’s translation memories, terminology, comments, review stages and project history in the same working setup.
Existing resources
Translation memories and terminology remain available to the linguistic teams.
Workflow stages
Translation and review can follow the client’s configured project process.
Context
Screenshots, comments or product information may be available within the environment.
Client review
Internal reviewers can work within the same system where the project setup allows.
What should the project manager track?
Requests
What new work has arrived and when it is due.
Languages
Which target languages are included in each request.
Files
Which source and target files belong to the current version.
Status
Whether each language is in translation, review, query resolution or delivery.
Queries
Which questions are open and which decisions have been confirmed.
Terminology
Whether new terminology decisions need to be added to project resources.
Client feedback
Which changes should be applied to later work.
Delivery
Which languages and files have been completed and returned.
Common multilingual project problems
Different instructions across teams
Language teams receive conflicting or outdated project requirements.
Terminology decisions are not shared
One language or reviewer changes a term without the decision reaching other relevant teams.
Too many separate email threads
Files, queries and approvals become difficult to track.
No stable linguistic resources
Every request begins with a completely new team that has no project history.
Unclear ownership
Teams do not know who can approve terminology or source-content decisions.
Source changes during translation
New source versions arrive without a clear process for identifying changed content.
Review feedback disappears
Approved corrections are not carried into later projects.
Every request treated as a new project
Recurring work loses the benefit of existing terminology, translation memories and project knowledge.
When does a project become a managed multilingual programme?
There is no fixed number of languages or words that automatically changes a translation project into a multilingual programme.
The need usually becomes clear when coordination itself becomes a significant part of the work.
Several target languages
Multiple language teams need to follow the same overall schedule.
Frequent requests
New work arrives regularly rather than as an occasional one-off project.
Shared terminology
Product and specialist terminology needs to remain aligned across content.
Several reviewers
Client or external review needs to be coordinated across languages.
Ongoing product changes
Software, websites or documentation continue to change after the first delivery.
PROJECT EXAMPLE
A high-volume multilingual programme
One VIAX project involved approximately 20 million translated words across 79 language pairs over around three years.
Some language batches reached approximately 500,000 words per week, and the programme involved around 500 linguists supported by eight project management and QA specialists.
~20M
Words translated
79
Language pairs
~500
Linguists involved
8
Project management & QA specialists
3 years
Project duration
PROJECT EXAMPLE
An ongoing fintech localization account
A different type of multilingual programme can be built around frequent daily requests rather than very large individual batches.
VIAX’s long-term fintech localization work covers 21 languages and around 9 million translated and localized words, with four to seven new requests arriving on a typical working day.
~9M
Words translated and localized
21
Languages
4–7
Requests daily
7+ years
Long-term cooperation
A practical multilingual workflow
Define the project
Confirm languages, content types, volumes, deadlines and review requirements.
Set up linguistic resources
Prepare the teams, terminology, translation memories and project instructions.
Receive and assign content
Review each request and distribute it to the appropriate language teams.
Translate, review and resolve queries
Complete the linguistic work while keeping questions and decisions organised.
Deliver and record feedback
Return the completed content and capture approved client changes.
Reuse what has been learned
Carry terminology, translation memories and project decisions into the next request.
FAQ
Frequently asked questions
What is a multilingual localization programme?
It is a coordinated translation and localization workflow covering several target languages, often across recurring requests, content types or releases.
Do we need one project manager for every language?
Not necessarily. A central project-management structure can coordinate several language teams, while language-specific translators and reviewers handle the linguistic work.
How do you keep terminology consistent across languages?
Approved terminology, project instructions, translation memories and recorded review decisions can be made available to the relevant linguistic teams.
Can new languages be added later?
Yes. Existing source terminology, project instructions and approved content can help extend an ongoing programme into additional languages.
Can a language team change during a long-term project?
Yes. Team composition may change because of volume, availability or project requirements. Maintaining clear project resources helps new linguists understand previous decisions.
Can localization be managed in our own platform?
Yes, where appropriate access is available. VIAX can work in client-provided CAT, TMS and localization environments.
How do you manage sudden increases in volume?
The project can add linguistic capacity while keeping the same central instructions, terminology, review process and project coordination.
When should we use managed multilingual project services?
They are useful when several languages, regular requests, changing volumes, multiple reviewers or ongoing content make coordination an important part of the work.
RELATED
Related VIAX resources
- Managed Multilingual ProjectsCoordination of ongoing multilingual work involving several languages, teams and deadlines.
- Technology & QualityTranslation memories, terminology, client platforms, review and QA processes.
- Terminology ManagementCreation and maintenance of approved terminology across languages and projects.
- Global Multilingual ProgrammeAround 20 million words across 79 language pairs.
- Fintech LocalizationLong-term localization across 21 languages with regular daily requests.
Planning ongoing multilingual work?
Send us the languages, content types, expected volume, frequency of requests and existing localization setup. We’ll review the project and recommend a suitable workflow.