Close
Enter your
text here

Project Management

Four More Tips to Quash the Cost of eDiscovery – eDiscovery Best Practices

Thursday, we covered the first four tips from Craig Ball’s informative post on his blog (Ball in your Court) entitled Eight Tips to Quash the Cost of E-Discovery with tips on saving eDiscovery costs.  Today, we’ll discuss the last four tips.

5. Test your Methods and Know your ESI: Craig says that “Staggering sums are spent in e-discovery to collect and review data that would never have been collected if only someone had run a small scale test before deploying an enterprise search”.  Knowing your ESI will, as Craig notes, “narrow the scope of collection and review with consequent cost savings”.  In one of the posts on our very first day of the blog, I relayed an actual example from a client regarding a search that included a wildcard of “min*” to retrieve variations like “mine”, “mines” and “mining”.  Because there are 269 words in the English language that begin with “min”, that overly broad search retrieved over 300,000 files with hits in an enterprise-wide search.  Unfortunately, the client had already agreed to the search term before finding that out, which resulted in considerable negotiation (and embarrassment) to get the other side to agree to modify the term.  That’s why it’s always a good idea to test your searches before the meet and confer.  The better you know your ESI, the more you save.

6. Use Good Tools: Craig provides another great analogy in observing that “If you needed to dig a big hole, you wouldn’t use a teaspoon, nor would you hire a hundred people with teaspoons.  You’d use the right power tool and a skilled operator.”  Collection and review tools must fit your requirements and workflow, so, guess what?  You need to understand those requirements and your workflow to pick the right tool.  If you’re putting together a wooden table, you don’t have to learn how to operate a blowtorch if all you need is a hammer and some nails, or a screwdriver and some screws for the job.  The better that the tools fit your workflow, the more you save.

7. Communicate and Cooperate: Craig says that “Much of the waste in e-discovery grows out of apprehension and uncertainty.  Litigants often over-collect and over-review, preferring to spend more than necessary instead of giving the transparency needed to secure a crucial concession on scope or methodology”.  A big part of communication and cooperation, at least in Federal cases, is the Rule 26(f) conference (which is also known as the “meet and confer”, here are two posts on the subject).  The more straightforward you make discovery through communication and cooperation, the more you save.

8. Price is What the Seller Accepts: Craig notes that there is much “pliant pricing” for eDiscovery tools and services and relayed an example where a vendor initially quoted $43.5 million to complete a large expedited project, only to drop that quote all the way down to $3.5 million after some haggling.  Yes, it’s important to shop around.  It’s also important to be able to know the costs going in, through predictable pricing.  If you have 10 gigabytes or 1 terabyte of data, providers should be able to tell you exactly what it will cost to collect, process, load and host that data.  And, it’s always good if the provider will let you try their tools for free, on your actual data, so you know whether those tools are worth the price.  The more predictable price and value of the tools and services are, the more you save.

So, what do you think?  What are you doing to keep eDiscovery costs down?  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.

Eight Tips to Quash the Cost of eDiscovery – eDiscovery Best Practices

By now, Craig Ball needs no introduction our readers as he has been a thought leader interview participant for the past three years.  Two years ago, we published his interview in a single post, his interview last year was split into a two part series and this year’s interview was split into a three part series.  Perhaps next year, I will be lucky enough to interview him for an hour and we can simply have a five-part “Ball Week” (like the Discovery Channel has “Shark Week”).  Hmmm…

