Close
Enter your
text here

Analysis

eDiscovery Best Practices: When Litigation Hits, The First 7 to 10 Days is Critical

When a case is filed, several activities must be completed within a short period of time (often as soon as the first seven to ten days after filing) to enable you to assess the scope of the case, where the key electronically stored information (ESI) is located and whether to proceed with the case or attempt to settle with opposing counsel.  Here are several of the key early activities that can assist in deciding whether to litigate or settle the case.

Activities:

  • Create List of Key Employees Most Likely to have Documents Relevant to the Litigation: To estimate the scope of the case, it’s important to begin to prepare the list of key employees that may have potentially responsive data.  Information such as name, title, eMail address, phone number, office location and where information for each is stored on the network is important to be able to proceed quickly when issuing hold notices and collecting their data.
  • Issue Litigation Hold Notice and Track Results: The duty to preserve begins when you anticipate litigation; however, if litigation could not be anticipated prior to the filing of the case, it is certainly clear once the case if filed that the duty to preserve has begun.  Hold notices must be issued ASAP to all parties that may have potentially responsive data.  Once the hold is issued, you need to track and follow up to ensure compliance.  Here are a couple of recent posts regarding issuing hold notices and tracking responses.
  • Interview Key Employees: As quickly as possible, interview key employees to identify potential locations of responsive data in their possession as well as other individuals they can identify that may also have responsive data so that those individuals can receive the hold notice and be interviewed.
  • Interview Key Department Representatives: Certain departments, such as IT, Records or Human Resources, may have specific data responsive to the case.  They may also have certain processes in place for regular destruction of “expired” data, so it’s important to interview them to identify potentially responsive sources of data and stop routine destruction of data subject to litigation hold.
  • Inventory Sources and Volume of Potentially Relevant Documents: Potentially responsive data can be located in a variety of sources, including: shared servers, eMail servers, employee workstations, employee home computers, employee mobile devices, portable storage media (including CDs, DVDs and portable hard drives), active paper files, archived paper files and third-party sources (consultants and contractors, including cloud storage providers).  Hopefully, the organization already has created a data map before litigation to identify the location of sources of information to facilitate that process.  It’s important to get a high level sense of the total population to begin to estimate the effort required for discovery.
  • Plan Data Collection Methodology: Determining how each source of data is to be collected also affects the cost of the litigation.  Are you using internal resources, outside counsel or a litigation support vendor?  Will the data be collected via an automated collection system or manually?  Will employees “self-collect” any of their own data?  Answers to these questions will impact the scope and cost of not only the collection effort, but the entire discovery effort.

These activities can result in creating a data map of potentially responsive information and a “probable cost of discovery” spreadsheet (based on initial estimated scope compared to past cases at the same stage) that will help in determining whether to proceed to litigate the case or attempt to settle with the other side.

So, what do you think?  How quickly do you decide whether to litigate or settle?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Best Practices: Documentation is Key to a Successful Discovery Effort
 

We like to point out good articles about eDiscovery on this blog to keep our readers aware of trends and best practices.  I recently read an article on InsideCounsel titled E-discovery: Memorializing the e-discovery process, written by Alvin Lindsay, which had some good specific examples of where good documentation is important to prevent sanctions and save litigation costs.

Litigation Holds

The author notes that, since the Zubulake opinions issued by Judge Shira Scheindlin in 2003 and 2004, 1) most jurisdictions have come to expect that parties must issue a litigation hold “as soon as litigation becomes reasonably foreseeable”, and 2) “oral” litigation holds are unlikely to be sufficient since the same Judge Scheindlin noted in Pension Committee that failure to issue a “written” litigation hold constitutes “gross negligence”.  His advice: “make sure the litigation hold is in writing, and includes at minimum the date of issue, the recipients and the scope of preservation”.  IT personnel responsible for deleting “expired” data (outside of retention policies) also need to receive litigation hold documentation; in fact, “it can be a good idea to provide a separate written notice order just for them”.  Re-issuing the hold notices periodically is important because, well, people forget if they’re not reminded.  For previous posts on the subject of litigation holds, click here and here.

Retention Policies and Data Maps

