Prepare product files for Chinese translation with document, name and official-source registers, cross-file checks and a free printable China documentation pack.
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.
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, English filename, 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.