Close
Enter your
text here

Analysis

Brad Jenkins of CloudNine Discovery – eDiscovery Trends

This is the first of the 2014 LegalTech New York (LTNY) Thought Leader Interview series.  eDiscoveryDaily interviewed several thought leaders after LTNY this year (don’t get us started) and generally asked each of them the following questions:

  1. What significant eDiscovery trends do you see for 2014?
  2. With new amendments to discovery provisions of the Federal Rules of Civil Procedure now in the comment phase, do you see those being approved this year and what do you see as the impact of those Rules changes?
  3. It seems despite numerous resources in the industry, most attorneys still don’t know a lot about eDiscovery?  Do you agree with that and, if so, what do you think can be done to improve the situation?
  4. What are you working on that you’d like our readers to know about?

Today’s thought leader is Brad Jenkins of CloudNine Discovery.  Brad has over 20 years of experience as an entrepreneur, as well as 15 years leading customer focused companies in the litigation support arena. Brad also writes the Litigation Support Industry Blog, which covers news about litigation support and eDiscovery companies’ funding activities, acquisitions & mergers and notable business successes. He has authored several articles on document management and litigation support issues, and has appeared as a speaker before national audiences on document management practices and solutions.  He’s also my boss!

What significant eDiscovery trends do you see for 2014?

Well, I think that technology assisted review tools will continue to gain traction and the software will continue to make the review process more intuitive.  I think predictive coding software is evolving to provide real-time predicted relevance scores for the collection as each document is reviewed.  One of our partners, Hot Neuron, announced last month that Version 4.0 of their Clustify software, is the first technology-assisted review tool to offer real-time predictive coding.  I also think that the technology associated with predictive coding will be used more in other areas of the eDiscovery life cycle, particularly Information Governance.

Another trend, one that I discussed last year, is integration of “best of breed” cloud-based applications to make the discovery process more seamless. Our alliance with BIA and the integration of their TotalDiscovery legal hold and collection tool to our review application, OnDemand®, has continued to be used by our clients to support preservation through production.  BIA has tremendous expertise and software to support the left side of the EDRM model and it’s a logical fit for the services and software we provide from collection to production.  Personally, I believe that the “best of breed” integrated applications approach is a preferable alternative to a complete solution because it’s difficult to be an expert in all phases of discovery.

I also think that it’s more difficult than ever for the small to medium sized firm to compete with the big firm that has most of the attention from the eDiscovery vendor market and has more resources in house to manage their discovery workload.  Most small to mid-sized firms lack the core competency, the infrastructure, the project management expertise and the overall personnel in house to provide the full range of services that large corporate clients are demanding, especially for litigation support and discovery services.  More than ever, these firms will need to leverage virtual resources to compete and provide the level of services their clients expect.

With new amendments to discovery provisions of the Federal Rules of Civil Procedure now in the comment phase, do you see those being approved this year and what do you see as the impact of those Rules changes?

I don’t really have a prediction as to whether they will be approved this year.  I know there has been controversy with some of the proposed rules changes, especially Rule 37(e), regarding the level of culpability required to justify severe sanctions for spoliation and that Judge Scheindlin and others have criticized the rule.  I wouldn’t be surprised to see some changes to that rule before adoption.  Regardless, it seems like a lot of attorneys don’t follow the rules adopted back in 2006, so the rules will only be effective if attorneys adhere to those rules and courts hold them to those standards.

It seems despite numerous resources in the industry, most attorneys still don’t know a lot about eDiscovery?  Do you agree with that and, if so, what do you think can be done to improve the situation?

Yes, I agree.  We work with a lot of firms whose attorneys lack basic eDiscovery fundamentals.  In some cases, the managing partners know that and have been asking for us to provide seminars and webinars to educate them on eDiscovery best practices.  And, we have been providing more consulting than ever to attorneys to assist them with technical language in requests for production to ensure that they receive the most useful form of production such as native files with included metadata.

As for what can be done, I think it’s imperative for each provider to provide resources to educate their clients and the legal profession as a whole.  We do that with our blog, eDiscoveryDaily.  As we approach 300,000 lifetime hits and 1,000 lifetime posts, both of which we will reach later this year, I’m proud of the knowledge base that this blog has become.  This year, we are also looking to really ramp up CLE training for attorneys that want to become more comfortable with technology.  There are numerous other great blogs and resources out there too.  I think we have to keep pushing and keep finding ways to reach attorneys and give them useful resources that can simplify the discovery process, which is what we’re all about at CloudNine.

What are you working on that you’d like our readers to know about?

