SDL Worldserver offers translation memory management and terminology management. It also offers workflow customisation. This means that you can change the workflow for different kinds of translation, such as marketing material versus a technical document. You can designate subject experts to work on these different projects, so that you are always using the very best people for each job. SDL Worldserver has several QA features; translators can attach comments and questions to the content, so that quality can be maintained and improved as it moves between different translators and reviewers. Let’s look at SDL Worldserver's pros. SDL Worldserver is probably the most robust and established system out there. It is a very traditional system, which means that anyone with any experience using SDL products should find it easy to use. It can have either server-based or cloud-based set up. A server-based set up is best for small teams of in-house translators or for teams concerned about privacy, whereas a cloud-based set up is better if you have external agencies you need to share content with. Another advantage of SDL WorldServer is that it allows you to customise workflows in great detail, with sequential or even concurrent steps, and even steps that can be retriggered – for example, if a translation is rejected at the review stage, it can go back to the translator. In terms of leverage from Translation Memories (TMs), you can define “Group TMs” and give them a priority as well as penalties. This means that, for example, you can reach out to TMs beyond your team only for the content not found in your TMs and assign them a penalty so they have to be reviewed. The final pro is that as SDL Trados Studio is one of the most popular CAT tools for freelance translators and language service providers, this means that anyone with Studio can work with files directly from SDL Worldserver. Let’s look at SDL Worldserver’s cons. SDL Worldserver is one of the most expensive translation management systems available. This is because prices are based on the total translation volume, meaning that the more you translate, the higher the cost. There is also no in-context review portal, meaning that translators cannot see how their translations will be laid out in the final version, which may matter for things like button text. Furthermore, translators must have their own Studio licence in order to work with files prepared and managed within SDL WorldServer. For translators without a Studio license, there is a web translation interface – however, this is not as powerful as the standard desktop Studio tool. And finally, although there is an API available to plug directly into your CMS, it needs to be heavily customised in order to allow a direct connection. This customisation must be done by a team of developers on your side. SDL Worldserver is particularly useful for in-house translation teams.