Perfect match warning?

I am wondering if there is a setting when perfect matching that will give a warning of some sort if you are perfect matching but there is a newer translation in the translation memory. I'm not sure I'm explaining myself well, so here's some context / an example:

Project A - "Desk" is translated as "escritorio" in Spanish.

Project B (at a later date) - "Desk" is translated as "escritorio" with TM leverage from project A, but client has requested we change our translation of "desk" as "pupitre".

Project B is imported into TM and "escritorio" is overwritten as "pupitre".

Project C - Client (at a later date) has made some updates to documents from Project A, so I leverage TM (with correct translation), but I also perfect match with Project A. Perfect matching overrides the TM leverage for new "pupitre" with old "escritorio". Project C is delivered, so now client is upset because we've used a term they already asked that we update. 

Considering it might not always be feasible to update all affected TM segments during project B based on this new term (assuming that I even recognize that "desk" had been translated previously in Project A while I am working on Project B), is there a perfect match or TM setting that would help avoid this? We can also include glossaries / termbases, but this also would assume that "desk" was selected for inclusion. 

Parents Reply Children
No Data