If you have multiple reviewers, you can assign document clusters or email threads to each reviewer as follows:

• Select all the profiles in the clusters or e-mail threads you want to assign as shown below.

• Click [R+ Review and Revision Tools > Global Add / Remove] and assign the reminder task "Documents\Review near-duplicates" to the reviewer, as shown below:

Reviewers can now see their assigned documents in using the following two views:

• [L+ Near duplicates > everything as docs : by Reviewer], and
• [L+ Near duplicates > attachments with emails : by Reviewer]

The screen shot below shows e-mails that have been threaded. Notice the 10 e-mails selected all have the same subject "Re: Your probe wire and tips", suggesting they all belong to the same thread.

After e-mail threading, all 10 were indeed determined to be part of the same thread and assigned thread number E0000046, as shown.  Consequently, instead of having to read 10 e-mails, with duplicated history, only the e-mail of 10.Sep.2012 11:32:19 AM needs to be read as it contains the history of all other 9 e-mails in the thread.

In this case, the e-mails were "clean" and threading worked perfectly. However, sometimes e-mails are not so "clean" or well structured and a single conversation is split into several threads. For example, see 27 e-mails that have been selected in the screenshot below. They all have a simlar subject with minor changes suggesting they belong to the same thread. However, they were split into 6 threads: E0000001, E0000002, E0000003, E0000004, E0000005 and E0000006. This means that instead of having to review 27 e-mails, only 6 need to be reviewed. Nevertheless, this can be reduced further by manually merging the threads together.

Even if e-mail subjects are the same, it doesn't mean all the emails belong to the same thread because e-mails are often structured as tree, rather than a straight line. Consider the diagram below:

It is quite likely all the participants of this conversation just clicked on "reply" to send their message without altering the subject, so all 20 e-mails would have the same subject, but they don't all belong to the same thread. After replying e-mail 5 with e-mail 6, one of the participants returned to e-mail 5 and replied it again with e-mail 7. Consequently e-mails 7, 8, 12, 14, 19 and 20 all have to be reviewed since each of them have additional history not found in the others.

Returning to the 27 e-mails in the screen shot above, we can see thread E0000001 is the primary thread in the conversation (as it has the most e-mails in it, just as thread 20 in the diagram is the primary thread in that conversation). We need to see if the e-mails in the other 5 threads shown should be part of E0000001 or are branches from E0000001, just as threads 7, 8, 14, 12 and 19 are branches in the above diagram. We will merge those threads whose entire content is contained in E0000001.

To determine which threads of a conversation should be merged and merge the threads:

• Open the [Near Duplicates > e-mails by Contact to merge threads] view.
  
• Expand the red category title for the contact whose e-mails you need to review and merge.
  
• Scan the summary column for emails with the same or similar subjects that have closely contiguous or dates that have different thread numbers, as these emails most likely part of the same thread. For example, see the screen shot above, and the 5 threads E0000002, E0000003, E0000004, E0000005 and E0000006.
  
• Select the reference document (the email from 22.Oct.2019 4:32:04 pm in the above example) of the primary thread (E0000001 in the above example).
  
• For each thread to merge, select its reference document and compare it to the reference document of the primary thread. This needs to be done one pair at a time. So, in the example, above we would compare the reference document of thread E0000001 with the reference document of thread E0000002, then the reference document of E0000001 with the reference document for thread E0000003, etc.
  
  After selecting the pair, click on [R+ Review and Revision Tools > Compare 2 documents] to compare the pair of documents.
  
  After analyzing the pair, the differences will be highlighted in yellow in your browser. Ignore differences in punctuation or e-mail headers (the block of text with the date, from, to, etc.) or signatures and see if the actual text of the primary thread reference document contains all the text of the other reference document. Sometimes differences are highlighted which are not differences, so double check any differences carefully.
  
• If the text matches, then the thread can be merged. Once you have compared the reference documents of all the threads, you can merge all threads that should be merged at once. In the above example, only the text of threads E0000004, E0000005 and E0000006 is contained in the primary thread (E0000001) and can be merged into E0000001. Threads E0000002 and E0000003 cannot be merged into the primary thread because their text is not fully contained in the reference document for the primary thread.
  
• To merge the threads, note the thread number of the primary thread and select the reference document of each thread to be merged (i.e. the reference documents of threads E0000004, E0000005 and E0000006 in the above example), and click on [R+ Near Duplicate Functions > Merge e-mail threads].
  
• You will be presented with a view with all e-mails grouped by their thread. Locate the group for the primary thread's thread number and select any e-mail in that thread.
  
  In the above example, the primary thread is E0000001 so we select an email in that thread as shown below.

• Then click "OK". The threads will be merged together, as shown below for the above example. Notice the 4 emails in threads E0000004, E0000005 and E0000006 now show they belong to thread E0000001.