When you think about eDiscovery, you are probably thinking about review. Review is the phase of eDiscovery where your team will actually discover potentially relevant documents and evidence needed for a matter. A document review distinguishes relevant data from irrelevant data and uncovers information and evidence about the facts and issues of the matter. However, there are important pitfalls to address in review which, if not properly managed, can jeopardize your case, especially around protecting privileged material.
In today’s digital world, billions emails, text messages, presentations, database files, electronic documents, and the like are sent and received every day, creating eDiscovery dilemmas for lawyers and judges. Any one of them could be the pivotal document that either builds a case or destroys one.
If there is one case that demonstrates the awesome power of eDiscovery, it is United States v. Microsoft, the infamous antitrust trial that began in the late 1990’s. A key contention was that Microsoft was conspiring against Sun Microsystems. Thanks to the review process, an internal email from Bill Gates surfaced. In it, he asked: “Do we have a clear plan on what we want Apple to do to undermine Sun?” It was a modern-day smoking gun.
A more recent case demonstrates the danger inherent in the review process. The Samsung v. Applelitigation pitted two tech giants against each other in an epic court battle between the world’s dominant smartphone makers. But the case also showed that even the biggest companies can stumble in the face of eDiscovery review.
During document review, Samsung’s outside counsel improperly redacted a sensitive Apple contract it had obtained during the discovery process, a contract that was under a protective order, limiting its use to the litigation alone. The associate then uploaded the contract to Samsung’s internal intranet, where it “went viral.” When Apple found out, sanctions soon followed.
Another example comes from Oracle v. Google, which pitted two more tech companies against each other in a high-stakes copyright dispute. In that case, Google’s famous search abilities didn’t seem to transfer to its document review process. During its privilege review, the company screened out an email that was labeled “Attorney Work Product.” But Google’s review did not catch nine drafts of the same email, which were then produced to Oracle. Worse yet, that email became a key piece of evidence against the company.
As you can see, document review is not a matter to be taken lightly. A well-executed review process can win a matter for your client. But even a well-intentioned review team can make mistakes that can sink a case or expose litigants to a negative inference or even incur sanctions.
Document review is the act of identifying responsive documents to produce and privileged documents to withhold from opposing counsel. Review is an iterative, learning process, meaning you will need to repeat and refine your work over and over again. Through this process, your team will uncover factual issues in a case and develop legal strategies to pursue based on information that is found in a collection of documents.
Due to the exploding volumes of evidence available for eDiscovery, your team should limit the scope of what needs to be reviewed whenever possible using targeted collection, filtering, and culling techniques prior to a manual review. Other advanced technologies can be used prior to or in combination with a human review to reduce the amount of documents the human reviewers must examine.
The review process is the most complex and expensive part of eDiscovery. In order to begin, many teams create a review guide to define the process and help reviewers make informed decisions. The guide should explain the facts in the case, the search terms being used, and the codes to be used to mark responsive, non-responsive, privileged, and other determinations. Consider how you will:
As discussed in Chapter 1, Federal Rule of Civil Procedure 26(f) requires parties to meet and confer about preserving discoverable information and to develop a proposed discovery plan addressing discovery of electronically stored information and the form or forms in which it should be produced.
According to Rule 26(f), eDiscovery topics covered must include preservation, the form of production, and privilege and work-product protection claims. Other important issues to be discussed include the scope of the review, the issues in dispute, the search protocols, and the mechanics of the production of materials between parties after review. Parties should also facilitate communication channels between team leaders in order to resolve issues quickly.
Start by determining what form your information will come in. Will the data set in question be all ESI or mixture of ESI and paper? Converting paper to an electronic format can simplify the process, keeping the entire review in one collection.
Consider how the ESI will be searched. Parties often redact ESI in the way they once redacted paper documents, by blacking out text. To make that possible, ESI is converted to an image file, such as TIFF, in a process that makes it no longer searchable. Files you can’t search aren’t much help, however, so after redaction, searchability needs to be restored by using “optical character recognition.” OCR technology can extract the remaining text from the TIFF image file, restoring searchability to the non-redacted sections.
This TIFF-OCR method is most appropriate for documents that are largely text based. It is much less fitting for complex, dynamic documents, such as spreadsheets or databases. Consider the types of files likely to be reviewed before agreeing to a conversion method.
Similarly, parties should address Bates numbering early in the process. The Bates system is still the standard tool for tracking reviewed documents, but native files are not easily Bates numbered. However, Bates numbers can serve as filenames for native files. If you expect to handle a large number of native files, negotiate the Bates numbering conventions to be used at the Meet and Confer.
It is possible to begin privilege review before human eyes even see the first document. Most digital review systems can search and tag documents that have privileged names, email addresses, law firm domains or legal terms before reviewers examine those documents. Reviewers are aware that a document is potentially privileged and can review it to confirm it is in fact a privileged communication or attorney work product.
Perhaps the most important consideration in the review process is the search terms to be employed. As mentioned earlier, this process will be iterative. You will continually refine your search as the review process begins. After negotiating an initial list of search terms, you will begin reviewing the documents returned using these terms.
If too many irrelevant documents are being returned you are experiencing “noise,” also commonly referred to as “false positive” search results. If that is the case, search criteria may be refined, optimized, and tweaked to get the desired results. You will have to narrow search terms if too many irrelevant documents are found and broaden the search if too few relevant documents are found. This may also involve testing different search technologies.
Use Misspellings: This may be counter-intuitive, but even in the age of spell check, people get words wrong. Include common misspellings in your list of search terms.
Look for code words and jargon: Consider terms that only the players in a matter might know. Use language real people use in their emails, not lawyerly terminology.
Learn Boolean logic: Boolean searches use connectors such as “AND”, “OR”, and “NOT” to provide more refined searches. Proximity searches can identify when specific words are used in the same sentence or paragraph.
Play Your Wild Cards: Symbols can replace one or more characters (i.e., e-disc*very)
Stemming: Reduces a word to its root form, as in “eating,” “eat,” and “eater.”
Stop Words Stop Pointless Searches: Stop words tell the search engine to ignore common words that will not help find important information, like the, and, or with.
Quality control and due diligence should be performed at every stage of the review process to ensure consistent and accurate document designation. One important consideration is to allow the review team to tag documents for “further review” when unsure of coding. The review platform should also be able to apply quality control restrictions such as automatically identifying duplicate documents, or grouping families of documents such as threaded emails and attachments for easy identification.
In order to QC your work, include a second level review of all designated production documents (or a sample of them) by senior attorneys and randomly review the team’s coding to check for inconsistencies. Provide feedback to the reviewers as they work in order to improve quality and spot issues as they arise.
As we briefly highlighted above in the Oracle v. Google example, a failure to protect privileged documents can ruin a case. When privileged documents are produced to opposing counsel, privilege could be waived. In some cases, it is possible to demand the documents be returned and stricken from the record, but, as attorneys often say, you can’t unring a bell. That is, opposing counsel knows what the document says and will certainly use that knowledge to the best of their ability.
The work product doctrine protects records such as documents which were prepared by the client, the attorney, or an agent for either the client or the attorney. Attorney-client privilege pertains to communications by and between the attorney (or his/her agent) and a client that were made for the purpose of giving or receiving legal advice.
In order to review for privilege, search the review data set using a list of search terms that will likely identify privileged documents. Some possible search terms include:
Be sure to provide all reviewers with a list of people and topics that may involve privilege. Parties should have a discovery agreement in place that allows inadvertently produced privileged documents to be returned. A Rule 502(d) order may also be sought, in order to protect against waiving privilege through inadvertent disclosure. Otherwise, the court may deem the privilege to be waived.
Remember that what you see on screen as an email or a document is actually a partial representation of all of the data and information in an electronic document. Meeting the obligation to produce data means choosing suitable forms of production which deliver the content without destroying the hidden and associated information in a file, such as its metadata.
Requesting parties often demand native production of reviewed documents, but native production is complicated and often involves a form of production that closely approximates the contents and usability of the source. When negotiating the production of reviewed materials to outside parties, determine if native production is the best approach or if there is a more appropriate form of production.
Important questions to consider include:
The document review process is one of the most critical phases of an eDiscovery project. In order to properly manage this process, make sure to: