Legal Alert: The Tax Court Approves the Use of Predictive Coding

by Eversheds Sutherland (US) LLP
Contact

On September 17, the U.S. Tax Court, in Dynamo Holdings LP v. Commissioner, 143 T.C. No. 9 (Sept. 17, 2014), held that a taxpayer could use predictive coding, over the objection of the Internal Revenue Service (IRS), to identify relevant electronically stored information (ESI) for production. This is the first Tax Court case to address the use of predictive coding in response to a discovery request.

Background – What Is Predictive Coding?

Predictive coding, also referred to as Technology Assisted Review, is a method to expedite the review of large volumes of electronic documents or information. At the outset of the review, the predictive coding platform identifies the distinct qualities of each document in the data set. The platform then generates a random, statistically sound sample or seed set of 1,000 documents for review. A senior-level reviewer codes the “seed set” of documents for relevance, and the reviewer’s decisions are fed back into the platform. The platform’s algorithm “learns” from the coding decision made by the reviewer to separate relevant documents from irrelevant documents based on the identifying characteristics of the documents. The algorithm codes the unreviewed documents as responsive or non-responsive or scores them numerically based on the predicted level of responsiveness. Tests are performed to ensure to a statistical certainty that the documents were accurately coded. The predictive coding platform is then asked to generate additional sets for review using what it has cumulatively learned from the reviewer’s coding decisions. When the algorithm generates a set of documents that achieves satisfactory rates of recall and precision, the manual reviewing stops, and the platform applies its algorithm to the greater set of documents. The resulting set is then ready for production (unless there are attorney-client privilege or work product concerns).

If there are privilege or work product concerns, human reviewers examine the resulting set to determine which documents may be withheld. This method greatly reduces the number of documents the human reviewer must examine, thereby decreasing costs. An alternative method is to use keywords to generate the first seed set. Some say that doing so expedites the iterative process described above, although speed might be achieved at the risk of missing categories of documents that were not caught by the keyword search.

Background – The Legal Context

The Tax Court rules were amended in 2010 to include ESI provisions essentially similar to the Federal Rules of Civil Procedure. See Tax Court Rule 70(a). The IRS has provided guidance to its attorneys regarding the preservation and discovery of ESI. See, e.g., Chief Counsel Notice 2012-17 (Sept. 13, 2012). Neither Tax Court nor IRS guidance addresses predictive coding.

The principal substantive issue involved in Dynamo was the tax treatment of transfers of property to the taxpayer from Beekman Vista, Inc., a corporation wholly owned by a Canadian citizen, Delia Moog. The taxpayer characterized these transfers as loans; the IRS characterized them as disguised gifts from Ms. Moog to her daughter and nephew, who indirectly owned the taxpayer. The case has a long procedural history, including a summons enforcement proceeding which originated in the Southern District of Florida and ultimately reached the U.S. Supreme Court. United States v. Clarke, 573 U.S. ___ (June 19, 2014). The Court in Clarke held that the taxpayer was entitled to an evidentiary hearing to determine whether the summons against its chief financial officer should be enforced. It does not appear that any further proceedings have occurred in the District Court after the Supreme Court’s decision.

The IRS filed a motion to compel production of ESI contained on two specified backup storage tapes or, alternatively, the tapes themselves (either originals or copies). The taxpayer requested that it be permitted to use agreed search criteria in combination with predictive coding to identify relevant documents on the two tapes. The taxpayer proposed to use human reviewers to identify privileged and protected confidential information (for example, health information), and then to produce relevant, nonprivileged ESI. The taxpayer estimated that, without predictive coding, the cost of reviewing 3.5 million to 7 million documents on the two tapes would be more than $500,000. The use of predictive coding would lower the number of documents reviewed to 200,000 to 400,000 and the cost of review to $85,000.

The IRS objected to the taxpayer’s request to use predictive coding, arguing that the taxpayer should instead produce the tapes in their entirety, subject to a “clawback” agreement under which the disclosure of any privileged or confidential information on the tapes would not be a waiver of any privilege. The IRS asserted that it needed the backup tapes to review metadata and verify the dates on which documents were created, as well as to ascertain all transfers to the taxpayer by Beekman. The IRS also asserted that predictive coding was an “unproven technology” which would not reliably identify relevant documents. On March 11, 2014, the Tax Court held a hearing at which the parties presented expert witnesses on the use of predictive coding.

Sutherland Observation: The taxpayer could have requested that the IRS share in the expense of using the method of the IRS’s choice. A protective order from the court could have shifted some or all of the cost of producing the ESI to the IRS. While the Tax Court has not yet addressed the issue of apportioning the expense related to discovery of ESI, Tax Court Rule 103(a) allows the court to issue a protective order to protect a party from undue burden or expense related to a discovery request. The order can dictate the method or procedure to be used during discovery, but the order can also apportion the expenses of a particular method between the parties. The apportionment of cost may convince the IRS to accept cost-saving methods of discovery proposed by taxpayers.


The Tax Court’s Decision

The court noted that neither party appeared to contest the fact that relevant information existed on the backup tapes. The court did not consider it appropriate to order the taxpayer to give the tapes to the IRS in their entirety subject to a clawback agreement. Although the parties could consent to such an agreement, the court was not willing to compel the taxpayer to do so.

