One of the most controversial topics in the translation industry comes up when the Vendor Manager asks for a translation test. Whether it is a specific sample for client, or a test during the recruitment process, we can not make up our minds about it. Is it necessary? Should it be paid?
The purpose of a test translation, as it names entails, is to test the quality of the translation the vendor can supply. However, each company uses their own methods and focuses on different things when assessing a test translation, so what might be acceptable to one company, doesn't necessarily mean it is for another. The quality of the translation is assessed against the standards of the company, so what the company and their clients think is a good quality translation may vary.
I mention this in particular because not all the companies might be a good fit for you as a freelancer and not all the freelancers that answer your company's advert are a good fit for your company. As a Vendor Manager or as a freelance business owner, starting a new collaboration is an important decision, the company might not pay you on time, the translation might be rejected by the end client, the communication might not be good, etc.
Although, test translations are widespread in the industry and it is perceived as a default procedure, some professionals see test translations as not useful, but a waste of time and money, or not reliable. I have found these articles by Alina Cincan and Steven Bussey about their take on translation tests worth reading.
The truth is that companies spend thousands of pounds per year on testing their vendors and it is a crucial step on the on-boarding process of many companies. Unlike other industries, any translation company might test more than 1,000 translators per year. A database changes constantly and it is not cheap to maintain one properly.
During my career, I have had the chance of being on both sides, and it is disappointing when the testing process is unsuccessful as both the translator and the company have spent time and money on it.
In my opinion, testing is just one way of ensuring the translator fulfils the company's requirements; accreditations, certificates and proven experience should also be taken into account when on-boarding a new translator.
As a Vendor Manager, recruiting translators and testing them is part of my responsibilities. I also look at company's spent on testing, and figures of the results obtained. Therefore, let me give you some information on my experience with translator testing and highlight the main issues that I see everyday in my job as a Vendor Manager when it comes to test translations.
I send tests out for translation every week, and around 30% of them are delivered late or not delivered at all. Forgetting the task or not being a priority is the number one problem when testing new translators. On the other hand, 5% of them are delivered within the same the day. The rushing of test translations is a common issue leading to spelling mistakes, minor miss-translations, not following the instructions properly...
The amount of people who ask for the test to be paid in advance, it is also surprising: less than 1% in my experience. If payment for the time invested in doing the test is important to your business principals, make sure to let the Vendor Manager know in advance.
I personally try to reach out with feedback to every person I test, however, if feedback has't been received after a few weeks, my advice is to follow up with the company to find out the result of the translation test.
I have also found some basic tips here, that everyone taking a test should definitely read before delivering any test translation.
In relation to this topic, a new wave of companies specialised in Vendor Management are selling their services to LSPs and direct clients alike. I have selected an articles mentioning testing processes you might want to read here.
What do you think about test translations? What has been your experience? I hope you find these insights useful and they help you on your day-to-day work.
Comments
Post a Comment