Among the considerations for documentation here are the actual retention and destruction policies, system-wide backup procedures and “actual (as opposed to theoretical) implementation of the firm’s recycle policy”, as well as documentation of discussions with any personnel regarding same.  A data map provides a guide for legal and IT to the location of data throughout the company and important information about that data, such as the business units, processes and technology responsible for maintaining the data, as well as retention periods for that data.  The author notes that many organizations “don’t keep data maps in the ordinary course of business, so outside counsel may have to create one to truly understand their client’s data retention architecture.”  Creating a data map is impossible for outside counsel without involvement and assistance at several levels within the organization, so it’s truly a group effort and best done before litigation strikes.  For previous posts on the subject of data maps, click here and here.

Conferences with Opposing Counsel

The author discusses the importance of documenting the nature and scope of preservation and production and sums up the importance quite effectively by stating: “If opposing parties who are made aware of limitations early on do not object in a timely fashion to what a producing party says it will do, courts will be more likely to invoke the doctrines of waiver and estoppel when those same parties come to complain of supposed production infirmities on the eve of trial.”  So, the benefits of documenting those limitations early on are clear.

Collecting, Culling and Sampling

Chain of custody documentation (as well as a through written explanation of the collection process) is important to demonstrating integrity of the data being collected.  If you collect at a broad level (as many do), then you need to cull through effective searching to identify potentially responsive ESI.  Documenting the approach for searching as well as the searches themselves is key to a defensible searching and culling process (it helps when you use an application, like FirstPass®, powered by Venio FPR™, that keeps a history of all searches performed).  As we’ve noted before, sampling enables effective testing and refinement of searches and aids in the defense of the overall search approach.

Quality Control

And, of course, documenting all materials and mechanisms used to provide quality assurance and control (such as “materials provided to and used to train the document reviewers, as well as the results of QC checks for each reviewer”) make it easier to defend your approach and even “clawback” privileged documents if you can show that your approach was sound.  Mistakes happen, even with the best of approaches.

So, what do you think?  These are some examples of important documentation of the eDiscovery process – can you think of others?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Case Law: Judge Peck Denies Recusal Motion in Da Silva Moore
 

It’s been a few weeks since we heard anything from the Da Silva Moore case.  If you’ve been living under a rock the past few months, Magistrate Judge Andrew J. Peck of the U.S. District Court for the Southern District of New York issued an opinion in this case in February making it one of the first cases to accept the use of computer-assisted review of electronically stored information (“ESI”).  However, the plaintiffs objected to the ruling and questioned Judge Peck’s relationship with defense counsel and with the selected vendor for the case, Recommind and ultimately formally requested the recusal of Judge Peck.  For links to all of the recent events in the case that we’ve covered, click here.

Last Friday, in a 56 page opinion and order, Judge Peck denied the plaintiffs’ motion for recusal.  The opinion and order reviewed the past several contentious months and rejected the plaintiffs’ arguments for recusal in the following areas:

Participation in conferences discussing the use of predictive coding:

“I only spoke generally about computer-assisted review in comparison to other search techniques…The fact that my interest in and knowledge about predictive coding in general overlaps with issues in this case is not a basis for recusal.”

“To the extent plaintiffs are complaining about my general discussion at these CLE presentations about the use of predictive coding in general, those comments would not cause a reasonable objective observer to believe I was biased in this case. I did not say anything about predictive coding at these LegalTech and other CLE panels that I had not already said in in my Search,Forward article, i.e., that lawyers should consider using predictive coding in appropriate cases. My position was the same as plaintiffs’ consultant . . . . Both plaintiffs and defendants were proposing using predictive coding in this case.  I did not determine which party’s predictive coding protocol was appropriate in this case until the February 8, 2012 conference, after the panels about which plaintiffs complain.”

“There are probably fewer than a dozen federal judges nationally who regularly speak at ediscovery conferences. Plaintiffs' argument that a judge's public support for computer-assisted review is a recusable offense would preclude judges who know the most about ediscovery in general (and computer-assisted review in particular) from presiding over any case where the use of predictive coding was an option, or would preclude those judges from speaking at CLE programs. Plaintiffs' position also would discourage lawyers from participating in CLE programs with judges about ediscovery issues, for fear of subsequent motions to recuse the judge (or disqualify counsel).”