Regardless, I’m a regular reader of his blog, Ball in your Court, as well, and, last week, he published a very informative post entitled Eight Tips to Quash the Cost of E-Discovery with tips on saving eDiscovery costs.  I thought we would cover those tips here, with some commentary:

  1. Eliminate Waste: Craig notes that “irrational fears [that] flow from lack of familiarity with systems, tools and techniques that achieve better outcomes at lower cost” results in waste.  Over-preservation and over-collection of ESI, conversion of ESI, failing to deduplicate and reviewing unnecessary files all drive the cost up.  Last September, we ran a post regarding quality control and making sure the numbers add up when you subtract filtered, NIST/system, exception, duplicate and culled (during searching) files from the collected total.  In that somewhat hypothetical example based on Enron data sets, after removing those files, only 17% of the collected files were actually reviewed (which, in many cases, would still be too high a percentage).  The less number of files that require attorney “eyes on”, the more you save.
  2. Reduce Redundancy and Fragmentation: While, according to the Compliance, Governance and Oversight Council (CGOC), information volume in most organizations doubles every 18-24 months, Craig points out that “human beings don’t create that much more unique information; they mostly make more copies of the same information and break it into smaller pieces.”  Insanity is doing the same thing over and over and expecting different results and insane review is reviewing the same documents over and over and (potentially) getting different results, which is not only inefficient, but could lead to inconsistencies and even inadvertent disclosures.  Most collections not only contain exact duplicates in the exact format (which can identified through hash-based deduplication), but also “near” duplicates that include the same content in different file formats (and at different sizes) or portions of the content in eMail threads.  The less duplicative content that requires review, the more you save.
  3. Don’t Convert ESI: In addition to noting the pitfalls of converting ESI to page-like image formats like TIFF, Craig also wrote a post about it, entitled Are They Trying to Screw Me? (discussed in this blog here).  ‘Nuff said.  The less ESI you convert, the more you save.
  4. Review Rationally: Craig discussed a couple of irrational approaches to review, including reviewing attachments without hits when the eMail has been determined to be non-responsive and the tendency to “treat information in any form from any source as requiring privilege review when even a dollop of thought would make clear that not all forms or sources of ESI are created equal when it comes to their potential to hold privileged content”.  For the latter, he advocates using technology to “isolate privileged content” as well as clawback agreements and Federal Rule of Evidence 502 for protection against inadvertent disclosure.  It’s also important to be able to adjust during the review process if certain groups of documents are identified as needing to be excluded or handled differently, such as the “All Rights Reserved” documents that I previously referenced in the “oil” AND “rights” search example.  The more intelligent the review process, the more you save.

There is too much to say about these eight tips to limit to one blog post, so on Monday (after the Good Friday holiday) we’ll cover tips 5 through 8.  The waiting is the hardest part.

So, what do you think?  What are you doing to keep eDiscovery costs down?  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.

Five Common Myths About Predictive Coding – eDiscovery Best Practices

During my interviews with various thought leaders (a list of which can be found here, with links to each interview), we discussed various aspects of predictive coding and some of the perceived myths that exist regarding predictive coding and what it means to the review process.  I thought it would be a good idea to recap some of those myths and how they compare to the “reality” (at least as some of us see it).  Or maybe just me.  🙂

1.     Predictive Coding is New Technology

Actually, with all due respect to each of the various vendors that have their own custom algorithm for predictive coding, the technology for predictive coding as a whole is not new technology.  Ever heard of artificial intelligence?  Predictive coding, in fact, applies artificial intelligence to the review process.  With all of the acronyms we use to describe predictive coding, here’s one more for consideration: “Artificial Intelligence for Review” or “AIR”.  May not catch on, but I like it.

Maybe attorneys would be more receptive to it if they understood as artificial intelligence?  As Laura Zubulake pointed out in my interview with her, “For years, algorithms have been used in government, law enforcement, and Wall Street.  It is not a new concept.”  With that in mind, Ralph Losey predicts that “The future is artificial intelligence leveraging your human intelligence and teaching a computer what you know about a particular case and then letting the computer do what it does best – which is read at 1 million miles per hour and be totally consistent.”

2.     Predictive Coding is Just Technology

Treating predictive coding as just the algorithm that “reviews” the documents is shortsighted.  Predictive coding is a process that includes the algorithm.  Without a sound approach for identifying appropriate example documents for the collection, ensuring educated and knowledgeable reviewers to appropriately code those documents and testing and evaluating the results to confirm success, the algorithm alone would simply be another case of “garbage in, garbage out” and doomed to fail.

As discussed by both George Socha and Tom Gelbmann during their interviews with this blog, EDRM’s Search project has published the Computer Assisted Review Reference Model (CARRM), which has taken steps to define that sound approach.  Nigel Murray also noted that “The people who really understand computer assisted review understand that it requires a process.”  So, it’s more than just the technology.

3.     Predictive Coding and Keyword Searching are Mutually Exclusive

