Documents in a Project
Your review manager has determined the total number of documents that can be assigned to you at one time in a stage. As you begin to code and save your documents, they will move from the Not Updated status to Updated. Documents in the Updated status are available for release. If the threshold for the stage is 100 documents, and you have coded and saved 50 documents, you will not be able to get more documents until the 50 reviewed documents are released. The maximum number of documents is the total of all your documents for the stage.
The default setting for displaying documents in your stage’s Results page is Not Updated. Use the Show Only menu and select All to display all the documents assigned to you in the stage. Selecting Updated will display only those documents you’ve reviewed, coded and saved. Before clicking the Release Updated button and moving your saved documents out of the stage and your permissions, you may want to QC the documents. Selecting Updated in the Show Only menu allows you to quickly access those documents.
Your administrator can also establish filters that ensure specific documents are reviewed first. Perhaps all documents need to be reviewed in the First Pass stage, but certain custodian documents need to be reviewed and coded first. The way your documents are grouped and the order they are displayed can also be set up and will appear in the Get More Documents summary dialog box.
As you code and save documents, their status will change from Not Updated to Updated. Upon closing a document, you will get a Refresh dialog box. Click the Refresh Search Results button to update your Results, moving the reviewed documents out of the Not Updated status to Updated.
Family Relationships
Typically, Review Projects are set up to keep document family relationships together; this means the entire family is treated as one document. If a parent document is assigned to you, all documents in the family will be included when you get documents. Therefore, the limit on the maximum number of documents might be exceeded when families are kept together for review.
Additionally, the project is set up to enforce certain rules based on the way documents are coded. When a project is set up to keep families together, the system looks at the rules and the family as a unit. Rules are enforced in order. If Rule 1 is met by any family member (for example, perhaps you are coding and saving an attachment), all documents in the family are considered to meet that rule and move as designated by the rule. Any other rules are irrelevant at that point.
If you are working in a Predict Project, the keep document family relationships together is not set up.