{"id":8498,"date":"2021-07-26T11:06:00","date_gmt":"2021-07-26T09:06:00","guid":{"rendered":"https:\/\/gemino.de\/?p=8498"},"modified":"2022-07-22T21:47:33","modified_gmt":"2022-07-22T19:47:33","slug":"efficient-in-country-reviews-a-question-of-knowledge","status":"publish","type":"post","link":"https:\/\/gemino.de\/en\/efficient-in-country-reviews-a-question-of-knowledge\/","title":{"rendered":"Efficient in-country reviews \u2013 a question of knowledge"},"content":{"rendered":"

In-country reviews can be challenging to implement in translation processes: Are we talking about changes or corrections? What specifications apply? Who should be involved? And, above all, are they really necessary? Gemino has answers to these questions and this article will demonstrate how insights can be gained even from basic, standardized reviews.<\/em><\/span><\/p>\n

 <\/p>\n

For our clients, in-country reviews and approvals are often unavoidable for regulatory reasons. They are mostly annoying, sometimes frustrating, and almost always time-consuming. We know that. We know our clients\u2019 most important question: How can processes for multilingual approvals be made as efficient as possible? The answer: The more we know, the less work you have.<\/p>\n

 <\/p>\n

Reviews as feedback: Knowing is good<\/h3>\n

Because we at Gemino are not (and cannot) always be briefed on all background information in advance, we evaluate the reviewed translations you send back to us. We review the changes, categorize them, and finally implement them in the final documents and the CAT tool or translation memories.<\/p>\n

So, a review does not just serve to approve of a single document, it can be general feedback. We want to understand what has been changed and, in the best case, draw conclusions so that there may be fewer changes in future translations.<\/p>\n

To do so, quite often, we also have to read between the lines: For it is not only a matter of terminology, meaning or assessing a change in its specific context. In every document, intentions, contexts, business goals, objectives and nuances often change.<\/p>\n

 <\/p>\n

Reviews as part of the workflow: Knowing in advance is better<\/h3>\n

We recommend defining workflows for in-country reviews in advance according to individual requirements. Specific roles, objectives and processes should be defined to avoid unnecessary workload as well as ambiguities and errors. The content and the people are prepared for each other:<\/p>\n

 <\/p>\n

Reviewer<\/h3>\n

Profile<\/strong><\/p>\n