Yulia Kovalskaya 

Confirming segments on a per segment basis would evoke a live QA as you confirm each segments seperately.

Batch selecting segments right clicking and changing the status to confirmed, does nothing but simply manage the segment status.
If you want to batch QA across the entire project / file then you can run the Verification Batch Task or use the short cut F8

I do trust this is exactly what you are after to optimise your task

Let me know how you get on

Lyds 

Yulia Kovalskaya 

Confirming segments on a per segment basis would evoke a live QA as you confirm each segments seperately.

Batch selecting segments right clicking and changing the status to confirmed, does nothing but simply manage the segment status.
If you want to batch QA across the entire project / file then you can run the Verification Batch Task or use the short cut F8

I do trust this is exactly what you are after to optimise your task

Let me know how you get on

Lyds 

Dear Lydia, 

there is something I do wrong:

You refer to this batch task, right? 

I run it, it takes time. But no notifications appear.

One more related question:

Can I set my 6-language TDB as terminology verifier in the general options of Trados? Or the verification options are defined for each specific project?

Thanks in advance!

Dear Lydia, 

I finally got to the problem! And discovered a very useful option along the way!

1. For whatever reason the batch task fails to show notifications in the segments (after I run the process, I have to enter the Reports tab and read the list of errors there, very unconfortable), and the F8 shortcut did not respond in my case either.

The thing is that I had to press together F8+Function key....may seem too obvious to someone but it took me time to figure it out, so I prefer to put it here in case other users get stuck with the issue.

2. After successfully running the check on a project consisting of non-confirmed segments with Translated status, I opened a 100% MT project  done with DeeplPro and ran the process without even changing the status of the segments to Translated, all of them unconfirmed NMTs. And it worked!!!!

So the conclusion is: I personally consider that Multiple Segment Confirmation is a useful function to include in the future  Studio versions, we really need it for certain tasks, but at least in this particular case, we can do without it!

Once again, thank you for your help!

Best regards!