We have been hard at work, making MotaWord the world's fastest human translation platform. Speed is certainly very important for our clients but more important than that is the quality of the translations we provide. Our goal is to have the highest possible quality for all the projects we undertake.
For our colleagues that work with us, certain things might not be too visible. For example the fact that a project they are working on is probably being translated simultaneously into multiple languages with the effort of hundreds of translators at all times. And dealing MotaWord has been running for about a year and half and during those 550 or so days we have pondered on how we can improve our translator database and the administering/monitoring of the translators in our platform – thus the TQS was born. The Translator Quality Score, or TQS, gives the translator a score percentage of their relative quality on the project after it is completed and proofread. This way we can get an idea of how proficient this specific translator is; of course, there are some mathematical components that need to be taken into account, but nothing too difficult.
Apart from all the curves, variables and formulae that MotaWord implements, we basically first generate an average of contributions on project basis. If the number of your contributions is lower than the threshold of this average, you are excluded from the TQS calculations of the project. Let’s say you contributed enough to the project, then we check every string to see if our proofreaders edited your translation: the more translations that are edited, the lower your TQS will be and vice-versa for a higher quality score.
Simply put, that is the whole process in a nutshell. It seems a bit complicated at first but after breaking it down, it just takes time to get used to the formulae and the process. Now, to clarify, the number obtained above doesn't represent the translator’s score entirely. We have noticed that there are some minimal things that our platform needs to work around. For example, word-styling preferences can also affect the TQS; sometimes a translator could have translated a segment that is 100% correct, however, style preferences will affect the TQS because the segment/string is registered as edited. We are currently developing a way to deal with these instances; they are not normally recurrent, but they do appear every now and then, and when they do, we fix them accordingly. If you’re a translator and you’re reading this, the best way to keep up with your TQS is by looking at the overview page of your translator dashboard.
Why is the TQS important and what are the translator benefits?
Among the descriptions you were probably wondering why the TQS is important and what the benefits of having a great TQS on our platform are: some of our clients prefer to have specific translators work on their projects and the best way to promote a skilled translator is via the TQS. These projects that our clients upload to our platform are offered only to translators with an outstanding TQS and are occasionally invite only. This way, our clients are satisfied with the quality of their translation and at the same time our translators are also pleased with the constant workflow. That is why we always say, “Be 100% sure of your translation before clicking ‘Commit’.” If our translators abide by this philosophy, things will run smoothly and at ease.
Please look forward to our upcoming blog posts soon! If there are ever any questions about anything, send us an email at firstname.lastname@example.org