Post-translation analysis (PTA) is a report of savings that you have achieved on TM and LiveDocs match rates – after translation is complete.

Normal analysis "predicts" how much you could save on translation memory matches. Post-translation analysis gives you the actual savings.

Post-translation analysis is for finding out how much each translator can bill.

Post-translation analysis looks at the match rate in every segment:


Post-translation analysis groups the match rates in the same way as normal analysis (101%, 100%, 95-99%, 85-94%, 75-84%, 50-74%, No match), and offers the report in the same format. But this time memoQ does not look up the segments in the translation memories. Instead, it takes the match rates that are already there in the segments.

Post-translation analysis makes most sense if the translation was done by several translators instead of just one. If there's only one translator (per target language), a simple analysis report gives an accurate estimate of the possible savings. But this is not possible if two or more translators are working.

Post-translation analysis is grouped by translator. You get a separate table for each translator who confirmed at least one segment in the project. This means you'll know who used what savings.

Match rates come from pre-translation or automatic lookups: Segments have match rates if they are filled in through pre-translation or automatic lookup and insertion. Otherwise, the match rate is zero, and that will appear in the post-translation analysis, too.

Need project manager edition: You can't do post-translation analysis in memoQ translator pro.

Works on delivered documents: In local projects, post-translation analysis works only if there is at least one document that was delivered from a delivery package.

Works if the translator is known: Post translation analysis counts segments where a translator was stored. If a segment doesn't say who confirmed it as a translator - or it wasn't confirmed by a translator -, it's not counted. This can happen if segments were translated by a user in the Reviewer 1 role rather than a Translator.

How to get here

Open a local project. In Project home, choose Overview. Click the Reports tab. Under Post-translation analysis, click Create new report now.

In online projects: Open an online project. In the memoQ online project window, choose Reports. Under Post-translation analysis, click Create new report now.


What can you do?

Work with a character count rather than a word count

If the documents had more internal repetitions than 100% matches from the translation memory

Fine-tune the count if the documents contain a lot of tags: Use tag weights

Write a description for each post-translation analysis report

Don't use Trados 2007-like word counts: Normally, memoQ counts words like Microsoft Word does. In the past, when Trados 2007 or earlier (Trados Translator's Workbench) used to be a dominant translation tool, it was important that memoQ could produce similar word counts - so that translation companies could compare them. This is no longer the case. Use the Trados 2007-like word counts only if your client still works with an early Trados version, and they insist on using it.

When you finish

To run the analysis, and produce the report: Click OK.

To return to the Overview pane, and not generate a report: Click Cancel.

To view the post-translation analysis from the Overview pane