How to Choose a Professional Translation Agency: Vetting, Pilot Projects, Security and SLAs

· 7 min read
Illustration of a small figure with a lantern choosing between three doors, one lit from within, a metaphor for choosing a translation agency.
On this pageBefore you shortlist: write down what you are buyingShortlist questions that separate agenciesDesigning a pilot that tells you somethingSecurity and data questions to settle before the contractSLA terms worth writing downAfter you sign: the first 90 daysFAQ

Choosing a professional translation agency from a sales call, a polished sample and a rate card tells you almost nothing about the vendor you will deal with on the third urgent job of the quarter. That job is where agencies differ: who actually translates, who checks, how fast questions get answered, and what happens when something is wrong. This guide is a selection process built to test those things before you sign.

It is written for the people who usually run the selection in a global company: localization and procurement leads, legal operations, marketing and product teams, and regulatory groups that need translated content they can rely on. The steps work for one language or twenty.

Before you shortlist: write down what you are buying

Most selection processes compare agencies against a vague idea of "quality". Agree internally on four things first, because they decide which agencies are even relevant:

  1. Content types and their risk. Contracts and regulatory text, product UI, marketing copy and internal training need different workflows. List them and mark which ones will be signed, filed, published or shown to customers.
  2. Languages and volume. Rough annual words or pages per language, and whether work arrives as large batches or a constant stream of small jobs.
  3. Systems. Where the content lives (CMS, code repository, document management, design files) and whether you expect the agency to connect to it.
  4. Who decides. Name the reviewers in each market who will judge the output. A vendor cannot pass a test whose judges change every week.

If your program is mostly large document sets, the scoping questions in how to scope and run large document translation programs belong in this brief too.

Shortlist questions that separate agencies

Send the same written questionnaire to three or so agencies. The point is not the answers themselves but how specific they are. Generic answers usually mean the process exists in the brochure, not in production.

AskA useful answerA warning sign
Who would translate and revise our content?Named profiles or anonymised CVs for the core team per language, with subject experience"Our network of thousands of native linguists"
What is your workflow for content that will be published or signed?Translation, revision by a second linguist, automated QA, final check; steps listed per tierOne price, no description of steps
When do you use machine translation?A written policy, per content type, with post-editing by qualified linguists and your approval required"Only when appropriate", or no answer
How do you handle terminology?A termbase maintained per client, with a named owner and a process for your reviewers' changes"Our translators are experts, they know the terms"
Who owns the translation memory?You do; exported in a standard format on request and at the end of the contractVague, or "it stays in our system"
How do you report quality?Error categories and severity agreed with you, reported on a scheduleCustomer satisfaction scores only

Certifications help with filtering. ISO 17100, the international standard for translation services first published in 2015, requires a production process of translation, revision and final verification, and sets qualification routes for translators: a graduate qualification in translation, a graduate qualification in another field plus two years of full-time professional translating, or five years of full-time professional translating. ISO 18587 covers full, human post-editing of machine translation output. A certificate tells you a process exists. It does not tell you who works on your files, which is why the next step matters more.

Designing a pilot that tells you something

A free sample of 300 words is the weakest evidence in the process. It is usually done by the best linguist available that day, with unlimited time. A paid pilot on real work is closer to what you will get later.

  1. Use your own difficult files. Mixed formats, a table, an embedded image with text, a section full of product names. Not a clean paragraph from your website.
  2. Make it the same for everyone. Same files, same instructions, same glossary, same deadline. Otherwise you are comparing conditions, not vendors.
  3. Plant a question. Leave one genuinely ambiguous sentence in the source. A strong vendor asks about it; a weak one guesses silently.
  4. Set a realistic deadline. The turnaround you would actually need in a normal week, not a generous one.
  5. Review blind. Your market reviewers score the output without knowing which vendor produced it, using one error scheme: accuracy, terminology, language, style, and formatting, each with a severity.
  6. Score the project, not just the text. Quote speed, query handling, file delivery, and how the vendor responds to your reviewers' feedback.