Relationship with defense counsel Ralph Losey:

“While I participated on two panels with defense counsel Losey, we never had any ex parte communication regarding this lawsuit. My preparation for and participation in ediscovery panels involved only ediscovery generally and the general subject of computer-assisted review. Losey's affidavit makes clear that we have never spoken about this case, and I confirm that. During the panel discussions (and preparation sessions), there was absolutely no discussion of the details of the predictive coding protocol involved in this case or with regard to what a predicative coding protocol should look like in any case. Plaintiffs' assertion that speaking on an educational panel with counsel creates an appearance of impropriety is undermined by Canon 4 of the Judicial Code of Conduct, which encourages judges to participate in such activities.”

Relationship with Recommind, the selected vendor in the case:

“The panels in which I participated are distinguishable. First, I was a speaker at educational conferences, not an audience member. Second, the conferences were not one-sided, but concerned ediscovery issues including search methods in general. Third, while Recommind was one of thirty-nine sponsors and one of 186 exhibitors contributing to LegalTech's revenue, I had no part in approving the sponsors or exhibitors (i.e., funding for LegalTech) and received no expense reimbursement or teaching fees from Recommind or LegalTech, as opposed to those companies that sponsored the panels on which I spoke. Fourth, there was no "pre-screening" of MSL's case or ediscovery protocol; the panel discussions only covered the subject of computer-assisted review in general.”

Perhaps it is no surprise that Judge Peck denied the recusal motion.  Now, the question is: will District Court Judge Andrew L. Carter, Jr. weigh in?

So, what do you think?  Should Judge Peck recuse himself in this case or does he provide an effective argument that recusal is unwarranted?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Trends: Where Does the Money Go? RAND Provides Some Answers
 

The RAND Corporation, a nonprofit research and analysis institution recently published a new 159 page report related to understanding eDiscovery costs entitled Where the Money Goes: Understanding Litigant Expenditures for Producing Electronic Discovery by Nicholas M. Pace and Laura Zakaras that has some interesting findings and recommendations.  To obtain either a paperback copy or download a free eBook of the report, click here.

For the study, the authors requested case-study data from eight Fortune 200 companies and obtained data for 57 large-volume eDiscovery productions (from both traditional lawsuits and regulatory investigations) as well as information from extensive interviews with key legal personnel from the participating companies.  Here are some of the key findings from the research:

  • Review Makes Up the Largest Percentage of eDiscovery Production Costs: By a whopping amount, the major cost component in their cases was the review of documents for relevance, responsiveness, and privilege (typically about 73 percent). Collection, on the other hand, only constituted about 8 percent of expenditures for the cases in the study, while processing costs constituted about 19 percent in the cases.  It costs about $14,000 to review each gigabyte and $20,000 in total production costs for each gigabyte (click here for a previous study on per gigabyte costs).  Review costs would have to be reduced by about 75% in order to make those costs comparable to processing, the next highest component.
  • Outside Counsel Makes Up the Largest Percentage of eDiscovery Expenditures: Again, by a whopping amount, the major cost component was expenditures for outside counsel services, which constituted about 70 percent of total eDiscovery production costs.  Vendor expenditures were around 26 percent.  Internal expenditures, even with adjustments made for underreporting, were generally around 4 percent of the total.  So, almost all eDiscovery expenditures are outsourced in one way or another.
  • If Conducted in the Traditional Manner, Review Costs Are Difficult to Reduce Significantly: Rates currently paid to “project attorneys during large-scale reviews in the US may well have bottomed out” and foreign review teams are often not a viable option due to “issues related to information security, oversight, maintaining attorney-client privilege, and logistics”.  Increasing the rate of review is also limited as, “[g]iven the trade-off between reading speed and comprehension…it is unrealistic to expect much room for improvement in the rates of unassisted human review”.  The study also notes that techniques for grouping documents, such as near-duplicate detection and clustering, while helpful, are “not the answer”.
  • Computer-Categorized Document Review Techniques May Be a Solution: Techniques such as predictive coding have the potential of reducing the review hours by about 75% with about the same level of consistency, resulting in review costs of less than $2,000 and total production costs of less than $7,000.  However, “lack of clear signals from the bench” that the techniques are defensible and lack of confidence by litigants that the techniques are reliable enough to reliably identify the majority of responsive documents and privileged documents are barriers to wide-scale adoption.

