Hi, I agree - depending on the skill of people, they may even confirm all MT matches without even looking - having the flexibility to override the TM Update settings in certain workflow steps would be great to have, ensuring that e.g. non native reviewers when involved in review would update a different TM. Either that or customizable TU statis  values that can get configured per worklow step...

 Luis Lopes  I'm not sure many in industry would agree with this decision. It's essentially suggesting that it makes more sense to change customer behaviour than to introduce a feature that would be expected / is common. Essentially, if one has a pool of new translators and experienced ones, this means the expected work in Trados will differ from a team that has only experienced translators.

Would an option to introduce a different shortcut that stores translation on project-level only, instead of into a TM, possibly be acceptable, knowing that this would probably mean less dev work?

We'd similarly like the small functionality where a project or working TM is used during translation/review and only at the Update TM workflow step, would the "master" TM get updated.

Hi Andrea,

With Trados Cloud we introduced a new concept in the form of Translation Unit status. This step was taken to remove the reliance on separate TMs but actually manage status of TUs in one TM. We have no plans to introduce Project/Working TMs in the future. We know this is a change for the industry, but our recommendation is to review and evaluate the use of Translation Unit statuses going forward, as we believe it's a better approach to managing this topic.

Thanks,
Luis