On this page
What the standards actually defineFour fit-for-purpose levelsTurning levels into numbersWhere undefined quality costs moneyWrite it down in one pageA procurement team asks for "good enough" Korean for a new product line. The vendor delivers lightly edited machine output. The help articles are fine. The warning label is not. Both sides did exactly what they agreed, because "good enough" was never defined per document.
The phrase is not the problem. Spending the same effort on an internal FAQ and a safety label would be wasteful in one direction or dangerous in the other. The problem is leaving "enough" undefined. This post sets out four quality levels, the process each one needs, and a simple way to turn them into measurable acceptance criteria.
What the standards actually define
Three references are worth knowing, because vendors will cite them and they mean less, or more, than people think.
The first two describe how a translation is produced. Only the third helps you judge a finished text. You need both kinds of reference: a process that makes the right outcome likely, and a measurement that tells you whether it happened.
Four fit-for-purpose levels
| Level | Typical content | Process | Acceptance |
|---|---|---|---|
| 1. Gist | Reading competitor pages, incoming emails, research | Raw MT or light post-editing | Reader understands the point; never published or quoted |
| 2. Internal | Internal knowledge base, meeting notes, low-traffic support macros | Full post-editing (ISO 18587) or translation with self-check | No critical errors; score threshold set low |
| 3. Published | Product UI, help center, website, marketing | Translation plus revision by a second linguist (ISO 17100), in-context check | No critical errors, few majors, higher threshold, style guide followed |
| 4. Critical | Contracts, labels, safety and medical text, patents, financial disclosures | As level 3, plus subject-matter review and owner sign-off | Zero critical and zero major errors; every number verified |
Two rules keep this honest. First, the level belongs to the content, not the budget. If a warning label is level 4, it stays level 4 when the quarter is tight. Second, content moves up when it is reused: a level 2 support macro copied into a public FAQ is now level 3 text with level 2 quality. For the difference between light and full post-editing in detail, see MT post-editing guidelines.
Turning levels into numbers
MQM-style scoring counts errors in a sample, weights them by severity, and normalises by word count. A widely used set of default severity multipliers is 1 for minor, 5 for major and 25 for critical. The worked example on the MQM site computes a simple score as one minus penalty points divided by word count, and treats any critical error as an automatic fail. Try it on a sample:
Weights 1 / 5 / 25. Score = (1 − penalty ÷ words) × 100. Any critical error fails. Illustrative model; calibrate thresholds on your own samples.
The useful part is not the number but the conversation it forces. Ask your reviewers to score a sample of Korean you already consider acceptable, and set each level's threshold just below that. Then the vendor, the reviewer and the budget owner are arguing about the same thing.
Where undefined quality costs money
The cost of a vague standard rarely shows up as a line item. It shows up as rework when a level 2 text turns out to be public, as support tickets about an unclear setting, or as a regulator's question about a label. The fix costs more than doing it right would have, because it now involves a release, a reprint or a lawyer. We look at the commercial side in silent attrition in SaaS and at reducing QA cost without lowering the bar in sampling and risk-based QA.
Write it down in one page
- List your content types and assign each a level.
- For each level, state the process: MT, post-editing, translation plus revision, expert review.
- State the acceptance rule: allowed errors by severity and a score threshold.
- Name who signs off at levels 3 and 4.
- Put the level in every translation request, so the vendor prices and staffs it correctly.
With that page in place, "good enough" becomes a perfectly respectable instruction. For choosing who does the work, see choosing an affordable translation service without compromising quality and AI vs human translation.
Need a quality definition your vendors can work to?
We help teams assign levels to their Korean content and set acceptance criteria, then translate to them. Talk to us →