Not surprisingly, the recommendations included taking “the bold step of using, publicly and transparently, computer-categorized document review techniques” for large-scale eDiscovery efforts.

So, what do you think?  Are you surprised by the cost numbers?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Best Practices: Test Your Searches Before the Meet and Confer
 

One of the very first posts ever on this blog discussed the danger of using wildcards.  For those who haven’t been following the blog from the beginning, here’s a recap.

A couple of years ago, I provided search strategy assistance to a client that had already agreed upon several searches with opposing counsel.  One search related to mining activities, so the attorney decided to use a wildcard of “min*” to retrieve variations like “mine”, “mines” and “mining”.

That one search retrieved over 300,000 files with hits.

Why?  Because there are 269 words in the English language that begin with the letters “min”.  Words like “mink”, “mind”, “mint” and “minion” were all being retrieved in this search for files related to “mining”.  We ultimately had to go back to opposing counsel and attempt to negotiate a revised search that was more appropriate.

What made that process difficult was the negotiation with opposing counsel.  My client had already agreed on over 200 terms with opposing counsel and had proposed many of those terms, including this one.  The attorneys had prepared these terms without assistance from a technology consultant (I was brought into the project after the terms were negotiated and agreed upon) and without testing any of the terms.

Since they had been agreed upon, opposing counsel was understandably resistant to modifying the terms.  The fact that my client faced having to review all of these files was not their problem.  We were ultimately able to provide a clear indication that many of the terms in this search were non-responsive and were able to get opposing counsel to agree to a modified list of variations of “mine” that included “minable”, “mine”, “mineable”, “mined”, “minefield”, “minefields”, “miner”, “miners”, “mines”, “mining” and “minings”.  We were able sort through the “minutia” and “minimize” the result set to less than 12,000 files with hits, saving our client a “mint”, which they certainly didn’t “mind”.  OK, I’ll stop now.

However, there were several other inefficient terms that opposing counsel refused to renegotiate and my client was forced to review thousands of additional files that they shouldn’t have had to review, which was a real “mindblower” (sorry, I couldn’t resist).  Had the client included a technical member on the team and had they tested each of these searches before negotiating terms with opposing counsel, they would have been able to figure out which terms were overbroad and would have been better prepared to negotiate favorable search terms for retrieving potentially responsive data.

When litigation is anticipated, it’s never too early to begin collecting potentially responsive data and assessing it by performing searches and testing the results.  However, if you wait until after the meet and confer with opposing counsel, it can be too late.

So, what do you think?  What steps do you take to assess your data before negotiating search terms?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Trends: Wednesday LTWC 2012 Sessions
 

As noted yesterday, LegalTech West Coast 2012 (LTWC) is happening this week and eDiscoveryDaily is here to report about the latest eDiscovery trends being discussed at the show.  There’s still time to check out the show if you’re in the Los Angeles area with a number of sessions (both paid and free) available and 69 exhibitors providing information on their products and services, including (shameless plug warning!) my company, CloudNine Discovery, which just announced yesterday release of Version 11 of our linear review application, OnDemand®, and will be exhibiting at booth #216 along with our partners, First Digital Solutions.  Come by and say hi!

Perform a “find” on today’s LTNY conference schedule for “discovery” and you’ll get 21 hits.  More eDiscovery sessions happening!  Here are some of the sessions in the main conference tracks:

10:30 – 12:00 AM:

Information Governance and Information Management

With the volume of electronically stored information (ESI) growing exponentially and the challenges surrounding managing it, protecting it, and developing effective policies are essential. Social media, email, IMs, web pages, mobile devices and the cloud have made a big job even bigger. How much or how little should you collect? How aggressive should you be? How can you be certain your approach and results are defensible?

