On this page
Why a register, and not a style guideThe templateExample entriesScore a riskWhere to look for risksTypical treatmentsKeep it aliveIn briefAsk a company's risk team what could stop a product launch in Korea, and you will hear about certification, supply chain and exchange rates. Translation rarely appears, even though the Korean label, manual, privacy notice and contract are what regulators, courts and customers actually read. A risk that is not written down has no owner, and a risk without an owner is managed by whoever happens to notice it.
Why a register, and not a style guide
Style guides and glossaries manage quality. A risk register manages consequences. It asks different questions: what could go wrong, how likely is it, how bad would it be, who owns it, and what are we doing about it. The structure below follows the familiar risk management cycle described in ISO 31000: identify the risk, analyse it, evaluate it against your appetite, treat it, then monitor and review. Nothing about translation needs a special method. It just needs to be on the list.
The template
Use these columns. Copy them into whatever tool your risk team already uses.
| Column | What goes in it |
|---|---|
| ID | A short reference, e.g. TR-07 |
| Content type | Which documents: labels, privacy notice, contracts, UI, patents |
| Risk description | Cause, event and consequence in one sentence: "Because X, Y may happen, leading to Z" |
| Likelihood (1–5) | How likely, given current controls |
| Impact (1–5) | How bad if it happens: legal, regulatory, financial, reputational |
| Score | Likelihood × impact |
| Current controls | What already reduces it: revision, glossary, legal sign-off |
| Treatment | What you will add, change or accept |
| Owner | The person who bears the consequence, not just the person who orders the translation |
| Review date / status | When it is next checked; open, treated, accepted, closed |
Example entries
These entries are illustrative, written for a generic company launching a product in Korea. Your scores will differ.
| ID | Risk | L | I | Treatment | Owner |
|---|---|---|---|---|---|
| TR-01 | Because label and manual are translated separately, the Korean versions may contradict each other, leading to a hold at certification or a recall | 3 | 5 | Translate the regulatory set as one job with one glossary; regulatory sign-off against the certificate | Regulatory |
| TR-02 | Because staff paste documents into public AI tools, confidential information may be retained by a third party | 4 | 4 | Approved secure tool; written policy; block consumer tools for sensitive teams | IT security |
| TR-03 | Because the privacy notice is machine translated without legal review, it may describe processing inaccurately, leading to regulatory exposure | 2 | 5 | Professional translation, revision, Korean counsel review | Legal |
| TR-04 | Because the English source changes after translation starts, mixed versions may be published | 4 | 3 | Source freeze; change requests; version IDs on every file | Localization |
| TR-05 | Because the campaign tagline is translated literally, it may read as awkward or offensive | 3 | 3 | Korean copywriting brief; in-market review before launch | Marketing |
| TR-06 | Because only one translator knows our patent terminology, a departure may cause delays and inconsistency | 2 | 4 | Maintain termbase; second qualified translator trained | IP |
Score a risk
Use your company's own scales if it has them. If not, a five-point scale for each and a simple product works. Try it:
Bands used here: 1–4 low, 5–9 medium, 10–16 high, 20–25 critical. They are an example; align them with your enterprise risk scale.
Where to look for risks
- Content that leaves the company and stays: labels, manuals, contracts, notices, filings. Errors here are durable and public.
- Tools: which AI and MT tools are in use, by whom, with what data terms. See when machine translation exposes confidential data.
- Process gaps: no revision step, no glossary, no source freeze, no in-context review.
- People: single points of failure, generalists on specialist content, no in-market reviewer.
- Vendors: subcontracting you do not know about, unclear security scope. Our post on ISO 17100 and ISO 27001 when choosing a partner lists the questions.
- Past incidents: every correction, complaint or reprint is a risk that already happened once.
Typical treatments
Process controls
Revision by a second linguist, glossaries, source freeze, in-context reviewFewer errors reach publicationThe standard tools. ISO 17100 builds revision into the process; ISO 18587 sets requirements for full post-editing of MT.Sign-off and fallbacks
Legal and regulatory sign-off, governing-language clauses, staged rolloutsErrors that slip through cost lessA contract clause stating which language prevails does not prevent errors but limits what they can do.Right process per content type
Raw MT, post-editing or professional translationBudget follows riskSee the content-type matrix.Keep it alive
A register that is filled once and forgotten is worse than none, because it suggests the risk is managed. Review it on a schedule and whenever something changes: a new market, a new tool, a new regulation. Add every translation incident as a new entry or a rescored one. Related reading: product launch documentation for Korea and how legal teams prevent translation-driven patent loss. If you want a second opinion on your Korean translation risks, contact us or see our services.
In brief
Who should own the translation risk register?
Whoever owns localization or language services, with each risk assigned to the business owner who bears the consequence: legal, regulatory, product or marketing. The register is a shared document, not a localization team's private list.
How often should we review it?
At a fixed interval, for example quarterly, and whenever something changes: a new market, a new AI tool, a new regulation, a new product line, or an incident.
Can we use our company's existing risk scoring scale?
Yes, and you should. Use the same likelihood and impact scales your enterprise risk process already uses, so translation risks can be compared with other risks and escalated the same way.