If you store the appropriate terminology in a MultiTerm termbase, you can use the Terminology Verifier (available in the Verification settings of your project) to make sure translators get a warning message if they don’t take over the target term from the termbase. You can find information on those settings here: docs.sdl.com/.../specifying-settings-for-the-terminology-verifier.

You will find more information on how to create a termbase here: Creating termbases.

If you work with terms that can have many different forms according to their place in the sentence, and you don’t wish to store all those forms as synonyms in a termbase, you might want to look at another tool for checking terminology in Studio. It’s called checkTerm and thanks to intelligent morphological technology, it provides a higher number of accurate results and less false positives when scanning your documents to verify terminology. See www.sdl.com/.../.

I have the problem with the Terminology Verifier in that I get far too many false positives so this limits its usefulness, at least for me. I only scan through the messages looking for critical terms.

It might be a settings problem: DE-EN 

For certain languages, the default term checks in Studio will indeed not be good enough, because there are too many possible forms of the term.

The reason why termCheck is so reliable is because it’s based on morphology. While classical statistical term checkers simply identify “similar” sequences of characters, checkTerm actually analyzes the text by stemming nouns and verbs, decomposing words with several components and checking the result against the termbase. This way the algorithm can correctly spot declined or conjugated words and individual parts of compositions. So, for instance, checkTerm will find “dial” as the regular form of “dialing” or all composites containing “dial”. Other check algorithms would fail to detect these because they can only check if a word used in a text uses similar characters to one in the termbase. See www.kaleidoscope.at/.../.

For certain languages, the default term checks in Studio will indeed not be good enough, because there are too many possible forms of the term.

The reason why termCheck is so reliable is because it’s based on morphology. While classical statistical term checkers simply identify “similar” sequences of characters, checkTerm actually analyzes the text by stemming nouns and verbs, decomposing words with several components and checking the result against the termbase. This way the algorithm can correctly spot declined or conjugated words and individual parts of compositions. So, for instance, checkTerm will find “dial” as the regular form of “dialing” or all composites containing “dial”. Other check algorithms would fail to detect these because they can only check if a word used in a text uses similar characters to one in the termbase. See www.kaleidoscope.at/.../.

Because terminology is so important, SDL should improve the native support; perhaps allow regex term definitions.
I have installed termCheck, but for some reason it does not appear in the Add-Ins -> I have contacted the Support.  

Unfortunately termCheck does not handle my simple TBs that do not have a Usage field,