Speakers are: Richard E. Davis, JD, e-Discovery Solutions Architect & Founder, Litigation Logistics, LLC; Jack Halprin, Head of eDiscovery, Google; Dawson Horn, III, Senior Litigation Counsel, Tyco International and David Yerich, Director, eDiscovery, UHG Legal Department, United Health Group.

The GARP® Principles and eDiscovery

Attendees will hear from experts on the GARP Principles and eDiscovery as well as:

  • Understand the importance of proactive records management through the eight GARP® Principles
  • Revisit the GARP® Principles and learn how their role is magnified by recent case law
  • Learn what to do before eDiscovery: how GARP® precedes and complements the EDRM

Speakers are: Gordon J. Calhoun, Esq., Lewis Brisbois Bisgaard &, Smith LLP; Lorrie DeCoursey, Former Law Firm Administrator and John J. Isaza, Esq., Partner, Rimon P.C.  Moderator: David Baskin, Vice President of Product Management, Recommind.

1:30 – 3:00 PM:

Practical Handbook for Conducting International eDiscovery – Tips and Tricks

This session will present a truly international view on how to conduct global eDiscovery from a practical perspective, including developing proactive global document retention policies and assuring multi-jurisdictional compliance, best practices of global data preservation and collection, successful data migration across jurisdictions, navigating unique cultural and procedural challenges in various global regions, handling multi-lingual data sets as well as strategic positioning of hosting data centers.

Speakers are: Monique Altheim, Esq., CIPP, The Law Office of Monique Altheim; George I. Rudoy, Founder & CEO, Integrated Legal Technology, LLC and David Yerich, Director, eDiscovery, UHG Legal Department, United Health Group.

Litigation Preparedness Through Effective Data Governance

Be prepared. This panel will go through the benefits of data governance in your litigation preparedness and discuss benefits such as:

  • Auto-classification of legacy and newly created content
  • What is email management and is it ready for prime-time?
  • Review the court's findings on the complexities of ESI, including metadata, native formats, back-up tapes, mobile devices, and legacy technology
  • Key questions to ask before outsourcing ESI to the cloud

Speakers are: Lorrie DeCoursey, Former Law Firm Administrator; John J. Isaza, Esq., Partner, Rimon P.C. and Ayelette Robinson, Director – Knowledge Technology, Littler Mendelson.  Moderator: Derek Schueren, GM, Information Access and Governance, Recommind.

3:30 – 5:00 PM:

Managed and Accelerated Review

As costs for review soar and volumes of data multiply at an almost exponential rate, traditional linear review seems to be giving way to new technologies that will enable faster, better, more defensible eDiscovery results. How can you be assured that this new approach will catch everything that needs to be captured? Will human review become obsolete? What do you need to ask when considering this new technology? How should it be incorporated into your overall litigation strategy?

Speakers are: Matthew Miller, Manager, Fraud Investigation & Dispute Services, Ernst & Young; Robert Miller, Founder, Rise Advisory Group, LLC; Former Discovery Counsel, BP; David Sun, Discovery Project Manager, Google.

eDiscovery Circa 2015: Will Aggressive Preservation/Collection and Predictive Coding be Commonplace?

Who's holding back on Predictive Coding, clients or outside counsel? This session will discuss if aggressive preservation/collection of predictive coding will become commonplace as well as:

  • How aggressive should clients be with preservation/collection?
  • How to use effective searching, sampling, and targeting tools and techniques to not over-collect

Speakers are: Gordon J. Calhoun, Esq., Lewis Brisbois Bisgaard &, Smith LLP; Lorrie DeCoursey, Former Law Firm Administrator and Greg Chan, Senior Regional Litigation Technology Manager, Bingham McCutchen LLP.  Moderator: David Baskin, Vice President of Product Management, Recommind.

In addition to these, there are other eDiscovery-related sessions today.  For a complete description for all sessions today, click here.

So, what do you think?  Are you planning to attend LTWC this year?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Trends: Welcome to LegalTech West Coast 2012!
 