In addition to our continued integration success with BIA and our partnership with Clustify, we recently released a brand new version of our review application OnDemand® , called Universal OnDemand.  We called it “Universal” because we have re-designed it to work in any browser, so clients can use it whether they prefer Internet Explorer, Firefox, Google Chrome or even Safari on a Mac.  We will be working to expand the application to support use with tablets this year and, as always, working to add features requested by our clients, who are the primary drivers of our development priorities.

We have also been working on a new advanced program that we call the Virtual BIG Firm™ program.  It’s a unique package of the full range of services that we have provided for years, along with our OnDemand review platform, for mid-sized firms that want to compete with the big firms, but don’t have the personnel, infrastructure or expertise to make it happen.  We created our Virtual BIG Firm program based on our experience working with over one hundred law firms for more than eleven years.  Our Virtual BIG Firm program appeals to firms interested in growing their practice.  These firms value continuing legal education, technology advances and they feel comfortable delegating.  It’s not for everybody, so we continue to offer our basic services and software as we always have, but for the firm that has a significant litigation workload but not the resources to fully manage it effectively, it’s a program that provides those resources at a fraction of what big firms spend on personnel & technology.

Thanks, Brad, for participating in the interview!

And to the readers, as always, 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.

If You’re Going to Attend Just One Session at LegalTech Next Week, Make it This Session – eDiscovery Best Practices

In just a few days, there will be big happenings in the New York area!  No, I’m not talking about the big game, I’m talking about the biggest legal technology event of the year, LegalTech New York (LTNY).  If you’re going to be attending the conference this year (and, if not, why not?), here is a session that is a “must attend” for anyone who wants to know leading judges’ perspectives on eDiscovery rules changes and best practices.

On Day 2 of the conference, Wednesday, February 5 at 9:00am, eDiscovery industry expert Craig Ball will lead a discussion with five renowned judges who have had significant impact on how lawyers manage legal technology.  The Day Two Keynote General Session Presentation – Judges Panel: Changing Rules and Best Practices in e-Discovery will include Craig and the following judges:

  • Honorable Lee H. Rosenthal, United States District Judge, Southern District of Texas
  • Honorable Shira A. Scheindlin, United States District Judge, Southern District of New York
  • Honorable John M. Facciola, United States Magistrate Judge, District of Columbia
  • Honorable James C. Francis, United States Magistrate Judge, Southern District of New York
  • Honorable Andrew J. Peck, United States Magistrate Judge, Southern District of New York

Most of these judges were discussed in Lisa Holton’s article (E-Discovery: A Front-Row Seat) as “trailblazing” judges in The American Lawyer (we covered it here) and we’ve covered a number of their decisions and opinions over the history of this blog.

As the summary of the session notes, when it comes to legal technology, few names are more synonymous with the industry than these panelists.  Craig will lead the discussion, as the judges share their views on today’s legal landscape with an eye towards what the future holds.  These eDiscovery pioneers will share their experiences and viewpoints to help attendees best prepare for the law and practice of tomorrow.

Craig referenced the session in his own excellent blog, Ball in Your Court, here. As Craig notes, “The judges will be discussing some of what you might expect, e.g., proposed Rules amendments, predictive coding, Rule 502 and expectations of lawyer technical competence.  We will also be exploring a few fresh issues, like the impact all those little screens are having on everyone in and out of court.”   Craig also indicated that there was “still time to add topics and questions of interest to you” – if there is a topic you would like him to cover, you can post a comment to his blog post here or email him at craig@ball.net.

Because this session is a Keynote General Session, it’s open to all attendees, so, if you’re at the show next week, this session is a must see.  Don’t miss it!

LTNY starts next Tuesday and eDiscovery Daily will be covering the show for the fourth straight year.  We will also be conducted our thought leader interview series at the show again for the fourth straight year as well!  After the show, we will publish the schedule for posting the interviews.  Stay tuned!

So, what do you think?  Are you attending LTNY this year?  Do you plan to attend this session?  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.

2013 eDiscovery Year in Review: eDiscovery Case Law, Part 2

As we noted yesterday, eDiscoveryDaily published 78 posts related to eDiscovery case decisions and activities over the past year, covering 62 unique cases!  Yesterday, we looked back at cases related to admissibility and eDiscovery cost reimbursement.  Today, let’s take a look back at cases related to production format disputes, search disputes and technology assisted review.

We grouped those cases into common subject themes and will review them over the next few posts.  Perhaps you missed some of these?  Now is your chance to catch up!

PRODUCTION FORMAT DISPUTES

Disputes regarding the form of production appear to be on the rise.  Typically, judges are instructing to provide searchable productions with metadata, but at least one judge ruled that “without Bates stamping and .tiff format, the plaintiff’s production was not reasonably usable”.  Go figure.  Here are the six cases involving production format disputes:

