Working With a Language Partner Long-Term: What Good Looks Like

What Good Looks Like

The Difference Between a Supplier and a Partner Most organizations manage translation as a transactional service. A project arises, a request is sent, a delivery is received, an invoice is paid. The next project starts from approximately the same point as the last one. Nothing accumulates. Nothing compounds. The organization is perpetually re-explaining its terminology, re-briefing its requirements, and re-discovering the same problems that appeared in previous projects.

A long-term language partner relationship works differently. Each project builds on the last.

Approved terminology is stored and applied automatically. Revision findings improve the next delivery. The translation partner develops institutional knowledge of your products, your markets, your legal frameworks, and your quality expectations — knowledge that a transactional vendor never develops because each interaction is treated as self-contained. The difference in quality between these two models compounds over time. After one project, the gap is small. After ten projects, it is significant. After five years, a well-managed long-term partner relationship produces translation that is measurably better, faster, and cheaper per unit than a transactional approach to the same volume of work.

This guide describes what a good long-term language partner relationship looks like — what it requires from both sides, what it produces, and how to recognize when it is and is not working. What Accumulates in a Good Long-Term Relationship The value of a long-term language partner relationship is not primarily in the relationship itself — it is in what accumulates within it. Three things compound in value over time. Translation Memory A translation memory (TM) is a database of previously translated content — source segments paired with their approved translations. In a properly managed translation relationship, every project adds to the TM, and every subsequent project draws on it.

The practical consequence: content that has already been translated and approved does not need to be translated again. A product manual that was translated last year, updated with changes this year, can have the unchanged sections populated from the TM automatically — only the changed sections require new translation. The unchanged sections are consistent with the previous version by definition.

Over time, for clients with stable core content — standard contract clauses, recurring regulatory language, product specifications that change incrementally — the TM match rate for new projects increases, costs decrease, and turnaround times shorten. A client whose TM is five years old and well-maintained is getting significantly more value from each project than a client starting from scratch.

What this requires: The TM must be maintained, not just accumulated. Approved corrections and terminology updates must be reflected in the TM, not left as overrides that diverge from the stored content. A TM that contains outdated approved translations is worse than no TM — it actively reintroduces errors. Terminology Database

A terminology database — a managed glossary of approved translations for key terms — is the mechanism that enforces consistency across documents, across projects, and across language versions.

In a new relationship, the glossary must be built — typically through an initial terminology extraction from existing documentation, followed by client approval of proposed translations for key terms. This initial investment takes time and effort from both parties.

In a mature relationship, the glossary is a living asset that grows with the product and the business. New product features, new regulatory terms, new contractual language — each addition is made once and applied automatically to all subsequent projects. The client stops discovering that a product name was translated differently in the French version than in the German one. The inconsistency was prevented before the translation was produced.

What this requires: The client must engage with terminology decisions. A glossary built entirely by the translation provider, without client input and approval, reflects the provider's best judgment about terminology — which may differ from what the client's engineers, legal team, or marketing function would actually want. The initial glossary-building exercise requires a few hours of the client's time. The payoff is years of consistent terminology without re-litigating the same decisions on every project. Institutional Knowledge Institutional knowledge is harder to quantify than TM matches or glossary entries, but it compounds at least as significantly. A translation partner who has worked with your organization for three years knows things about your content that cannot be codified in a database:

The level of formality your legal documents use in each target language The terminology preferences your in-country teams have expressed over multiple review cycles The subject-matter context of your products — what they do, who uses them, in what environments

The regulatory frameworks your documentation must meet and how those affect translation choices

The specific weaknesses and sensitivities of your review process — which reviewers care deeply about which dimensions of quality

The history of specific terminology decisions and why they were made This accumulated knowledge makes the partner's work better in ways that are difficult to replicate. A new translation provider starting a relationship with the same organization must reconstruct this knowledge from scratch — and will make mistakes during the reconstruction period that an established partner would not make.

What this requires: The knowledge must be documented where possible. A style guide, a reviewer preferences document, a list of historical terminology decisions — these reduce the risk that institutional knowledge walks out the door if the primary contact on either side changes. A relationship that exists only in the memories of specific individuals is fragile. What Good Looks Like: Twelve Indicators A long-term language partner relationship that is working well shows the following characteristics. Use them as a benchmark for evaluating your current or prospective translation relationships.

In a mature relationship, terminology is consistent across documents and across projects as a matter of routine, not as a result of constant vigilance. You should not be finding and correcting the same terminology inconsistency in each delivery. If you are, either the TM and glossary are not being applied correctly, or the glossary needs updating to reflect decisions that have been made since it was last reviewed.

Counterintuitively, turnaround time should improve as a partner relationship matures. Projects with high TM match rates deliver faster than projects starting from scratch. Translators familiar with your content and terminology work more efficiently than translators encountering it for the first time. Briefing time decreases as the provider's institutional knowledge increases.

