Over the nine years since it first rose to prominence in eDiscovery, technology-assisted review has expanded to include numerous new tools, more potential workflows, and a variety of legal issues
In “Alphabet Soup: TAR, CAL, and Assisted Review,” we discussed TAR’s rise to prominence and the challenges that it has created for practitioners. In “Key Terms and Concepts,” we discussed the key terms and concepts practitioners need to know. In “Applications, Aptitudes, and Effectiveness,” we discussed use cases, relative merits, and overall efficacy. In “Are You Allowed to Use TAR?,” we discussed case law on authorization to use TAR. In “Can You Be Compelled to Use TAR?,” we discussed case law on being compelling or directed to use TAR. In “When Is the Right Time for TAR Process Objections?,” we discussed case law on objection timing. In “What TAR Process Results Are Objectionable?,” we discussed case law on how good is good enough. In this Part, we review case law discussing process transparency requirements.
Another common question regarding the use of TAR approaches in discovery is whether process transparency is required. Process transparency in this context refers to transparency regarding how the chosen TAR approach is being deployed in the case, for example: how the chosen tool is being configured, how it is being trained, how its results are being tested, and to what standards of recall and precision it is being held. In some cases, process transparency has even included disclosure of the actual (non-privileged) documents used in the seed sets and control sets, including non-relevant documents. But, is any or all of that required?
Although there is some variation in the cases considering this question, the short answer is that process transparency is preferred but is not typically required absent some demonstrated deficiency in the process’s results.
In many of the early cases addressing the use of TAR approaches, the party seeking to use TAR voluntarily offered a lot of transparency into their proposed TAR process. Given the novelty at that time of using a TAR approach, this voluntary transparency was offered to help overcome objections and secure agreement from their opponent and approval from their judge.
For a time, the pattern in these early cases made it seem like a high level of transparency might be a requirement for TAR use, despite the facts that: (a) transparency in those cases was often offered voluntarily to help overcome objections to what was then a novel approach and (b) traditional document review approaches were never that transparent (or expected to be).
Not all cases have involved voluntary process transparency, however, and in cases where transparency has not been offered voluntarily, courts have expressed displeasure but have declined to compel transparency absent some demonstrated deficiency in the results:
The [plaintiffs] want to know, not whether a document exists or where it is, but rather how [the defendants] used certain documents before disclosing them. Rule 26(b)(1) doesn’t make such information disclosable. [emphasis added]
Though he concluded he could not compel the defendants to make the requested disclosure, the Judge did describe the defendants’ refusal as “troubling” and “below what the Sedona Conference endorses.” He also warned the Defendants that there could be consequences for uncooperativeness:
An unexplained lack of cooperation in discovery can lead a court to question why the uncooperative party is hiding something, and such questions can affect the exercise of discretion. [emphasis added]
Courts are split as to the degree of transparency required by the producing party as to its predictive coding process. In some cases, parties have agreed to – or courts have ordered – transparency into the TAR or predictive coding processes. In other cases, courts have not required production of seed set documents. [internal citations omitted, emphasis added]
In this case, the Magistrate Judge also split, coming to different conclusions regarding the requested process information and the requested document samples:
Notably, [the plaintiff] has not provided any specific examples of deficiencies in [the defendant’s] document production or any specific reason why it questions the adequacy of [the defendant’s] document collection and review. Without more detailed reasons why production of [the defendant’s] TAR information is needed, the court is unwilling to order [the defendant] to produce such information. [emphasis added]
The Judge ultimately agreed with the Magistrate Judge that the plaintiff was not entitled to discovery of the defendant’s process details:
“The scope of the obligation to search for, and produce, ESI is circumscribed by Federal Rule of Civil Procedure 26(g) . . . .” Karl Schieneman & Thomas C. Gricks III, The Implications of Rule 26(g) on the Use of Technology-Assisted Review, 7 Fed. Cts. L. Rev. 239, 243 (2013). But “[n]othing in Rule 26(g) obligates counsel to disclose the manner in which documents are collected, reviewed and produced in response to a discovery request.” Id. at 254. [emphasis added]
Upcoming in this Series
Up next in the final Part of this series, we will conclude our discussion of assisted review with a look at some case law discussing the combination of search terms and TAR approaches, as well as a review of some key takeaways from across the series.