Basic Workflows#

Filters Pre-Determined with no Email Thread Exclusion Utilization#

1. Make a ‘Master’ View for each custodian or scope, minus the relevant dupe set.
2. Run any filters over the data (date range, domains, key terms, etc.) to create a ‘To Review’ View. It is recommended to run one filter at a time, so that the reduction per filter can easily be tracked and reported on at a later time. It is also recommended to use a standardized naming convention.
3. For auditing purposes, use an organizational code to flag all documents in the ‘To Review’ View as ‘Review Required’.
4. Run advanced tools (ETA, ND) over the ‘To Review’ View.
5. For all documents in the ‘To Review’ View, use either the ‘Number of Views’ splitter or Automation review to place documents into review for 1st level/contract reviewers.
6. During review, the advanced tools will be used by case management users to speed up review and quality control check the work of contract reviewers.
7. When review is complete, QC is performed. Basic QC consists of making sure that all files organizational coded as ‘Review Required’ have been tagged. Frequently, end users will provide additional checks they require. Common examples include, each relevant/responsive document receiving a confidentiality designation and making sure all documents with a ‘Redact Require’ tag have received a redaction.
8. After the completion of QC, the documents are prepped for delivery. This includes, creating tiffs for documents (if necessary) and making sure all the documents with redactions receive new OCR text.
9. The delivery is created and exported based on the client specifications.

Filters Pre-Determined and Email Thread Exclusion Utilization#

1. Make a ‘Master’ View for each custodian or scope, minus the relevant dupe set.
2. Run any filters over the data (date range, domains, key terms, etc.) to create a ‘Prior to ETA Exclusion’ View. It is recommended to run one filter at a time so that reduction per filter can easily be tracked and reported on at a later time. It is also recommended to use a standardized naming convention.
3. Run the ETA advanced tool over the ‘Prior to ETA Exclusion’ View.
4. Create a finalized view called ‘To Review’ using all documents in the ‘Prior to ETA Exclusion’ View and utilizing the ‘ETA Email Suppression’ exclusion option.
5. For auditing purposes, use an organizational code to flag all documents in the ‘To Review’ View as ‘Review Required’.
6. Run advanced tools (ETA, ND) over the ‘To Review’ View.
7. For all documents in the ‘To Review’ View, use either the ‘Number of Views’ splitter or Automation review to place documents into review for 1^st level/contract reviewers.
8. During review, the advanced tools will be used by case management users to speed up review and quality control check the work of contract reviewers.
9. When the review is completed, QC is performed. Basic QC consists of ensuring that all the files organizational coded as ‘Review Required’ have been tagged. Frequently, end users will provide additional checks they require. Common examples include, each relevant/responsive document receiving a confidentiality designation and ensuring all the documents with a ‘Redact Require’ tag have received a redaction.
10. After the completion of QC, documents are prepped for delivery. This includes creating tiffs for documents (if necessary) and ensuring all the documents with redactions receive new OCR text.
11. The delivery is created and exported based on client specifications.

Advanced Tools Workflows#

Filters Pre-Determined with no Email Thread Exclusion Utilization#

1. Make a ‘Master’ View for each custodian or scope, minus the relevant dupe set.
2. Run any filters over the data (date range, domains, key terms, etc.) to create a ‘To Review’ View. It is recommended to run one filter at a time, so that the reduction per filter can easily be tracked and reported on at a later time. It is also recommended to use a standardized naming convention.
3. For auditing purposes, use an organizational code to flag all the documents in the ‘To Review’ View as ‘Review Required’.
4. Run the advanced tools (ETA, ND) over the ‘To Review’ View.
5. Use the metadata filter to create a View called ‘ND Review’ for all the documents (and their family members) with a ‘ND Doc Count’ of 10 or greater. For some projects, it may be advisable to change the number of files in a ND group to consider depending on what percentage of all files are found using this methodology.
6. Use the metadata filter to create a View called ‘ETA Review’ for all the documents (and their family members) with an ‘ETA Doc Count’ or 10 or greater. For some projects, it may be advisable to change the number of files in an ETA group to consider depending on what percentage of all files are found using this methodology.
7. Combine the results of the ND and ETA Views to create a master ‘Advanced Tools Review’. Ideally this set of data will be 25% or less of the overall corpus of data.
8. Create a new View called ‘Linear Review’ for all the documents from the ‘To Review’ View minus the results of the ‘Advanced Tools’ review using the ‘View IDs’ exclusion option.
9. For auditing purposes, use an organizational code to flag all documents in the ‘Advanced Tools Review’ View as ‘AT Review’ and all documents in the ‘Linear Review’ View as ‘Linear Review’.
10. For all documents in the ‘Linear Review’ View, use either the ‘Number of Views’ splitter or Automation review to place documents into review for 1^st level/contract reviewers.
11. For all documents in the ‘Advanced Tools’ View, have second level/advanced reviewers all log into the same View and complete the review via the advanced tools. Reviewers should communicate about which ND groups they are addressing.
12. When the review is complete, QC is performed. Basic QC consists of making sure that all the files organizational coded as ‘Review Required’ have been tagged. Frequently, end users will provide additional checks they require. Common examples include, each relevant/responsive document receiving a confidentiality designation and ensuring all the documents with a ‘Redact Require’ tag have received a redaction.
13. After the completion of QC, documents are prepped for delivery. This includes creating tiffs for documents (if necessary) and making sure all the documents with redactions receive new OCR text.
14. The delivery is created and exported based on client specifications.

