Practical guide · Word documents

Write a translation brief your reviewer can check

Explain who will read the document, which terms matter and what must stay unchanged. Then use those instructions to review the translated wording and the Word export.

October 30, 2026 · Original preparation exercise

Try it with a small Word example

Our fictional customer update uses the name Demo Workspace, a date, three files, a filename and an approval condition. The English source has been created and checked. The brief below prepares an English to French review exercise.

This is an original, manually prepared example. The product, date and quantities are fictional. No translation or translated export produced by the service is presented here.

Start with the reader and the purpose

“Make it natural” leaves the reviewer with little to check. Say who the text is for, where it will appear and what the reader should do next. A customer announcement and an internal note may need different wording even when they describe the same change.

For this exercise, an agency is preparing a customer update in French for France. The brief asks for clear, direct language and vous. For your document, replace those choices with the audience and tone you actually need.

Name the terms that matter

Write down a small set of preferred terms before the work starts. Explain product names separately from ordinary words: Demo Workspace stays unchanged, while the ordinary word workspace has a French preference. Check each term in context rather than treating a word list as a guarantee.

Preferred terms for this fictional example
English sourcePreferred French
workspaceespace de travail
project filesfichiers du projet
review notesnotes de révision

Adapt the grammar to the surrounding sentence. If your team already uses another term, change the preference and tell the reviewer why. An inconsistent term can recur throughout the document; defining it gives you a concrete review question.

Protect references and facts

List the text that must remain exact. In this source, {project_name} is a placeholder and launch-checklist.docx is a filename. If the filename is rewritten, a colleague may look for a file that does not exist.

The source also mentions three files and the fictional date 14 November 2026. The date can use a local format in French, but its meaning and the quantity must stay the same. Ask for unclear references to be flagged rather than completed with invented facts.

A translation brief you can adapt

Copy this example, then replace its audience, language and terms with your own. In the Reasoning Translator web workflow, these instructions belong in the optional Translation brief field. That field provides instructions for the work; the result still needs review.

Translate this fictional customer update from English into French for France.
Audience: customers receiving a product update prepared by an agency. Use clear, direct language and address readers as vous.
Keep the fictional product name Demo Workspace unchanged.
Preferred terms: workspace → espace de travail; project files → fichiers du projet; review notes → notes de révision. Adapt grammar as needed and flag conflicts.
Preserve {project_name} and launch-checklist.docx exactly.
Preserve the quantity of three files and the date 14 November 2026. The date format may be localized without changing its meaning.
Keep the uncertainty in may need further review and the condition in Do not publish until the client reviewer has approved the wording.
Preserve the headings, the three numbered actions and the responsibilities table, including each role.
Flag ambiguous wording rather than adding facts. Do not add prices, promises about availability, performance or quality, or an approval that the source does not contain.

Check the condition behind a sentence

The source ends with an approval rule. A shorter sentence can look tidy while dropping the condition that makes it usable.

Original source
Do not publish until the client reviewer has approved the wording.
Manual illustration of an omission
Publish the update.

The edited example removes the reviewer’s approval condition. It is a manually written illustration, not an observed error from a translation tool. When you review a real result, check who acts, what is required and whether a negation or qualification has disappeared.

Review the wording and the exported file

Keep the original beside the actual translation. Record what you observe and the decision you make for each check. The following checks have not been run on a product translation or translated export for this example.

  1. Product nameKeep every occurrence of Demo Workspace unchanged.
  2. Preferred termsCheck workspace, project files and review notes in their surrounding sentences.
  3. Quantity and dateKeep three files and 14 November 2026. The date format may be localized.
  4. Literal referencesKeep {project_name} and launch-checklist.docx character for character.
  5. Approval conditionKeep the instruction not to publish until the client reviewer has approved the wording.
  6. UncertaintyKeep the meaning of may need further review. Do not turn it into an approval.
  7. CompletenessCheck the title, three section headings, three numbered actions and every table cell.
  8. Word readabilityOpen the export and inspect accents, lists and the responsibilities table.

A downloadable Word file can still need review. Open it in your usual editor before sharing it. Exact pagination and advanced Word features are not guaranteed, and a readable source does not prove that a future export will preserve every detail.

Put the brief into your workflow

Start with one document and instructions you can verify. Keep the source, the brief and your review decisions together so the next person can see what was requested and what was checked.

Explore the public translation walkthroughSee plans and pricing