Project Management

Post-editing Analysis


Please see our main article about Analysis for general information.

The post-editing analysis show the "editing effort" - how much the linguist or the proofreader had to edit the text. When a linguist clicks on an untranslated segment, the current highest translation memory match, machine translation, and/or non-translatable match gets saved for that segment and is later used to calculate the post-editing analysis. For the Review post-editing analysis (in projects with workflow), the results are calculated as a difference between the translator's text and the proofreader's text.

The post-editing analysis is based on the target. Therefore, it must be launched after the post-editing job has been completed.

The post-editing analysis in Memsource extends the traditional translation memory analysis to also include machine translation (MT) and non-translatables (NT).

To run an analysis, open the project, select one or multiple jobs and click on the Analyze button. You will see the following options:

  • Type (Select Post-editing)
  • Name - If left empty, it will automatically be named "Analysis #1", etc. Renaming macros can be used to generate names automatically.
  • Analyze TM post-editing (Calculates the post-editing effort for matches from the translation memory.)
  • Analyze NT post-editing (Calculates the post-editing effort for Non-translatable segments.)
  • Analyze MT post-editing (Calculates the post-editing effort for Machine translation.)
  • Exclude confirmed segments
  • Exclude locked segments
  • Exclude numbers
  • Analyze by linguist (group jobs by Linguists)
  • Analyze by language (group jobs by target language)
  • Source / Target


Analyze TM Post-editing 

The Analyze TM post-editing option is used for calculating the post-editing effort for matches from the translation memory (TM).

Doing Analysis with Analyze TM post-editing enabled:

  • Is intended for a low-quality TM that can contain high percent matches that need to be heavily edited by the Linguist.
  • Will show the post-editing effort for the translation memory.
  • Contains only 100% matches in the analysis (in-context 101% matches from the TM have no effect on the calculation).


Note: A 100% match from the TM can become 0% if completely edited by the Linguist. Any match from the TM can become a 100% match if accepted by the Linguist without any change.


Analysis with Analyze TM post-editing disabled:

  • Is intended for a high-quality TM where the matches should be edited as little as possible to keep the cost low.
  • Will show both 101% and 100% (similar to the Default Analysis).
  • Shows TM matches offered to the Linguist when the segment opened (not the actual Linguist's post-editing effort)
  • Will show the post-editing effort for machine translation and non-translatables.

Machine Translation and Non-translatables

Similar to the Analyze TM post-editing settings, there are options to Analyze NT post-editing and to Analyze MT post-editing. Based on these settings, the MT and NT results can show the post-editing effort for each segment, reflecting the changes made by the Linguist when compared to the MT and NT suggestions. 

  • If the MT or NT suggestion was accepted without further editing (the Linguist did not need to change it at all), it would come up as a 100% match in the analysis.
  • If, on the other hand, the Linguist changes the MT, the match rate will be lower. The score-counting algorithm is identical to the one that we use to calculate the score of translation memory fuzzy matches.
  • For NTs, any editing will cause the segment in question to become 0-49% NT.

If this option is disabled, the editing effort of the Linguist will not be calculated and the analysis result will be similar to default analysis results:

  • The entries from MT/NT without any estimated score will be in TM 0%-49% match. (These will be shown as fully translated by the Linguist; the MT is completely ignored.)
  • MTQE and Memsource translated matches higher than 75% will be in the MT column in their respective matches.
Was this article helpful?



Please sign in to leave a comment.