Filters Pre-Determined and Email Thread Exclusion Utilization#

1. Make a ‘Master’ View for each custodian or scope, minus the relevant dupe set.
2. Run any filters over the data (date range, domains, key terms, etc.) to create a ‘Prior to ETA Exclusion’ View. It is recommended to run one filter at a time so that reduction per filter can easily be tracked and reported on at a later time. It is also recommended to use a standardized naming convention.
3. Run the ETA advanced tool over the ‘Prior to ETA Exclusion’ View.
4. Create a finalized View called ‘To Review’ using all documents in the ‘Prior to ETA Exclusion’ View and utilizing the ‘ETA Email Suppression’ exclusion option.
5. For auditing purposes, use an organizational code to flag all documents in the ‘To Review’ View as ‘Review Required’.
6. Run advanced tools (ETA, ND) over the ‘To Review’ View.
7. Use the metadata filter to create a View called ‘ND Review’ for all documents (and their family members) with a ‘ND Doc Count’ of 10 or greater. For some projects it may be advisable to change the number of files in a ND group to consider depending on what percentage of all files are found using this methodology.
8. Use the metadata filter to create a View called ‘ETA Review’ for all documents (and their family members) with an ‘ETA Doc Count’ or 10 or greater. For some projects it may be advisable to change the number of files in an ETA group to consider depending on what percentage of all files are found using this methodology.
9. Combine the results of the ND and ETA Views to create a master ‘Advanced Tools Review’. Ideally this set of data will be 25% or less of the overall corpus of data.
10. Create a new View called ‘Linear Review’ for all documents from the ‘To Review’ View minus the results of the ‘Advanced Tools’ review using the ‘View IDs’ exclusion option.
11. For auditing purposes, use an organizational code to flag all documents in the ‘Advanced Tools Review’ View as ‘AT Review’ and all documents in the ‘Linear Review’ View as ‘Linear Review’.
12. For all documents in the ‘Linear Review’ View, use either the ‘Number of Views’ splitter or Automation review to place documents into review for 1^st level/contract reviewers.
13. For all documents in the ‘Advanced Tools’ View, have 2^nd level/advanced reviewers all log into the same View and complete the review via the advanced tools. Reviewers should communicate about which ND groups they are addressing.
14. When the review is completed, QC is performed. Basic QC consists of making sure that all files organizational coded as ‘Review Required’ have been tagged. Frequently, end users will provide additional checks they require. Common examples include, each relevant/responsive document receiving a confidentiality designation and ensuing all the documents with a ‘Redact Require’ tag have received a redaction.
15. After the completion of QC, documents are prepped for delivery. This includes creating tiffs for documents (if necessary) and ensuring all the documents with redactions receive new OCR text.
16. The delivery is created and exported based on client specifications.

Filters Not Yet Determined with no Email Thread Exclusion Utilization#

