How a Translation Agency Boosts Global Business in 2025

Updated · 6 min read
On this pageThe reference process: ISO 17100A project from start to finishIntake: where most problems are preventedPreparation: the invisible engineeringTranslation and revisionAutomated QA and final verificationClose-out: what makes the next job cheaperQuestions that show whether the steps happenShort answers

A buyer sends a 6,000-word user guide to an agency on Monday and gets the Korean back on Friday. From the outside it looks like one person typed for four days. In practice the file passed through intake, preparation, translation, a second-linguist revision, automated checks and a final verification, and the typing was perhaps half of the time. If you know what those translation process steps are, you can tell which ones you are paying for and which ones were quietly skipped.

This post walks through a normal agency project for an English-to-Korean job, step by step, and ends with the questions that reveal whether the steps really happen. For the wider question of how to pick an agency in the first place, see trust criteria for choosing a translation agency, and for a full selection process with a pilot scorecard and SLA terms, how to choose a professional translation agency.

The reference process: ISO 17100

Most agency workflows are built around ISO 17100, the international standard for translation services, published in 2015. It sets requirements for the parts of the process that affect quality and delivery. The production steps it describes are: translation (including the translator's own check), revision by a second person, and then optional review, optional proofreading, and a final verification before release. Revision by a second linguist is the step the standard makes obligatory, and it is also the step most often dropped from cheap quotes.

The standard also covers what happens around production: documented linguist competences, agreements with the client, feedback handling, archiving and data protection. Raw machine translation followed by post-editing is outside its scope; that has its own standard, ISO 18587, which sets requirements for full human post-editing of machine output.

A project from start to finish

StageWhoWhat actually happensWhat you see
1. IntakeProject managerChecks the files open, counts words, runs them against the translation memory, asks about audience, purpose and formatA quote with new words and matches listed separately; a few questions
2. PreparationPM or engineerConverts files into a bilingual format, protects tags and code, loads your glossary and memory, writes instructionsNothing, unless the files are scanned PDFs or locked
3. TranslationTranslatorTranslates, researches terms, checks own work against the sourceQuestions about ambiguous terms
4. RevisionSecond linguistCompares every segment against the source: meaning, omissions, terminology, registerUsually nothing; sometimes a query
5. Automated QAPM or reviserRuns checks for numbers, tags, untranslated segments, glossary terms, punctuationNothing
6. Final verificationProject managerExports back to the original format, checks layout, confirms all instructions were followedThe delivered file
7. Close-outProject managerUpdates the translation memory and glossary, archives, records feedbackBetter matches on the next job

Intake: where most problems are prevented

The project manager's first job is to find out what you did not say. Is the Korean for engineers or end users? Will it be printed, so text expansion matters for layout? Are there product names that must stay in English? Is there an older Korean version that should be kept consistent? A good intake email has three to five questions like these. An agency that sends no questions on a technical manual has probably not opened the file.

Intake also produces the word-count analysis. Agencies compare the new text against their translation memory of your earlier jobs. Microsoft's localization guidance describes how partial, "fuzzy" matches get a percentage score, and notes that projects often set a threshold, such as 65%, below which a match is treated as new text. That is why your quote shows several word counts with different rates. More on reading those numbers in translation memory reuse as an asset.

Preparation: the invisible engineering

Translators rarely work in your Word file or InDesign document directly. The agency converts it into a bilingual format in a CAT tool, where formatting is protected as tags and only text is editable. Exchange formats such as XLIFF (an OASIS standard) and TMX for translation memories let files and memories move between tools. Done well, the Korean comes back in the same layout with nothing broken. Done badly, you get a file where every bold word has lost its formatting, or where a translator has accidentally translated a variable name in your software strings.

This is also when the PM writes the job instructions: glossary, style sheet, reference material, the audience and the questions answered at intake. The translator should never have to guess these.

Translation and revision

The translator works segment by segment, with memory matches and glossary terms shown alongside. Queries go back through the PM to you. For English-to-Korean, typical queries are about who the reader is (which affects the level of formality throughout), whether a term should be a loanword or a native-Korean term, and what an ambiguous English sentence actually means. "Remove the cover and the filter" can mean two parts or one assembly; the translator needs to know which.

The reviser then reads source and target side by side. This is not proofreading. The reviser is looking for a missed sentence, a negation that flipped, a unit that changed, a term that drifted between chapters. A translator cannot reliably catch these in their own work, which is why the standard insists on a second person. For how this step changes when machine translation is involved, see machine translation post-editing with human QA.

Translation-only tiers. Many agencies sell a cheaper tier with no second linguist. That can be fine for internal reading. For anything published, signed, filed or sent to customers, ask for revision explicitly and check that the quote names it.

Automated QA and final verification

After revision, QA software checks what humans miss when tired: a number that differs between source and target, a missing tag, a segment left in English, a glossary term not used, double spaces, inconsistent translations of the same sentence. The tool produces a list; a person decides which warnings are real. Then the PM exports the file, opens it in its original format, and checks that tables, captions and page breaks still work in Korean. Korean text usually takes a different amount of space from English, so a button label or table column that fitted in English may overflow.

Close-out: what makes the next job cheaper

When you send corrections after delivery, a good agency puts them into the translation memory and glossary, not just into your file. Otherwise the same error comes back on the next update. Ask at the end of each project whether your feedback was recorded, and ask for a TMX export of your memory once a year; it is your asset. For service levels and response times you can write into an agreement, see working with an agency: SLAs and communication.

Questions that show whether the steps happen

  1. Who will translate and who will revise this file, and what are their subject backgrounds?
  2. Is revision by a second linguist included in this quote?
  3. Which QA checks do you run, and can I see the report for this job?
  4. How will you handle my glossary and earlier Korean versions?
  5. How are my corrections fed back into the memory?
  6. If machine translation is used at any stage, where, and who post-edits it?
  7. How are my files stored, and who can access them?

Clear answers to these tell you more than any brochure. If you are weighing an agency against an individual translator, the same questions apply; see translation company vs freelancer.

Short answers

Is revision by a second linguist always included?

Not always. ISO 17100 treats revision by a second person as a required step, but many agencies sell a translation-only tier for internal or low-risk text. Ask which tier your quote covers and get it in writing.

What is the difference between revision and review?

In ISO 17100 terms, revision is a bilingual comparison of source and target by a second linguist. Review is an optional monolingual read of the target for its intended use, often by a subject expert or your own team.

Does an ISO 17100 certificate guarantee a good Korean translation?

No. It shows the agency has a documented process and checks its linguists' qualifications. It says nothing about who will work on your file. Ask for the profile of the assigned translator and reviser as well.

Want to see the process on your own file?

Send a sample and we will show you the intake questions, the revision notes and the QA report, not just the Korean. Contact us →

Work with us

Clear scope, clear price, Korean you can rely on.

Translation and localization into Korean with specialist review and a quote before work starts.

Get a free quote