If turnaround times are not improving, or are getting worse, this is a signal that TM is not being maintained or that the translator pool assigned to your account has turned over.

A translator working on a new relationship generates many queries — about terminology, context, usage preferences, and formatting requirements. A translator who has worked with your content for two years generates far fewer, because the answers to most recurring questions are already documented in the project setup or have been resolved in previous projects.

If you are receiving the same questions on each project, the answers are not being captured and retained. This is a process failure, not a familiarity failure.

Feedback from your in-country reviewers or internal review process should produce measurable improvement over time — fewer of the same errors appearing in subsequent deliveries. If review findings from year three look similar to review findings from year one, the feedback loop is not working. Either feedback is not being communicated to the provider in actionable form, or the provider is not incorporating it into the process.

You should have a specific project manager who knows your organization, your content, and your history with the provider. Not a general inbox. Not a rotating roster of whoever is available. A named individual who can answer questions about your account, who recognizes your documents when they arrive, and who manages your projects with the context of the relationship rather than treating each one as a standalone assignment.

A good partner communicates about issues before they become problems — rather than informing you of a delay when the delivery is already late, or identifying a source document ambiguity after translation is complete rather than before it begins. Proactive communication is a sign of a provider who is managing your project rather than processing it.

A partner who tells you what you want to hear is not a partner — they are a vendor trying to protect the account. A genuine partner will tell you when a deadline is not achievable, when a source document has problems that will affect translation quality, when a quality concern in a previous delivery was caused by something on your side rather than theirs, and when the volume you are asking for in the time you have given cannot be delivered to the quality you need.

Honesty about limitations is uncomfortable in the short term. It prevents expensive failures that comfortable agreement would not have prevented.

A provider who has spent three years working with your organization should understand the context of what they are translating — what your products do, who your customers are, what markets you compete in, what regulatory frameworks govern your industry. This understanding shows in the quality of translation decisions — the choice between a technical and a consumer register for the same content, the selection of a regulatory term that aligns with the applicable framework, the handling of a product name in a market where it has specific associations.

You can test this by asking your provider to explain the context of a recent project. If they can speak to it with genuine understanding rather than generic description, the institutional knowledge is developing. If they cannot, it is not.

In a well-managed relationship, the translation memory and terminology database built over the course of the relationship belong to the client. They should be exportable in standard formats (TMX for translation memory, TBX for terminology) at any point, without negotiation. A provider who treats TM and glossary as proprietary assets that they own is not managing the relationship in your interest.

Confirm at the start of a new relationship that your TM and glossary are yours, that you can request an export at any time, and what the format of that export will be.

Quality in a mature relationship should be consistent across projects — not excellent some of the time and poor at others. Episodic quality variation typically indicates either an inconsistent translator pool (different translators assigned to different projects with no continuity) or inconsistent application of TM and glossary (some projects benefit from it, others do not). Consistent quality requires consistent process. If you notice significant variation between deliveries from the same provider, the process is not being applied uniformly.

As the TM match rate for your content increases, the cost per word for translation should decrease — because an increasing proportion of each delivery is drawn from previously approved and stored content rather than translated fresh. A provider who does not offer TM- based pricing discounts for repeat content over time is either not maintaining TM or not applying it to pricing.

This does not mean costs should decrease indefinitely — rate changes, complexity variation, and new content types will affect pricing. But the trend in cost per unit of output for stable content should be downward over a multi-year relationship.

People change roles. Your primary contact at the translation provider leaves. Your internal project manager who managed the relationship moves to a different team. In a well-managed relationship, this does not materially disrupt quality or continuity — because the institutional knowledge is documented in the process, the TM, and the glossary, rather than residing solely in the heads of specific individuals.

If a relationship has survived one or more personnel changes on either side without a significant quality disruption, it is well-institutionalized. If personnel change consistently resets the relationship to near-zero, the knowledge management is inadequate. What Good Long-Term Relationships Require From the Client

A long-term language partner relationship is not simply a service that you purchase. It requires active participation from the client to function well. The most common reason good long-term translation relationships fail is not provider underperformance — it is client disengagement. Engage with terminology decisions. The glossary cannot be built without your input and approval. Terminology decisions made by the provider without client review may not reflect your actual preferences and may need to be corrected retrospectively — which is more expensive than getting them right initially.

Communicate feedback in actionable form. "The quality was poor" is not actionable feedback. "Section 3.2, the term [X] was translated as [Y] — the approved translation is [Z]" is. The quality of your feedback determines the quality of improvement the provider can make.

Maintain consistent contact. Providers who have regular communication with a client contact — even brief, routine updates — maintain institutional knowledge better than those who receive documents at irregular intervals with no contextual communication.

