Translate English-only content into several languages.
Make the same idea work for readers in several languages, with the right meaning, terminology, and tone.
Try it now
Copy the prompt into your AI tool of choice, then answer its questions as they come.
Paste it into any AI chat to start. For most people, this is all you need.
Everything on this page in one paste: the prompt plus the full plan, every step and what to check. Use it for longer moves, to plan ahead, to share with a colleague, or if your AI can't open links.
How it goes
What the AI will do
- Translate the content for the intended audiences and check meaning, terminology, tone, and formatting across versions.
What to have ready
- The English content; target languages or audiences if known. Existing terminology and translations can help.
Where you come in
- Clarify ambiguous source wording and choose between useful regional or tonal alternatives.
What you'll get
You have usable translated versions for the chosen audiences, with terminology aligned and material ambiguities or review limits identified.
You're done when
You have usable translated versions for the chosen audiences, with terminology aligned and material ambiguities or review limits identified.
These are general instructions, not a description of this user's particular AI system, tools, access, or circumstances. Adapt the method to the user's goal and the capabilities you can actually use, while preserving the activity's essential sequence, review points, and intended result. ### Start with the activity and the user's context Read the complete activity and guide the user through it. Use the activity prompt yourself; the user does not need to paste it again. Keep the responsibilities of the user, the AI, and any colleague clear. Begin with what the user has already supplied. Establish the intended result and resolve missing context through focused questions when needed. Work within the activity's stated scope, permissions, required confirmations, and stopping points, including any deliberate order for introducing information. Make progress with the available information and reasonable, clearly identified assumptions where the activity allows them. ### Check the capabilities needed for this work Inspect relevant available tools, connectors, and data. Use small, relevant, non-destructive checks to establish whether necessary access or a capability actually works. Naming a product does not establish access to it. Let this activity determine what needs checking; do not impose a universal preliminary questionnaire or a full system audit. When useful access is missing: - Explain what you cannot reach and how that material would help. - Investigate practical setup, connection, export, or other access alternatives before asking the user to gather material or troubleshoot. - If progress depends on access, request only the specific user action or permission needed to enable it or provide the material another way. Continue useful independent work while awaiting the response. - Offer to walk the user through an export or upload. Welcome files, links, copied text, rough notes, or an interview as supported by your system and the activity, and use the best available route. If the missing access is optional, continue with what is available. ### Ask focused questions and respect the answers Ask questions only when necessary to complete the work well or satisfy the activity's required review points. Build on answers already supplied. Ask one question at a time, or a small group of closely related questions. Wait on work that depends on the answer, and continue useful work that does not. Explain unfamiliar language with examples where helpful. Confirm answers or decisions you supply on the user's behalf before treating them as the user's final answers or decisions. This does not require separate approval of every sourced finding; follow the activity's specific review requirements. ### Keep evidence and independent contributions distinct Distinguish evidence, inference, and missing information. Check your work against the source material. Use independent agents when your system actually supports delegation and independent investigation or review would improve the work: - Give each agent a bounded brief and the context appropriate to its role. - Keep discovery independent until synthesis where the activity requires it. Preserve any requirement for the user or colleagues to contribute before seeing other explanations. - Follow the activity's stated fallback and any required confirmation when independent agents or fresh contexts are unavailable. Preserve reviewer isolation where required; describe shared-context or sequential passes accurately. ### Produce, check, and revise the result Do the substantive investigation and production. Carry the activity through to the most complete, usable result within its scope, rather than ending with a plan or handing the main work back to the user. When missing information does not prevent useful work, proceed with clearly identified assumptions where the activity permits them. Check the result against the activity's completion criteria. At each substantive delivery, state what is complete and any material unfinished work, assumptions, helpful missing information, and remaining uncertainty. Explain how these affect what the user can use, and help the user revise the result. Preserve the activity's stopping point. Do not turn a rehearsal, investigation, or test-design activity into execution that the user has not authorized. Translate this English-language content into the languages needed by its intended audiences, preserving its meaning and making each version natural to read. ### 1. Understand the source, audiences, and context. Read the entire source, including tables, captions, notes, and text within images where accessible. Identify the purpose, audience, desired action, tone, and any expressions whose meaning depends on context. Check what file formats and translation or document tools are actually available. Help me supply missing text or a supported export when necessary. Use relevant available emails, messages and chats, meeting transcripts, briefs, documents, and project files to understand the intended recipients, market, terminology, and prior wording decisions. Consult existing glossaries and previous translations where useful, checking their relevance and currency rather than copying them uncritically. Establish target languages and regional variants. Ask a focused question if these are unknown or if source ambiguity would change the translation. When two formulations would carry meaning differently, present concrete alternatives with plain-English explanations—for example, a formal address or a warmer conversational one—and wait before treating a consequential choice as settled. ### 2. Prepare the terminology and translate. Identify names, product terms, technical language, abbreviations, and repeated phrases that need consistent treatment. Use established terminology where supported and keep a small working glossary for this task. Preserve names or quoted original terms when translation would misidentify them. Translate the whole content, preserving claims, qualifications, commitments, quantities, and relationships between sections. Make idioms natural without adding or removing meaning. Adapt date, number, and address presentation to the audience where appropriate, but do not change currencies, measurements, substantive examples, or promises without an agreed basis. Keep important unresolved terms visible for review rather than hiding a guess in fluent prose. If the original itself is unclear, ask about that first or provide two clearly explained candidate readings. Maintain formatting and editable structure where the tools permit; account for text expansion and writing direction in the output. ### 3. Check each version and the collection. - Compare every version against the English source section by section. - Check omissions, additions, negation, dates, numbers, names, links, tone, and terminology. - Check that tables and lists still associate each value with the correct label. - Read each translation for naturalness and consistency, using available language capabilities honestly. Where another capable reviewer or independent language check is available and useful, have it inspect the translation against the source and resolve material findings. Back-translation may help reveal a discrepancy but is not proof of quality. Do not claim native-speaker, independent, or professional review that did not occur. Identify any language or format that your actual capabilities cannot assess adequately. ### 4. Deliver and refine. Provide complete versions in suitable editable files or clearly separated text, labeled by language and regional variant. Keep notes about terminology choices and unresolved wording outside the translated copy. Inspect generated documents where possible to catch overflow, missing characters, or direction errors. Invite feedback from me or a supplied reviewer and revise consistently across affected versions. Finish with the translations, useful terminology notes, and a precise account of material remaining uncertainty. Do not publish or distribute the content as part of this activity. These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.
View full AI instructions
Translate English-only content into several languages.
What the AI will do
- Translate the content for the intended audiences and check meaning, terminology, tone, and formatting across versions.
What you can provide
- The English content; target languages or audiences if known. Existing terminology and translations can help.
Where you'll take part
- Clarify ambiguous source wording and choose between useful regional or tonal alternatives.
What you'll get
You have usable translated versions for the chosen audiences, with terminology aligned and material ambiguities or review limits identified.
Activity context
Make the same idea work for readers in several languages, with the right meaning, terminology, and tone.
For the user
Share the content and the audiences or languages you have in mind. The AI can consult relevant briefs, correspondence, glossaries, and earlier translations. You’ll settle meaningful ambiguities and choose a tone or regional variant where needed.
Guidance for the AI
These are general instructions, not a description of this user's particular AI system, tools, access, or circumstances. Adapt the method to the user's goal and the capabilities you can actually use, while preserving the activity's essential sequence, review points, and intended result.
Start with the activity and the user's context
Read the complete activity and guide the user through it. Use the activity prompt yourself; the user does not need to paste it again. Keep the responsibilities of the user, the AI, and any colleague clear.
Begin with what the user has already supplied. Establish the intended result and resolve missing context through focused questions when needed. Work within the activity's stated scope, permissions, required confirmations, and stopping points, including any deliberate order for introducing information. Make progress with the available information and reasonable, clearly identified assumptions where the activity allows them.
Check the capabilities needed for this work
Inspect relevant available tools, connectors, and data. Use small, relevant, non-destructive checks to establish whether necessary access or a capability actually works. Naming a product does not establish access to it. Let this activity determine what needs checking; do not impose a universal preliminary questionnaire or a full system audit.
When useful access is missing:
- Explain what you cannot reach and how that material would help.
- Investigate practical setup, connection, export, or other access alternatives before asking the user to gather material or troubleshoot.
- If progress depends on access, request only the specific user action or permission needed to enable it or provide the material another way. Continue useful independent work while awaiting the response.
- Offer to walk the user through an export or upload. Welcome files, links, copied text, rough notes, or an interview as supported by your system and the activity, and use the best available route. If the missing access is optional, continue with what is available.
Ask focused questions and respect the answers
Ask questions only when necessary to complete the work well or satisfy the activity's required review points. Build on answers already supplied. Ask one question at a time, or a small group of closely related questions. Wait on work that depends on the answer, and continue useful work that does not. Explain unfamiliar language with examples where helpful.
Confirm answers or decisions you supply on the user's behalf before treating them as the user's final answers or decisions. This does not require separate approval of every sourced finding; follow the activity's specific review requirements.
Keep evidence and independent contributions distinct
Distinguish evidence, inference, and missing information. Check your work against the source material.
Use independent agents when your system actually supports delegation and independent investigation or review would improve the work:
- Give each agent a bounded brief and the context appropriate to its role.
- Keep discovery independent until synthesis where the activity requires it. Preserve any requirement for the user or colleagues to contribute before seeing other explanations.
- Follow the activity's stated fallback and any required confirmation when independent agents or fresh contexts are unavailable. Preserve reviewer isolation where required; describe shared-context or sequential passes accurately.
Produce, check, and revise the result
Do the substantive investigation and production. Carry the activity through to the most complete, usable result within its scope, rather than ending with a plan or handing the main work back to the user. When missing information does not prevent useful work, proceed with clearly identified assumptions where the activity permits them.
Check the result against the activity's completion criteria. At each substantive delivery, state what is complete and any material unfinished work, assumptions, helpful missing information, and remaining uncertainty. Explain how these affect what the user can use, and help the user revise the result.
Preserve the activity's stopping point. Do not turn a rehearsal, investigation, or test-design activity into execution that the user has not authorized.
Your AI prompt
Translate this English-language content into the languages needed by its intended audiences, preserving its meaning and making each version natural to read.
1. Understand the source, audiences, and context.
Read the entire source, including tables, captions, notes, and text within images where accessible. Identify the purpose, audience, desired action, tone, and any expressions whose meaning depends on context. Check what file formats and translation or document tools are actually available. Help me supply missing text or a supported export when necessary.
Use relevant available emails, messages and chats, meeting transcripts, briefs, documents, and project files to understand the intended recipients, market, terminology, and prior wording decisions. Consult existing glossaries and previous translations where useful, checking their relevance and currency rather than copying them uncritically.
Establish target languages and regional variants. Ask a focused question if these are unknown or if source ambiguity would change the translation. When two formulations would carry meaning differently, present concrete alternatives with plain-English explanations—for example, a formal address or a warmer conversational one—and wait before treating a consequential choice as settled.
2. Prepare the terminology and translate.
Identify names, product terms, technical language, abbreviations, and repeated phrases that need consistent treatment. Use established terminology where supported and keep a small working glossary for this task. Preserve names or quoted original terms when translation would misidentify them.
Translate the whole content, preserving claims, qualifications, commitments, quantities, and relationships between sections. Make idioms natural without adding or removing meaning. Adapt date, number, and address presentation to the audience where appropriate, but do not change currencies, measurements, substantive examples, or promises without an agreed basis.
Keep important unresolved terms visible for review rather than hiding a guess in fluent prose. If the original itself is unclear, ask about that first or provide two clearly explained candidate readings. Maintain formatting and editable structure where the tools permit; account for text expansion and writing direction in the output.
3. Check each version and the collection.
- Compare every version against the English source section by section.
- Check omissions, additions, negation, dates, numbers, names, links, tone, and terminology.
- Check that tables and lists still associate each value with the correct label.
- Read each translation for naturalness and consistency, using available language capabilities honestly.
Where another capable reviewer or independent language check is available and useful, have it inspect the translation against the source and resolve material findings. Back-translation may help reveal a discrepancy but is not proof of quality. Do not claim native-speaker, independent, or professional review that did not occur. Identify any language or format that your actual capabilities cannot assess adequately.
4. Deliver and refine.
Provide complete versions in suitable editable files or clearly separated text, labeled by language and regional variant. Keep notes about terminology choices and unresolved wording outside the translated copy. Inspect generated documents where possible to catch overflow, missing characters, or direction errors.
Invite feedback from me or a supplied reviewer and revise consistently across affected versions. Finish with the translations, useful terminology notes, and a precise account of material remaining uncertainty. Do not publish or distribute the content as part of this activity.
Done when
You have usable translated versions for the chosen audiences, with terminology aligned and material ambiguities or review limits identified.
These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.
These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.