Court Declines to Impose Default Judgment, But Orders Searchable Production and Extends Deadlines. In Kwan Software Engineering, Inc. v. the defendant Technologies, LLC, California District Judge Susan Illston denied the plaintiff’s motion for terminating sanctions against the defendant for late, non-searchable productions, but did order the defendant to produce documents in a searchable format with metadata and extended the pretrial schedule so that the plaintiff would not be prejudiced by the late productions.

Court Denies Plaintiff’s Request for Native Production, Allows PDFs Instead. In Westdale Recap Props. v. Np/I&G Wakefield Commons, North Carolina Magistrate Judge James E. Gates upheld the plaintiff’s motion to compel the defendants to conduct supplemental searches and production, but denied the plaintiff’s motion with regard to requiring the defendant to produce ESI in native format, instead finding that “production in the form of searchable PDF’s is sufficient”.

Judge Sides with Both Parties in Form of Production Dispute. The opinion in Kwasniewski v. Sanofi-Aventis U.S. LLC suggests that producing parties can satisfy their obligation to produce documents in an organized manner by offering a table of contents, rendering text searchable, indicating which data responds to which request, and including certain metadata, such as Bates numbers.

Defendant Compelled by Court to Produce Metadata. In AtHome Care, Inc. v. The Evangelical Lutheran Good Samaritan Society, Idaho District Judge B. Lynn Winmill granted the plaintiff’s motion to compel documents, ordering the defendant to identify and produce metadata for the documents in this case.

Court Rules Production Must be TIFFs with Bates Numbers. In Branhaven, LLC v. Beeftek, Inc., Maryland Magistrate Judge Susan K. Gauvey sanctioned plaintiff’s attorneys for wrongfully certifying the completeness of their eDiscovery production and also ruled that defendants “demonstrated that without Bates stamping and .tiff format”, the plaintiff’s production “was not reasonably usable and therefore was insufficient under Rule 34”.

Waste Management Wants to Throw Away the Metadata. In the case In Re: Waste Management of Texas, Inc., a Texas appeals court refused to grant Waste Management’s petition for writ of mandamus to direct the trial court to withdraw its order to produce native, electronic format with all metadata.

SEARCH DISPUTES

Disputes regarding search terms, with regard to which terms to perform and also whether search terms should be disclosed, were also on the rise this year.  Believe it or not, one plaintiff referred to Boolean searching as “unprecedented”.  Here are the five cases we covered regarding search term disputes:

Court Orders Plaintiff to Perform Some Requested Searches Despite the Plaintiff’s Claim that they’re “Unprecedented”. In Swanson v. ALZA Corp., California Magistrate Judge Kandis A. Westmore granted in part and denied in part the defendant’s request to compel the plaintiff to apply its search terms to his ESI, ordering some of the search terms to be performed, despite the plaintiff’s assertion that the “the application of Boolean searches was unprecedented”.

Without Meet and Confer Approval of its “Triangulating” Approach to Discovery, Defendant Ordered to Supplement Production. In Banas v. Volcano Corp., California District Judge William H. Orrick determined that a defendant’s approach to discovery in which identifying the relevant documents by “triangulating” the defendant’s employees wasn’t discussed with the plaintiff beforehand in a meet and confer. Despite the fact that the court did “not find that defendant’s production technique was unreasonable”, the defendant was ordered to supplement its responses since the approach wasn’t discussed and it left out multiple deponents.

Use of Model Order Doesn’t Avoid Discovery Disputes. In MediaTek, Inc. v. Freescale Semiconductor, Inc., when the parties could not agree on search terms, California Magistrate Judge Jacqueline Scott Corley ordered one party to run test searches before lodging objections and required both parties to meet and confer before approaching the court with further discovery disputes.

If Production is Small, Does that Mean ESI is Being Withheld? In American Home Assurance Co. v. Greater Omaha Packing Co., Nebraska District Judge Lyle E. Strom ruled (among other things) that the defendants must disclose the sources it has searched (or intends to search) for electronically stored information (ESI) to the plaintiffs and, for each source, identify the search terms used.

Court Forces Defendant to Come to Terms with Plaintiff Search Request. In Robert Bosch LLC v. Snap-On, Inc., Michigan District Judge Robert H. Cleland granted the plaintiff’s motion to compel with regard to specific search terms requested for the defendant to perform. The judge denied the plaintiff’s request for sanctions to award attorneys’ fees and expenses incurred in bringing its motion to compel.

TECHNOLOGY ASSISTED REVIEW