I’ve talked to some people that think that predictive coding and key word searching are mutually exclusive, i.e., that you wouldn’t perform key word searching on a case where you plan to use predictive coding.  Not necessarily.  Ralph Losey advocates a “multimodal” approach, noting it as: “more than one kind of search – using predictive coding, but also using keyword search, concept search, similarity search, all kinds of other methods that we have developed over the years to help train the machine.  The main goal is to train the machine.”

4.     Predictive Coding Eliminates Manual Review

Many people think of predictive coding as the death of manual review, with all attorney reviewers being replaced by machines.  Actually, manual review is a part of the predictive coding process in several aspects, including: 1) Subject matter knowledgeable reviewers are necessary to perform review to create a training set of documents for the technology, 2) After the process is performed, both sets (the included and excluded documents) are sampled and the samples are reviewed to determine the effectiveness of the process, and 3) The resulting responsive set is generally reviewed to confirm responsiveness and also to determine whether the documents are privileged.  Without manual review to train the technology and verify the results, the process would fail.

5.     Predictive Coding Has to Be Perfect to Be Useful

Detractors of predictive coding note that predictive coding can miss plenty of responsive documents and is nowhere near 100% accurate.  In one recent case, the producing party estimated as many as 31,000 relevant documents may have been missed by the predictive coding process.  However, they also estimated that a much more costly manual review would have missed as many as 62,000 relevant documents.

Craig Ball’s analogy about the two hikers that encounter the angry grizzly bear is appropriate – the one hiker doesn’t have to outrun the bear, just the other hiker.  Craig notes: “That is how I look at technology assisted review.  It does not have to be vastly superior to human review; it only has to outrun human review.  It just has to be as good or better while being faster and cheaper.”

So, what do you think?  Do you agree that these are myths?  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.

2012 eDiscovery Year in Review: eDiscovery Case Law, Part 1

2012 was quite a year from an eDiscovery standpoint, with a number of cases that impacted how organizations handle discovery.  There were case decisions that broke new ground (such as technology assisted review) and other cases that showed that many organizations still have a lot to learn in terms of inadvertent disclosures of privileged documents and sanctions assessed due to spoliation.

As we did last year, it seems appropriate to review cases from 2012 before moving forward to this year.  eDiscoveryDaily published 98 posts related to eDiscovery case decisions and activities over the past year, covering 62 unique cases!  And, believe it or not, we still didn’t cover every case that had eDiscovery impact.  Sometimes, you want to cover other topics too.

Nonetheless, for the cases we did cover, we grouped them into common subject themes and will review them over the next few posts (a few of them could be categorized in more than one category, so we took our best shot).  Perhaps you missed some of these?  Now is your chance to catch up!

PROPORTIONALITY / COOPERATION

There were certainly at least a handful of cases where proportionality of eDiscovery and cooperation between parties was at issue.  Here are three such cases:

Plaintiffs Should Pay for Extensive Discovery Prior to Class Certification.  In Boeynaems v. LA Fitness International, LLC, Pennsylvania District Judge Michael Baylson held that “where (1) class certification is pending and (2) the plaintiffs have asked for very extensive discovery, compliance with which will be very extensive, that absent compelling equitable circumstances to the contrary, the plaintiffs should pay for the discovery they seek . . . . Where the burden of discovery expense is almost entirely on the defendant, principally because the plaintiffs seek class certification, then the plaintiffs should share the costs.”

There’s a New Sheriff in Town – Judge Facciola.  In Taydon v. Greyhound Lines, Inc., District of Columbia Magistrate Judge John Facciola laid down the law to the parties in the case requiring cooperation on eDiscovery issues after “[t]he filing of forty-page discovery motions accompanied by thousands of pages of exhibits” and made it clear that the parties would be expected to “meet and confer in person in a genuine, good faith effort to plan the rest of discovery”.

Tennessee Court Orders Split eDiscovery Costs, Plaintiff Bond for Additional Discovery.  In considering the allocation of costs in this contentious business dispute, Tennessee Magistrate Judge Joe B. Brown (not to be confused with TV’s Judge Joe Brown) ordered the parties to split the expenses related to material they had not already produced in Lubber Inc. v. Optari, LLC.

PRIVILEGE / INADVERTENT DISCLOSURES

There were a few cases related to privilege issues, with parties failing the five factor test and paying the price for inadvertent disclosures of privileged documents (even when disclosing two privileged pages out of two million pages produced!).  Here are five cases where disclosure of privileged documents was addressed:

Another Disclosure of Privileged Documents Fails the Five Factor Test.  In Inhalation Plastics, Inc. v. Medex Cardio-Pulmonary, Inc., Ohio Magistrate Judge Norah McCann King found that the defendant had waived the attorney-client privilege was waived for 347 emails inadvertently produced, because they failed all factors in the five factor test to determine whether the inadvertent disclosure entitles the producing party to the return of the documents in question.

Counsel, The Inadvertent Disclosure “Buck” Stops With You.  In Blythe v. Bell, North Carolina Business Superior Court Judge James L. Gale denied a motion for an order compelling the return of privileged documents inadvertently disclosed by the defendants, ruling that privilege had been waived on those documents.

Privilege Waived Because Defendants Failed to Notice “Something Had Gone Awry” with Their Production.  In D’Onofrio v. Borough of Seaside Park, New Jersey Magistrate Judge Tonianne Bongiovanni denied the defendants’ motion for discovery to reclaim privileged documents that were inadvertently produced, finding that privilege was waived because the defendants failed to take reasonable measures to rectify the disclosure.

Inadvertent Disclosure By Expert Waives Privilege.  In Ceglia v. Zuckerberg (the case where Paul Ceglia is suing claiming 84% ownership of Facebook due to an alleged agreement he had with Mark Zuckerberg back in 2003), New York Magistrate Judge Leslie G. Foschio ruled that an information technology expert’s inadvertent disclosure waived the attorney-client privilege where the plaintiff could not show that it (1) took reasonable steps to prevent the disclosure of the e-mail and (2) took reasonable steps to rectify the error once it discovered the disclosure.

Two Pages Inadvertently Disclosed Out of Two Million May Still Waive Privilege.  In Jacob v. Duane Reade, Inc., Magistrate Judge Theodore Katz of the US District Court for the Southern District of New York found that a privileged, two-page email that was inadvertently produced did not have to be returned and that the privilege had been waived because the producing party, Duane Reade, had failed to request its return in a timely manner. According to Defendants’ counsel, the ESI production involved the review of over two million documents in less than a month; that review was accomplished with the assistance of an outside vendor and document review team.

EDISCOVERY COST REIMBURSEMENT

In 2011, there were several cases where the prevailing party was awarded reimbursement of eDiscovery costs.  Last year, that trend reversed somewhat as there were some cases where requests for reimbursement of eDiscovery costs was denied (or only partially granted).  Here are five cases, some of which fall into each category:

Court Reduces, But Allows, Reimbursement of eDiscovery Costs.  In Moore v. The Weinstein Company LLC, noting it had wide discretion to determine costs recoverable by a prevailing party under federal statutes providing for the taxation of costs, a court reduced costs awarded for eDiscovery expenditures based on its analysis of which costs were reasonable, necessary, and taxable.

Trend Has Shifted Against Reimbursement of eDiscovery Costs.  Last year, the trend seemed to be to award the prevailing party reimbursement of eDiscovery costs. Now, that trend appears to have been reversed with those requests being denied (or reversed) by the courts. Now, here is another case where reimbursement of eDiscovery costs was denied.

Google Awarded $1 Million from Oracle, But Denied Discovery Costs.  Judge William Alsup ordered Oracle to pay Google $1 million as reimbursement for Google’s fees for a court-appointed expert in their court battle over intellectual property and Google’s Android software. However, the ruling is only a partial victory for Google, who was seeking $4 million from Oracle in reimbursement of costs associated with the case.

No Race Tires on This Vehicle, Taxation of eDiscovery Costs Granted.  Last May, in Race Tires America, Inc. v. Hoosier Racing Tire Corporation, the winning defendants were awarded $367,000 as reimbursement for eDiscovery costs. (Hoosier Daddy!) But, then in March, an appellate court reversed all but $30,370 of those costs, implementing a narrow interpretation of 28 U.S.C. § 1920(4) for assigning those costs. Now, a new case addresses the issue of taxation of costs once again.

Not So Fast On eDiscovery Cost Reimbursement.  Today, we look at another eDiscovery ruling where a significant reduction in award amount was ruled.

We’re just getting started!  Tomorrow, we will cover cases related to social media and technology assisted review.  Stay tuned!

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.

More Self-Documentation Features for Review Solutions – eDiscovery Best Practices

