How do you translate a risk register so that a possible event does not become a confirmed incident, a mitigation plan does not become an installed control, and a numerical score is not mistaken for a universal safety rating? Risk management translation must preserve the relationships among objectives, uncertainty, events, causes, consequences, likelihood, controls and decisions. This guide focuses on precise translation of risk terms, likelihood scales, residual risks, escalation thresholds and treatment records.
Readers searching for ISO 31073:2022 risk vocabulary translation, translate risk assessment terms, bilingual risk register, likelihood versus probability translation, residual risk definition across languages or multilingual risk treatment reports need decisions they can audit. A reader in another country must be able to distinguish what might happen from what has happened, which consequences are being estimated, what assumptions support an assessment, and who accepts any remaining exposure.
ISO 31073:2022 is a published ISO vocabulary standard covering generic risk management terms. The standard provides terminology; it does not make one organisation’s risk appetite, scoring matrix or compliance duties automatically valid everywhere. The article uses original teaching examples to explain translation practice, not proprietary definitions copied from the standard. Context, local law and the organisation’s documented assessment method remain essential.
Quick answer: preserve status, source, scope and decision
To translate risk terminology without mixing uncertain events, their consequences, controls and management decisions, begin with the document’s purpose and audience. Mark what is known, what is merely proposed, what depends on a condition, and what still needs independent checking. Keep names, numbers, dates, units, geography, evidence levels, owner roles and any exceptions attached to the statements they qualify. This protects the reader from an apparently fluent translation that reaches a materially different decision.
A useful working rule is to read a multinational risk register twice before translating: first for its ordinary meaning, and then for the decisions a foreign-language reader might make after seeing it. The second reading matters most. The difference between ‘may’, ‘must’, ‘recommended’, ‘approved’, ‘tested’ and ‘implemented’ can alter conduct. The translator should never upgrade a suggestion into an obligation or convert an incomplete record into a verified outcome.
What this standard does—and does not—establish
ISO 31073:2022 is a vocabulary standard defining generic terms related to organisational risk management. It is not a universal table of acceptable risk scores, a regulatory permission to operate, or a substitute for the organisation’s own approved risk criteria.
The authoritative starting point for the edition and formal scope is the ISO catalogue entry for ISO 31073:2022. This article applies practical translation principles to original fictional scenarios. It does not claim to provide the complete standard, ISO’s licensed definitions or a professional certification opinion. Organisation-specific terminology, jurisdictional requirements and current source records must be checked with responsible specialists.
Eight foundations for translating the record
1. Uncertainty is not an incident
Risk descriptions address uncertainty around objectives; incident reports record events that occurred. Translating a possible event in the past tense can turn planning information into false news, while translating an actual incident conditionally can hide an important operational fact.
For risk owners and reviewers, the editorial question is not simply whether every technical noun appears in the target language. Ask what action a reader could justifiably take from this sentence, which document supports that action and whether any caveat was lost when the sentence became smoother. Write down the preferred term, its operational meaning, the owning specialist and the one context in which the term would be misleading. This small discipline makes terminology reusable without flattening the underlying reasoning.
2. Scores are defined locally
A score of four may mean rare, possible, likely or severe depending on the scale. Do not translate digits as self-explanatory assessments. Carry the legend, orientation, time horizon and calculation method with the translated chart.
For risk owners and reviewers, the editorial question is not simply whether every technical noun appears in the target language. Ask what action a reader could justifiably take from this sentence, which document supports that action and whether any caveat was lost when the sentence became smoother. Write down the preferred term, its operational meaning, the owning specialist and the one context in which the term would be misleading. This small discipline makes terminology reusable without flattening the underlying reasoning.
3. Consequences need direction and unit
A financial loss, a health impact and a service delay cannot be treated as the same outcome. Preserve whose objectives are affected, magnitude, currency, unit, exposure and any upper or lower bounds.
For risk owners and reviewers, the editorial question is not simply whether every technical noun appears in the target language. Ask what action a reader could justifiably take from this sentence, which document supports that action and whether any caveat was lost when the sentence became smoother. Write down the preferred term, its operational meaning, the owning specialist and the one context in which the term would be misleading. This small discipline makes terminology reusable without flattening the underlying reasoning.
4. Control and treatment are not synonyms
A control may already exist; a treatment is a decision or process for changing risk. The presence of a proposed action in a register does not prove the action has been implemented or tested.
For risk owners and reviewers, the editorial question is not simply whether every technical noun appears in the target language. Ask what action a reader could justifiably take from this sentence, which document supports that action and whether any caveat was lost when the sentence became smoother. Write down the preferred term, its operational meaning, the owning specialist and the one context in which the term would be misleading. This small discipline makes terminology reusable without flattening the underlying reasoning.
5. Appetite, tolerance and acceptance need owners
Statements about acceptable risk reflect governance roles and decisions, not a translator’s personal view. Keep the actor, condition, scope and documented authority attached to every acceptance sentence.
For risk owners and reviewers, the editorial question is not simply whether every technical noun appears in the target language. Ask what action a reader could justifiably take from this sentence, which document supports that action and whether any caveat was lost when the sentence became smoother. Write down the preferred term, its operational meaning, the owning specialist and the one context in which the term would be misleading. This small discipline makes terminology reusable without flattening the underlying reasoning.
6. Use evidence dates
Risk changes over time. A translated report with a score but no as-of date can be read as current when it is not. Preserve revision, monitoring date, incident data period and next-review trigger.
For risk owners and reviewers, the editorial question is not simply whether every technical noun appears in the target language. Ask what action a reader could justifiably take from this sentence, which document supports that action and whether any caveat was lost when the sentence became smoother. Write down the preferred term, its operational meaning, the owning specialist and the one context in which the term would be misleading. This small discipline makes terminology reusable without flattening the underlying reasoning.
7. Preserve negative outcomes and opportunities
Risk management may involve potential adverse effects and opportunities. An overly narrow translation of risk as catastrophe can obscure uncertainty affecting objectives in either direction.
For risk owners and reviewers, the editorial question is not simply whether every technical noun appears in the target language. Ask what action a reader could justifiably take from this sentence, which document supports that action and whether any caveat was lost when the sentence became smoother. Write down the preferred term, its operational meaning, the owning specialist and the one context in which the term would be misleading. This small discipline makes terminology reusable without flattening the underlying reasoning.
8. Ask the owner before normalising terms
Risk terminology overlaps with insurance, medicine, safety engineering, finance and cybersecurity. Maintain an approved project glossary and escalate terms with domain-specific meanings instead of guessing from an ordinary dictionary.
For risk owners and reviewers, the editorial question is not simply whether every technical noun appears in the target language. Ask what action a reader could justifiably take from this sentence, which document supports that action and whether any caveat was lost when the sentence became smoother. Write down the preferred term, its operational meaning, the owning specialist and the one context in which the term would be misleading. This small discipline makes terminology reusable without flattening the underlying reasoning.
Practical translation cases: invented source statements, risks and editorial decisions
The following examples are deliberately fictional and are not quotations from ISO 31073:2022. Each case starts with a realistic English source statement. The analysis shows how a translation can accidentally create an unsupported claim, then describes a safer interpretation and a check a bilingual reviewer can perform. The examples work across language pairs because the central problem is conceptual: preserve evidence, time, scope and authority before choosing elegant words.
1. Risk statement
Source example: “There is a possibility that a supplier outage delays dispatch in one region.” Imagine a bilingual editor receiving this sentence as one entry in a multinational risk register. The source author is not merely conveying a subject; the author is describing a particular stage of knowledge or action. Before translating, identify the actor, the relevant time, the statement’s evidentiary status and the consequence a reasonable reader might infer. Note which details are actually present and which would have to be confirmed elsewhere.
How readers can be misled: Writing that a supplier outage has happened creates a false incident report. This error can occur even where every individual dictionary choice seems plausible. A professional-looking document may encourage a reader to act on a conclusion that the underlying record never supported. Do not conceal this difficulty by replacing a technical sentence with a comforting generality; the restriction, condition or distinction is often precisely why the source author included it.
Meaning-preserving version: Retain the possible event, affected objective and geographic boundary. If the target language requires a longer construction, use it. The objective is to reproduce the original authority and claim boundary, not the number of words. Keep nearby notes, numerical legends and linked definitions available, because isolated sentences can produce contradictory translations when detached from their tables or procedural context.
Review question: Check incident records before changing tense. Then ask a second reader to explain the practical implication without seeing the original. If the reader believes a permission, conclusion or event exists when the source describes only a possibility or work in progress, revise the wording. This is an observable comprehension failure, not a matter of literary preference.
2. Objective
Working sentence: “The stated objective is to ship 95 percent of orders within two days.” The writer of a multinational risk register may assume the local team already knows the project history. A distant reader usually does not. Identify whether the sentence is an instruction, description, forecast, hypothesis, recommendation or decision. Preserve that status explicitly when the equivalent word in another language could be interpreted more broadly.
Problem to avoid: Reducing the objective to speedy delivery removes the measurable benchmark. A smooth paraphrase can make the sentence less accurate if it removes a qualifier or substitutes a more familiar category. This is especially serious where the target document will be entered into a database, compared across countries or read later without the speaker present to clarify the original intent.
Editorial treatment: Keep the target, denominator, service population and time measure. Avoid importing conclusions from a different paragraph or a more recent document. Where a defined term has no compact equivalent, consider a short explanation on first use and consistent terminology afterward. If an ambiguity cannot be resolved from the available records, flag it for the owner rather than silently inventing an answer.
Evidence check: Read the performance definition used by the business. A reviewer should be able to point to the source line and supporting material for each claim in the translation. When a number, role or date appears in both languages, confirm that it refers to the same unit, person, period and stage. Record unresolved questions before release.
3. Cause
Fictional extract: “An ageing network switch may contribute to a service interruption.” Consider the recipient: a colleague, regulator, researcher or member of the public may understand the same phrase differently. The purpose of translation is to transfer the source statement’s justified meaning into that reader’s working language. That requires preserving not only a term, but also the relationship among the term, the people involved and the evidence.
False implication: Calling an ageing switch the proven cause of an incident is unwarranted. The damage is not always dramatic or immediate. It may appear later, when an action tracker, funding note, safety review or public summary uses the translated sentence as evidence of something stronger than it really says. A good editor notices the inflation at the point of translation rather than during a later dispute.
Safer expression: Preserve the causal uncertainty and distinction from investigation findings. Make the qualifying information visible in the same sentence or an immediately adjacent sentence. Do not bury it in a glossary that readers may never open. Where the source is itself ambiguous, give the responsible author a specific question about scope, timing or authority instead of asking for a vague approval of the whole translation.
Release test: Check whether fault analysis has concluded. Check whether the corrected text remains valid if extracted into a slide, email or table cell. A translation that only works with an inaccessible footnote may fail in actual operational use. Carry essential qualifiers into the excerpt that readers will see.
4. Event
Illustrative wording: “Loss of a primary data connection is the assessed event.” Begin with a concrete mental model of what the source is saying and what it is not saying. Do not translate a specialised term before understanding the procedure that generated the statement. A careful translator will often ask for the adjacent chart, evidence register, decision minute or method note before choosing the final phrase.
Likely mistranslation: Translating ‘event’ as loss amount confuses occurrence with effect. This changes the reader’s mental model. The target text can be grammatically excellent and still imply a different event, certainty, permission or outcome. In specialised translation, that is a factual error rather than a harmless stylistic difference, and it deserves the same attention as a wrong figure.
Correction: Identify the occurrence separately from cost and downstream delays. Explain an unfamiliar term when necessary, but never replace a carefully limited claim with a broader promise. The wording should remain defensible when read by someone outside the original team. If the document travels across jurisdictions, retain defined names and record where local procedures could require separate legal or technical review.
Verification task: Compare the risk description and impact table. Finally, compare the translated sentence against a small checklist: actor, action, time, condition, evidence, measurement and next decision. Not all seven appear in every sentence, but none should be invented. A second reviewer can mark which attributes were preserved and which require author confirmation.
5. Consequence
Source example: “The impact model includes missed orders and emergency shipping costs.” Imagine a bilingual editor receiving this sentence as one entry in a multinational risk register. The source author is not merely conveying a subject; the author is describing a particular stage of knowledge or action. Before translating, identify the actor, the relevant time, the statement’s evidentiary status and the consequence a reasonable reader might infer. Note which details are actually present and which would have to be confirmed elsewhere.
How readers can be misled: Collapsing distinct effects into a single financial total hides what is being valued. This error can occur even where every individual dictionary choice seems plausible. A professional-looking document may encourage a reader to act on a conclusion that the underlying record never supported. Do not conceal this difficulty by replacing a technical sentence with a comforting generality; the restriction, condition or distinction is often precisely why the source author included it.
Meaning-preserving version: Keep individual consequence categories and avoid double counting. If the target language requires a longer construction, use it. The objective is to reproduce the original authority and claim boundary, not the number of words. Keep nearby notes, numerical legends and linked definitions available, because isolated sentences can produce contradictory translations when detached from their tables or procedural context.
Review question: Verify units and baseline assumptions. Then ask a second reader to explain the practical implication without seeing the original. If the reader believes a permission, conclusion or event exists when the source describes only a possibility or work in progress, revise the wording. This is an observable comprehension failure, not a matter of literary preference.
6. Likelihood category
Working sentence: “The matrix labels a category ‘possible’ for a stated annual frequency band.” The writer of a multinational risk register may assume the local team already knows the project history. A distant reader usually does not. Identify whether the sentence is an instruction, description, forecast, hypothesis, recommendation or decision. Preserve that status explicitly when the equivalent word in another language could be interpreted more broadly.
Problem to avoid: Treating ‘possible’ as an everyday vague adjective removes the scale meaning. A smooth paraphrase can make the sentence less accurate if it removes a qualifier or substitutes a more familiar category. This is especially serious where the target document will be entered into a database, compared across countries or read later without the speaker present to clarify the original intent.
Editorial treatment: Translate the category with its defined frequency range. Avoid importing conclusions from a different paragraph or a more recent document. Where a defined term has no compact equivalent, consider a short explanation on first use and consistent terminology afterward. If an ambiguity cannot be resolved from the available records, flag it for the owner rather than silently inventing an answer.
Evidence check: Read the matrix legend in the source document. A reviewer should be able to point to the source line and supporting material for each claim in the translation. When a number, role or date appears in both languages, confirm that it refers to the same unit, person, period and stage. Record unresolved questions before release.
7. Probability
Fictional extract: “The model estimates a 0.02 annual probability under specified assumptions.” Consider the recipient: a colleague, regulator, researcher or member of the public may understand the same phrase differently. The purpose of translation is to transfer the source statement’s justified meaning into that reader’s working language. That requires preserving not only a term, but also the relationship among the term, the people involved and the evidence.
False implication: Reporting two percent per month radically alters the estimate. The damage is not always dramatic or immediate. It may appear later, when an action tracker, funding note, safety review or public summary uses the translated sentence as evidence of something stronger than it really says. A good editor notices the inflation at the point of translation rather than during a later dispute.
Safer expression: Retain numerical value, time basis and conditional assumptions. Make the qualifying information visible in the same sentence or an immediately adjacent sentence. Do not bury it in a glossary that readers may never open. Where the source is itself ambiguous, give the responsible author a specific question about scope, timing or authority instead of asking for a vague approval of the whole translation.
Release test: Recalculate conversions only if required and approved. Check whether the corrected text remains valid if extracted into a slide, email or table cell. A translation that only works with an inaccessible footnote may fail in actual operational use. Carry essential qualifiers into the excerpt that readers will see.
8. Frequency
Illustrative wording: “Three disruptions were recorded over five years of observations.” Begin with a concrete mental model of what the source is saying and what it is not saying. Do not translate a specialised term before understanding the procedure that generated the statement. A careful translator will often ask for the adjacent chart, evidence register, decision minute or method note before choosing the final phrase.
Likely mistranslation: Calling that three disruptions per year invents a trend. This changes the reader’s mental model. The target text can be grammatically excellent and still imply a different event, certainty, permission or outcome. In specialised translation, that is a factual error rather than a harmless stylistic difference, and it deserves the same attention as a wrong figure.
Correction: Preserve event count and the five-year observation period. Explain an unfamiliar term when necessary, but never replace a carefully limited claim with a broader promise. The wording should remain defensible when read by someone outside the original team. If the document travels across jurisdictions, retain defined names and record where local procedures could require separate legal or technical review.
Verification task: Review the incident log and observation gaps. Finally, compare the translated sentence against a small checklist: actor, action, time, condition, evidence, measurement and next decision. Not all seven appear in every sentence, but none should be invented. A second reviewer can mark which attributes were preserved and which require author confirmation.
9. Severity
Source example: “The impact score is high because of critical patient-service exposure.” Imagine a bilingual editor receiving this sentence as one entry in a multinational risk register. The source author is not merely conveying a subject; the author is describing a particular stage of knowledge or action. Before translating, identify the actor, the relevant time, the statement’s evidentiary status and the consequence a reasonable reader might infer. Note which details are actually present and which would have to be confirmed elsewhere.
How readers can be misled: Converting high to near-certain confuses consequence size with likelihood. This error can occur even where every individual dictionary choice seems plausible. A professional-looking document may encourage a reader to act on a conclusion that the underlying record never supported. Do not conceal this difficulty by replacing a technical sentence with a comforting generality; the restriction, condition or distinction is often precisely why the source author included it.
Meaning-preserving version: Keep severity apart from frequency and name the service affected. If the target language requires a longer construction, use it. The objective is to reproduce the original authority and claim boundary, not the number of words. Keep nearby notes, numerical legends and linked definitions available, because isolated sentences can produce contradictory translations when detached from their tables or procedural context.
Review question: Inspect the severity descriptor table. Then ask a second reader to explain the practical implication without seeing the original. If the reader believes a permission, conclusion or event exists when the source describes only a possibility or work in progress, revise the wording. This is an observable comprehension failure, not a matter of literary preference.
10. Risk matrix
Working sentence: “The register multiplies ordinal likelihood and impact categories for prioritisation.” The writer of a multinational risk register may assume the local team already knows the project history. A distant reader usually does not. Identify whether the sentence is an instruction, description, forecast, hypothesis, recommendation or decision. Preserve that status explicitly when the equivalent word in another language could be interpreted more broadly.
Problem to avoid: Treating the result as a physical probability suggests false precision. A smooth paraphrase can make the sentence less accurate if it removes a qualifier or substitutes a more familiar category. This is especially serious where the target document will be entered into a database, compared across countries or read later without the speaker present to clarify the original intent.
Editorial treatment: Explain the score as defined prioritisation, not a universal quantified fact. Avoid importing conclusions from a different paragraph or a more recent document. Where a defined term has no compact equivalent, consider a short explanation on first use and consistent terminology afterward. If an ambiguity cannot be resolved from the available records, flag it for the owner rather than silently inventing an answer.
Evidence check: Check the adopted scoring convention. A reviewer should be able to point to the source line and supporting material for each claim in the translation. When a number, role or date appears in both languages, confirm that it refers to the same unit, person, period and stage. Record unresolved questions before release.
11. Uncertainty range
Fictional extract: “Expected losses vary widely across alternative input assumptions.” Consider the recipient: a colleague, regulator, researcher or member of the public may understand the same phrase differently. The purpose of translation is to transfer the source statement’s justified meaning into that reader’s working language. That requires preserving not only a term, but also the relationship among the term, the people involved and the evidence.
False implication: Publishing a single unqualified number removes sensitivity information. The damage is not always dramatic or immediate. It may appear later, when an action tracker, funding note, safety review or public summary uses the translated sentence as evidence of something stronger than it really says. A good editor notices the inflation at the point of translation rather than during a later dispute.
Safer expression: Retain the range and method limitation in the translation. Make the qualifying information visible in the same sentence or an immediately adjacent sentence. Do not bury it in a glossary that readers may never open. Where the source is itself ambiguous, give the responsible author a specific question about scope, timing or authority instead of asking for a vague approval of the whole translation.
Release test: Read the sensitivity analysis and date. Check whether the corrected text remains valid if extracted into a slide, email or table cell. A translation that only works with an inaccessible footnote may fail in actual operational use. Carry essential qualifiers into the excerpt that readers will see.
12. Existing control
Illustrative wording: “Backup power is installed but its last full-load test failed.” Begin with a concrete mental model of what the source is saying and what it is not saying. Do not translate a specialised term before understanding the procedure that generated the statement. A careful translator will often ask for the adjacent chart, evidence register, decision minute or method note before choosing the final phrase.
Likely mistranslation: Describing the presence of equipment as a successful control ignores effectiveness. This changes the reader’s mental model. The target text can be grammatically excellent and still imply a different event, certainty, permission or outcome. In specialised translation, that is a factual error rather than a harmless stylistic difference, and it deserves the same attention as a wrong figure.
Correction: State installation status and the failed test separately. Explain an unfamiliar term when necessary, but never replace a carefully limited claim with a broader promise. The wording should remain defensible when read by someone outside the original team. If the document travels across jurisdictions, retain defined names and record where local procedures could require separate legal or technical review.
Verification task: Inspect maintenance and validation evidence. Finally, compare the translated sentence against a small checklist: actor, action, time, condition, evidence, measurement and next decision. Not all seven appear in every sentence, but none should be invented. A second reviewer can mark which attributes were preserved and which require author confirmation.
13. Proposed control
Source example: “The team proposes an additional failover connection next quarter.” Imagine a bilingual editor receiving this sentence as one entry in a multinational risk register. The source author is not merely conveying a subject; the author is describing a particular stage of knowledge or action. Before translating, identify the actor, the relevant time, the statement’s evidentiary status and the consequence a reasonable reader might infer. Note which details are actually present and which would have to be confirmed elsewhere.
How readers can be misled: A proposal is not an operating safeguard today. This error can occur even where every individual dictionary choice seems plausible. A professional-looking document may encourage a reader to act on a conclusion that the underlying record never supported. Do not conceal this difficulty by replacing a technical sentence with a comforting generality; the restriction, condition or distinction is often precisely why the source author included it.
Meaning-preserving version: Keep future status and responsible implementation owner. If the target language requires a longer construction, use it. The objective is to reproduce the original authority and claim boundary, not the number of words. Keep nearby notes, numerical legends and linked definitions available, because isolated sentences can produce contradictory translations when detached from their tables or procedural context.
Review question: Verify procurement and commissioning dates. Then ask a second reader to explain the practical implication without seeing the original. If the reader believes a permission, conclusion or event exists when the source describes only a possibility or work in progress, revise the wording. This is an observable comprehension failure, not a matter of literary preference.
14. Preventive action
Working sentence: “Training is intended to reduce the chance of misrouting hazardous goods.” The writer of a multinational risk register may assume the local team already knows the project history. A distant reader usually does not. Identify whether the sentence is an instruction, description, forecast, hypothesis, recommendation or decision. Preserve that status explicitly when the equivalent word in another language could be interpreted more broadly.
Problem to avoid: Saying training removes all risk makes an absolute safety promise. A smooth paraphrase can make the sentence less accurate if it removes a qualifier or substitutes a more familiar category. This is especially serious where the target document will be entered into a database, compared across countries or read later without the speaker present to clarify the original intent.
Editorial treatment: Preserve the intended mechanism and any monitoring limits. Avoid importing conclusions from a different paragraph or a more recent document. Where a defined term has no compact equivalent, consider a short explanation on first use and consistent terminology afterward. If an ambiguity cannot be resolved from the available records, flag it for the owner rather than silently inventing an answer.
Evidence check: Check training completion and later incidents. A reviewer should be able to point to the source line and supporting material for each claim in the translation. When a number, role or date appears in both languages, confirm that it refers to the same unit, person, period and stage. Record unresolved questions before release.
15. Detective action
Fictional extract: “An alert is configured to flag unusual payment patterns.” Consider the recipient: a colleague, regulator, researcher or member of the public may understand the same phrase differently. The purpose of translation is to transfer the source statement’s justified meaning into that reader’s working language. That requires preserving not only a term, but also the relationship among the term, the people involved and the evidence.
False implication: Translating the alert as fraud prevention overstates what detection does. The damage is not always dramatic or immediate. It may appear later, when an action tracker, funding note, safety review or public summary uses the translated sentence as evidence of something stronger than it really says. A good editor notices the inflation at the point of translation rather than during a later dispute.
Safer expression: Distinguish detection from prevention and investigation. Make the qualifying information visible in the same sentence or an immediately adjacent sentence. Do not bury it in a glossary that readers may never open. Where the source is itself ambiguous, give the responsible author a specific question about scope, timing or authority instead of asking for a vague approval of the whole translation.
Release test: Review the alert definition and handling workflow. Check whether the corrected text remains valid if extracted into a slide, email or table cell. A translation that only works with an inaccessible footnote may fail in actual operational use. Carry essential qualifiers into the excerpt that readers will see.
16. Corrective action
Illustrative wording: “The incident response team repaired the failed service after the disruption.” Begin with a concrete mental model of what the source is saying and what it is not saying. Do not translate a specialised term before understanding the procedure that generated the statement. A careful translator will often ask for the adjacent chart, evidence register, decision minute or method note before choosing the final phrase.
Likely mistranslation: Calling the repair a preventive control changes its timing. This changes the reader’s mental model. The target text can be grammatically excellent and still imply a different event, certainty, permission or outcome. In specialised translation, that is a factual error rather than a harmless stylistic difference, and it deserves the same attention as a wrong figure.
Correction: Preserve that it responded after an event. Explain an unfamiliar term when necessary, but never replace a carefully limited claim with a broader promise. The wording should remain defensible when read by someone outside the original team. If the document travels across jurisdictions, retain defined names and record where local procedures could require separate legal or technical review.
Verification task: Check the incident timeline. Finally, compare the translated sentence against a small checklist: actor, action, time, condition, evidence, measurement and next decision. Not all seven appear in every sentence, but none should be invented. A second reviewer can mark which attributes were preserved and which require author confirmation.
17. Residual risk
Source example: “After tested controls, a remaining interruption risk is assessed as medium.” Imagine a bilingual editor receiving this sentence as one entry in a multinational risk register. The source author is not merely conveying a subject; the author is describing a particular stage of knowledge or action. Before translating, identify the actor, the relevant time, the statement’s evidentiary status and the consequence a reasonable reader might infer. Note which details are actually present and which would have to be confirmed elsewhere.
How readers can be misled: Translating medium as zero risk creates unsupported reassurance. This error can occur even where every individual dictionary choice seems plausible. A professional-looking document may encourage a reader to act on a conclusion that the underlying record never supported. Do not conceal this difficulty by replacing a technical sentence with a comforting generality; the restriction, condition or distinction is often precisely why the source author included it.
Meaning-preserving version: Identify the remaining exposure and the rating method. If the target language requires a longer construction, use it. The objective is to reproduce the original authority and claim boundary, not the number of words. Keep nearby notes, numerical legends and linked definitions available, because isolated sentences can produce contradictory translations when detached from their tables or procedural context.
Review question: Compare pre-control and post-control assessments. Then ask a second reader to explain the practical implication without seeing the original. If the reader believes a permission, conclusion or event exists when the source describes only a possibility or work in progress, revise the wording. This is an observable comprehension failure, not a matter of literary preference.
18. Inherent risk
Working sentence: “The team assessed exposure before considering existing controls.” The writer of a multinational risk register may assume the local team already knows the project history. A distant reader usually does not. Identify whether the sentence is an instruction, description, forecast, hypothesis, recommendation or decision. Preserve that status explicitly when the equivalent word in another language could be interpreted more broadly.
Problem to avoid: Substituting the post-control rating conceals the initial scenario. A smooth paraphrase can make the sentence less accurate if it removes a qualifier or substitutes a more familiar category. This is especially serious where the target document will be entered into a database, compared across countries or read later without the speaker present to clarify the original intent.
Editorial treatment: Specify which assessment state the number represents. Avoid importing conclusions from a different paragraph or a more recent document. Where a defined term has no compact equivalent, consider a short explanation on first use and consistent terminology afterward. If an ambiguity cannot be resolved from the available records, flag it for the owner rather than silently inventing an answer.
Evidence check: Find the assessment methodology. A reviewer should be able to point to the source line and supporting material for each claim in the translation. When a number, role or date appears in both languages, confirm that it refers to the same unit, person, period and stage. Record unresolved questions before release.
19. Risk owner
Fictional extract: “The operations director is accountable for oversight of this risk.” Consider the recipient: a colleague, regulator, researcher or member of the public may understand the same phrase differently. The purpose of translation is to transfer the source statement’s justified meaning into that reader’s working language. That requires preserving not only a term, but also the relationship among the term, the people involved and the evidence.
False implication: Naming the translator or analyst as owner changes accountability. The damage is not always dramatic or immediate. It may appear later, when an action tracker, funding note, safety review or public summary uses the translated sentence as evidence of something stronger than it really says. A good editor notices the inflation at the point of translation rather than during a later dispute.
Safer expression: Preserve the formally assigned role, not an assumed contact. Make the qualifying information visible in the same sentence or an immediately adjacent sentence. Do not bury it in a glossary that readers may never open. Where the source is itself ambiguous, give the responsible author a specific question about scope, timing or authority instead of asking for a vague approval of the whole translation.
Release test: Check the approved register. Check whether the corrected text remains valid if extracted into a slide, email or table cell. A translation that only works with an inaccessible footnote may fail in actual operational use. Carry essential qualifiers into the excerpt that readers will see.
20. Action owner
Illustrative wording: “The facilities team must install a monitoring sensor by 30 June.” Begin with a concrete mental model of what the source is saying and what it is not saying. Do not translate a specialised term before understanding the procedure that generated the statement. A careful translator will often ask for the adjacent chart, evidence register, decision minute or method note before choosing the final phrase.
Likely mistranslation: Calling the accountable risk owner the implementer can misdirect work. This changes the reader’s mental model. The target text can be grammatically excellent and still imply a different event, certainty, permission or outcome. In specialised translation, that is a factual error rather than a harmless stylistic difference, and it deserves the same attention as a wrong figure.
Correction: Keep responsibility for action separate from risk accountability. Explain an unfamiliar term when necessary, but never replace a carefully limited claim with a broader promise. The wording should remain defensible when read by someone outside the original team. If the document travels across jurisdictions, retain defined names and record where local procedures could require separate legal or technical review.
Verification task: Verify the action tracker. Finally, compare the translated sentence against a small checklist: actor, action, time, condition, evidence, measurement and next decision. Not all seven appear in every sentence, but none should be invented. A second reviewer can mark which attributes were preserved and which require author confirmation.
21. Deadline
Source example: “Control testing is due by the end of the following quarter.” Imagine a bilingual editor receiving this sentence as one entry in a multinational risk register. The source author is not merely conveying a subject; the author is describing a particular stage of knowledge or action. Before translating, identify the actor, the relevant time, the statement’s evidentiary status and the consequence a reasonable reader might infer. Note which details are actually present and which would have to be confirmed elsewhere.
How readers can be misled: Replacing a relative deadline with a guessed calendar date may mislead. This error can occur even where every individual dictionary choice seems plausible. A professional-looking document may encourage a reader to act on a conclusion that the underlying record never supported. Do not conceal this difficulty by replacing a technical sentence with a comforting generality; the restriction, condition or distinction is often precisely why the source author included it.
Meaning-preserving version: Resolve the source reporting period before converting the date. If the target language requires a longer construction, use it. The objective is to reproduce the original authority and claim boundary, not the number of words. Keep nearby notes, numerical legends and linked definitions available, because isolated sentences can produce contradictory translations when detached from their tables or procedural context.
Review question: Consult the document version and local calendar. Then ask a second reader to explain the practical implication without seeing the original. If the reader believes a permission, conclusion or event exists when the source describes only a possibility or work in progress, revise the wording. This is an observable comprehension failure, not a matter of literary preference.
22. Escalation trigger
Working sentence: “A measured outage beyond two hours requires escalation.” The writer of a multinational risk register may assume the local team already knows the project history. A distant reader usually does not. Identify whether the sentence is an instruction, description, forecast, hypothesis, recommendation or decision. Preserve that status explicitly when the equivalent word in another language could be interpreted more broadly.
Problem to avoid: Omitting the duration threshold changes when the protocol activates. A smooth paraphrase can make the sentence less accurate if it removes a qualifier or substitutes a more familiar category. This is especially serious where the target document will be entered into a database, compared across countries or read later without the speaker present to clarify the original intent.
Editorial treatment: Keep the trigger, unit and required destination. Avoid importing conclusions from a different paragraph or a more recent document. Where a defined term has no compact equivalent, consider a short explanation on first use and consistent terminology afterward. If an ambiguity cannot be resolved from the available records, flag it for the owner rather than silently inventing an answer.
Evidence check: Read the escalation procedure. A reviewer should be able to point to the source line and supporting material for each claim in the translation. When a number, role or date appears in both languages, confirm that it refers to the same unit, person, period and stage. Record unresolved questions before release.
23. Risk appetite
Fictional extract: “The board has a low appetite for unplanned interruption of emergency services.” Consider the recipient: a colleague, regulator, researcher or member of the public may understand the same phrase differently. The purpose of translation is to transfer the source statement’s justified meaning into that reader’s working language. That requires preserving not only a term, but also the relationship among the term, the people involved and the evidence.
False implication: Turning a governance preference into a legal prohibition overstates its force. The damage is not always dramatic or immediate. It may appear later, when an action tracker, funding note, safety review or public summary uses the translated sentence as evidence of something stronger than it really says. A good editor notices the inflation at the point of translation rather than during a later dispute.
Safer expression: Attribute the preference to the board and preserve service scope. Make the qualifying information visible in the same sentence or an immediately adjacent sentence. Do not bury it in a glossary that readers may never open. Where the source is itself ambiguous, give the responsible author a specific question about scope, timing or authority instead of asking for a vague approval of the whole translation.
Release test: Verify the adopted risk statement. Check whether the corrected text remains valid if extracted into a slide, email or table cell. A translation that only works with an inaccessible footnote may fail in actual operational use. Carry essential qualifiers into the excerpt that readers will see.
24. Tolerance threshold
Illustrative wording: “The procedure permits no more than one failed backup test per cycle.” Begin with a concrete mental model of what the source is saying and what it is not saying. Do not translate a specialised term before understanding the procedure that generated the statement. A careful translator will often ask for the adjacent chart, evidence register, decision minute or method note before choosing the final phrase.
Likely mistranslation: Calling the tolerance a recommended target rather than a limit weakens the rule. This changes the reader’s mental model. The target text can be grammatically excellent and still imply a different event, certainty, permission or outcome. In specialised translation, that is a factual error rather than a harmless stylistic difference, and it deserves the same attention as a wrong figure.
Correction: Preserve inequality, cycle definition and authorising source. Explain an unfamiliar term when necessary, but never replace a carefully limited claim with a broader promise. The wording should remain defensible when read by someone outside the original team. If the document travels across jurisdictions, retain defined names and record where local procedures could require separate legal or technical review.
Verification task: Check the threshold notation. Finally, compare the translated sentence against a small checklist: actor, action, time, condition, evidence, measurement and next decision. Not all seven appear in every sentence, but none should be invented. A second reviewer can mark which attributes were preserved and which require author confirmation.
25. Risk acceptance
Source example: “A named executive approved a limited exception until the upgrade date.” Imagine a bilingual editor receiving this sentence as one entry in a multinational risk register. The source author is not merely conveying a subject; the author is describing a particular stage of knowledge or action. Before translating, identify the actor, the relevant time, the statement’s evidentiary status and the consequence a reasonable reader might infer. Note which details are actually present and which would have to be confirmed elsewhere.
How readers can be misled: Translating acceptance as permanent safety approval removes the expiry and conditions. This error can occur even where every individual dictionary choice seems plausible. A professional-looking document may encourage a reader to act on a conclusion that the underlying record never supported. Do not conceal this difficulty by replacing a technical sentence with a comforting generality; the restriction, condition or distinction is often precisely why the source author included it.
Meaning-preserving version: Keep scope, authorised signer, expiry and exception controls. If the target language requires a longer construction, use it. The objective is to reproduce the original authority and claim boundary, not the number of words. Keep nearby notes, numerical legends and linked definitions available, because isolated sentences can produce contradictory translations when detached from their tables or procedural context.
Review question: Review the signed exception record. Then ask a second reader to explain the practical implication without seeing the original. If the reader believes a permission, conclusion or event exists when the source describes only a possibility or work in progress, revise the wording. This is an observable comprehension failure, not a matter of literary preference.
26. Treatment option
Working sentence: “Management is comparing avoidance, reduction, transfer and acceptance.” The writer of a multinational risk register may assume the local team already knows the project history. A distant reader usually does not. Identify whether the sentence is an instruction, description, forecast, hypothesis, recommendation or decision. Preserve that status explicitly when the equivalent word in another language could be interpreted more broadly.
Problem to avoid: Writing that all four measures have been implemented contradicts the decision stage. A smooth paraphrase can make the sentence less accurate if it removes a qualifier or substitutes a more familiar category. This is especially serious where the target document will be entered into a database, compared across countries or read later without the speaker present to clarify the original intent.
Editorial treatment: Present options as alternatives until one is authorised. Avoid importing conclusions from a different paragraph or a more recent document. Where a defined term has no compact equivalent, consider a short explanation on first use and consistent terminology afterward. If an ambiguity cannot be resolved from the available records, flag it for the owner rather than silently inventing an answer.
Evidence check: Inspect the minutes of the risk committee. A reviewer should be able to point to the source line and supporting material for each claim in the translation. When a number, role or date appears in both languages, confirm that it refers to the same unit, person, period and stage. Record unresolved questions before release.
27. Insurance transfer
Fictional extract: “The company bought coverage subject to exclusions and deductibles.” Consider the recipient: a colleague, regulator, researcher or member of the public may understand the same phrase differently. The purpose of translation is to transfer the source statement’s justified meaning into that reader’s working language. That requires preserving not only a term, but also the relationship among the term, the people involved and the evidence.
False implication: Claiming risk disappeared because insurance exists hides retained exposure. The damage is not always dramatic or immediate. It may appear later, when an action tracker, funding note, safety review or public summary uses the translated sentence as evidence of something stronger than it really says. A good editor notices the inflation at the point of translation rather than during a later dispute.
Safer expression: State that certain financial consequences may be transferred subject to terms. Make the qualifying information visible in the same sentence or an immediately adjacent sentence. Do not bury it in a glossary that readers may never open. Where the source is itself ambiguous, give the responsible author a specific question about scope, timing or authority instead of asking for a vague approval of the whole translation.
Release test: Read the coverage summary and exclusions. Check whether the corrected text remains valid if extracted into a slide, email or table cell. A translation that only works with an inaccessible footnote may fail in actual operational use. Carry essential qualifiers into the excerpt that readers will see.
28. Reassessment
Illustrative wording: “The risk is scheduled for review after a supplier change.” Begin with a concrete mental model of what the source is saying and what it is not saying. Do not translate a specialised term before understanding the procedure that generated the statement. A careful translator will often ask for the adjacent chart, evidence register, decision minute or method note before choosing the final phrase.
Likely mistranslation: Calling the assessment up to date after the change defeats the trigger. This changes the reader’s mental model. The target text can be grammatically excellent and still imply a different event, certainty, permission or outcome. In specialised translation, that is a factual error rather than a harmless stylistic difference, and it deserves the same attention as a wrong figure.
Correction: Describe the pending reassessment and what changed. Explain an unfamiliar term when necessary, but never replace a carefully limited claim with a broader promise. The wording should remain defensible when read by someone outside the original team. If the document travels across jurisdictions, retain defined names and record where local procedures could require separate legal or technical review.
Verification task: Compare the supplier record to assessment date. Finally, compare the translated sentence against a small checklist: actor, action, time, condition, evidence, measurement and next decision. Not all seven appear in every sentence, but none should be invented. A second reviewer can mark which attributes were preserved and which require author confirmation.
A complete workflow for a multilingual project
1. Identify the reader and consequence
Decide whether the translation is for technical reviewers, executives, staff, suppliers, researchers or the general public. Different audiences need different supporting explanations, but they must receive the same substantive facts. Write down the operational decision the document is expected to support so the reviewer knows where an error would matter.
2. Freeze the source version
Record a document ID, author, date, language, approval status and attachments. A later English revision should not be silently mixed with an earlier translation. Changes affecting numbers, conditions, status or roles need explicit reconciliation and a fresh review of dependent target-language passages.
3. Build a concept glossary, not a word list
For every recurring specialist term, store its meaning in this project, an approved target-language expression, a sentence that illustrates it, an owner and any prohibited misleading equivalents. A glossary should reveal conceptual boundaries instead of hiding them behind one-to-one substitutions.
4. Translate the conditions as carefully as the headline
First draft meaning, then refine readability. Check negation, conditional clauses, comparative figures, scale labels, units, time zones, named authorities and exception language. Never let an appealing headline contradict the qualifiers that make a claim accurate.
5. Conduct a domain review
Ask a relevant specialist to confirm that the translation represents a defensible operational statement. A bilingual editor checks language; a domain reviewer checks whether the statement is technically meaningful. Neither person should assume the other has done both jobs.
6. Test comprehension without the original
Give a sample passage to a target-language reader and ask them what happened, what remains uncertain, who is responsible and what they should do next. Compare the answers with the source. Where the answers diverge, revise the wording and test the confusing segment again.
7. Approve and distribute controlled versions
Record the approver, release date, document status and intended channels. If a translation is withdrawn or superseded, make the status visible to recipients. A published translation can do more harm than an unpublished draft if it remains easy to find after the source assumptions have changed.
8. Maintain corrections
When a reader reports an unclear or misleading passage, reproduce the issue, identify the affected language versions, judge the consequence, make a controlled correction and notify downstream users when necessary. Translation quality is a continuing evidence practice, not a one-time proofreading ceremony.
Quality checklist before any translation is released
A finished translation of risk registers, likelihood scales, consequence statements and treatment records should survive a specific test: can a new reader accurately describe the statement’s source, current status, time frame, scope and next action without guessing? Ask the reviewer to verify exact numbers, dates, confidence and conditions against the controlled source; confirm that the target reader has enough context to tell observation from inference and an option from a decision. The test is stronger than asking whether the prose ‘sounds natural’, because beautiful prose can conceal material mistakes.
For consequential statements, retain traceable source references and evidence of review. Do not introduce invented approvals, certifications, zero-risk claims or universal conclusions. Where a legal, safety, clinical or engineering judgment is involved, assign it to the responsible professional rather than asking a language editor to make an unauthorised decision. The translation team’s responsibility is to communicate the evidence and its limits accurately.
Frequently asked questions
Can I translate a technical document with machine translation alone?
Automatic tools can help create a first draft, especially for controlled and repetitive wording, but risk registers, likelihood scales, consequence statements and treatment records contain distinctions that may change decisions. Have competent humans verify status, uncertainty, figures, dates, exceptions, specialist terminology and intended audience before publishing consequential claims.
Should every technical term have only one translated word?
Consistency is useful, but not at the expense of accuracy. A concept can need a short explanation, a retained original-language label or different forms in different grammatical contexts. Keep one conceptual definition and record approved expressions with examples.
What if a source phrase is ambiguous?
Ask the author a focused question and record the answer. If confirmation is unavailable, preserve uncertainty or label the translation as provisional for the intended audience. Do not create authority or precision merely to make the sentence read smoothly.
Does citing an ISO number mean the organisation is certified?
No. Citing a published standard or guidance document is not the same as demonstrating that an organisation has met a certification scheme or legal obligation. Check what the specific edition actually covers and describe any certification claim only when independently supported.
What is the best final check before release?
Ask a target-language reader to state the practical action, evidence level, responsibility and timing they understand. If their explanation differs materially from the source, the translation needs repair even if it is grammatically flawless.
Can this article replace specialist advice?
No. It teaches document translation and evidence discipline. Specialist regulatory, clinical, legal, engineering, safety and local emergency requirements must be checked with the relevant authorised sources and qualified people.
Official reference and the existing eduKate learning pathway
Verify the edition and scope at the ISO catalogue for ISO 31073:2022. This article explains an original translation workflow and invented teaching cases. It does not reproduce licensed ISO clauses, promise compliance or imply ISO endorsement.
For the broader system of transferring meaning across languages, follow the existing Master Art of Translation — Complete System (EDKSG-TRANS-MASTER-WORLD-000). The protected Vocabulary Learning Hub builds the concepts behind specialist terms, while How English Works — Translation and Meaning Across Languages helps readers understand how syntax, context and reader interpretation interact. This article is one narrowly scoped application underneath those established resources, not a new general translation hub.
The final measure of success is not how professional a paragraph appears. It is whether a reader working in another language can make the same justified interpretation, recognise the same uncertainty and understand the same next decision as a careful reader of the source. Translate what the evidence allows, preserve what remains unresolved, and give the responsible people enough clarity to act without creating new facts.