Decide when AI translation is suitable for customer instructions by checking meaning, numbers, warnings, qualified review and the cost of correcting mistakes.
Direct answer: Use AI only as a draft aid when someone competent in the target language and subject can verify the complete instructions before customers receive them. For safety-relevant, regulated or consequential instructions, let a qualified specialist decide the translation and review process. If you cannot verify what a customer will understand and do, do not publish the AI translation merely because it sounds fluent or translates back neatly.
An error in descriptive copy may confuse a reader. An error in an instruction can change an action: what to connect, which amount to enter, when to stop or whether a warning applies. The quality test must follow that action, not just the apparent quality of the language.
The parent guide to choosing the right AI tool covers general evaluation. Here, use the consequence-preserving translation review, an editorial method that traces each instruction through its conditions, translation and expected reader behaviour.
Applies to: organisations translating instructions for customers, with UK conventions as the starting point. Product, sector and legal requirements vary by destination country and contract; obtain appropriate specialist advice for the actual use.
Decide what a mistranslation could cause
Begin with the actions customers will take. Identify instructions involving safety, payment, account access, irreversible changes or an eligibility condition. Keep these separate from descriptive background text so the review effort follows the consequence.
Write the outcome each step should produce. “The customer selects the correct delivery option before confirming the order” is inspectable. “The translation is natural” does not tell you whether the customer will choose the right option.
My default is specialist-led translation for instructions whose error could cause harm or a difficult-to-reverse loss. A competent practitioner may prefer machine translation followed by professional review for suitable material. That can be reasonable when the reviewer has authority to reject and redo it, rather than being asked to approve a fixed cheap output.
The Institute of Translation and Interpreting argues for professional expertise to lead technology choices in consequential translation. Its position on the value of professional translators is a professional association's judgement, not an independent benchmark proving an error rate for every AI system.
Repair the source before translating it
Save the approved source version and identify the person responsible for its technical meaning. Remove ambiguous pronouns, unexplained abbreviations and references such as “press it again” when several controls could fit. An unclear source creates a decision the translator should not have to guess.
Keep established product labels and interface terms consistent. If the destination interface is already translated, obtain its official labels rather than translating the English names independently. Otherwise the customer may understand the sentence but be unable to find the named control.
Create a short terminology list containing the source term, intended meaning and any approved target-language equivalent. Do not ask AI to invent an authoritative technical term and then use its answer as the reference for checking itself.
Resolve missing conditions with the document owner. Translation cannot establish an absent temperature limit, unsupported guarantee or unclear cancellation rule. Mark the gap and pause that passage until the governing information is available.
Keep action, condition and warning together
For each step, inspect the actor, action, object, condition and expected result. Confirm that the translation preserves who acts and whether the action is required, optional or prohibited. Pay particular attention to negative wording and phrases limiting when a step applies.
Numbers need more than digit matching. Check the unit, decimal convention, date format, currency and relationship to the instruction. A correctly copied number can still become wrong if its unit changes or a range becomes a single value.
Warnings must remain connected to the relevant action and appear before the customer could need them. A warning moved into a general note at the end may no longer perform the same practical function, even when every sentence was translated accurately.
| Element | Reviewer checks | Reason it matters |
|---|---|---|
| Action | Who does what to which object | Avoids applying a step to the wrong component or account |
| Condition | When the step applies and what must happen first | Preserves eligibility and prerequisites |
| Quantity | Value, unit, range and local notation | Prevents a correct digit string acquiring the wrong meaning |
| Warning | Prohibition, timing and location | Keeps risk information available before the action |
| Result | What the reader should observe | Makes failure recognisable instead of encouraging repetition |
This table is a review aid, not a product-safety standard. Use any applicable technical requirements and qualified review process for the actual product.
Check understanding with the right people
Have the target-language reviewer compare the complete translation with the approved source and reference material. Give them the context, screenshots or product terminology needed to understand the intended use, through an authorised channel.
Then ask a representative reader to explain the action in their own words, where doing so is appropriate. Use a safe mock-up or fictional example when the real action would carry risk. Do not ask an unqualified person to operate dangerous equipment as a translation test.
A reader misunderstanding the same step repeatedly is a reason to revise the instruction, even if it is grammatically correct. Record whether the problem comes from translation, layout, source ambiguity or missing prior knowledge. Each cause needs a different correction.
Do not treat translation back into English as independent assurance. It can highlight a discrepancy, but two generated versions may repeat a shared interpretation or smooth away the same ambiguity. Target-language and subject review remain necessary for consequential instructions.
Calculate the complete review cost
Imagine a small maker translating fourteen instruction steps, including five safety-relevant conditions. The following figures are illustrative assumptions, not professional quotations, market rates or measured AI performance.
Assume AI drafting costs £4 in additional service use. A qualified reviewer charges an illustrative £48 per hour and needs fifty minutes for the initial comparison: 50 ÷ 60 × £48 = £40. Correcting terminology and meaning takes another thirty-five minutes: 35 ÷ 60 × £48 = £28.
The total is already £4 + £40 + £28 = £72. A final twenty-minute review of the corrected document adds 20 ÷ 60 × £48 = £16, bringing the route to £88. It involves 50 + 35 + 20 = 105 minutes of professional review and correction, plus the maker's preparation and coordination time.
Now suppose a professional offers a hypothetical £90 package covering the same source, target language, review scope and final deliverable. The apparent saving from AI is only £90 − £88 = £2. Differences in responsibility, included revision and turnaround could easily matter more than those two pounds.
This comparison does not establish that professional work always costs £90 or that AI always creates this workload. It shows why comparing a generation fee with a finished translation quote is misleading. Ask providers to define equivalent deliverables, and let the qualified person choose an appropriate method.
Count all five safety-relevant conditions explicitly during review. Four correctly preserved conditions do not compensate for a fifth that reverses the safe action. Do not convert that small count into a reassuring overall accuracy percentage.
Preserve version control and a correction route
Assign the translated document a version linked to the approved source. Record its language, intended market, reviewer and unresolved limitations. This is an operational record, not a claim that a professional has approved work when they have not.
If the source changes, identify which translations require review. Do not assume a small English edit is inconsequential in another language. Keep the previous approved version available where necessary to understand what customers received.
Before publication, determine how you would correct an important error: replace the file, update the relevant interface and contact affected customers through the authorised process where needed. Legal duties vary, so obtain local advice when a particular error or product creates that question.
Avoid uploading confidential source material to an unapproved translation service. Establish its processing and retention arrangements before a trial, or use fictional text that preserves only the structure you need to assess.
Choose the route before your next release
- Spend thirty minutes identifying consequential steps and resolving source ambiguities with the responsible author.
- Obtain an appropriate target-language and subject review arrangement before generating a customer-facing draft. Agree the deliverable and revision scope.
- Reserve time before release for complete comparison, correction and safe reader-understanding checks. Let the reviewer set a realistic allowance for the material.
- Publish only the approved version and retain its relationship to the source. Stop if a material condition remains unclear or nobody can verify the target-language instruction.
Related guides
Frequently asked questions
Is AI translation acceptable for a simple password-reset guide?
It may help draft the language, but account access is still consequential. Check the exact interface labels, recovery conditions and warnings against the service's approved instructions, then have a competent target-language reviewer verify the meaning. Do not introduce shortcuts that change identity checks or security protections. If an official translation already exists, assess whether linking to it is more appropriate than creating a competing version. The workflow becomes simpler when the material is low-risk and easily verified, but a short guide is not automatically harmless simply because it contains only a few steps.
Can a bilingual colleague approve the translation?
Possibly, if their language ability, subject knowledge and assigned responsibility genuinely match the task. Being conversationally fluent does not automatically establish competence in technical terminology or safety-relevant instructions. Give the reviewer the approved source and sufficient time, and let them flag limits rather than expecting a courtesy approval. For consequential or regulated material, obtain the qualified review appropriate to the product and jurisdiction. The right question is whether the person can explain and verify the instruction customers will follow, not whether they are the nearest available colleague who speaks the language.
Should I translate screenshots as well as the written steps?
Check what the customer will actually see. A translated instruction referring to controls shown only in another language can cause confusion, but editing screenshot labels can also misrepresent the real interface. Prefer authentic screenshots from the supported target-language interface when you have permission to use them. Verify their version and account conditions alongside the text. If no localised interface exists, preserve its actual labels and explain them clearly in the surrounding instruction. Keep screenshots and text under the same review process so an update does not leave them describing different versions of the task.
Does a disclaimer make an unchecked translation acceptable?
No. A disclaimer does not help a customer identify which instruction is wrong or prevent them acting on it. If the document is intended to guide an action, provide a version that has been reviewed to the standard the consequence requires. Where the translation is only an informal aid, state its limited purpose and direct the reader to appropriate verified assistance before consequential action. Do not assume that a warning transfers your responsibilities to the user. Specific legal effects depend on the jurisdiction, product and contract and require advice from a qualified professional.
What if the target language needs more space than the design allows?
Adjust the layout rather than forcing the translator to remove a material condition. Check that warnings, labels and steps remain readable at the actual delivery size, including on mobile screens or printed inserts. A shortened phrase can be acceptable when the reviewer confirms that its meaning remains clear, but a fixed visual design is not evidence that every language can safely fit the same space. Test the final rendered version, not just a text document. If space remains inadequate, change the format or provide an appropriate accessible continuation that customers can actually use.
Can I reuse a reviewed translation for a similar product?
Only after checking whether the action, terminology, quantities and conditions are genuinely unchanged. Similar appearance is not enough. A different model, account flow or market may require a different instruction despite sharing much of the wording. Give the reviewer the differences and preserve the connection to the approved source version. Reuse can reduce work, but it should not bypass the review of changed meaning. If the original translation's rights or agreement restrict reuse, resolve that too. Treat an approved passage as a controlled asset with a defined scope, rather than a universal block of safe text.
Sources and verification
- Institute of Translation and Interpreting: When results matter, consulted 11 September 2026 for its professional position on expert-led translation. It is not used as an independent accuracy benchmark.
- The review method, fourteen-step example and all prices are illustrative editorial constructions. No translation was tested or professionally approved for this article.
- The parent was read in supplied project content. Its specified public URL could not be retrieved, so supplied internal paths are retained.
This article is practical guidance. Apply it in proportion to your tools, evidence, risks, and responsibilities.
