eDiscovery Case of the Week with Kelly Twigger
Hosted by eDiscovery expert and practicing attorney Kelly Twigger, Case of the Week delivers insightful, no-nonsense analysis of the latest case law decisions shaping ediscovery and litigation practice. Each week, Kelly breaks down key rulings from courts across the country, highlighting practical takeaways for litigators and legal professionals. With a deep understanding of electronically stored information (ESI) and years of expertise in the field, Kelly equips listeners with the knowledge they need to navigate complex ediscovery issues and use case law to their advantage. Whether you're a seasoned litigator or just starting out, Case of the Week will keep you informed and ahead of the curve.
eDiscovery Case of the Week with Kelly Twigger
Are Your Legal Hold and Preservation Processes Subject to Discovery?
Discover the intricate details behind a pivotal court ruling involving Uber Technologies Inc. that is reshaping the landscape of electronic discovery. What happens when transparency in data preservation becomes paramount in litigation? Join me, Kelly Twigger, as I guide you through the unfolding legal drama of Uber's multi-district litigation over alleged sexual misconduct by its drivers. We'll unravel the implications of United States Magistrate Judge Lisa Cisneros' significant decision, focusing on the motion to compel Uber to reveal its litigation hold practices and ESI preservation details. As we explore this case, you'll gain valuable insights into the court's emphasis on the importance of custodial and non-custodial data in legal proceedings.
Understand the ripple effects of this ruling on large organizations and their ESI preservation obligations. The court's decision sheds light on the critical need for detailed information about data custodians and highlights the balance between proportionality and relevance in document preservation. We'll discuss how Uber's response to these demands has influenced the ongoing litigation and the broader implications for eDiscovery practices. Whether you're a legal professional or simply fascinated by the complexities of the legal system, this episode is packed with insights and practical guidance to keep you informed in the evolving realm of electronic data management.
Doe LS 340 v. Uber Techs., Inc.
Read the blog about this case- eDiscovery Assistant Blog
eDiscovery Assistant Website
Sign up for Kelly's Case of the Week Newsletter here
eDiscovery Assistant Free 7 day Trial (no credit card required)
Thank you for tuning in to Case of the Week with Kelly Twigger. If you found today’s discussion helpful, don’t forget to subscribe, rate, and leave a review wherever you get your podcasts. For more insights and resources on eDiscovery, visit eDiscovery Assistant and explore our practical tools, case law library, and on-demand education from the eDiscovery Academy. Join us next episode as we break down another important case shaping the future of eDiscovery.
Welcome to the Case of the Week podcast, where each week, we break down a recent decision in electronic discovery case law and talk about the practical impact for you and your clients and keep you up to date on your obligations with electronically stored information as evidence. If you're a litigator, legal professional or you love the power of ESI as much as I do, this is the place to be. I'm Kelly Twigger, the CEO and founder of eDiscovery Assistant and the principal at ESI Attorneys, with more than 25 years of experience navigating the evolving landscape of litigation and eDiscovery. I'm a practicing attorney, author, speaker, entrepreneur and now podcaster who works as a discovery strategist and expert for clients at ESI Attorneys and to provide that knowledge to all legal professionals through our e-discovery assistant platform. In each episode, we'll tackle a new decision in e-discovery case law and how it shapes both your litigation strategy and planning for risk mitigation. If you're ready for blunt, actionable insights that keep you ahead of the curve, and maybe a few laughs along the way, this is your go-to podcast. Subscribe or follow now to start embracing the power of our Case of the Week series brought to you by eDiscovery Assistant.
Kelly Twigger:This week's decision raises the issue of what details a party has to provide about the custodians and legal hold put in place for a matter. This decision is one of several over the last few years that is requiring parties to exchange much more detail about custodians on hold and the efforts to preserve ESI, including what sources of ESI are being preserved and when. All right, let's dive into this week's decision. It comes to us from EnRA, ubertech's Passenger Sexual Assault Litigation. The title for this actual decision is Doe vs Uber Technologies Inc, but it is part of the larger series of the MDL litigation. This is a decision from January 9th of 2024 from United States Magistrate Judge Lisa Cisneros. Judge Cisneros has 24 cases in our e-discovery system database and, as always, we add the issues for each of the decisions in our database from our proprietary issue tagging structure. Those issues for this week's decision include attorney-client privilege, attorney work, product, legal hold, scope of preservation and protective order. All right, what are the facts before us? We are before the court on a motion to enforce pretrial order number two and compel Uber to produce information regarding its litigation hold and the scope of its preservation of ESI.
Kelly Twigger:The underlying litigation here is a multi-district litigation in which plaintiffs who were alleged victims of sexual assault or harassment by their Uber drivers alleged that Uber failed to implement appropriate safety precautions to protect them. The plaintiffs alleged that Uber was aware that its drivers were engaging in sexual misconduct or sexual assault against their passengers as early as 2014. Prior to this MDL, multiple individual cases against Uber were filed in California state court, which were consolidated according to that court's structure based on similar allegations. Now, in this case, on November 3rd quote an interim measure pending the party's proposal of a more tailored order concerning the preservation of relevant information and a way to ensure the preservation of documents and all ESI that may be discoverable in relation to any of the issues in this litigation. Close quote the parties then began to meet and confer to discuss the scope of Uber's evidence, preservation efforts and a proposed protective order. Uber declined to provide certain information regarding preservation efforts until a protective order was entered. The parties could not agree a theme we often see here on Case of the Week and the plaintiffs filed this motion on December 14, 2023. Now the final protective order between the parties was issued on December 28, 2023, so just two weeks later. That also does not sound like a very fun holiday vacation for the lawyers.
Kelly Twigger:Once the order was issued, uber provided some information on its preservation efforts on January 4 and January 8, 2024, including a list of 15,700 current and past employees subject to a legal hold, with only their job title, no names and no information about when the holds were issued. Of those 15,700, 10,200 of the employees were on hold for other unrelated matters. So right now we just have a list of job titles that were placed on hold, no other information about the matter for which they were placed on hold, who was in that job title at the time, who the actual person is that's on hold. The court then held a hearing on the motion on January 8, 2024, at which Uber confirmed that it had also produced documents from the California cases in which it claimed represented all of the information that plaintiffs sought about the sources of ESI, including both custodial and non-custodial sources. So remember here the plaintiffs want two things they want to know about the custodians that were placed on hold and they want to know about the sources of ESI that are related, both custodial and non-custodial.
Kelly Twigger:When we say non-custodial or custodial, for those of you who don't understand that term, that means something that is within a custodian's control. So I, as a custodian, may have control over my email, over specific SharePoint sites, over Slack, over Teams, data, whatever is specifically tied to me as a custodian and what you would search, based on me as the custodian, would be custodial data. Non-custodial data are data sources where information is stored that are not tied to a custodian. So think long-term databases or, like a salesforcecom, any kind of business related database that stores information for the company financial information, sales information, production information. Anything like that would be in databases that would not be custodian based. So we call those non-custodial data sources.
Kelly Twigger:Now here, because the plaintiffs had not been able to review all of the information provided by Uber in advance of the hearing, it asked the court to order disclosure of the categories included in their motion, to the extent that Uber had not already done so. Now, if you listen to the timeline here and that's always one of the things we focus on on case of the week you know that this motion was filed on December 14th. Uber ultimately produced information eight days after the protective order was entered, on the 28th, on the 4th, and then the hearing was held on the 8th and Uber also produced more information on the 8th. So essentially, plaintiffs are saying and the court is saying nobody's had a chance to look at the information that Uber provided. Now, what did the plaintiffs ask here from the court? Well, they asked the court to order Uber to do three things Immediately produce basic details surrounding its litigation holds, including the names, job titles and dates of employment of the recipients of the hold notices, the dates of issue and what litigation or claim the holds relate to. Two immediately disclose information as to the ESI sources enumerated in pretrial order number two, paragraph three, including non-custodial sources that Uber has preserved and when it preserved them, when such ESI sources were used, what they were used for, the general types of information they house and which Uber employees used or had access to those sources. And three, suspend Uber's company-wide document destruction policies for a period of time to allow plaintiffs to determine what, if any, relevant ESI has been destroyed. All right, let's turn to the court's analysis on those three asks.
Kelly Twigger:The court begins here with Uber's duty to preserve, stating that as soon as a potential claim is identified, a party has a duty to preserve evidence which it knows or reasonably should know is relevant to the action, including suspending any document retention policy and putting a legal hold in place to ensure preservation. Now, none of that comes as a surprise to us. We've known what the scope of the duty to preserve is and when it arises for a very long time. The court here also notes, however, that the duty to preserve includes an obligation to quote, identify, locate and maintain information that is relevant to specific, predictable and identifiable litigation close quote but that organizations are not required to preserve every document, and that's going to be important later in our analysis.
Kelly Twigger:Plaintiffs here argue that Uber unreasonably withheld basic facts around his litigation holds, including names, job titles, dates of employment for each recipient, the dates of issue and what claim the holds relate to, and that the information they are requesting was not subject to attorney-client privilege. Uber argues that the information they are requesting was not subject to attorney-client privilege. Uber argues that the Rule 26F checklist provided by the Northern District of California states that parties may provide quote the names and or general job titles of descriptions for custodians for whom ESI is preserved close quote and that they have complied with the language of that checklist by providing a list of job titles. Now I think, looking at the face of the list that they provided, as well as the checklist, that it's pretty obvious that Uber's actions are not really in keeping with what the court intended to be provided under that checklist. But let's hear what the court has to say.
Kelly Twigger:The court looked to recent precedent and found that Uber's position was not supported by the law. According to the court, the basic details surrounding a legal hold are not protected by either the attorney client or the work product privilege, and that the details about the hold, including when and to whom holds are given, are fair game. The court also found that, while plaintiffs are not entitled to exactly what Uber employees were told through the hold, they are entitled to know what the employees are doing to identify, collect and preserve ESI. Now, the disclosures that plaintiffs sought here included whether the legal hold related to a case or complaint involving allegations of sexual assault or sexual harassment, and Uber says that the plaintiffs are not entitled to that information. The court found here that the plaintiffs are entitled to that information that allowed them to evaluate whether Uber had met its preservation obligations and, given that a sexual harassment or assault case could have put Uber on notice of its duty to preserve, uber was required to tell plaintiffs which legal holds pertained to any case or complaint alleging such behavior by one of its drivers. With that, the court granted the motion for information about the legal holds pertains to any case or complaint alleging such behavior by one of its drivers. With that, the court granted the motion for information about the legal holds. The court then turned to the second question about information sought by plaintiffs about Uber's sources of ESI, and the court begins there by acknowledging that neither the plaintiffs or the court have been able to review the documents as I mentioned earlier in which Uber claims the information that plaintiffs requested is listed as such.
Kelly Twigger:The court looked at the legal question of what Uber is required to provide and held that quote. Parties are entitled to know what kinds and categories of ESI a party has collected and preserved and what specific actions were taken to that end. Close quote, citing the checklist for the Rule 26 meet and confer that I mentioned earlier. The court held that quote. The disclosure of information, including non-custodial sources of the ESI, is expected in the ordinary course of discovery. Close quote, identify and discuss. Quote a list of systems, if any, that contain ESI not associated with individual custodians. Close quote, such as enterprise databases. That's the non-custodial data sources that I was discussing earlier. The disclosure of non-custodial data sources will facilitate the party's ability to meet and confer regarding the scope of evidence preservation and, if necessary, propose a modified preservation order for this court's consideration. That's what the court is hoping to get out of the party's discussion.
Kelly Twigger:Following that, the court granted plaintiffs motion in part and required Uber to disclose the following information about the sources of ESI it preserved and specifically, what sources of ESI it preserved, when each source was preserved, when each ESI source was used, what each source was used for and the general types of information housed in each source. Owing to the shared number of employees that Uber has, the court declines to order Uber to provide information about which employees used or had access to each source of ESI, as the plaintiffs had requested. Finally, the court addressed the third request from plaintiffs the requested suspension of Uber's document destruction policies that remained in place Now. Plaintiffs alleged that the continued destruction policies may be allowing for relevant ESI to be destroyed every day, and they asked the court to suspend Uber's destruction policies until the parties could come to an agreement about a more tailored preservation order contemplated by pretrial order number two. Plaintiffs argue that the notice of the litigation began no later than 2013, but that Uber maintained only a six-month email retention policy from September 2015 to January 2023 and deleted Slack messages that were more than 90 days old during that period In January 2023, and deleted Slack messages that were more than 90 days old during that period. In January 2023, uber changed its email policy to retain emails not subject to a litigation hold for 24 months. Uber argued that Plaintiff's request was overbroad, that the company-wide suspension affects far more than just its rideshare application business, and that there's no legal basis to support the request to take off all of their document retention policies for the entire company. The court agreed with Uber here and found that the request was overly broad, noting that Uber has already suspended automatic deletion of its emails for thousands of custodians. The court also noted that the plaintiffs did not show that the relief sought addressed plaintiffs' concerns about the destruction of documents in earlier years and that a suggestion that potentially relevant ESI could be lost going forward is not sufficient to order the document destruction policies to be taken offline. With that, the court denied plaintiffs' request to order the suspension of Uber's company-wide policies.
Kelly Twigger:What are our takeaways from today's decision? Well, the biggest takeaway from today's case is that you need to understand the scope of information you may have to provide about efforts to identify and preserve ESI. For a matter, this decision is not an anomaly. It's one that I brought up because it's back to basics again. It's a bigger scope here because it's an MDL and Uber is a large company with more than 20,000 employees, but that doesn't change the legal precedent of this case.
Kelly Twigger:In fact, the decisions that the court cites to as a basis for its decision here involve individual parties. That means that, regardless of the size of your client, you need to be tracking all of the data about your preservation efforts. That includes, for each custodian, the dates of the hold that was sent, agreed to, the dates of the employment, the custodian's role, title, sources of ESI, date of custodial interview, etc. Track everything. For non-custodial data sources, you need to know the name of the source, the types of data stored in it, the liaison for that source, how long the source has been active at the company or the client and the date range of data stored in it. How can you access that data source, which includes working with the liaison between legal and IT or whoever has access to the source on preservation processes for each individual source of ESI?
Kelly Twigger:Now, in short, this decision makes it clear that in the Northern District of California, parties do need to exchange detailed information about efforts to preserve that are both custodial and non-custodial sources of ESI, including when legal holds were issued. Now, those of us who work in eDiscovery 24-7 know that this exchange of information is the best way to move things forward quickly, but there are risks of information being provided, of information that gets provided during those exchanges becoming public and suggesting larger organizations to increase litigation or requests that may not be above board or on par with the needs of the case. That was Uber's concern here, and the court correctly narrowed the focus of the motion to what was appropriate for the case. For you representing clients who are in larger organizations who are going to receive these types of requests, you need to be on notice to be able to argue sufficiently, tailoring the request so that the court can understand what is proportional to the needs of the case and what is overly broad. All right, that's our case of the week for this week.
Kelly Twigger:Thanks so much for joining me. We'll be back again next week with another decision from our eDiscovery Assistant database, as always. If you have suggestions for a case to be covered on the case of the week, please drop me a line. If you'd like to receive our case of the Week delivered to your inbox via our weekly newsletter. You can sign up for that at ediscoveryassistantcom backslash blog and if you're interested in doing a free trial of our case law and resource database, please jump to ediscoveryassistantcom to sign up and get started. Thanks for joining me on the Case of the Week podcast Tune in next episode as I discuss a new decision in eDiscovery case law and identify the issues you need to be paying attention to and how they can help you do better discovery for your clients and leverage the power of ESI. Be sure to subscribe and leave a review to help others discover the show and be kept in the know on all things electronic discovery. I'm Kelly Twigger. See you next time.