With technology assisted review having been approved in several cases in 2012, we started to see some results of that process last year and conclusion of the plaintiff’s efforts to recuse Judge Peck in DaSilva Moore.  We also saw the approval of a multi-modal approach in one case and asked the question whether 31,000 missed relevant documents is an acceptable outcome in another.  Here are six cases related to technology assisted review from 2013:

Plaintiffs’ Supreme Effort to Recuse Judge Peck in Da Silva Moore Denied. As we discussed back in July, attorneys representing lead plaintiff Monique Da Silva Moore and five other employees filed a petition for a writ of certiorari with the US Supreme Court arguing that New York Magistrate Judge Andrew Peck, who approved an eDiscovery protocol agreed to by the parties that included predictive coding technology, should have recused himself given his previous public statements expressing strong support of predictive coding. On October 7, that petition was denied by the Supreme Court.

Judge Says “Dude, Where’s Your CAR?” Ralph Losey describes a unique case in his e-Discovery Team ® blog (Poor Plaintiff’s Counsel, Can’t Even Find a CAR, Much Less Drive One). In Northstar Marine, Inc. v. Huffman, the defendant’s motion to enforce the parties’ document production agreement was granted after Alabama Magistrate Judge William E. Cassady rejected the plaintiff’s excuse that “it is having difficulty locating an inexpensive provider of electronic search technology to assist with discovery”.

Is it OK for an eDiscovery Vendor to Work on Both Sides of a Case?  Back in June, we covered a case where the plaintiffs’ motion to compel the defendant to meet and confer to establish an agreed protocol for implementing the use of predictive coding software was dismissed (without prejudice) after the defendants stated that they were prepared to meet and confer with the plaintiffs and their non-disqualified ESI consultants regarding the defendants’ predictive coding process. The sticking point may be the ESI consultant in dispute.

Never Mind! Plaintiffs Not Required to Use Predictive Coding After All. Remember EORHB v. HOA Holdings, where, in a surprise ruling, both parties were instructed to use predictive coding by the judge? Well, the judge has changed his mind.

Plaintiffs’ Objections to Defendant’s Use of Keyword Search before Predictive Coding Rejected. In the case In Re: Biomet M2a Magnum Hip Implant Products Liability Litigation (MDL 2391), the Plaintiffs’ Steering Committee in a Multi District Litigation objected to the defendant’s use of keyword searching prior to performing predictive coding and requested that the defendant go back to its original set of 19.5 million documents and repeat the predictive coding without performing keyword searching. Indiana District Judge Robert L. Miller, Jr. denied the request.

Is 31,000 Missed Relevant Documents an Acceptable Outcome?  It might be, if the alternative is 62,000 missed relevant documents. In January, we reported on the first case for technology assisted review to be completed, Global Aerospace Inc., et al, v. Landow Aviation, L.P. dba Dulles Jet Center, et al, in which predictive coding was approved last April by Virginia State Circuit Court Judge James H. Chamblin. Now, as reported by the ABA Journal (by way of the Wall Street Journal Law Blog), we have an idea of the results from the predictive coding exercise.

Tune in Monday for more key cases of 2013!

So, what do you think?  Did you miss any of these?  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.

Six eDiscovery Predictions for 2014, Part One – eDiscovery Trends

It’s that time of year, where people make predictions for the coming year for all sorts of things, including electronic discovery trends for the coming year.  Though I have to say, I’ve seen fewer predictions this year than in past years.  Nonetheless, I feel compelled to offer some of my own predictions.  If they turn out right, you heard it here first!

Prediction 1: Predictive coding technologies will become more integrated into the discovery process, for more than just review.

Two or three years ago, predictive coding (a.k.a., technology assisted review or computer assisted review) was a promising technology that had yet to be officially accepted in the courts.  Then, in 2012, cases such as Da Silva Moore v. Publicis Groupe & MSL Group, Global Aerospace Inc., et al, v. Landow Aviation, L.P. dba Dulles Jet Center, et al and In re Actos (Pioglitazone) Products Liability Litigation, predictive coding was approved (and there was at least two other cases where it was contemplated).  So, it’s beginning to be used, though most attorneys still don’t fully understand how it works or understand that it’s not a “turn-key” software solution, it includes a managed process that uses the software.

It’s not going out on a limb to say that this year predictive coding technologies will be more widely used; however, I think those technologies will branch out beyond review to other phases of the eDiscovery life cycle, including Information Governance.  Predictive coding is not new technology, it’s basically artificial intelligence applied to the review process, so it’s logical that same technology can be applied to other areas of the discovery life cycle as well.

Prediction 2: The proposed amendments will be adopted, but it will be a struggle.

