Choosing a language partner: what predicts a working relationship
Price per word says little about a language partner. Capacity, terminology control, revision and candor show how the work will really go.
In short: Many organizations pick a language partner on price per word and then spend the next two years managing the consequences. The factors that predict whether the relationship works are capacity under pressure, terminology governance, a named revision step, and a provider's willingness to turn down a deadline it cannot meet.
What a language partner is responsible for
A language partner carries meaning between languages across everything an organization produces: contracts, filings, product interfaces, training material, marketing, and the conversations that happen in the room. The word "partner" matters in that description. A vendor takes an order, while a partner tells you when the order is wrong.
Five factors that predict a good relationship
1. Capacity that holds under load
Any provider can perform well on a two-page test document. The better question is what happens when four hundred pages arrive on a Thursday with a Sunday deadline. A credible answer names a team and states a limit. An unconditional yes is the answer that should worry you.
2. Terminology governance
When an organization uses a term of art, such as a product name, a contractual definition or a regulatory phrase, that term has to render identically in every document, indefinitely. This calls for a managed glossary and a person who owns it. Without both, consistency depends on whichever linguist happened to be free that day.
3. A revision step that is named and staffed
Under ISO 17100, a second qualified linguist reviews the translation against the source. This is the step most often removed from cheap quotes, and its absence stays invisible until something goes wrong in public.
4. Subject-matter routing
A pharmaceutical dossier and a shareholders' agreement belong on different desks. Ask how the provider assigns work and what happens when the right specialist is unavailable.
5. Willingness to refuse
The most useful signal in a procurement conversation is a provider that declines a deadline, flags an ambiguity in your source text, or tells you a document does not need certification. Saying so can cost the provider the sale, which is why it tells you so much.
What a low price per word can hide
| What you are quoted | What may have been removed | Where the gap shows up |
|---|---|---|
| Unusually low per-word rate | Independent revision step | Inconsistency across a set of documents |
| Flat rate for all content | Subject-matter specialists | Technical or legal terms that read plausibly and are wrong |
| Machine output with light edits | Full post-editing | Fluent text that says something different |
| No project management line | Coordination and quality assurance | You end up managing the project yourself |
Questions to ask before signing
- Which people will work on the account, and who covers the work when they are on leave?
- Can you show a glossary you maintain for an existing client, with the client details removed?
- What is your ISO 17100 certificate number, and which body audited you?
- Describe a project that went wrong and what changed afterward.
- What would lead you to turn down a piece of this work?
Frequently asked questions
Is one partner better than several?
Use one partner for anything where terminology consistency matters, which covers most regulated and product content. Several providers can be justified for high-volume, low-risk material where speed is the main concern.
Is machine translation acceptable?
Yes, for internal comprehension and for high-volume, low-risk content that receives human post-editing. For certified, contractual or public-facing material, the economics stop working once revision is priced properly.
How can a provider be tested before committing?
Send a genuinely difficult sample from your real content, not a clean marketing page, and set a realistic deadline instead of a generous one. Then ask an internal colleague who knows the subject to review the output.
What does ISO 17100 actually require?
It requires qualified linguists, an independent revision step, documented project records, and defined competences for everyone involved. As a process standard, it guarantees method. It does not guarantee style.
Who owns the translation memory?
Settle this at the start. The translation memory and glossary belong to the client as assets, and a provider that will not release them has built a switching cost into the relationship by design.
Working with Bayan Group
Bayan Translation handles certified work under ISO 17100 and ISO 9001. ZED covers localization and outsourced language operations, and McLingo provides the technology layer beneath both. See Sectors & Brands for how the brands fit together, or get in touch with a real document and a real deadline.