Prepare a German to Chinese technical query sheet: source references, terminology decisions and review owners, with a published medical-device project.
View the file review example ↓Start a German-to-Chinese query record
For a German technical file, an unresolved term needs a source reference and a decision owner. Keep the question, context and proposed Chinese wording together so an answer can be applied consistently across the file set.
From reading to a project
Start a German-to-Chinese query record
German terminology query · made-up example
- Source entry
- DE-QUERY-001 · Anschluss
- Context needed
- Document revision / section / component or diagram reference
- Chinese options · not yet approved
- 连接／接头／接口——需结合部件和图示确认。
- Decision record
- Owner / response / approved wording / affected occurrences
Review status: questions to confirm
Give the question a stable reference
Use the source file, revision, page or string ID so the reviewer can find the same passage.
Ask for a decision, not a guess
Include enough product context to explain why more than one Chinese rendering is plausible.
Apply and retain the answer
Record the owner and decision, then check affected occurrences and update the agreed terminology.
Related published experience
Jiangsu Xinlikang MedicalGerman → Chinese / English
Technical documentation for imported medical devices.
The Xinlikang record covers German medical-device documentation into Chinese and English and records seven working days. It establishes related project experience; this mock query sheet is not a delivered client file.
For technical questions during Chinese translation, provide the current source files and actual language, revision identifiers, unresolved terms and relevant diagrams or context. Identify the technical decision owner, approved references, Chinese reviewer and required question-log format; agree how decisions and affected passages are returned.
Make the question specific enough to answer
A useful technical query identifies one uncertainty and gives the source owner enough context to resolve it. Include the file and revision, page or string reference, the German wording and the relevant figure or surrounding passage. State what is unclear and, where useful, offer provisional Chinese options with the reason for each. Do not present a proposed rendering as an approved term.
In the made-up example above, Anschluss has more than one possible Chinese rendering. A term list alone may not show whether the passage concerns a connection, connector or interface. The component, diagram and sentence context help the technical owner answer the actual question. Keep the question open when that information is missing.
The number of questions is not a quality score. Clear source files and approved references may need few queries. Repeated questions may reveal missing context, an unclear answer or a decision that was not shared with the relevant people. Read the content and handling of the questions before drawing a conclusion about the translator.
Keep query status separate from translation status
A source question, a proposed Chinese phrase and a completed review are different records. Give each query a stable identifier and record who is expected to act next. A response such as “please refer to the manual” does not close the question if the manual version or relevant location is still unknown.
The following is a self-created workflow example, not a customer record or a required service configuration. Agree the statuses and return record for your project.
| State | Record before moving on | Next action |
|---|---|---|
| Open | Source location, question and provisional Chinese options. | Name the person who can clarify the source. |
| Context requested | The missing diagram, revision or reference. | Source owner supplies or identifies the information. |
| Response recorded | Responder, answer, date and any limits on its use. | Check whether the original question is resolved. |
| Chinese wording applied | Selected wording and affected file locations. | Perform the agreed language and reference checks. |
| Checks recorded | What was checked and which items remain open. | Return the record to the named review owner. |
Apply the answer within its stated scope
Record the confirmed meaning and where it applies. An answer for one component or document revision may not apply to every occurrence of the same German word. Check the affected passages, diagrams and Chinese terminology references before making a global replacement.
If an answer changes after Chinese review, identify the superseded decision and the files that used it. Keep a source change separate from a correction to Chinese wording. The source owner decides technical meaning; the agreed reviewer checks the Chinese rendering against that decision.
Where permitted and useful, retain the confirmed terminology with its context for later projects. Preserve exceptions rather than reducing the answer to an isolated word pair. A recurring question may need better source guidance, but it can also concern a genuinely different product or context.
Agree the query handover before translation starts
Name the contact who can route technical questions and the person who can confirm source meaning. Agree a response arrangement that fits the project milestones, and state how unanswered items will be identified in a working delivery. Do not assume that a shared mailbox has the authority or context to decide every question.
For a quotation, supply a non-sensitive sample of the file structure or query format if you have one. Identify the source language and revision, intended Chinese readers, the required review and whether you want tracked edits, a bilingual query log or another return format. These records should be agreed with the file set; they are not automatically included in every project.