Tell the provider when something changes. If a product is renamed, if a regulatory framework changes, if a new market is being entered, if a reviewer has identified a systematic issue — tell the provider immediately. The provider cannot apply knowledge they do not have.

Give the relationship time. A long-term relationship takes time to mature. The value of TM compounds over years, not months. A client who switches providers every 18 months never experiences the compounding returns of a mature relationship — and pays more per unit of quality than a client who commits to building one. Recognizing When a Relationship Is Not Working Not all long-term relationships should continue. A relationship that is not working often shows these signs:

The same errors recur across multiple projects. If feedback from one project is not reflected in the next, the feedback loop is broken. Discuss this specifically with your provider contact — if the issue persists, it is a process failure that is unlikely to self-correct.

Terminology is inconsistent despite a maintained glossary. Either the glossary is not being applied to the workflow, or the workflow does not enforce glossary use. Ask your provider to confirm how the glossary is activated in the translation tool for your projects.

Turnaround times are increasing, not decreasing. A mature relationship should get faster, not slower. If turnaround times are deteriorating, the provider may be over-committed, understaffed on your account, or managing your projects with less priority than previously. Your named contact changes frequently. High turnover in the project management role assigned to your account suggests an organizational issue that will affect quality and continuity regardless of the underlying translation capability.

You are being asked the same questions repeatedly. Questions about context, terminology, or format that were answered in previous projects should not recur. If they do, the answers are not being retained in the project setup.

Quality varies significantly between projects. Episodic quality variation, discussed above, indicates inconsistent process application — often caused by an inconsistent translator pool or inconsistent TM application.

When a relationship shows these signs, the right first step is a direct conversation with the provider about the specific issues — not immediately switching. Many relationship problems are process problems that can be corrected with explicit discussion. A provider who responds to a specific concern with concrete process changes is worth working with. A provider who responds with reassurance but no specific change is not. The Economics of Long-Term Partnership The economic case for a long-term partner relationship is straightforward but often underestimated.

Direct costs decrease. TM match discounts reduce per-word costs as the match rate for stable content increases. Briefing time decreases. Error correction cycles decrease. Reprinting or republishing cost arising from quality failures decreases.

Indirect costs decrease. The time your team spends managing the translation relationship — briefing, chasing, reviewing, correcting — decreases as the provider's institutional knowledge grows and process maturity increases.

Risk decreases. The probability of a significant quality failure — a mistranslated regulatory document, an inconsistent multilingual product launch, a legal document with terminology errors — decreases as the provider's familiarity with your content and requirements increases. Speed increases. Faster turnaround on repeat content frees your timeline for the steps that follow translation — review, approval, publication, launch.

Against these benefits, the cost of switching providers — rebuilding TM, rebuilding glossary, absorbing the quality risk of a new provider's learning curve, re-establishing institutional knowledge — is high. Organizations that switch translation providers regularly to obtain marginally lower rates are systematically destroying value that the departing provider built up over the course of the relationship.

This does not mean that a relationship that is genuinely not working should be continued indefinitely. A relationship that is not improving, not applying TM, not incorporating feedback, and not delivering consistent quality should be ended regardless of the switching costs. But a relationship that is performing well should be maintained and invested in — not disrupted to save a few percent on per-word rates.

Summary: What to Look for in a Long-Term Language Partner At the start of a relationship: Will TM and terminology database be maintained and applied from the first project? Is there a named project manager who will maintain continuity? Are TM and glossary assets owned by the client and exportable on request? Does the provider have a structured feedback and improvement process? Is the provider ISO 17100:2015 certified — with mandatory revision applied consistently?

As the relationship matures: Is terminology more consistent than it was a year ago? Are turnaround times improving for stable content? Is the volume of review feedback decreasing over time? Does your project manager understand your business, not just your files? Are costs per unit decreasing for high-match-rate content?

If the relationship is long-established: Does it survive personnel changes without quality disruption? Is the TM a genuine asset — large, maintained, and consistently applied? Are the same errors still appearing, or has the feedback loop closed them? Would switching providers impose a genuine cost — in time, quality risk, and lost institutional knowledge?

If most of these indicators are positive, the relationship is working. Invest in it. Working With Business Team Translations Business Team Translations has maintained long-term translation relationships with clients including Flextronics (since 2008), Zwack Unicum (since 2007), UniCredit (since 2010), Poli-Farbe, Kallos, 3DHISTECH, and many others. Some of these relationships span fifteen or more years and involve tens of millions of HUF in cumulative project value built on maintained translation memories, managed terminology, and consistent project management.

We maintain client-specific TM and glossary assets, apply them to every project, and provide

TM exports on request. We assign named project managers to accounts. We treat feedback as process improvement input, not dispute management. Our ISO 17100:2015 and ISO 9001:2015 certifications apply to every project — not selectively.

If you are building or reviewing a long-term translation partner relationship, we are happy to discuss what that looks like in practice.