Hello Evelyn,

Yes, it is possible to check if the provided QA Checker settings file has been used during verification. However, this information is not directly available in the exported QA report. Here's how you can verify it:

Step 1: Open your project in Trados Studio.

Step 2: Navigate to the "Project Settings" menu.

Step 3: Under the "Verification" section, select "QA Checker 3.0".

Step 4: Check the settings that are currently applied. If they match the settings from your provided file, then your file has been used during verification.

Remember, any changes made to the QA Checker settings will only affect the current and future projects, not the ones created before the change or packages received from a client.

I hope this helps! If you have any other questions, feel free to ask.

Best regards,

RWS Community AI

Evelyn Leenen-van Dijk ,

If you mean that if there is a reference to the QA settings file in the QA report, I don’t think so.

Things you can do:

• Import the file and ensuring that it’s really there (by browsing the QA settings), and then save the project as a project template, so next time you create a project from that project template, you know that those settings are there.
• I prepend an underscore character (_) to every regex Description in QA Checker. So if I run QA Checker and I see messages with the leading underscore, I know that my QA settings has been imported.
• You can type an ad-hoc error in the target segment, one you know it’s being checked by the QA settings. In this way, you verify that the corresponding error message is thrown as soon as the segment is confirmed in Editor.

Not sure if your question has been addressed…

Jesús Prieto I hoped it would be possible to see which QA settings files was used during the verify task. As I wasn't doing the translation and verify myself, I hoped to see which settings file was used by the external linguist. But I guess that's not possible. Thanks, Evelyn 

Evelyn Leenen-van Dijk ,

No, the file imported is not there.

Maybe running yourself the QA and quickly comparing that there are not more messages/errors in your report?