Score the feedback round. Send each vendor your reviewers' comments on the pilot and see what comes back. Do they fix the file only, or also update the glossary and memory? Do they push back where your reviewer was wrong? How a vendor handles its first correction is a good preview of the next two years.

Many pilots fail because the reviewers are the problem: preferential edits marked as errors, or comments that contradict the glossary. Agree the review rules before the pilot starts. Our piece on translation QA methods that cut cost without hurting quality explains how to separate real errors from preference, and terminology management for consistent global messaging covers the glossary side.

Security and data questions to settle before the contract

Translation vendors see content before it is public: unreleased products, contracts, HR files, financial reporting. Your security team will have its own questionnaire; make sure it covers the parts specific to translation work:

  • How files are transferred and stored, and who in the agency can access them.
  • Which freelancers and subcontractors work on your content, and in which countries.
  • Whether any machine translation or AI tool used on your content stores or learns from it.
  • What happens to your files, memories and termbases when the contract ends.

Where personal data is involved and the GDPR applies, the agency is a processor working for you, and Article 28 requires that you use only processors giving sufficient guarantees, that they do not engage another processor without your prior specific or general written authorisation, and that the data is deleted or returned at your choice when the services end. If your organisation requires a certified information security management system, ask whether the agency is certified to ISO/IEC 27001 and what the certificate's scope covers.

SLA terms worth writing down

"Fast, flexible, high quality" is not enforceable. A service level agreement turns it into numbers you can review every quarter. Typical terms:

AreaWhat to define
Quotes and intakeResponse time for a quote; how scope changes are confirmed
DeliveryShare of jobs delivered on the agreed date; how delays are announced and how early
QueriesHow fast vendor questions reach you and your answers reach the translator
QualityError categories and severities; the threshold that triggers a rework at no cost
CorrectionsTurnaround for fixing reported errors; confirmation that memory and glossary were updated
EscalationA named contact above the project manager, and when to use them
ReportingA regular report on volume, on-time delivery and quality findings, and a review meeting

Keep the numbers modest and real. An SLA the vendor cannot meet gets ignored by both sides within a month. Price belongs in the same review: compare total cost for the same scope, not rates. Comparing translation pricing like for like shows how.

After you sign: the first 90 days

The selection does not end with the contract. Plan a short onboarding: share style guides and reference material, run a terminology kickoff with your market reviewers, and agree how the first month's jobs will be reviewed more closely than usual. Hold the first quarterly review with real data from the SLA report. If you are weighing how much machine translation to allow as volume grows, the hybrid AI and human translation model is a useful starting point for that conversation. For a different take on the relationship itself, see why a language partner should be hired like a key executive.

The best evidence about an agency is how it handles its first correction, not its best sample.

FAQ

How many agencies should we shortlist?

Three is usually enough to compare. Send all of them the same questionnaire and the same pilot so the answers are comparable; more vendors mostly add evaluation work without adding information.

Should a pilot project be paid?

Yes. A paid pilot is treated as real work, staffed by the people you would actually get, and gives you the right to use the output. A free test is often done by the strongest linguist available that week.

Does ISO 17100 certification mean an agency is good?

It shows the agency has a documented process with translation, revision and final verification, and that it checks linguists against defined qualification routes. It does not tell you who will work on your files or how they handle your subject matter. Treat it as a filter, then test.

What SLA terms matter most?

Delivery against agreed dates, response time for queries and quotes, how corrections are handled and how quickly, who you escalate to, and how quality issues are classified and reported. Each term should be measurable and reviewed on a schedule.

Running a vendor selection?

We are happy to take part in a structured pilot on your own files, with the team who would actually do the work, and our specialists bring deep experience in English-to-Korean legal, technical and corporate content. See our services or ask about a pilot →

Work with us

Before you sign, make sure both versions agree.

Contracts, policies and regulatory filings translated into Korean and checked clause by clause.

Get a free quote