Prepare Chinese documents for business cooperation, technical handovers and product content. Compare real file scopes and use the free document registers.
Working with China · start with the recipient
Choose the document task for your Chinese counterpart
Choose your task, identify the Chinese readers and prepare the actual files. These are planning routes; each linked case describes its own recorded project scope.
Share company credentials with a Chinese partner
For your project A Chinese procurement or partnership team
- Files to list
- List the company-qualification files requested by your counterpart, the legal entities and each source language.
- Handover to agree
- Agree the Chinese entity names, file references and which originals should accompany the translation.
Related project record
COSCO ShippingEnglish / Arabic / Spanish → Chinese
The COSCO record covers company-qualification documents translated from English, Arabic and Spanish into Chinese.
Hand over technical documents to a Chinese team
For your project Chinese engineering, operations or service readers
- Files to list
- Identify the technical documents, product manuals, model references and diagrams that your recipient needs.
- Handover to agree
- Keep part identifiers, figure references and source revisions connected; name the owner of technical questions.
Related project record
HF TireTech GroupEnglish → Chinese / Thai / Malay / Hindi
The HF TireTech record covers English tire-technology files, product manuals and technical standards translated into Chinese and other target languages.
Present your products to Chinese readers
For your project Chinese customers and the team reviewing product text
- Files to list
- Export the website product text with product IDs, page references and the fields that need Chinese wording.
- Handover to agree
- Separate approved product facts from draft marketing text; identify who approves Chinese names and wording.
Related project record
DecathlonFrench → Chinese
The Decathlon record covers French website product content translated into Chinese for the China market.
Prepare imported-device technical files in Chinese
For your project The Chinese readers named by your device-document team
- Files to list
- List the device models, technical documents, source revisions and the Chinese reading purpose of each file.
- Handover to agree
- Keep parameters, units and model references tied to the source; identify the reviewer for technical questions.
Related project record
Jiangsu Xinlikang MedicalGerman → Chinese / English
The Xinlikang record covers German technical documentation for imported medical devices translated into Chinese and English.
Use the registers below to record the agreed file set. Confirm recipient-specific requirements with your counterpart; a translated pack does not establish procurement acceptance, engineering approval or product registration.
Agree the handover with your Chinese counterpart
Start with the person who will read the Chinese documents and the decision or task they need to carry out. An initial partnership discussion, technical handover and product-content review need different file sets. Ask your counterpart which files they need, in which format and for what use; record that request beside the actual source versions.
Build a short file list with the recipient, intended use, source language, source revision and required Chinese output for each item. Identify who approves company and product names, who answers technical questions and how later source changes will be identified. The four routes above connect common preparation tasks to existing file guides and related project records.
Download the project preparation pack
Bring product files, Chinese versions, approved names and open questions into one project record before requesting translation or documentation support.
Download the printable preparation pack (PDF, 3 pages) →
Version 1.0 · Updated 9 October 2026. The PDF contains four blank registers, cross-file checks and a fictional example. Print in A4 landscape. No login or email address is required.
Download editable project registers (XLSX, 5 sheets) →
Editable workbook version 1.0 · Updated 5 November 2026. Four blank registers provide 20 rows each for files, names, official sources and open questions; a separate fictional example shows how to use the fields. The workbook records the actual source language. Approval dates are blank until confirmed. The original printable PDF is unchanged.
Start with a non-sensitive inventory of filenames, versions and question owners. Discuss confidentiality and the permitted transfer method before sharing complete sensitive documents. No login or email address is required to download the workbook.
This is a document-coordination template. The listed document types are examples, not a mandatory submission list. Product-specific filing, testing and certification requirements need separate confirmation from the relevant authority or qualified specialist.
Four records that keep the project clear
Keep document versions, names, official sources and unconfirmed requirements in separate records. This makes it easier to discuss the files you have and the questions that still need a decision.
| Record | Fields | What to confirm |
|---|---|---|
| Document register | Product / model, Source filename / language, Document ID, Source version, Chinese version, Intended use, Owner, Approval date | Record the actual source revision and Chinese revision separately. Leave an unconfirmed approval date blank. |
| Names and protected terms | Company / product / term, Source name, Approved Chinese name, Abbreviation / do-not-translate rule, Approver / date | Distinguish an approved Chinese name from a provisional translation. Record where a protected identifier must stay unchanged. |
| Official source register | Agency, Document title, Applicable product, Version / effective date, Original URL, Last checked date | Use the original official source. Record which product it applies to and when its current status was checked. A URL alone does not establish applicability. |
| Requirements awaiting confirmation | Open question, Product / document, Evidence / source, Decision owner, Status, Decision / date | Keep unresolved requirements visible. A completed translation does not establish filing acceptance, a test result or certification. |
Check the manual, labels and technical files together
A revision to a model name or specification can affect several documents. These checks help identify mismatches for the product or documentation owner to resolve.
| Check | What to review | Record |
|---|---|---|
| Product identity | Company name, product name and model identifiers agree across files. | Approved names and any document-specific exceptions. |
| Document versions | The manual, labels and technical files refer to the intended source revision. | Source and Chinese versions, plus documents affected by a change. |
| Specifications | Numbers, units, ranges and model-specific data agree. | Source reference and unresolved discrepancies. |
| Warnings and instructions | The same approved warning or instruction has a consistent meaning across files. | Document IDs, locations and the owner of unclear source content. |
| Cross-references | Figures, part names, document references and revision references match. | Broken or outdated references requiring correction. |
| Terms and protected strings | Approved Chinese terms, abbreviations and unchanged identifiers follow the recorded rules. | Term-list revision and approver. |
| Unconfirmed requirements | Translation status and product-specific approval status are recorded separately. | Open question, evidence needed and decision owner. |
Illustrative example: a control-panel document set
Illustrative example only. This fictional control-panel project is not a customer record or a statement of mandatory requirements.
Source revisions are identified, but Chinese names, cross-file consistency and any product-specific requirements remain unconfirmed. No approval date is implied.
| Product / model | English filename | Document ID | Source version | Chinese version | Intended use | Owner | Approval date |
|---|---|---|---|---|---|---|---|
| CP-01 | operator-manual-en.docx | DOC-001 | A | Pending | Operator reference | Documentation lead | — |
| CP-01 | panel-labels-en.xlsx | DOC-002 | B | Pending | Panel text | Product engineer | — |
| CP-01 | technical-data-en.pdf | DOC-003 | A | Pending | Technical reference | Product engineer | — |
Prepare a useful project enquiry
Describe the product or model, intended use, available source files, source revisions, target Chinese audience and required date. Identify the person who can approve names and answer technical questions.
Use the project enquiry form to discuss scope. If product-specific requirements remain unclear, see our China regulatory research service. Translation progress and regulatory conclusions are separate records.
Choosing a supplier? Compare responsibilities with the Chinese translation vendor evaluation worksheet. For software screens, use the Chinese MES and SCADA QA checklist.