Changes to Federal Rules for eDiscovery have been drafted and have been approved for public comment.  However, several people have raised concerns about some of the new rules.  Judge Shira Scheindlin has criticized proposed Rule 37(e), intended to create a uniform national standard regarding the level of culpability required to justify severe sanctions for spoliation, for creating “perverse incentives” and encouraging “sloppy behavior.”

U.S. Sen. Christopher Coons (D-Del.), who chairs the Subcommittee on Bankruptcy and the Courts, predicted that some proposed restrictions – such as reducing the number of depositions, interrogatories and requests for admission for each case – “would do nothing about the high-stakes, highly complex or highly contentious cases in which discovery costs are a problem.”  Senator Coons and Sherrilyn Ifill, president of the NAACP Legal Defense and Educational Fund Inc., also expressed concerns that those limits would likely restrict plaintiffs in smaller cases in which discovery costs are not a problem.

Needless to say, not everybody is a fan of all of the new proposed rules, especially Rule 37(e).  But, the proposed rules have gotten this far and there are a number of lobbyists pushing for adoption.  So, I think they’ll be adopted, but not without some controversy and struggle.

Prediction 3: The eDiscovery industry will continue to consolidate and many remaining providers will need to continue to reinvent themselves.

Every year, I see several predictions that more eDiscovery vendors will fail and/or there will be more consolidation in the industry.  And, every year there is consolidation.  Here’s the latest updated list of mergers, acquisitions and investments since 2001, courtesy of Rob Robinson.  But, every year there also new players in the market, so the number of providers never seems to change dramatically.  Last year, by my count, there were 225 exhibitors at Legal Tech New York (LTNY), with many, if not most of them in the eDiscovery space.  This year, the partial list stands at 212.  Not a tremendous drop off, if any.

Nonetheless, there will be more pressure on eDiscovery providers than ever before to provide services at reasonable prices, yet turn a profit.  I’ve seen bold predictions, like this one from Albert Barsocchini at NightOwl Discovery in which he predicted the possible end of eDiscovery processing fees.  I’m not sure that I agree that they’re going away entirely, but I do see further commoditization of several eDiscovery services.  The providers that offer truly unique software offerings and/or expert services to complement any commodity-based services that they offer will be the ones best equipped to meet market demands, profitably.

On Monday, I predict I’ll have three more predictions to cover.  Hey, at least that’s one prediction that should come true!

So, what do you think?  Do you have any eDiscovery predictions for 2014?  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.

Moneycase: Should Your Law Practice Be Run Like a Baseball Team? — eDiscovery Trends

Remember the movie Moneyball (adapted from the book of the same name) about Oakland A’s general manager Billy Beane’s use of computer-generated analytics to pick his players to successfully assemble a baseball team that advanced to the baseball playoffs while spending a fraction of the budget as other teams?  Can law firms learn from that example?

According to Angela Hunt in a recent article in Law Technology News (Why Attorneys Love-Hate Data Analytics), maybe they can.  As she notes in her article, James Michalowicz, managing director of Huron Legal advises firms to use big data and performance metrics to minimize legal spending.

Like the old-time baseball experts in Moneyball that scoffed at the use of computer-analytics to pick baseball players, some attorneys question the benefits in the legal arena.  “As much as I think the use of analytics is now penetrating the sports world, I think it’s slower in the legal world,” Michalowicz told Law Technology News. Since a law firm’s value depends heavily on its legal knowledge base, installing a program that does all the heavy thinking can make attorneys feel like their hard-earned legal education is being undermined, explains Michalowicz. “There’s this emotional piece to it. Lawyers don’t want to rely on data. It’s a challenge to their pride.”

However, for large firms and corporations that deal with litigation regularly, Michalowicz recommends using strategic case analytics, a predictive technology that helps attorneys pick their battles.  As the article notes, “[b]y evaluating venue data and case histories within a jurisdiction, law firms and corporate legal departments can give unbiased advice on whether to litigate or settle.”

The past three years, at LegalTech New York (LTNY), we have conducted and published a Thought Leader Series of interviews with various thought leaders in the litigation and eDiscovery industry (here’s the link to this year’s set of interviews).  One of the interviews was with Don Philbin, President and Founder of Picture It Settled®, which is a predictive analytics tool for the settlement negotiation process.  To support this process, they collected data for about ten thousand cases – not just the outcomes, but also the incremental moves that people make in negotiation.  If Billy Beane were an attorney, he’d love it!

Over the next few weeks, we’ll look at other analytics mechanisms to improve efficiency in the litigation and discovery process.

So, what do you think?  Do you employ any data analytics in your discovery practice?   Please share any comments you might have or if you’d like to know more about a particular topic.

Image © 2011 – Sony Pictures

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.

Does Size Matter? – eDiscovery Replay