Today is the start of LegalTech® West Coast 2012 (LTWC) and eDiscoveryDaily is here to report about the latest eDiscovery trends being discussed at the show.  Over the next two days, we will provide a description each day of some of the sessions related to eDiscovery to give you a sense of the topics being covered.  If you’re in the Los Angeles area, come check out the show – there are a number of sessions (both paid and free) available and 69 exhibitors providing information on their products and services, including (shameless plug warning!) my company, CloudNine Discovery, which just announced today release of Version 11 of our linear review application, OnDemand®, and will be exhibiting at booth #216 along with our partners, First Digital Solutions.  Come by and say hi!

Perform a “find” on today’s LTNY conference schedule for “discovery” and you’ll get 19 hits.  So, there is plenty to talk about!  Sessions in the main conference tracks include:

10:30 AM – 12:00 PM:

A "Stormy" Subject…Exploring Cloud-Based eDiscovery

Can your organization better manage costs and increase control over discovery by bringing eDiscovery tools in-house or in-firm? What are the advantages and drawbacks of eDiscovery in the cloud? In this session, the panel will:

  • Explore insourcing v. outsourcing market trends
  • Discuss the pros and cons inherent in cloud/SaaS v. on premises e-discovery software solutions
  • Examine challenges when collecting and preserving discoverable data stored in the cloud

Speakers are: Scott Sachs, eDiscovery Attorney, Atkinson Andelson and Adam Sand, Associate General Counsel, Ancestry.com.  Moderator: Wayne Wong, Managing Consultant, Kroll Ontrack.

1:30 – 3:00 PM:

Under Fire: Defending and Challenging Technology-Assisted Review

Intelligent Review? Predictive Coding? Smart review? Whatever you call it, amidst growing data volumes and dwindling resources, traditional linear document review is quickly going the way of the dinosaur. In this session, the panel will:

  • Explore the "what", "why", and "how" behind  technology-assisted review
  • Discuss cutting-edge opinions from the bench
  • Provide you with tips to help overcome your organization's objections to using intelligent review technology

Speakers are: Tom Werner, Associate, Irell & Manella, LLP; Jeffrey Fowler, Partner, O'Melveny & Myers, LLP and Pallab Chakraborty, Director of eDiscovery, Oracle.  Moderator: Andrea Gibson, Product Director, Kroll Ontrack.

3:30 – 5:00 PM:

Exploring Hot eDiscovery Trends: FRCP Amendments, Social Media, and Emerging Case Law

eDiscovery evolves at the speed of light. If your organization is standing still, you are losing ground. In this session, the panel will:

  • Explore how eDiscovery evolved in 2011, with a look into how it will continue to change in the remainder of 2012
  • Analyze whether potential amendments to the Federal Rules of Civil Procedure are even possible, and what the amendments might entail discuss "hot" trends impacting eDiscovery such as social media.

Panelists are: Ron S. Best, EDD Staff Attorney & Director, Litigation Systems, Munger, Tolles & Olson, LLP and Eric Chan, Associate, O'Melveny & Myers, LLP.  Moderator: Joel Vogel, Vice President, Discovery Products and Services, Kroll Ontrack.

In addition to these, there are other eDiscovery-related sessions today.  For a complete description for all sessions today, click here.

So, what do you think?  Are you planning to attend LTWC this year?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Trends: For Da Silva Moore Addicts
 

I am getting prepared to head for sunny Los Angeles for LegalTech West Coast shortly, so today I’m getting by with a little help from my friends.  Tomorrow and Wednesday, I’ll be covering the show.  It wouldn’t be a week in eDiscovery without some tidbits about the Da Silva Moore case, so here are some other sources of information and perspectives about the eDiscovery case of the year (so far).  But, first, let’s recap.

Several weeks ago, in Da Silva Moore v. Publicis Groupe & MSL Group, No. 11 Civ. 1279 (ALC) (AJP) (S.D.N.Y. Feb. 24, 2012), Magistrate Judge Andrew J. Peck of the U.S. District Court for the Southern District of New York issued an opinion making it likely the first case to accept the use of computer-assisted review of electronically stored information (“ESI”) for this case.  However, on March 13, District Court Judge Andrew L. Carter, Jr. granted plaintiffs’ request to submit additional briefing on their February 22 objections to the ruling.  In that briefing (filed on March 26), the plaintiffs claimed that the protocol approved for predictive coding “risks failing to capture a staggering 65% of the relevant documents in this case” and questioned Judge Peck’s relationship with defense counsel and with the selected vendor for the case, Recommind.