Having decided that only relevant ESI needed to be produced, the court sought to find a “happy medium” that would require the taxpayer to produce relevant nonprivileged ESI but would reduce the costs of doing so by reducing the universe of documents that had to be manually reviewed for privilege. The court relied on a leading article on predictive coding by Magistrate Judge Andrew Peck, the substance of which was adopted by the court in Moore. Moore v. Publicis Groupe SA, 2012 WL 1446534 (S.D.N.Y. 2012). Other courts have followed the example from Moore, recommending predictive coding as a method of producing responsive ESI in discovery. In F.D.I.C., the court ordered the parties to consider predictive coding. F.D.I.C. v. Bowden, CV413-245, 2014 WL 2548137 (S.D. Ga. June 6, 2014). See also, In re Actos (Pioglitazone) Products Liab. Litig., 6:11-MD-2299, 2012 WL 7861249 (W.D. La. July 27, 2012) (approving the use of predictive coding); Hinterberger v. Catholic Health Sys., Inc., 08-CV-380S F, 2013 WL 2250603 (W.D.N.Y. May 21, 2013) (recommending predictive coding to parties who showed a lack of progress in resolving issues pertaining to ESI).

The court disagreed with the IRS assertion that predictive coding was “unproven technology,” noting that the technology industry considered predictive coding to be widely accepted for both limiting e-discovery to relevant documents and producing ESI without undue burden. Because the taxpayer had represented that it would retain electronic discovery experts to meet with IRS counsel and to devise a search acceptable to the IRS, the court saw no reason why the taxpayer should not be able to use predictive coding. The court also stated that, in the event the IRS could demonstrate that the taxpayer’s approach did not produce all relevant documents, the IRS could renew its motion to compel.

Sutherland Observations: The Tax Court is in many ways an ideal forum in which to advocate for cost-saving technology such as predictive coding because it places great emphasis on reducing the cost of discovery, as evidenced by the informal discovery process required under that court’s rules. As noted above, other courts have also begun to allow litigants to use similar technology. This is a very welcome development, given the sometimes exorbitant costs of e-discovery.

 

 

 

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Eversheds Sutherland (US) LLP | Attorney Advertising

Written by:

Eversheds Sutherland (US) LLP
Contact
more
less

Eversheds Sutherland (US) LLP on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
Sign up using*

Already signed up? Log in here

*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
Privacy Policy (Updated: October 8, 2015):
hide

JD Supra provides users with access to its legal industry publishing services (the "Service") through its website (the "Website") as well as through other sources. Our policies with regard to data collection and use of personal information of users of the Service, regardless of the manner in which users access the Service, and visitors to the Website are set forth in this statement ("Policy"). By using the Service, you signify your acceptance of this Policy.

Information Collection and Use by JD Supra

JD Supra collects users' names, companies, titles, e-mail address and industry. JD Supra also tracks the pages that users visit, logs IP addresses and aggregates non-personally identifiable user data and browser type. This data is gathered using cookies and other technologies.

The information and data collected is used to authenticate users and to send notifications relating to the Service, including email alerts to which users have subscribed; to manage the Service and Website, to improve the Service and to customize the user's experience. This information is also provided to the authors of the content to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

JD Supra does not sell, rent or otherwise provide your details to third parties, other than to the authors of the content on JD Supra.

If you prefer not to enable cookies, you may change your browser settings to disable cookies; however, please note that rejecting cookies while visiting the Website may result in certain parts of the Website not operating correctly or as efficiently as if cookies were allowed.

Email Choice/Opt-out

Users who opt in to receive emails may choose to no longer receive e-mail updates and newsletters by selecting the "opt-out of future email" option in the email they receive from JD Supra or in their JD Supra account management screen.

Security

JD Supra takes reasonable precautions to insure that user information is kept private. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. However, please note that no method of transmitting or storing data is completely secure and we cannot guarantee the security of user information. Unauthorized entry or use, hardware or software failure, and other factors may compromise the security of user information at any time.

If you have reason to believe that your interaction with us is no longer secure, you must immediately notify us of the problem by contacting us at info@jdsupra.com. In the unlikely event that we believe that the security of your user information in our possession or control may have been compromised, we may seek to notify you of that development and, if so, will endeavor to do so as promptly as practicable under the circumstances.

Sharing and Disclosure of Information JD Supra Collects

Except as otherwise described in this privacy statement, JD Supra will not disclose personal information to any third party unless we believe that disclosure is necessary to: (1) comply with applicable laws; (2) respond to governmental inquiries or requests; (3) comply with valid legal process; (4) protect the rights, privacy, safety or property of JD Supra, users of the Service, Website visitors or the public; (5) permit us to pursue available remedies or limit the damages that we may sustain; and (6) enforce our Terms & Conditions of Use.

In the event there is a change in the corporate structure of JD Supra such as, but not limited to, merger, consolidation, sale, liquidation or transfer of substantial assets, JD Supra may, in its sole discretion, transfer, sell or assign information collected on and through the Service to one or more affiliated or unaffiliated third parties.

Links to Other Websites

This Website and the Service may contain links to other websites. The operator of such other websites may collect information about you, including through cookies or other technologies. If you are using the Service through the Website and link to another site, you will leave the Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We shall have no responsibility or liability for your visitation to, and the data collection and use practices of, such other sites. This Policy applies solely to the information collected in connection with your use of this Website and does not apply to any practices conducted offline or in connection with any other websites.

Changes in Our Privacy Policy

We reserve the right to change this Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our privacy policy will become effective upon posting of the revised policy on the Website. By continuing to use the Service or Website following such changes, you will be deemed to have agreed to such changes. If you do not agree with the terms of this Policy, as it may be amended from time to time, in whole or part, please do not continue using the Service or the Website.

Contacting JD Supra

If you have any questions about this privacy statement, the practices of this site, your dealings with this Web site, or if you would like to change any of the information you have provided to us, please contact us at: info@jdsupra.com.

- hide
*With LinkedIn, you don't need to create a separate login to manage your free JD Supra account, and we can make suggestions based on your needs and interests. We will not post anything on LinkedIn in your name. Or, sign up using your email address.