Technical Checklist

 

 

 

 

Some clients are very specific with their preferences, particularly those in niche, superspecialized, or interdisciplinary fields. Such clients provide a “technical checklist” containing the preferred translation for terms.

 

Note:

 

The technical checklist may be sent as a separate Reference file, or it may be appended within the document itself. Please scan through to the end of all files to check if the client has added a technical checklist.

 

When a technical checklist is to be adhered to, the file sent to you will contain the checklist terms highlighted in magenta.

 

Please follow the technical checklist strictly, even if this conflicts with your usual technical word choice.

 

If the client’s chosen term is incorrect, inappropriate, or misspelled, check with the client via ulatusCommunicate/Questions Sheet. Use Remarks in case you notice this at the time of delivery. It is critical that you bring this discrepancy to the author’s notice through our communication mediums.

 

Our clients are very particular about technical checklist compliance. Please ensure that the translation of terms in the client’s checklist is done correctly and consistently.

 

For large projects without a client-submitted technical checklist, we may ask our translation team to compile a glossary of technical terms used in the translation. This will then be sent to the client for approval.

 

Create a glossary per the assignment. A best professional practice is each translator/translation checker maintaining a customized glossary during translation. You can create and share the glossary with the translation team (or client) through ulatusCommunicate. Stakeholders add, discuss, and finalize the terms, ensuring that consistency is maintained across files. So even if a technical checklist has not been provided by the client, do maintain glossaries for your assignments.

 

 

PREVIOUS | NEXT

 

 

 

 

 

Copyright © 2019 Ulatus