As we discussed yesterday, one feature of review solutions that often gets overlooked is the ability for the review solution to automatically document searching and review activities.  Not only does that make it easier to identify potential issues in the process; it also facilitates the ability for attorneys to demonstrate a defensible approach to discovery to the court.

Yesterday, we discussed self-documentation with regard to keeping a search history to support easy “tweaking” of searches and document the natural iterative process of searching, facilitating the ability for attorneys to demonstrate a defensible search approach to discovery to the court. Let’s discuss two other areas where self-documentation can assist in the discovery analysis and review process:

Review Set Assignment and Tracking: When a review effort requires multiple reviewers to meet the review and production deadline, assigning documents to each reviewer and tracking each reviewer’s progress to estimate completion is critical and can be extremely time consuming to perform manually (especially for large scale review projects involving dozens or even hundreds of reviewers).  A review application, such as OnDemand®, that automates the assignment of documents to the reviewers and automatically tracks their review activity and throughput eliminates that manual time, enabling the review supervisor to provide feedback to the reviewers for improved review results as well as reassign documents as needed to maximize reviewer productivity.

Track Tag and Edit Activity: Review projects involving multiple attorneys and reviewers can be difficult to manage.  The risk of mistakes is high.  For example, privileged documents can be inadvertently tagged non-privileged and important notes or comments regarding individual documents can be inadvertently deleted.  One or more of the users in your case could be making these mistakes and not even be aware that it’s occurring.  A review application, such as OnDemand®, that tracks each tagging/un-tagging event and each edit to any field for a document can enable you to generate an audit log report to look for potential mistakes and issues.  For example, generate an audit log report showing any documents where the Privileged tag was applied and then removed.  Audit log reports are a great way to identify mistakes that have occurred, determine which user made those mistakes, and address those mistakes with them to eliminate future occurrences.  Using the self-documentation feature of an audit log report can enable you to avoid inadvertent disclosures of privileged documents and other potential eDiscovery production issues.

So, what do you think?  How important are self-documentation features in a review solution to you?  Can you think of other important self-documentation features in a review solution?  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.

When Considering Review Solutions, Don’t Forget About Self-Documentation – eDiscovery Best Practices

When evaluating eDiscovery review solutions, there are a number of features that attorneys consider as part of their selection process.  For example: What searching capabilities does the solution have?  How does it handle native files?  How does it support annotations and redactions of images?  Can it support conceptual clustering and predictive coding?  But, one feature that often gets overlooked is the ability for the review solution to automatically document searching and review activities.  Not only does that make it easier to identify potential issues in the process; it also facilitates the ability for attorneys to demonstrate a defensible approach to discovery to the court.

There are at least three areas where self-documentation can assist in the discovery analysis and review process:

Searching: An application, such as FirstPass®, powered by Venio FPR™, that keeps track of every search in a search history can provide assistance to attorneys to demonstrate a defensible search approach.  eDiscovery searching is almost always an iterative process where you perform a search, analyze the results (often through sampling of the search results, which FirstPass also supports), then adjust the search to either add, remove or modify terms to improve recall (when responsive information is being missed) or improve precision (when the terms are overly broad and yielding way too much non-responsive information, such as the “mining” example we’ve discussed previously).

Tracking search history accomplishes two things: 1) it makes it easier to recall previous searches and “tweak” them to run a modified version of the search without starting from scratch (some searches can be really complex, so this can be a tremendous time saver) and, 2) it documents the natural iterative process of searching, facilitating the ability for attorneys to demonstrate a defensible search approach to discovery to the court, if necessary.  And, if you don’t think that ever comes up, check out these case summaries here, here, here and here.   Not only that, the ability to look at previous searches can be a shorten the learning curve for new users that need to conduct searches by giving them examples after which to pattern their own searches.

Tomorrow, we’ll discuss the other two areas where self-documentation can assist in the discovery analysis and review process.  Let the anticipation build!

So, what do you think?  How important are self-documentation features in a review solution to you?  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.

New eDiscovery Guidelines for Northern District of California – eDiscovery Trends

The U.S. District Court for the Northern District of California has announced new Guidelines for counsel and litigants regarding the discovery of electronically stored information (“ESI”) effective as of last Tuesday (November 27). The Guidelines were developed by a bench-bar committee chaired by Magistrate Judge Elizabeth D. Laporte in partnership with the Court’s Rules Committee and unanimously approved by the entire Court.

