Monolingual Proofreading - Native Edit Instructions


____ Monolingual Proofreading - Native Edit Instructions ____


In the translation industry, the use of translation management systems (TMS) has brought about enormous benefits, but it has also come with different sets of challenges. One such difficulty is the impact that the segmentation and presentation of source texts in the TMS interface can have in the overall coherence and cohesion of the target text.

The objective of this task is to adjust the translated product to achieve a higher degree of fluency and naturalness of expression in the target language, and address any issues that were not apparent within the TMS.

Please, use the target document to go over the translation and identify any areas of improvements. Do not perform your review in the translation editor, unless bilingual context is necessary (more detail in the Process section!

Areas of interest

As you review the text, be on the lookout for improvements across all areas listed below. However, we ask you to focus specifically on fluency and style as the main objectives of the review process.

This is based on TWB’s quality categories, which you can read more about here.

:pushpin: Fluency: Issues related to the form or content of a text, irrespective of whether it is a translation or not. Examples:

  • Punctuation
  • Spelling
  • Grammar
  • Inconsistencies

:pushpin: Style: Create a translation that sounds idiomatic (natural) when you read it and is appropriate for the readers. Examples:

  • Awkward
  • Inconsistent
  • Unidiomatic

:pushpin: Accuracy: Make sure the translation communicates the meaning of the original text correctly and precisely. Examples:

  • Addition or omission
  • Mistranslation
  • Under-translation or over-translation

:pushpin: Terminology: Look at whether or not the keywords and phrases are translated accurately and if the same translation is used for each term throughout the text.

:pushpin: Design: Whether or not the translation is formatted properly. Does the document contain easy to read and follow tables, images, or other visual elements?


If you have any questions or need anything, please do not hesitate to contact your Project Officer. They will be happy to help out!

Native edit

Review package

You will be provided with:

  1. The source document submitted for translation
  2. The latest draft version of the target text in its final format
  3. A link to a job in our Translation Management Tool
  4. Reference material (as available)
    a. Terminology base
    b. Partner-specific guide and reference
    c. General language style guide


Given the file format we work with, you will review the target file and implement your changes directly in it.

  • Important: the new file is used to update the TMS automatically. Please, preserve the structure and formatting of the text as much as possible.
  • Tracked changes: if this functionality is available, please activate tracked changes. Here is how to do it in Word, for example.

Here is our suggested way of approaching the task:

  1. Familiarize yourself with the general structure and content of the source file.

  2. Go over the translated file and review the text according to the areas of interest outlined above.
    a. Process: You may choose to do them all at once, and perform individual readings for each category (this depends on the size of the document and the time available).
    b. Issues: if you find issues, implement the changes directly in the file.
    c. Queries: if you require input from the Partner or the Project Officer, we encourage you to reach out!

  3. Take advantage of automated checks
    a. Spell-checker: if possible in the target file you are working with, we advise you run a native spell-checker in the tool you are working on. The quality of spell-checkers varies greatly across systems!
    b. Other tools: if you have other tools available that you usually use, you are more than welcome to apply them!

  4. Perform one final read of the document.
    a. If you would like to receive an updated version of the target, you can either contact your PM or (if possible with the file format you’re working on) download it from the editor by clicking on Document>Preview Translation.

  5. Handover notes: you may come across issues in the source file, problems you are unable to resolve, or areas in which you still think improvements could be made.
    a. Submit these to the PO as soon as possible, in case anything can be done about it while doing the review .
    b. Otherwise, please compile pending points or comments in an email and share them with your PO

  6. After the PO imports the changes into the TMS, you will receive a link to confirm the segments and finalize the review process
    a. Segment confirmation: anything that was not modified during the import will already be confirmed. All other segments should contain your edits, so you can confirm they were imported correctly.
    b. Quality assurance: run the quality assurance check in Phrase TMS. You can learn more about it here and here.

Pre-delivery Checklist

:ballot_box_with_check: Completed the review of the document based on all categories detailed in Areas of Interest
:ballot_box_with_check: Reached out to Project Officer to clarify any open points before delivery
:ballot_box_with_check: Performed automated checks, including:

  • Spell check
  • Quality assurance

:ballot_box_with_check: Performed a final read of the document
:ballot_box_with_check: Compiled handover notes for Project Officer