Even those of us at eDiscovery Daily have to take an occasional vacation (see above); however, instead of “going dark” for the week, we thought we would use the week to do something interesting.  Up to this week, we have had 815 posts over 3+ years of the blog.  Some have been quite popular, so we thought we would “replay” the top four all-time posts this week in terms of page views since the blog began (in case you missed them).  Casey Kasem would be proud!  Apparently, my catchy title worked as, with over 1,150 lifetime views, here is the third most viewed post all time, originally published in March 2011.  Enjoy!

______________________________

I admit it, with a title like “Does Size Matter?”, I’m looking for a few extra page views.  😉

I frequently get asked how big does an ESI collection need to be to benefit from eDiscovery technology.  In a recent case with one of my clients, the client had a fairly small collection – only about 4 GB.  But, when a judge ruled that they had to start conducting depositions in a week, they needed to review that data in a weekend.  Without the ability to cull the data and using OnDemand® to manage the linear review, they would not have been able to make that deadline.  So, they clearly benefited from the use of eDiscovery technology in that case.

But, if you’re not facing a tight deadline, how large does your collection need to be for the use of eDiscovery technology to provide benefits?

I recently conducted a webinar regarding the benefits of First Pass Review – aka Early Case Assessment, or a more accurate term (as George Socha points out regularly), Early Data Assessment.  One of the topics discussed in that webinar was the cost of review for each gigabyte (GB).  Extrapolated from an analysis conducted by Anne Kershaw a few years ago (and published in the Gartner report E-Discovery: Project Planning and Budgeting 2008-2011), here is a breakdown:

Estimated Cost to Review All Documents in a GB:

  • Pages per GB:                      75,000
  • Pages per Document:        4
  • Documents Per GB:            18,750
  • Review Rate:                        50 documents per hour
  • Total Review Hours:            375
  • Reviewer Billing Rate:        $50 per hour

Total Cost to Review Each GB:      $18,750

Notes: The number of pages per GB can vary widely.  Page per GB estimates tend to range from 50,000 to 100,000 pages per GB, so 75,000 pages (18,750 documents) seems an appropriate average.  50 documents reviewed per hour is considered to be a fast review rate and $50 per hour is considered to be a bargain price.  eDiscovery Daily provided an earlier estimate of $16,650 per GB based on assumptions of 20,000 documents per GB and 60 documents reviewed per hour – the assumptions may change somewhat, but, either way, the cost for attorney review of each GB could be expected to range from at least $16,000 to $18,000, possibly more.

Advanced culling and searching can enable you to cull out 70-80% of most collections as clearly non-responsive without having to conduct attorney review on those files.  If you have merely a 2 GB collection and assume the lowest review cost above of $16,000 per GB, the use of advanced culling and searching to cull out 70% of the collection can save $22,400 in attorney review costs.  Is that worth it?

So, what do you think?  Do you use eDiscovery technology for only the really large cases or ALL cases?   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.

The Number of Pages in Each Gigabyte Can Vary Widely – eDiscovery Replay

Even those of us at eDiscovery Daily have to take an occasional vacation (see above); however, instead of “going dark” for the week, we thought we would use the week to do something interesting.  Up to this week, we have had 815 posts over 3+ years of the blog.  Some have been quite popular, so we thought we would “replay” the top four all-time posts this week in terms of page views since the blog began (in case you missed them).  Casey Kasem would be proud!  With nearly 1,000 lifetime views, here is the fourth most viewed post all time, originally published in July 2012.  Enjoy!

_________________________

A while back, we talked about how the average number of pages in each gigabyte is approximately 50,000 to 75,000 pages and that each gigabyte effectively culled out can save $18,750 in review costs.  But, did you know just how widely the number of pages per gigabyte can vary?

The “how many pages” question comes up a lot and I’ve seen a variety of answers.  Michael Recker of Applied Discovery posted an article to their blog last week titled Just How Big Is a Gigabyte?, which provides some perspective based on the types of files contained within the gigabyte, as follows:

“For example, e-mail files typically average 100,099 pages per gigabyte, while Microsoft Word files typically average 64,782 pages per gigabyte. Text files, on average, consist of a whopping 677,963 pages per gigabyte. At the opposite end of the spectrum, the average gigabyte of images contains 15,477 pages; the average gigabyte of PowerPoint slides typically includes 17,552 pages.”

Of course, each GB of data is rarely just one type of file.  Many emails include attachments, which can be in any of a number of different file formats.  Collections of files from hard drives may include Word, Excel, PowerPoint, Adobe PDF and other file formats.  So, estimating page counts with any degree of precision is somewhat difficult.