Then, on April 5, Judge Peck issued an order in response to Plaintiffs’ letter requesting his recusal, directing plaintiffs to indicate whether they would file a formal motion for recusal or ask the Court to consider the letter as the motion.  On April 13, (Friday the 13th, that is), the plaintiffs did just that, by formally requesting the recusal of Judge Peck (the defendants issued a response in opposition on April 30).  But, on April 25, Judge Carter issued an opinion and order in the case, upholding Judge Peck’s opinion approving computer-assisted review.

Not done, the plaintiffs filed an objection on May 9 to Judge Peck's rejection of their request to stay discovery pending the resolution of outstanding motions and objections (including the recusal motion, which has yet to be ruled on.  Then, last Monday, Judge Peck issued a stay, stopping defendant MSLGroup's production of electronically stored information.

More News

And, there’s even more news.  As Sean Doherty of Law Technology News reports, last Monday, Judge Peck denied an amicus curiae (i.e., friend-of-the-court) brief filed in support of the plaintiffs' motion for recusal.  For more on the filing and Judge Peck’s denial of the motion, click here.

Summary of Filings

Rob Robinson of ComplexD has provided a thorough summary of filings in a single PDF file.  He provides a listing of the filings, a Scribd plug-in viewer of the file – all 1,320 pages(!), so be patient as the page takes a little time to load – and a link to download the PDF file.  The ability to search through the entire case of filings for key issues and terms is well worth it.  Thanks, Rob!

Da Silva Moore and the Role of ACEDS

Also, Sharon Nelson of the Ride The Lightning blog (and a previous thought leader interviewee on this blog) has provided a very detailed blog post regarding the in depth investigation that the Association of Certified E-Discovery Specialists® (ACEDS™) has conducted on the case, including requesting financial disclosures for Judge Peck for 2008, 2009, 2010 and 2011 (for items including for “honoraria” and “teaching fees.”).  She wonders why “a certification body would want to be so heavily involved in an investigation of a judge in a very controversial case” and offers some possible thoughts as to why.  A very interesting read!

So, what do you think?  Are you “maxed out” on Da Silva Moore coverage yet?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Case Law: Judge Peck Stays Defendant’s Production in Da Silva Moore
 

Yesterday, we discussed the latest event in the eDiscovery case of the year – the defendant’s response opposing the plaintiff’s motion for recusal.  I thought today we would discuss the plaintiffs’ latest objection – to United States District Court Magistrate Judge Andrew J. Peck's rejection of their request to stay discovery pending the resolution of outstanding motions and objections.  However, news in this case happens quickly.

In a short, one-page order on Monday, Judge Peck issued a stay, stopping defendant MSLGroup's production of electronically stored information in Da Silva Moore v. Publicis Groupe & MSL Group, (Case No. 11-CV-1279).

Here is the content of the order:

“On reconsideration, for the reasons stated at today's conference (see transcript), the Court has granted plaintiffs' request to stay MSL's production of ESI, pending Judge Carter's decision on plaintiffs' motions for collective action certification and to amend their complaint.  Defendants have consented to the stay. Jurisdictional discovery regarding Publicis, and discovery between plaintiff and MSL unrelated to MSL's ESI production, are not stayed.

Plaintiffs' May 9, 2012 objections to my prior denial of the stay (Dkt. No. 190) are moot.”

That’s it – short and sweet (to the plaintiffs, at least).

This came after the plaintiffs filed an objection last Wednesday (May 9) to Judge Peck's rejection of their request to stay discovery pending the resolution of outstanding motions and objections. Those motions include a ruling on the plaintiffs' objections to Judge Peck's dismissal of the plaintiffs' issues associated with discovery with predictive coding, the plaintiffs' motion for Peck to recuse himself from the case and motions for conditional certification of collective action and for leave to file a second amended complaint.

For a brief recap and links to prior events in this highly contentious case, yesterday’s blog post provides background since Judge Peck’s order approving computer-assisted review.