1. Make a ‘Master’ View for each custodian or scope, minus the relevant dupe set.
2. Run ECA advanced tools (CA, RA) over the ‘Master’ Views.
3. Case managers utilize the CA tool to investigate specific concepts and export out the concept list to help identify search terms. Users should work alongside their service provider to get search term reports and determine a finalized search term list for the project.
4. Case managers utilize the RA tool to investigate specific domains and email users to help identify the most relevant users. This can be used for creating domain/username exclusion or creating search terms based on specific domains. Users should work alongside their service provider to receive reduction reports to determine the overall impact of utilizing these filters on a project.
5. Run any filters (based on findings from the advanced tools) over the ‘Master’ View (date range, domains, key terms, etc.) to create a finalized ‘To Review’ View. It is recommended to run one filter at a time so that reduction per filter can easily be tracked and reported on at a later time. It is also recommended to use a standardized naming convention.
6. For auditing purposes, use an organizational code to flag all documents in the ‘To Review’ View as ‘Review Required’.
7. Run advanced tools (ETA, ND) over the ‘To Review’ View.
8. Use the metadata filter to create a View called ‘ND Review’ for all documents (and their family members) with a ‘ND Doc Count’ of 10 or greater. For some projects it may be advisable to change the number of files in a ND group to consider depending on what percentage of all files are found using this methodology.
9. Use the metadata filter to create a View called ‘ETA Review’ for all documents (and their family members) with an ‘ETA Doc Count’ or 10 or greater. For some projects it may be advisable to change the number of files in an ETA group to consider depending on what percentage of all files are found using this methodology.
10. Combine the results of the ND and ETA Views to create a master ‘Advanced Tools Review’. Ideally this set of data will be 25% or less of the overall corpus of data.
11. Create a new View called ‘Linear Review’ for all documents from the ‘To Review’ View minus the results of the ‘Advanced Tools’ review using the ‘View IDs’ exclusion option.
12. For auditing purposes, use an organizational code to flag all documents in the ‘Advanced Tools Review’ View as ‘AT Review’ and all documents in the ‘Linear Review’ View as ‘Linear Review’.
13. For all documents in the ‘Linear Review’ View, use either the ‘Number of Views’ splitter or Automation review to place documents into review for 1^st level/contract reviewers.
14. For all documents in the ‘Advanced Tools’ View, have 2^nd level/advanced reviewers all log into the same View and complete the review via the advanced tools. Reviewers should communicate about which ND groups they are addressing.
15. When the review is completed, QC is performed. Basic QC consists of making sure that all files organizational coded as ‘Review Required’ have been tagged. Frequently, end users will provide additional checks they require. Common examples include, each relevant/responsive document receiving a confidentiality designation and making sure all documents with a ‘Redact Require’ tag have received a redaction.
16. After the completion of QC, documents are prepped for delivery. This includes creating tiffs for documents (if necessary) and making sure all documents with redactions receive new OCR text.
17. The delivery is created and exported based on client specifications.

Filters Pre-Determined and Email Thread Exclusion Utilization#

1. Make a ‘Master’ View for each custodian or scope, minus the relevant dupe set.
2. Run ECA advanced tools (CA, RA) over the ‘Master’ Views.
3. Case managers utilize the CA tool to investigate specific concepts and export out the concept list to help identify search terms. Users should work alongside their service provider to get search term reports and determine a finalized search term list for the project.
4. Case managers utilize the RA tool to investigate specific domains and email users to help identify the most relevant users. This can be used for creating domain/username exclusion or creating search terms based on specific domains. Users should work alongside their service provider to receive reduction reports to determine the overall impact of utilizing these filters on a project.
5. Run any filters (based on findings from the advanced tools) over the ‘Master’ View (date range, domains, key terms, etc.) to create a ‘Prior to ETA Exclusion’ View. It is recommended to run one filter at a time so that reduction per filter can easily be tracked and reported on at a later time. It is also recommended to use a standardized naming convention.
6. Run the ETA advanced tool over the ‘Prior to ETA Exclusion’ View.
7. Create a finalized View called ‘To Review’ using all documents in the ‘Prior to ETA Exclusion’ View and utilizing the ‘ETA Email Suppression’ exclusion option.
8. For auditing purposes, use an organizational code to flag all documents in the ‘To Review’ View as ‘Review Required’.
9. Run the advanced tools (ETA, ND) over the ‘To Review’ View.
10. Use the metadata filter to create a View called ‘ND Review’ for all documents (and their family members) with a ‘ND Doc Count’ of 10 or greater. For some projects it may be advisable to change the number of files in a ND group to consider depending on what percentage of all files are found using this methodology.
11. Use the metadata filter to create a View called ‘ETA Review’ for all documents (and their family members) with an ‘ETA Doc Count’ or 10 or greater. For some projects it may be advisable to change the number of files in an ETA group to consider depending on what percentage of all files are found using this methodology.
12. Combine the results of the ND and ETA Views to create a master ‘Advanced Tools Review’. Ideally this set of data will be 25% or less of the overall corpus of data.
13. Create a new View called ‘Linear Review’ for all documents from the ‘To Review’ View minus the results of the ‘Advanced Tools’ review using the ‘View IDs’ exclusion option.
14. For auditing purposes, use an organizational code to flag all documents in the ‘Advanced Tools Review’ View as ‘AT Review’ and all documents in the ‘Linear Review’ View as ‘Linear Review’.
15. For all documents in the ‘Linear Review’ View, use either the ‘Number of Views’ splitter or Automation review to place documents into review for 1^st level/contract reviewers.
16. For all documents in the ‘Advanced Tools’ View, have 2^nd level/advanced reviewers all log into the same View and complete the review via the advanced tools. Reviewers should communicate about which ND groups they are addressing.
17. When the review is completed, QC is performed. Basic QC consists of making sure that all files organizational coded as ‘Review Required’ have been tagged. Frequently, end users will provide additional checks they require. Common examples include, each relevant/responsive document receiving a confidentiality designation and ensuring all the documents with a ‘Redact Require’ tag have received a redaction.
18. After the completion of QC, documents are prepped for delivery. This includes creating tiffs for documents (if necessary) and making sure all documents with redactions receive new OCR text.
19. The delivery is created and exported based on client specifications.