In fact, the same exact content ported into different applications can be a different size in each file, due to the overhead required by each application.  To illustrate this, I decided to conduct a little (admittedly unscientific) study using yesterday’s one page blog post about the Apple/Samsung litigation.  I decided to put the content from that page into several different file formats to illustrate how much the size can vary, even when the content is essentially the same.  Here are the results:

  • Text File Format (TXT): Created by performing a “Save As” on the web page for the blog post to text – 10 KB;
  • HyperText Markup Language (HTML): Created by performing a “Save As” on the web page for the blog post to HTML – 36 KB, over 3.5 times larger than the text file;
  • Microsoft Excel 2010 Format (XLSX): Created by copying the contents of the blog post and pasting it into a blank Excel workbook – 128 KB, nearly 13 times larger than the text file;
  • Microsoft Word 2010 Format (DOCX): Created by copying the contents of the blog post and pasting it into a blank Word document – 162 KB, over 16 times larger than the text file;
  • Adobe PDF Format (PDF): Created by printing the blog post to PDF file using the CutePDF printer driver – 211 KB, over 21 times larger than the text file;
  • Microsoft Outlook 2010 Message Format (MSG): Created by copying the contents of the blog post and pasting it into a blank Outlook message, then sending that message to myself, then saving the message out to my hard drive – 221 KB, over 22 times larger than the text file.

The Outlook example was probably the least representative of a typical email – most emails don’t have several embedded graphics in them (with the exception of signature logos) – and most are typically much shorter than yesterday’s blog post (which also included the side text on the page as I copied that too).  Still, the example hopefully illustrates that a “page”, even with the same exact content, will be different sizes in different applications.  As a result, to estimate the number of pages in a collection with any degree of accuracy, it’s not only important to understand the size of the data collection, but also the makeup of the collection as well.

So, what do you think?  Was this example useful or highly flawed?  Or both?  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.

Plaintiffs’ Supreme Effort to Recuse Judge Peck in Da Silva Moore Denied – eDiscovery Case Law

As we discussed back in July, attorneys representing lead plaintiff Monique Da Silva Moore and five other employees filed a petition for a writ of certiorari with the US Supreme Court arguing that New York Magistrate Judge Andrew Peck, who approved an eDiscovery protocol agreed to by the parties that included predictive coding technology, should have recused himself given his previous public statements expressing strong support of predictive coding.  Earlier this month, on October 7, that petition was denied by the Supreme Court.

Da Silva Moore and her co-plaintiffs had argued in the petition that the Second Circuit Court of Appeals was too deferential to Peck when denying the plaintiff’s petition to recuse him, asking the Supreme Court to order the Second Circuit to use the less deferential “de novo” standard.

The plaintiffs have now been denied in their recusal efforts in four courts.  Here is the link to the Supreme Court docket item, referencing denial of the petition.

This battle over predictive coding and Judge Peck’s participation has continued for over 18 months.  For those who may have not been following the case or may be new to the blog, here’s a recap.

Last year, back in February, Judge Peck issued an opinion making this case 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 the 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, 2012, 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, on May 14, Judge Peck issued a stay, stopping defendant MSLGroup’s production of electronically stored information.  On June 15, in a 56 page opinion and order, Judge Peck denied the plaintiffs’ motion for recusal.  Judge Carter ruled on the plaintiff’s recusal request on November 7 of last year, denying the request and stating that “Judge Peck’s decision accepting computer-assisted review … was not influenced by bias, nor did it create any appearance of bias”.

The plaintiffs then filed a petition for a writ of mandamus with the Second Circuit of the US Court of Appeals, which was denied this past April, leading to their petition for a writ of certiorari with the US Supreme Court, which has now also been denied.

So, what do you think?  Will we finally move on to the merits of the case?  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.

For Successful Discovery, Think Backwards – eDiscovery Best Practices

The Electronic Discovery Reference Model (EDRM) has become the standard model for the workflow of the process for handling electronically stored information (ESI) in discovery.  But, to succeed in discovery, regardless whether you’re the producing party or the receiving party, it might be helpful to think about the EDRM model backwards.

Why think backwards?

You can’t have a successful outcome without envisioning the successful outcome that you want to achieve.  The end of the discovery process includes the production and presentation stages, so it’s important to determine what you want to get out of those stages.  Let’s look at them.

Presentation

As a receiving party, it’s important to think about what types of evidence you need to support your case when presenting at depositions and at trial – this is the type of information that needs to be included in your production requests at the beginning of the case.

Production

The format of the ESI produced is important to both sides in the case.  For the receiving party, it’s important to get as much useful information included in the production as possible.  This includes metadata and searchable text for the produced documents, typically with an index or load file to facilitate loading into a review application.  The most useful form of production is native format files with all metadata preserved as used in the normal course of business.

