START HERE
Provide the authoritative source, target language and locale, audience, purpose, approved terminology and delivery format. If the source is unfinished, label revisions and changes. A brief should make the task clear to translators and reviewers, not bury them in unrelated material.
Identify the authoritative source
Label files with a revision and date. State whether comments, tracked changes, hidden sheets and notes are in scope. When sending similar files, identify the authoritative copy and reference-only versions rather than expecting the recipient to infer this from names.
Word, Excel and PowerPoint may contain text in headers, charts, shapes and notes. List required coverage. Provide samples of scanned material, text inside images and complex objects to confirm support; matching extensions do not imply identical processing.
Specify language and audience
Name the source and target languages, regional usage and intended reader: staff, customers, investors or technical specialists. Purpose affects terminology, units, dates and tone. ‘Translate into English’ does not settle these choices.
An illustrative brief might request an English support manual from Chinese, preserve model numbers and units, require both translated and bilingual files, and assign safety warnings to a named reviewer. This example is not a sufficient acceptance standard for every safety-critical or legal document.
Supply relevant context and terms
Prioritise approved product names, brand spelling, abbreviation definitions and final prior translations. Include deprecated terms and explain why they should no longer be used. Consistency with an obsolete version is not the same as correctness.
Mark relevant chapters and versions instead of supplying an unlimited reference archive. Remove unnecessary personal information and unauthorised client material. Decide what may be uploaded and who can access it under your organisation's requirements.
Agree on delivery and changes
Specify translated-only or bilingual output, editable or reading copies, and who checks layout and specialist content. AI-assisted translation does not replace every professional approval or guarantee unchanged complex formatting.
When the source changes, identify affected passages before deciding what to update. Assign an approver, feedback format and review deadline to avoid contradictory edits. Yuzhu Cloud and Wali have separate product entry points; do not assume shared accounts, allowances or materials.
A practical comparison
| Brief field | Example | Owner |
|---|---|---|
| Source and scope | Manual v3; tables included, internal comments excluded | Document owner |
| Language and audience | Chinese to English; technical support | Business owner |
| Terminology | Retain models; glossary v2 | Subject reviewer |
| Delivery and approval | Editable English and bilingual copies | Delivery owner |
Before you sign off
- Separate the authoritative source from reference files.
- Specify locale, audience, units and tone.
- Confirm support for scans and unusual objects using samples.
- Agree on format, access and specialist review responsibilities.
Frequently asked questions
Which formats does Yuzhu Cloud support?
Current public information covers DOCX, XLSX, PPTX, TXT and common subtitle formats. Check current product information or provide samples for PDF, scanned material and unusual objects.
Will layout remain exactly unchanged?
That cannot be guaranteed. Text length, fonts, tables and objects can change the layout. Review the delivery in the intended software.
Scope and related product information
This guide explains preparation and review; confirm current format support and service scope before processing.
Examples in this guide illustrate a review method, not a customer case or a performance result. Product availability changes with version and account configuration.
AI document translation and bilingual delivery | Yuzhu Cloud →Current clients and installation guidance →