Make the source clear
Write a source message with an explicit request and confirmed information. Avoid ambiguous dates and unexplained abbreviations when they could confuse the recipient.
Choose the source and target languages in the translator. The model translates the supplied wording; it does not know your private agreements or schedule.
- Clarify the source request.
- Check the date format.
- Select the language pair.
Check practical details
Compare amounts, units, names and deadlines after translation. A polite formulation should not create a new promise or change who is expected to act.
Consider local reading conventions when reviewing dates and tone. If you adapt the wording, keep the underlying information unchanged.
- Verify the recipient name.
- Compare quantities and dates.
- Check responsibility and tone.
Review before sharing
Ask a capable target-language reader to review sensitive wording when appropriate. A back translation may reveal a problem, but it does not certify accuracy.
If the message is an email, copy the reviewed text into your email client and check the actual recipients and attachments yourself.
- Review important terminology.
- Read the final request.
- Check the email client details.
Worked example
Please confirm whether the 20 labels can be ready by Friday. We have not agreed a delivery date yet.
The translated message must ask for confirmation and preserve that no delivery date has been agreed.
This fictional example illustrates a request that must not become a confirmed delivery promise.
Before you finish
- Numbers and units unchanged.
- No invented commitment.
- Date is unambiguous.
- Tone fits the recipient.
Questions and answers
Can fluent wording hide a changed commitment?
Yes. Compare requests, conditions and promises directly with the source.
Does back translation prove accuracy?
No. It is a clue for review and can repeat or miss the same error.