bAIbel AV guidesGuides and tutorialsbAIbel AV →

Guides / Formatting, review and editing

Send for review in Trados or memoQ

A translation is sent for review in the reviewer's tool format (Trados Studio, memoQ or bAIbel AV).

  • Intermediate
  • 1 video · 3:50
  • Shown on AV 0.2.11

Before you start

  • A confirmed translation.
  • A reviewer with bAIbel AV, Trados Studio or memoQ.
Video 1 · 3:50

Send for Review, Import Review and Compare Versions

A translation is sent for review in the reviewer's tool format (Trados Studio, memoQ or bAIbel AV). The reviewer opens it in AV with structure locked, edits, comments and returns it. Import Review lists every change before applying it, including rows changed on both sides, and Compare Versions writes a Word report of what the review changed. Returns from Trados and memoQ are read the same way.

Step by step

  1. Three routes: the reviewer uses bAIbel AV, Trados Studio or memoQ

    Your reviewer may use bAIbel AV, Trados Studio or memoQ. AV writes the file their tool reads, and reads back what they return. Only bAIbel AV's screens are shown here.

  2. Start from a confirmed translation

    Marta has translated the check-out card for a holiday-rental client and confirmed every row. Now a colleague, Sam, reviews it.

  3. In Project Files, right-click the file: the Review group

    In Project Files, right-click the file. The Review group has Send for Review…, Import Review… and Compare Versions (Word)….

  4. Choose Send for Review…, and for Trados Studio choose the formatting codes

    Choose the reviewer's tool. For Trados Studio, AV writes a .sdlxliff. Formatting codes: Full sends the bold, tabs and line breaks as tags the reviewer can see and keep; None sends plain text.

  5. For memoQ, a .mqxliff

    For memoQ, a .mqxliff. Without codes, memoQ would drop this card's tab and line break, so AV warns and won't send it that way.

  6. For bAIbel AV, a .xdxliff; click Send

    Sam uses bAIbel AV, so choose it: a .xdxliff, which keeps everything, so there is no formatting choice. Send.

  7. Find the file in the project's export\review folder and send it

    AV writes the file into the project's export\review folder and records this version as revision 2, Sent for review. Send the file to Sam however you usually send files.

  8. Sending again replaces the first send record; click Cancel

    While a file is out for review, Send for Review says so. A new send replaces the record of the first, and a return of the earlier file would then not be read. Cancel.

  9. Reviewer: add the file to a project and open it

    Sam adds the .xdxliff to a project in his own AV and opens it. As it opens, a notice says what is locked: he can change translations, statuses and comments, but not split or join segments, or edit the source. The History header (Ctrl+H) keeps the reminder: sent to you for review.

  10. Reviewer: splitting or joining is refused

    Splitting a segment (Ctrl+T) is refused, and AV says why. The same goes for joining, section breaks and source edits: the file must come back with the segments that were sent.

  11. Reviewer: edit, confirm and add a comment with Ctrl+M

    Sam rewords row 4 and confirms it (Ctrl+Enter). His project has no TM to write to, so AV says once that confirmed rows are not saved to a TM. On row 10 he selects bond and adds a Reviewer comment (Ctrl+M): the client's own word, so it stays.

  12. Reviewer: Export File and send it back

    When he has finished, Sam uses Export File in Project Files. It writes the .xdxliff in the same form, with his changes, for him to send back to Marta.

  13. Right-click the file, Import Review… and choose the returned file

    Back with Marta: right-click the file, Import Review…, and choose Sam's file. Before anything changes, AV lists what came back, row by row: changes, a status, comments, and two rows both of them changed.

  14. For rows changed on both sides, choose Keep mine or Take the reviewer's; click Import

    Rows 8 and 9 were changed by both. Keep mine is the default: keep it on row 8, where Marta's version has the brief's please. On row 9, Take the reviewer's. Import.

  15. Check what came back: unconfirmed changes, a query, comments

    Sam's changes come in unconfirmed, amber, for Marta to confirm. Row 11 is queried, and his comments are on their rows. Row 10's comment quotes bond, the word he marked.

  16. Compare Versions (Word)… from Review returned to Now

    To see what the review changed, Compare Versions (Word)… from revision 3, Review returned, to Now. An import is not saved as a version, so Now is the document after it.

  17. Read the Word comparison report

    AV writes the comparison as a Word document: four rows changed, with Sam's wording marked against Marta's, and each status change.

  18. A return from Trados Studio

    A return from Trados Studio is read the same way. Here the reviewer also changed row 6's Spanish, so that row is refused: the translation may no longer match your source.

  19. A return from memoQ

    From memoQ, a row the reviewer edited but left unconfirmed comes back as a status change: Confirmed → Unconfirmed.

  20. Who confirms what

    A reviewer's change comes back unconfirmed, for you to confirm. A row changed on both sides stays yours unless you choose otherwise. A changed source, or a split or joined segment, is refused, and AV says why.

Recorded on 5 November 2026 with AV 0.2.11. The videos replay AI model answers recorded earlier, so what an AI model writes for you may differ.