Judging by Jerzy's answer below, would a whole new status not be an option (confirmed but not for TM import)? We currently leave segments we don't want in our TMs as "untranslated" to avoid mixing up real draft segments that still require work and drafts that are the result of a consciencious decision. This however messes up progress statistics.

 Gwen Gondry Christen Wilburn 

Perhaps you can work with Project TMs?  Part of the principle of using a Project TM is that you won't update up your Main TM at all until the project is signed of as really complete.  So your project stats are maintained, you can use the translate/review/signed off status as needed to work on the files, and in then end have a TM updated with exactly what you wanted.

Indeed Paul.

The trouble is that we have a great deal of related documents which must be used for cross-referencing, consistency, etc. and which might not have been properly tagged or indentified as beign useful for specific concurrent projects. We cannot identify which concurrent document(s) our authors might have gotten their inspiration from to draft parts of their reports. Running analyses with TMs that would not contain the latest state of affairs might be misleading, so "project TMs" are rather "temporary topical TMs" containing over 100K segments and which we try to maintain in the best state possible without drowning into maintenance. We use these temporary topical TMs to analyse any incoming document and provide our translators with as much input as possible.

I have to admit that the "temporary" aspect tends to stretch to a year or so because of a lenghty validation process before we actually import a translation into a proper institutional TM. Some documents will actually never make it there because of quality issues for instance, but they will remain in the TEMP TMs so their segments can be re-used and reviewed in the future.

All of this is rather unorthodox I reckon. It might be too specific a use case to warrant further development.

Gwen Gondry 

Well, this status is already there. Just put all unwanted segments on Sign-off rejected and lock them. This way they will never be changed by Studio in any automated process and will be always ignored when updating TMs.

So the best solution would be indeed a shortcut in Studio Editor during translation, allowing you to REJECT a segment. This is now possible only in review and sign-off mode, but is missing and would be really useful within the translation process.

Gwen Gondry 

Well, this status is already there. Just put all unwanted segments on Sign-off rejected and lock them. This way they will never be changed by Studio in any automated process and will be always ignored when updating TMs.

So the best solution would be indeed a shortcut in Studio Editor during translation, allowing you to REJECT a segment. This is now possible only in review and sign-off mode, but is missing and would be really useful within the translation process.

Of course, you're right! Everyone here works in translation mode and only occasionally in review mode, which means I'd never thought of that option. Thanks a lot for suggesting it, and for reinforcing the need for a Reject button/shortcut in future Studio releases!

Gwen Gondry Due to ISO 17100 certification every single job here goes at least once in the review mode. Beside this, if you get a badly segmented file and are not able to merge segments due to the nature of the file, entering translation and rejecting these segments plus locking them is the only way to deliver fully translated text without spoiling your own valuable TM.