Updated December 9, 2010
The features and functionality provided by the review platform will help shape your workflow and is probably one of the most important factors when selecting your service provider. The following outlines some of the basic review features that need to be included in system:
Whether you require simple review and coding for Responsive, Non-Responsive and Privilege documents, or in-depth subjective coding, the system should allow you to create your own coding scheme and apply it to the documents loaded into the system. Some questions to ask are:
The review platform must allow basic Boolean or other robust searching of the text and metadata of the documents. Phrase, proximity, wild cards, concept, fuzzy, near-dupes and other types of search tools are beneficial, but their importance will be determined by your review strategy. The system should also allow you to sort your results by various criteria such as date, custodian, and subject line. Search speed will impact each and every operation, and thus system speed is a prime consideration.
Alternative search tools, such as concept searching and visualization, should also be considered.
The ease and simplicity of creating and assigning folders or review sets to attorney review teams for review is essential. You should ask your service provider candidate(s):
Most discovery projects have both paper data as well as ESI. Identifying a service provider whose platform can handle both formats will allow you to centralize your review in one place.
Your review platform must support your production needs, and production processes need to integrate back to the review platform. For example, items previously produced need to be tracked in the review system, so you should factor these needs into your considerations.
Depending on your review requirements, redaction capabilities may be an essential feature for your review. If you are in a native format review platform, be sure to understand the workflow the service provider uses to generate image files for redaction purposes.
During production, you will want the redacted version to be the only one included in the produced dataset. It is important to understand how the service provider handles this to ensure that redacted text is removed from the Tiff or PDF image file, as well as, the text/metadata files if applicable.
As you are applying redactions to documents within the review platform, is the application tracking this information to, among other things, automatically create Confidentiality Logs that correspond to the redactions on produced documents?
Likewise, when you code to withhold a document from production due to privilege, are those codes automatically generating Privilege Logs, complete with privilege codes and any other supporting information that you may want to associate with each record withheld from production?
The system should have some functionality to print and/or share documents offline. Be sure to understand what capabilities you have available and any limitations or possible hardware or software requirements.
Administrative functions in the system should include the ability to:
The review system should allow you to effectively manage and report on your review team and document set. These reports should be produced daily or support a dynamic report generated through the administrative function in the system. The following reports may be desired:
Other review features that are not essential, but that are certainly beneficial may include: Hit highlighting, Concept searching, Auto-categorization, Email threading and Email visualization tools.