Prioritized Review

The Prioritized Review queue serves documents that are most likely to be coded on the positive choice (ex. Relevant) with a small set of documents included for index health. The documents included for index health are system-selected to help the model develop a better range of training.

Prioritized Review gives you the option to review family documents together. When you enable Include Family, Active Learning serves documents with their family documents to reviewers. All family documents included in the index are served to the reviewer, including documents that were previously coded.

Note: Family-based review is optimized for email and attachments only. Textual near duplicates and threads aren't supported.

This page contains the following information:

Adding Reviewers

From the project homepage, admins can add reviewers to each queue on a user-by-user basis or in bulk.

Note: After you ARM an Active Learning project, you must re-add reviewers to the queue.

To add reviewers:

  1. Click Add Reviewers in the queue modal.
  2. Find and select an individual reviewer, or type to enter a reviewer name. You can also click All Users to select every user in the group.
  3. Click the green check mark to save your changes.
  4. Click the red X to cancel reviewer changes.

Note: We recommend no more than 150 concurrent reviewers per project. Concurrent reviewers are defined as reviewers making coding decisions in an Active Learning queue. There is no limit to how many reviewers you can add to a queue as long as the number of concurrent reviewers remains at 150 or fewer.

Starting the Prioritized Review queue

To start the Prioritized Review queue:

  1. Successfully add reviewers to the queue.
  2. If you want to review family documents, toggle the Include Family field. For more information, see Considerations for family-based review.

    Note: Once you click Start Review, you can't change your family review settings.

    1. Next to Family Field, select the relational field you want to review from the drop-down. This drop-down includes the friendly name of all relational fields in the workspace. Note that family review is optimized for email and attachments.
  3. Click Start Review.

The next time an active reviewer accesses the view for the Active Learning project, they will see a blue banner which indicates they have access to the queue. The view also displays any documents coded by the logged in user for that particular Active Learning project. The Prioritized Review queue serves documents that are most likely to be relevant with a small set of documents included for index health. The Active Learning model only builds once you have at least five documents coded with the positive choice and five coded with the negative choice. However, if you start the Prioritized Review queue before a model build occurs, the queue initially serves up random documents.

After the project begins, you can see the following items in the Prioritized Review queue modal:

  • Coded - the number of documents coded and skipped in the Prioritized Review queue.
  • Active Reviewers - the number of reviewers added to the project.

Admins can pause the review at any point in the project by clicking the Pause Review button on the project modal. Once the review is paused, the access point on the document view is disabled. You can restart the review at any time. Documents coded on the review field while the review is paused are included the next time the model rebuilds. For more information, see Project Setup.

Considerations for family-based review

Enabling Include Family, lets you leverage the efficiency of Active Learning while letting you review and code all documents in a family together. There are several special considerations to keep in mind as this setting is not needed for every case. Review the following special considerations prior to starting your review.

Project setup considerations

In order for family documents to be served together in Prioritized Review, the parent documents and their family must all be added to the classification index. This includes documents without text.

Note: Textually empty documents will receive a rank at 50 (visible on the histogram), but they must be included in order to be served up to reviewers.

Prioritized Review considerations

  • Family-based review is only available for new projects or Prioritized Review queues that have never been started.
  • Once you click Start Review, you can't edit the Include Family settings. This means you can't turn family-based review on or off mid-project.
  • If you have any families with more than 100 documents, we recommend removing those families from the classification index and reviewing them manually. Large families can slow down the review process.

Reviewer considerations

  • Family review is optimized for email and attachments, and documents are sorted in the queue by control number. Using a relational field other than the family group relational field, such as the email thread group or textual near duplicate identification group fields can cause undesirable results.
  •  When family-based review is enabled and the document that served to a reviewer has family, the documents are presented to the reviewer in ascending control number order.
    • Upon requesting a document, the document with the lowest control number is served first, which is typically the parent document of the family
    • When a reviewer clicks Save and Next, the next document in the family is served, letting the reviewer to review family documents in an intuitive order.
    • This means the first document you see may not necessarily be the document most likely to be relevant; you could see a family document first.
  • Reviewers must code documents based on the so-called "four corners rule". This means that a document should be judged responsive or not responsive based solely on the extracted text of that document only. Documents that are relevant based on family members should not be coded relevant on the Active Learning review field. Although individual anomalies will not hurt the algorithm, too many in aggregate could cause a higher error rate. For more information on reviewer protocol and best practices, see Relativity Assisted Review Reviewer Protocol.

  • A document and its family are assigned to a single reviewer. If a reviewer is removed from the project after a set of family documents have been assigned and reviewed, you may need to manually find those unreviewed "abandoned" family documents.
    Use the following saved searches to find all unreviewed "abandoned" family documents:

    Search 1

    • Conditions: <Project Name> Reviewed On is set
    • Related items: 
      • + Family
    • Fields:
      • <Review field>
      • <Project Name>::Prioritized Review
      • <Project Name> Reviewed On
      • <Project Name> Reviewers::User
      • <Family Field>

    Search 2

    • Conditions: (Saved Search) document is in <Saved Search 1
      <Project Name> Reviewed On is not set

      Note: To find unreviewed documents for a specific user, substitute the <Project Name> Reviewers::User in place of the <Project Name> Reviewed On field.

    • Fields:
      • <Family Field>

Adding new documents

If you want to add new documents to your Active Learning project after review has begun, complete the following:

  1. Click Pause Review to stop the review queue.
  2. Add your new documents to the saved search used as the searchable set for the classification index.
  3. Navigate the Analytics indexes tab, and then click the classification index used to create your Active Learning project.
  4. On the index console, click Populate Index: Incremental.
  5. Once the index finishes populating, return to your review queue and click Start Review.

Note: All documents, including the newly added documents, are given a rank score after the incremental population.

If one of the new documents is part of a group of family documents that was already reviewed in Active Learning, the document can be reviewed by any reviewer. The other previously reviewed family documents won't be served again with this new document.