For the producing party, it’s important to save costs, so it’s important to agree to a production format that minimizes production costs.  Converting files to an image based format (such as TIFF) adds costs, so producing in native format can be cost effective for the producing party as well.  It’s also important to determine how to handle issues such as privilege logs and redaction of privileged or confidential information.

Addressing production format issues up front will maximize cost savings and enable each party to get what they want out of the production of ESI.

Processing-Review-Analysis

It also pays to determine early in the process about decisions that affect processing, review and analysis.  How should exception files be handled?  What do you do about files that are infected with malware?  These are examples of issues that need to be decided up front to determine how processing will be handled.

As for review, the review tool being used may impact production specs in terms of how files are viewed and production of load files that are compatible with the review tool, among other considerations.  As for analysis, surely you test search terms to determine their effectiveness before you agree on those terms with opposing counsel, right?

Preservation-Collection-Identification

Long before you have to conduct preservation and collection for a case, you need to establish procedures for implementing and monitoring litigation holds, as well as prepare a data map to identify where corporate information is stored for identification, preservation and collection purposes.

As you can see, at the beginning of a case (and even before), it’s important to think backwards within the EDRM model to ensure a successful discovery process.  Decisions made at the beginning of the case affect the success of those latter stages, so don’t forget to think backwards!

So, what do you think?  What do you do at the beginning of a case to ensure success at the end?   Please share any comments you might have or if you’d like to know more about a particular topic.

P.S. — Notice anything different about the EDRM graphic?

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 Daily is Three Years Old!

We’ve always been free, now we are three!

It’s hard to believe that it has been three years ago today since we launched the eDiscoveryDaily blog.  We’re past the “terrible twos” and heading towards pre-school.  Before you know it, we’ll be ready to take our driver’s test!

We have seen traffic on our site (from our first three months of existence to our most recent three months) grow an amazing 575%!  Our subscriber base has grown over 50% in the last year alone!  Back in June, we hit over 200,000 visits on the site and now we have over 236,000!

We continue to appreciate the interest you’ve shown in the topics and will do our best to continue to provide interesting and useful posts about eDiscovery trends, best practices and case law.  That’s what this blog is all about.  And, in each post, we like to ask for you to “please share any comments you might have or if you’d like to know more about a particular topic”, so we encourage you to do so to make this blog even more useful.

We also want to thank the blogs and publications that have linked to our posts and raised our public awareness, including Pinhawk, Ride the Lightning, Litigation Support Guru, Complex Discovery, Bryan College, The Electronic Discovery Reading Room, Litigation Support Today, Alltop, ABA Journal, Litigation Support Blog.com, Litigation Support Technology & News, InfoGovernance Engagement Area, EDD Blog Online, eDiscovery Journal, Learn About E-Discovery, e-Discovery Team ® and any other publication that has picked up at least one of our posts for reference (sorry if I missed any!).  We really appreciate it!

As many of you know by now, we like to take a look back every six months at some of the important stories and topics during that time.  So, here are some posts over the last six months you may have missed.  Enjoy!

Rodney Dangerfield might put it this way – “I Tell Ya, Information Governance Gets No Respect”

Is it Time to Ditch the Per Hour Model for Document Review?  Here’s some food for thought.

Is it Possible for a File to be Modified Before it is Created?  Maybe, but here are some mechanisms for avoiding that scenario (here, here, here, here, here and here).  Best of all, they’re free.

Did you know changes to the Federal eDiscovery Rules are coming?  Here’s some more information.

Count Minnesota and Kansas among the states that are also making changes to support eDiscovery.

By the way, since the Electronic Discovery Reference Model (EDRM) annual meeting back in May, several EDRM projects (Metrics, Jobs, Data Set and the new Native Files project) have already announced new deliverables and/or requested feedback.

When it comes to electronically stored information (ESI), ensuring proper chain of custody tracking is an important part of handling that ESI through the eDiscovery process.

Do you self-collect?  Don’t Forget to Check for Image Only Files!

The Files are Already Electronic, How Hard Can They Be to Load?  A sound process makes it easier.

When you remove a virus from your collection, does it violate your discovery agreement?

Do you think that you’ve read everything there is to read on Technology Assisted Review?  If you missed anything, it’s probably here.

Consider using a “SWOT” analysis or Decision Tree for better eDiscovery planning.

If you’re an eDiscovery professional, here is what you need to know about litigation.

BTW, eDiscovery Daily has had 242 posts related to eDiscovery Case Law since the blog began!  Forty-four of them have been in the last six months.

Our battle cry for next September?  “Four more years!”  🙂

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.