More to come, I’m sure.

So, what do you think?  Will computer-assisted review be derailed in this case after all?  Was Judge Peck right to stay production?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Case Law: Defendant Responds to Plaintiffs’ Motion for Recusal in Da Silva Moore
 

Geez, you take a week or so to cover some different topics and a few things happen in the most talked about eDiscovery case of the year.  Time to catch up!  Today, we’ll talk about the response of the defendant MSLGroup Americas to the plaintiffs’ motion for recusal in the Da Silva Moore case.  Tomorrow, we will discuss the plaintiffs’ latest objection – to Magistrate Judge Andrew J. Peck's rejection of their request to stay discovery pending the resolution of outstanding motions and objections.  But, first, a quick recap.

Several weeks ago, in Da Silva Moore v. Publicis Groupe & MSL Group, No. 11 Civ. 1279 (ALC) (AJP) (S.D.N.Y. Feb. 24, 2012), Judge Peck of the U.S. District Court for the Southern District of New York issued an opinion making it likely the first case to accept the use of computer-assisted review of electronically stored information (“ESI”) for this case.  However, on March 13, District Court Judge Andrew L. Carter, Jr. granted plaintiffs’ request to submit additional briefing on their February 22 objections to the ruling.  In that briefing (filed on March 26), the plaintiffs claimed that the protocol approved for predictive coding “risks failing to capture a staggering 65% of the relevant documents in this case” and questioned Judge Peck’s relationship with defense counsel and with the selected vendor for the case, Recommind.

Then, on April 5, Judge Peck issued an order in response to Plaintiffs’ letter requesting his recusal, directing plaintiffs to indicate whether they would file a formal motion for recusal or ask the Court to consider the letter as the motion.  On April 13, (Friday the 13th, that is), the plaintiffs did just that, by formally requesting the recusal of Judge Peck.  But, on April 25, Judge Carter issued an opinion and order in the case, upholding Judge Peck’s opinion approving computer-assisted review.

As for the motion for recusal, that’s still pending.  On Monday, April 30, the defendant filed a response (not surprisingly) opposing the motion for recusal.  In its Memorandum of Law in Opposition to Plaintiffs’ Motion for Recusal or Disqualification, the defendants noted the following:

  • Plaintiffs Agreed to the Use of Predictive Coding: Among the arguments here, the defendants noted that, after prior discussions regarding predictive coding, on January 3, the “[p]laintiffs submitted to the Court their proposed version of the ESI Protocol, which relied on the use of predictive coding. Similarly, during the January 4, 2012 conference itself, Plaintiffs, through their e-discovery vendor, DOAR, confirmed not only that Plaintiffs had agreed to the use of predictive coding, but also that Plaintiffs agreed with some of the details of the search methodology, including the “confidence levels” proposed by MSL.”
  • It Was Well Known that Judge Peck Was a Leader In eDiscovery Before The Case Was Assigned to Him: The defendants referenced, among other things, that Judge Peck’s October 2011 article, Search, Forward discussed “computer-assisted coding,” and that Judge Peck stated in the article: “Until there is a judicial decision approving (or even critiquing) the use of predictive coding, counsel will just have to rely on this article as a sign of judicial approval.”
  • Ralph Losey Had No Ex Parte Contact with Judge Peck: The defendants noted that their expert, Ralph Losey, “has never discussed this case with Judge Peck” and that his “mere appearance” at seminars and conferences “does not warrant disqualification of all judges who also appear.”

As a result, the defendants argued that the court should deny plaintiffs motion for recusal because:

  • Judge Peck’s “Well-Known Expertise in and Ongoing Discourse on the Topic of Predictive Coding Are Not Grounds for His Disqualification”;
  • His “Professional Relationship with Ralph Losey Does Not Mandate Disqualification”;
  • His “Comments, Both In and Out of the Courtroom, Do Not Warrant Recusal”; and
  • His “Citation to Articles in his February 24, 2012 Opinion Was Proper”.

For details on these arguments, click the link to the Memorandum above.  Judge Carter has yet to rule on the motion for recusal.

So, what do you think?  Did the defendants make an effective argument or should Judge Peck be recused?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.