Translation vendor management is the process of finding, testing, onboarding, assigning, scoring and paying the translators, reviewers and agencies that deliver your multilingual content. Good vendor management protects quality, keeps deadlines predictable and controls cost. The core tools are a vendor scorecard, a clear onboarding test, shared terminology and one system that records every job.
If your vendor list lives in a spreadsheet and your quality feedback lives in email threads, this guide shows how to build a process that scales from five linguists to five hundred.
What Translation Vendor Management Includes
A vendor is any external language professional or company: a freelance translator, a reviewer, a subtitle specialist or a full language service provider (LSP). Vendor management covers the whole relationship, not only the purchase order. It sits next to translation project management and the wider discipline of localization management, and it is where most hidden quality and cost problems start.
The Vendor Management Lifecycle
| Stage | What to do | Output |
|---|---|---|
| 1. Sourcing | Find candidates by language pair, domain and certification | Shortlist |
| 2. Vetting | Check references, experience and tool skills | Qualified candidates |
| 3. Test | Give a paid or short test in your domain and review it blind | Test score |
| 4. Onboarding | Share style guide, glossary, instructions and tool access | Active vendor |
| 5. Assignment | Match jobs by language, subject and availability | Accepted job |
| 6. Evaluation | Score quality, timeliness and communication after each job | Vendor scorecard |
| 7. Payment and review | Pay on time, review rates yearly, retire weak vendors | Stable vendor pool |
How to Build a Vendor Scorecard
A scorecard turns opinions into numbers you can compare. Keep it short enough that project managers actually fill it in. A simple weighting that works for many teams looks like this:
| Criterion | Suggested weight | How to measure |
|---|---|---|
| Quality | 40% | Reviewer error counts, or a formal LQA score per job |
| On-time delivery | 20% | Share of jobs delivered by the deadline |
| Terminology and style compliance | 15% | Glossary and style guide deviations |
| Communication | 10% | Response time and clarity of queries |
| Price and flexibility | 15% | Rate vs market, availability for urgent work |
Adjust the weights to your business. A legal team may put quality at 60%, while a support team may value speed more. For the quality column, a consistent translation quality assurance process gives you comparable data from job to job.
Quality Standards to Require From Vendors
For regulated or high-risk content, ask vendors to follow a recognized standard. ISO 17100 defines requirements for translation services, including translator qualifications, a revision step by a second linguist and project management practices. Even if a vendor is not certified, you can copy the principle: every translation is revised by a different qualified person before delivery.
Spreadsheets vs a Translation Management System
| Need | Spreadsheets and email | Translation management system |
|---|---|---|
| Vendor profiles and rates | Manual, quickly outdated | Central and searchable |
| Job assignment | Email chains | One-click assignment with deadlines |
| Shared translation memory and glossary | Files sent back and forth | Live access inside the editor |
| Quality scoring | Ad hoc notes | Structured LQA scoring per job |
| Access control | Full files shared by email | Role-based access to projects only |
A translation management system removes the manual work behind most of the problems above. You can also automate routine steps such as assignment and notifications with workflow automation instead of chasing people by email.
KPIs to Track for Every Vendor
Numbers make vendor conversations fair and specific. Track a small set of indicators per vendor and per language pair: the average quality score per 1,000 words, the percentage of jobs delivered on time, the share of jobs accepted on first request, the number of queries per job, and the average turnaround per 1,000 words. When a vendor scores low, look at the cause before you replace them. Unclear source text, missing context and a missing glossary are often responsible, and these are problems on your side, not theirs.
Common Vendor Management Mistakes
- Choosing only on price. The cheapest rate often costs more after rework and missed deadlines.
- No feedback loop. Vendors cannot improve if nobody tells them what was wrong.
- Depending on one vendor per language. Keep a backup for every critical pair.
- Not sharing context. Give vendors the glossary, style guide, screenshots and the purpose of the text.
- Ignoring data security. Limit what vendors can see and sign confidentiality agreements.
Pay attention to money as well. Clear rates, reuse of translation memory and fair discounts for repetitions are part of controlling localization cost.
Frequently Asked Questions
How many vendors per language do I need?
At least two for every business-critical language pair, so a holiday or illness never stops a release.
What is the difference between a vendor and an LSP?
A vendor is any supplier. An LSP is a company that manages translators and projects for you, so it can also be one of your vendors.
How often should vendors be evaluated?
Score every job, then review the aggregate results quarterly and renegotiate or replace vendors once a year.
Manage Linguists in One Workspace With WordBeam
WordBeam lets you invite internal reviewers and agencies at no extra seat cost, share glossary and translation memory, assign jobs and track LQA scores in one place. See pricing and start a free trial with 14 days and 10,000 words.