As stated in the announcement: “Counsel and litigants should familiarize themselves with the Guidelines and immediately begin using the revised Standing Order for All Judges of the Northern District of California when preparing case management statements and the Checklist as appropriate when meeting and conferring.”

As noted in the announcement, in addition to the Standing Order noted above, the package of new ESI-related documents is comprised of:

In the announcement, Judge Laporte stated: “These tools are designed to promote cooperative e-discovery planning as soon as practicable that is tailored and proportionate to the needs of the particular case to achieve its just, speedy and inexpensive resolution, consistent with Rule 1 of the Federal Rules of Civil Procedure… The Court requires counsel to be familiar with these tools and confirm in the initial case management statement that they have reviewed the Guidelines regarding preservation and decided whether to enter into a stipulated order governing e-discovery, in light of the Model Stipulated Order.”

To confirm that familiarity and understanding by counsel, paragraph 6 of the Standing Order requires that all Joint Case Management Statements include:

“A brief report certifying that the parties have reviewed the Guidelines Relating to the Discovery of Electronically Stored Information (“ESI Guidelines”), and confirming that the parties have met and conferred pursuant to Fed. R. Civ. P. 26(f) regarding reasonable and proportionate steps taken to preserve evidence relevant to the issues reasonably evident in this action.”

As noted in this blog previously, other courts, such as the Southern District of New York (pilot program) and the Eastern District of Texas (for patent cases) have implemented standards for handling ESI, at least in certain situations.

So, what do you think?  Should all District courts adopt similar standards and provide similar guidelines and checklists?  If not, why not?  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.

EDBP.com, A Lawyer Centric Work Flow Model for eDiscovery – eDiscovery Best Practices

Take a closer look – that’s not the EDRM model you see above.  It’s the new EDBP model.

EDBP stands for Electronic Discovery Best Practices and is the brainchild of Ralph Losey, whose e-Discovery Team® blog is one of the must-read blogs (and one of the most in-depth) in the industry.  Ralph is also National e-Discovery Counsel with the law firm of Jackson Lewis, LLP, an Adjunct Professor at the University of Florida College of Law teaching eDiscovery and advanced eDiscovery and has also previously been a thought leader interviewee on this blog.  Other than all that, he’s not very busy.

As Ralph describes on his blog, “EDBP is a new reference of legal best practices for practicing attorneys and paralegals.  It is also an open project where other specialists in the field are invited to make contributions.”  He also notes that “The ten-step diagram…serves as the basic structure of the tasks performed by attorneys in electronic discovery practice. This structure may also change with time to keep up with evolving attorney practices.”

According to the EDBP site (ironically at EDBP.com), the stated mission is as follows:

“The purpose of EDBP is to provide a model of best practices for use by law firms and corporate law departments. EDBP is designed to be an educational resource for all lawyers striving to stay current with the latest thinking on excellence in legal services in electronic discovery law.”

Other notable aspects about EDBP:

  • It’s lawyer-centric, designed to address legal services, not the work of vendors.  As a result, it’s different in scope from EDRM, which covers non-legal service activities as well.  “The EDBP chart will focus solely on legal practice and legal services. It will be by and for lawyers only and the paralegals who assist their legal services”.
  • It does not address minimum standards for legal services, but instead “embodies an evolving understanding of excellence in legal services”.  In other words, if it were a final exam, you’re expected to ace the exam, not just get a passing grade.

The EDBP site also provides linked detailed write ups of each of the color coded sections, entitled Pre-Suit (gray), Preservation (blue), Cooperation (red), C.A.R. (green), Productions (yellow) and Evidence (turquoise?).  The sections include links to resources of information, such as The Sedona Conference® (including flowcharts) and case cites, as well as references to Federal Rules.

On his blog, Losey says “I am writing the beginning statements of best practices (about half-way through) and will serve as the first editor and gate-keeper for future contributions from others.”  The site also provides a place to provide your email address to subscribe to updates and a comments section to leave a comment for suggestions on how to improve EDBP.  It will be interesting to see how this site evolves – it promises to be an invaluable resource for eDiscovery best practices for lawyers and other legal services personnel.

So, what do you think?  Do you think EDBP will be a useful resource?  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 Daily is Two Years Old Today!
 

It’s hard to believe that it has been two years ago today since we launched the eDiscoveryDaily blog.  Now that we’ve hit the “terrible twos”, is the blog going to start going off on rants about various eDiscovery topics, like Will McAvoy in The Newsroom?   Maybe.  Or maybe not.  Wouldn’t that be fun!

As we noted when recently acknowledging our 500th post, we have seen traffic on our site (from our first three months of existence to our most recent three months) grow an amazing 442%!  Our subscriber base has nearly doubled in the last year alone!  We now have nearly seven times the visitors to the site as we did when we first started.  We continue to appreciate the interest you’ve shown in the topics and will do our best to continue to provide interesting and useful eDiscovery news and analysis.  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, The Electronic Discovery Reading Room, Unfiltered Orange, Litigation Support Blog.com, Litigation Support Technology & News, Ride the Lightning, InfoGovernance Engagement Area, Learn About E-Discovery, Alltop, Law.com, Justia Blawg Search, Atkinson-Baker (depo.com), ABA Journal, Complex Discovery, Next Generation eDiscovery Law & Tech Blog 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!

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!

We talked about best practices for issuing litigation holds and how issuing the litigation hold is just the beginning.

By the way, did you know that if you deleted a photo on Facebook three years ago, it may still be online?

We discussed states (Delaware, Pennsylvania and Florida) that have implemented new rules for eDiscovery in the past few months.

We talked about how to achieve success as a non-attorney in a law firm, providing quality eDiscovery services to your internal “clients” and how to be an eDiscovery consultant, and not just an order taker, for your clients.

We warned you that stop words can stop your searches from being effective, talked about how important it is to test your searches before the meet and confer and discussed the importance of the first 7 to 10 days once litigation hits in addressing eDiscovery issues.

We told you that, sometimes, you may need to collect from custodians that aren’t there, differentiated between quality assurance and quality control and discussed the importance of making sure that file counts add up to what was collected (with an example, no less).

By the way, did you know the number of pages in a gigabyte can vary widely and the same exact content in different file formats can vary by as much as 16 to 20 times in size?

We provided a book review on Zubulake’s e-Discovery and then interviewed the author, Laura Zubulake, as well.

BTW, eDiscovery Daily has had 150 posts related to eDiscovery Case Law since the blog began.  Fifty of them have been in the last six months.

P.S. – We still haven't missed a business day yet without a post.  Yes, we are crazy.

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 Milestones: Our 500th Post!

One thing about being a daily blog is that the posts accumulate more quickly.  As a result, I’m happy to announce that today is our 500th post on eDiscoveryDaily!  In less than two years of existence!

When we launched on September 20, 2010, our goal was to be a daily resource for eDiscovery news and analysis and we have done our best to deliver on that goal.  During that time, we have published 144 posts on eDiscovery Case Law and have identified numerous cases related to Spoliation Claims and Sanctions.   We’ve covered every phase of the EDRM life cycle, including:

We’ve discussed key industry trends in Social Media Technology and Cloud Computing.  We’ve published a number of posts on eDiscovery best practices on topics ranging from Project Management to coordinating eDiscovery within Law Firm Departments to Searching and Outsourcing.  And, a lot more.  Every post we have published is still available on the site for your reference.

Comparing our first three months of existence with our most recent three months, we have seen traffic on our site grow an amazing 442%!  Our subscriber base has nearly doubled in the last year alone!

And, we have you to thank for that!  Thanks for making the eDiscoveryDaily blog a regular resource for your eDiscovery news and analysis!  We really appreciate the support!

I also want to extend a special thanks to Jane Gennarelli, who has provided some wonderful best practice post series on a variety of topics, ranging from project management to coordinating review teams to learning how to be a true eDiscovery consultant instead of an order taker.  Her contributions are always well received and appreciated by the readers – and also especially by me, since I get a day off!

We always end each post with a request: “Please share any comments you might have or if you’d like to know more about a particular topic.”  And, we mean it.  We want to cover the topics you want to hear about, so please let us know.

Tomorrow, we’ll be back with a new, original post.  In the meantime, feel free to click on any of the links above and peruse some of our 499 previous posts.  Maybe you missed some?  😉

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.