Collection

10 Tips for LegalTech Vendors – eDiscovery Best Practices

We’ve mentioned Ralph Losey from Jackson Lewis several times on this blog, including last year’s thought leader interview at LegalTech New York and our interview with him again this year, which will be published on March 1.  We’re discussing another interesting article from Losey, but this time it’s Adam Losey.  His article 10 Tips for LegalTech Vendors, that appeared in Law Technology News has some interesting tips that all vendors (especially those exhibiting at trade shows) should bear in mind.  Here are his tips, along with some of my comments:

  1. Hand over the mouse. As Losey notes, “If you get time in front of potential clients to demonstrate a product, give them the mouse. Let attendees try your tools, with you serving as their guide.”  That sounds great in theory.  It has been my experience, however, that most attendees that stop by and request a demo are reluctant to “drive” right there at the show (believe me, I’ve offered).  Giving them the ability to “test drive” the product for free in their offices after the show tends to get a better response, in my experience.
  2. Add value. Losey advocates more “than just delivering high-quality work product and hyper-responsive client service”.  There are plenty of ways to do this.  For example, helping a client out by directing them to the right vendor that provides a service that you don’t can be just as helpful as the services that you provide for them.
  3. Be humble and keep innovating.  Especially in the ever-changing eDiscovery industry, it’s important to continue to adapt.  That doesn’t just mean offering the latest “buzzword” technology, it also means providing a mechanism for clients to request features and enhancements and addressing those within rollout updates.
  4. Don’t bad-mouth the competition.  Needless to say, you should never do that.  If a client or prospect asks you to compare your solution to another, it’s always best to point out what your solution does well, or what it offers that is unique, not what (you think) the competition does poorly.
  5. Share. In essence, Losey reiterates that here: “Show me why you are the best, not why everyone else is the worst.”  This enables eDiscovery practitioners to draw their own conclusions and share their knowledge with colleagues, which carries more weight than if it came from the vendor, who has a vested interest.
  6. Stop pushing unnecessary services.  Doing so may net a little more business in the short run, but can cost long-term business when the client becomes more educated and realizes that those costs are unnecessary and dumps you.  It’s better to be flexible enough to provide just the services the client needs – they will appreciate it and want to do business with you again.
  7. Leave the legal work to the lawyers.  The vendor’s responsibility is to provide the attorney information regarding the handling of ESI necessary to make an informed decision, not to make that decision for the attorney.
  8. Reach out to new lawyers.  Great point!  As Losey notes, new lawyers are the ones handling eDiscovery at most firms, so reaching out to them as law students is a great way to establish a foothold.
  9. Let me export a privilege log with a click.  I would extend this to production logs, exception logs, etc.  It should be a no-brainer to select the documents you want, the fields you want on the report, click a button and export to Excel.
  10. Let me kick the tires on a case for free.  Clients always understand an application better when working with their own data, as opposed to a demo database.  That’s why (shameless plug warning!) CloudNine offers a 100% No-Risk Trial Offer on OnDemand®, so that our clients can try it with their own data (even as much as 100 GB or more), at no risk.  What better way to get them to try your product?

So, what do you think?  How do your vendors stack up?  Please share any comments you might have or if you’d like to know more about a particular topic.

P.S. — Happy 84th Birthday, Dad!

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.

Brad Jenkins of CloudNine Discovery – eDiscovery Trends

This is the first of the 2013 LegalTech New York (LTNY) Thought Leader Interview series.  eDiscoveryDaily interviewed several thought leaders at LTNY this year and generally asked each of them the following questions:

  1. What are your general observations about LTNY this year and how it fits into emerging trends?
  2. If last year’s “next big thing” was the emergence of predictive coding, what do you feel is this year’s “next big thing”?
  3. 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 14 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 e-discovery companies’ funding activities, acquisitions & mergers and notable business successes. He has authored many 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 are your general observations about LTNY this year and how it fits into emerging trends?

Well, clearly the technology assisted review/predictive coding wave is the most popular topic here at the show.  I think I counted at least six sessions discussing the topic and numerous vendors touting their tools.  And, this blog covered it and the cases using quite a bit last year.  I’m sure you’ll hear that from a lot of the folks you’re interviewing.

Another trend that I’m seeing is integration of applications to make the discovery process more seamless, especially the integration of cloud-based collection and review applications.  We have an alliance with BIA and their TotalDiscovery legal hold and collection tool, which can export data into our review application, OnDemand®, which our clients are using quite successfully to collect data and move it along the process.  I think the “best of breed” approach between an application that’s focused on the left side of the EDRM model and one that’s focused on the right side is an approach that makes sense for a lot of organizations.

If last year’s “next big thing” was the emergence of predictive coding, what do you feel is this year’s “next big thing”?

I’m not sure that I see just one thing as the “next big thing”.  I certainly see the continued focus on integration of applications as one big thing.  Another big thing that I see is a broadening acceptance of technology assisted review from more than just predictive coding.  For example, clustering similar documents together can make review more efficient and more accurate and we provide that in OnDemand through our partnership with Hot Neuron’s Clustify™.

Perhaps the biggest thing that I see is education and adoption of the technology.  Many lawyers still don’t actively use the technology and don’t find the applications intuitive.  We’ve worked hard to make OnDemand easy to use, requiring minimal or no training.  A lot of vendors tout their products as easy to use, but we’re backing our claim with our free no risk trial of OnDemand that includes free data assessment, free native processing, free data load and free first month hosting for the first data set on any new OnDemand project.  We feel that we have a team of “Aces” and a hand full of aces is almost impossible to beat.  So, the free no risk trial reflects our confidence that clients that try OnDemand will embrace its ease-of-use and self-service features and continue to use it and us for their discovery needs.

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

In addition to our integration success with BIA, our partnership with Clustify and our free no risk trial, we’re also previewing the initial release of the mobile version of OnDemand.  The first mobile version will be designed for project administrators to add users and maintain user rights, as well as obtain key statistics about their projects.  It’s our first step toward our 2013 goal of making OnDemand completely platform independent and we are targeting a third quarter release of a new redesigned version of OnDemand that will support that goal.

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.

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

As we noted the past two days, eDiscoveryDaily published 98 posts related to eDiscovery case decisions and activities over the past year, covering 62 unique cases!  Yesterday, we looked back at cases related to social media and the first cases approving technology assisted review.  Today, let’s take a look back at cases related to admissibility and the duty to preserve and produce electronically stored information (ESI).

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!

ADMISSIBILITY AND DUTY TO PRESERVE AND PRODUCE

Admissibility of ESI, and the duty to preserve and produce it, is more at issue than ever.  Whether the issue is whether certain emails should be considered privileged, whether cloning of computer files is acceptable or whether text messages require substantiation of authorship, parties are disputing what ESI should actually be admissible in litigation.  Parties are also disputing when and where litigation holds are required and whether collection and search practices are acceptable.  In short, there are numerous disputes about data being produced and not being produced.  Here are (a whopping) sixteen cases related to admissibility and the duty to preserve and produce ESI:

Emails Between Husband and Wife Are Not Privileged, If Sent from Work Computer.  In United States v. Hamilton, the Fourth Circuit found that the district court had not abused its discretion in finding that e-mails between the defendant and his wife did not merit marital privilege protection because the defendant had used his office computer and his work e-mail account to send and receive the communications and because he had not taken steps to protect the e-mails in question, even after his employer instituted a policy permitting inspection of e-mails and he was on notice of the policy.

Defendant Had Duty to Preserve Despite No Physical Possession of Documents.  In Haskins v. First American Title Insurance Co., a court found that an insurance company had a duty to issue a litigation hold to its independent title agents because litigation was reasonably foreseeable and the duty to preserve extends to third parties, as long as the documents are “within a party’s possession, custody, or control.” Although it did not have physical possession, the insurance company controlled the agents’ documents because it had “‘the legal right or ability to obtain the documents from [the agents] upon demand.’”

Defendant Compelled to Produce Additional Discovery to Plaintiff.  In Freeman v. Dal-Tile Corp., a case alleging harassment and discrimination, among other claims, against her former employer Dal-Tile Corporation, the plaintiff brought a motion to compel, asserting that some of the defendant’s discovery responses related to its search for ESI were deficient.

Defendant Claiming Not Reasonably Accessible Data Has Some ‘Splaining To Do.  In Murray v. Coleman, the plaintiff alleged harassment and retaliation in connection with his employment with the New York State Department of Correctional Services (DOCS). This discovery dispute arose when the plaintiff requested access to certain electronic records, alleging that the defendants withheld them.

Cloning of Computer Files: When There’s a Will, There’s a Way.  In Matter of Tilimbo, a court held it was permissible to order cloning of computer files where doing so did not place an unreasonable burden on a nonparty, appropriate steps were taken to protect any privileged information, and the nonparty had not previously produced the requested information in hard copy.

Citing Rule 26(g), Court Orders Plaintiff’s Counsel to Disclose Search Strategy.  Our 501st post on the blog addresses S2 Automation LLC v. Micron Technology, where New Mexico District Judge James Browning ordered the plaintiff’s attorneys to disclose the search strategy their client used to identify responsive documents, based on Federal Rule 26(g) that requires attorneys to sign discovery responses and certify that they are “complete and correct.”

Judge Scheindlin Says “No” to Self-Collection, “Yes” to Predictive Coding.  When most people think of the horrors of Friday the 13th, they think of Jason Voorhees. When US Immigration and Customs thinks of Friday the 13th horrors, do they think of Judge Shira Scheindlin?  New York District Judge Scheindlin issued a decision on Friday, July 13, addressing the adequacy of searching and self-collection by government entity custodians in response to Freedom of Information Act (FOIA) requests.

Plaintiff Compelled to Produce Mirror Image of Drives Despite Defendant’s Initial Failure to Request Metadata.  In Commercial Law Corp., P.C. v. FDIC, Michigan District Judge Sean F. Cox ruled that a party can be compelled to produce a mirror image of its computer drives using a neutral third-party expert where metadata is relevant and the circumstances dictate it, even though the requesting party initially failed to request that metadata and specify the format of documents in its first discovery request.

Court Allows Third Party Discovery Because Defendant is an “Unreliable Source”.  Repeatedly referring to the defendant’s unreliability and untrustworthiness in discovery and “desire to suppress the truth,” Nebraska Magistrate Judge Cheryl R. Zwart found, in Peter Kiewit Sons’, Inc. v. Wall Street Equity Group, Inc., that the defendant avoided responding substantively to the plaintiff’s discovery requests through a pattern of destruction and misrepresentation and therefore monetary sanctions and an adverse jury instruction at trial were appropriate.

Inadmissibility of Text Messages Being Appealed.  In October 2011, we covered a caseCommonwealth v. Koch – where a Pennsylvania Superior Court ruled text messages inadmissible, declaring that parties seeking to introduce electronic materials, such as cell phone text messages and email, must be prepared to substantiate their claim of authorship with “circumstantial evidence” that corroborates the sender’s identity. That case, where Amy N. Koch was originally convicted at trial on drug charges (partially due to text messages found on her cell phone), is now being appealed to the state Supreme Court.

Another Case with Inadmissible Text Messages.  Above, we discussed a case where a Pennsylvania Superior Court ruled text messages inadmissible, declaring that parties seeking to introduce electronic materials, such as cell phone text messages and email, must be prepared to substantiate their claim of authorship with “circumstantial evidence” that corroborates the sender’s identity. That case is now being appealed to the state Supreme Court. Today, we have another case – Rodriguez v. Nevada – where text messages were ruled inadmissible.

Court Grants Plaintiff’s Motion to Compel Mirror-Imaging of Defendant’s Computers.  In approving a motion for expedited discovery in United Factory Furniture Corp. v. Alterwitz, Magistrate Judge Cam Ferenbach granted the plaintiff’s motion for a mirror-imaging order after determining the benefit outweighed the burden of the discovery, and it denied as unnecessary the plaintiff’s motion for an order to preserve evidence and a preliminary injunction from spoliation of evidence.

Court Orders eDiscovery Evidentiary Hearing When Parties Are Unable to Cooperate.  A month ago, in Chura v. Delmar Gardens of Lenexa, Inc., Magistrate Judge David J. Waxse ordered an evidentiary hearing to discuss the sufficiency of the defendant’s search for ESI and format of production in response to the plaintiff’s motion to compel additional searching and production.

At The Eleventh Hour, Encrypted Hard Drive Is Decrypted.  In our previous post regarding the case U.S. v. Fricosu, Colorado district judge Robert Blackburn ruled that Ramona Fricosu must produce an unencrypted version of her Toshiba laptop’s hard drive to prosecutors in a mortgage fraud case for police inspection. Naturally, the defendant appealed. On February 21st, the 10th U.S. Circuit Court of Appeals refused to get involved, saying Ramona Fricosu’s case must first be resolved in District Court before her attorney can appeal. She would have been required to turn over the unencrypted contents of the drive as of March 1. However, at the last minute, Colorado federal authorities decrypted the laptop.

Court Rules Exact Search Terms Are Limited.  In Custom Hardware Eng’g & Consulting v. Dowell, the plaintiff and defendant could not agree on search terms to be used for discovery on defendant’s forensically imaged computers. After reviewing proposed search terms from both sides, and the defendant’s objections to the plaintiff’s proposed list, the court ruled that the defendant’s proposed list was “problematic and inappropriate” and that their objections to the plaintiff’s proposed terms were “without merit” and ruled for use of the plaintiff’s search terms in discovery.

KPMG Loses Another Round to Pippins.  As discussed previously in eDiscovery Daily, KPMG sought a protective order in Pippins v. KPMG LLP to require the preservation of only a random sample of 100 hard drives from among those it had already preserved for this and other litigation or shift the cost of any preservation beyond that requested scope. Lawyers for Pippins won a ruling last November by Magistrate Judge James Cott to use all available drives and Judge Cott encouraged the parties to continue to meet and confer to reach agreement on sampling. However, the parties were unable to agree and KPMG appealed to the District Court. In February, District Court Judge Colleen McMahon upheld the lower court ruling.

Tune in tomorrow for more key cases of 2012 and, once again, the most common theme of the year!

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.

Percentage of eDiscovery Sanctions Cases Declining – eDiscovery Trends

According to Kroll Ontrack, the percentage of eDiscovery cases addressing sanctions “dropped by approximately ten percent” compared to 2011, while “cases addressing procedural issues more than doubled”.  Let’s take a closer look at the numbers and look at some cases in each category.

As indicated in their December 4 news release, in the past year, Kroll Ontrack experts summarized 70 of the most significant state and federal judicial opinions related to the preservation, collection, review and production of electronically stored information (ESI). The breakdown of the major issues that arose in these eDiscovery cases is as follows:

  • Thirty-two percent (32%) of cases addressed sanctions regarding a variety of issues, such as preservation and spoliation, noncompliance with court orders and production disputes.  Out of 70 cases, that would be about 22 cases addressing sanctions this past year.  Here are a few of the recent sanction cases previously reported on this blog.
  • Twenty-nine percent (29%) of cases addressed procedural issues, such as search protocols, cooperation, production and privilege considerations.  Out of 70 cases, that would be about 20 cases.  Here are a few of the recent procedural issues cases previously reported on this blog.
  • Sixteen percent (16%) of cases addressed discoverability and admissibility issues.  Out of 70 cases, that would be about 11 cases.  Here are a few of the recent discoverability / admissibility cases previously reported on this blog.
  • Fourteen percent (14%) of cases discussed cost considerations, such as shifting or taxation of eDiscovery costs.  Out of 70 cases, that would be about 10 cases.  Here are a few of the recent eDiscovery costs cases previously reported on this blog.
  • Nine percent (9%) of cases discussed technology-assisted review (TAR) or predictive coding.  Out of 70 cases, that would be about 6 cases.  Here are a few of the recent TAR cases previously reported on this blog, how many did you get?

While it’s nice and appreciated that Kroll Ontrack has been summarizing the cases and compiling these statistics, I do have a couple of observations/questions about their numbers (sorry if they appear “nit-picky”):

  • Sometimes Cases Belong in More Than One Category: The case percentage totals add up to 100%, which would make sense except that some cases address issues in more than one category.  For example, In re Actos (Pioglitazone) Products Liability Litigation addressed both cooperation and technology-assisted review, and Freeman v. Dal-Tile Corp. addressed both search protocols and discovery / admissibility.  It appears that Kroll classified each case in only one group, which makes the numbers add up, but could be somewhat misleading.  In theory, some cases belong in multiple categories, so the total should exceed 100%.
  • Did Cases Addressing Procedural Issues Really Double?: Kroll reported that “cases addressing procedural issues more than doubled”; however, here is how they broke down the category last year: 14% of cases addressed various procedural issues such as searching protocol and cooperation, 13% of cases addressed various production considerations, and 12% of cases addressed privilege considerations and waivers.  That’s a total of 39% for three separate categories that now appear to be described as “procedural issues, such as search protocols, cooperation, production and privilege considerations” (29%).  So, it looks to me like the percentage of cases addressing procedural issues actually dropped 10%.  Actually, the two biggest category jumps appear to be discoverability and admissibility issues (2% last year to 16% this year) and TAR (0% last year to 9% this year).

So, what do you think?  Has your organization been involved in any eDiscovery opinions this year?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

Louisiana Order Dictates That the Parties Cooperate on Technology Assisted Review – eDiscovery Case Law

During this Thanksgiving week, we at eDiscovery Daily thought it would be a good time to catch up on some cases we missed earlier in the year.  So, we will cover a different case each day this week.  Enjoy!

In the case In re Actos (Pioglitazone) Products Liability Litigation, No. 6:11-md-2299, (W.D. La. July 27, 2012), a case management order applicable to pretrial proceedings in a multidistrict litigation consolidating eleven civil actions, the court issued comprehensive instructions for the use of technology-assisted review (“TAR”).

In an order entitled “Procedures and Protocols Governing the Production of Electronically Stored Information (“ESI”) by the Parties,” U.S. District Judge Rebecca Doherty of the Western District of Louisiana set forth how the parties would treat data sources, custodians, costs, and format of production, among others. Importantly, the order contains a “Search Methodology Proof of Concept,” which governs the parties’ usage of TAR during the search and review of ESI.

The order states that the parties “agree to meet and confer regarding the use of advanced analytics” as a “document identification mechanism for the review and production of . . . data.” The parties will meet and confer to select four key custodians whose e-mail will be used to create an initial sample set, after which three experts will train the TAR system to score every document based on relevance. To quell the fears of TAR skeptics, the court provided that both parties will collaborate to train the system, and after the TAR process is completed, the documents will not only be randomly sampled for quality control, but the defendants may also manually review documents for relevance, confidentiality, and privilege.

The governance order repeatedly emphasizes that the parties are committing to collaborating throughout the TAR process and requires that they meet and confer prior to contacting the court for a resolution.

So, what do you think?  Should more cases issue instructions like this?  Please share any comments you might have or if you’d like to know more about a particular topic.

Case Summary Source: Applied Discovery (free subscription required).  For eDiscovery news and best practices, check out the Applied Discovery Blog here.

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 Best Practices: Quality Control, Making Sure the Numbers Add Up

 

Yesterday, we wrote about tracking file counts from collection to production, the concept of expanded file counts, and the categorization of files during processing.  Today, let’s walk through a scenario to show how the files collected are accounted for during the discovery process.

Tracking the Counts after Processing

We discussed the typical categories of excluded files after processing – obviously, what’s not excluded is available for searching and review.  Even if your approach includes a technology assisted review (TAR) methodology such as predictive coding, it’s still likely that you will want to do some culling out of files that are clearly non-responsive.

Documents during review may be classified in a number of ways, but the most common ways to classify documents as to whether they are responsive, non-responsive, or privileged.  Privileged documents are also typically classified as responsive or non-responsive, so that only the responsive documents that are privileged need be identified on a privilege log.  Responsive documents that are not privileged are then produced to opposing counsel.

Example of File Count Tracking

So, now that we’ve discussed the various categories for tracking files from collection to production, let’s walk through a fairly simple eMail based example.  We conduct a fairly targeted collection of a PST file from each of seven custodians in a given case.  The relevant time period for the case is January 1, 2010 through December 31, 2011.  Other than date range, we plan to do no other filtering of files during processing.  Duplicates will not be reviewed or produced.  We’re going to provide an exception log to opposing counsel for any file that cannot be processed and a privilege log for any responsive files that are privileged.  Here’s what this collection might look like:

  • Collected Files: 101,852 – After expansion, 7 PST files expand to 101,852 eMails and attachments.
  • Filtered Files: 23,564 – Filtering eMails outside of the relevant date range eliminates 23,564 files.
  • Remaining Files after Filtering: 78,288 – After filtering, there are 78,288 files to be processed.
  • NIST/System Files: 0 – eMail collections typically don’t have NIST or system files, so we’ll assume zero files here.  Collections with loose electronic documents from hard drives typically contain some NIST and system files.
  • Exception Files: 912 – Let’s assume that a little over 1% of the collection (912) is exception files like password protected, corrupted or empty files.
  • Duplicate Files: 24,215 – It’s fairly common for approximately 30% of the collection to include duplicates, so we’ll assume 24,215 files here.
  • Remaining Files after Processing: 53,161 – We have 53,161 files left after subtracting NIST/System, Exception and Duplicate files from the total files after filtering.
  • Files Culled During Searching: 35,618 – If we assume that we are able to cull out 67% (approximately 2/3 of the collection) as clearly non-responsive, we are able to cull out 35,618 files.
  • Remaining Files for Review: 17,543 – After culling, we have 17,543 files that will actually require review (whether manual or via a TAR approach).
  • Files Tagged as Non-Responsive: 7,017 – If approximately 40% of the document collection is tagged as non-responsive, that would be 7,017 files tagged as such.
  • Remaining Files Tagged as Responsive: 10,526 – After QC to ensure that all documents are either tagged as responsive or non-responsive, this leaves 10,526 documents as responsive.
  • Responsive Files Tagged as Privileged: 842 – If roughly 8% of the responsive documents are privileged, that would be 842 privileged documents.
  • Produced Files: 9,684 – After subtracting the privileged files, we’re left with 9,684 responsive, non-privileged files to be produced to opposing counsel.

The percentages I used for estimating the counts at each stage are just examples, so don’t get too hung up on them.  The key is to note the numbers in red above.  Excluding the interim counts in black, the counts in red represent the different categories for the file collection – each file should wind up in one of these totals.  What happens if you add the counts in red together?  You should get 101,852 – the number of collected files after expanding the PST files.  As a result, every one of the collected files is accounted for and none “slips through the cracks” during discovery.  That’s the way it should be.  If not, investigation is required to determine where files were missed.

So, what do you think?  Do you have a plan for accounting for all collected files during discovery?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

eDiscovery Best Practices: Quality Control, It’s a Numbers Game

 

Previously, we wrote about Quality Assurance (QA) and Quality Control (QC) in the eDiscovery process.  Both are important in improving the quality of work product and making the eDiscovery process more defensible overall.  For example, in attorney review, QA mechanisms include validation rules to ensure that entries are recorded correctly while QC mechanisms include a second review (usually by a review supervisor or senior attorney) to ensure that documents are being categorized correctly.  Another overall QC mechanism is tracking of document counts through the discovery process, especially from collection to production, to identify how every collected file was handled and why each non-produced document was not produced.

Expanded File Counts

Scanned counts of files collected are not the same as expanded file counts.  There are certain container file types, like Outlook PST files and ZIP archives that exist essentially to store a collection of other files.  So, the count that is important to track is the “expanded” file count after processing, which includes all of the files contained within the container files.  So, in a simple scenario where you collect Outlook PST files from seven custodians, the actual number of documents (emails and attachments) within those PST files could be in the tens of thousands.  That’s the starting count that matters if your goal is to account for every document in the discovery process.

Categorization of Files During Processing

Of course, not every document gets reviewed or even included in the search process.  During processing, files are usually categorized, with some categories of files usually being set aside and excluded from review.  Here are some typical categories of excluded files in most collections:

  • Filtered Files: Some files may be collected, and then filtered during processing.  A common filter for the file collection is the relevant date range of the case.  If you’re collecting custodians’ source PST files, those may include messages outside the relevant date range; if so, those messages may need to be filtered out of the review set.  Files may also be filtered based on type of file or other reasons for exclusion.
  • NIST and System Files: Many file collections also contain system files, like executable files (EXEs) or Dynamic Link Library (DLLs) that are part of the software on a computer which do not contain client data, so those are typically excluded from the review set.  NIST files are included on the National Institute of Standards and Technology list of files that are known to have no evidentiary value, so any files in the collection matching those on the list are “De-NISTed”.
  • Exception Files: These are files that cannot be processed or indexed, for whatever reason.  For example, they may be password-protected or corrupted.  Just because these files cannot be processed doesn’t mean they can be ignored, depending on your agreement with opposing counsel, you may need to at least provide a list of them on an exception log to prove they were addressed, if not attempt to repair them or make them accessible (BTW, it’s good to establish that agreement for disposition of exception files up front).
  • Duplicate Files: During processing, files that are exact duplicates may be put aside to avoid redundant review (and potential inconsistencies).  Some exact duplicates are typically identified based on the HASH value, which is a digital fingerprint generated based on the content and format of the file – if two files have the same HASH value, they have the same exact content and format.  Emails (and their attachments) may be identified as duplicates based on key metadata fields, so an attachment cannot be “de-duped” out of the collection by a standalone copy of the same file.

All of these categories of excluded files can reduce the set of files to actually be searched and reviewed.  Tomorrow, we’ll illustrate an example of a file set from collection to production to illustrate how each file is accounted for during the discovery process.

So, what do you think?  Do you have a plan for accounting for all collected files during discovery?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

eDiscovery Trends: iDiscovery

 

Yesterday was a day that tech enthusiasts and ordinary people alike had circled on their calendar since it was confirmed as the date of Apple’s press event to unveil the iPhone5. Apple proudly boasted that it had sold 400 million iOS devices by the end of June of this year, which can in part be attributed to the smoothly operating software running on their devices. Advances in mobile high tech have made these portable computers accessible and their presence inescapable even among late adopters. What is simple and intuitive from a user standpoint, however, can prove challenging and fickle to a computer forensics expert.

Richard Lutkus of Law Technology News writes that there are many factors that must be considered when investigating an iOS device, such as “device model, generation, storage capacity, iOS version, iCloud activation status, and passcode protection status. One example of the importance of these identification questions is iCloud, which is Apple's information syncing service. The presence and status of this service may be important because information found on an iOS device could be automatically synced to one or several computers or other iOS devices.”

Lutkus points out that mobile device forensics requires skills that not all computer forensic professionals possess. For example, an important part of the preservation of a mobile device is isolation from all data networks to ensure no changes occur on the device, such as a remote wipe.  A few ways of isolating the hardware include a signal blocking “Faraday” bag, removing the SIM card, or enabling airplane mode. From there, the two methods of imaging an iOS device are logical capture and physical imaging. Lutkus explains, “Logical capture is the preservation of all active (no file fragments or other ephemera) files on a device. This method is similar to an iTunes backup in that it saves the same types of data as iTunes backups. In contrast, physical imaging captures everything that a logical capture does, but includes deleted file fragments, temporary cache files, and other ephemera. Generally, physical imaging is more desirable if it is technically possible. Though slower, this approach is widely accepted, is compatible with most forensic tools, and preserves all data on a device.”

There are other challenges in preserving the data in an iOS device, especially hardware newer than the iPhone 4S and Ipad 3, which include encryption of even unallocated space of memory when a passcode has been used. The quality of data one might expect to find after imaging and decrypting could include: “contacts, call logs, speed dials, voicemail, Bluetooth devices, screenshots, bookmarks, web clips, calendars, messages, email, attachments, internet history, internet cookies, photos, audio recordings, notes, videos, music, app list, keystroke information, GPS coordinates, wi-fi network memberships, user names and passwords, map searches, app-specific data, cell tower information, serial number, device name, device IMEI (international mobile equipment identify number), device serial number, version, and generation, etc.” This type of information can be crucial in the first 7 to 10 days after litigation hits, as we have previously covered here. These devices seem to know so much about us that companies like Apple have had to release statements to state they are not recording and storing your location in response to allegations of privacy invasion. With the number of expected sales of the iPhone5 potentially adding between a quarter and a half percent to America’s GDP, there will be millions more iPhone’s will making their ways into the hands of consumers and eventually, no doubt, into the hands of mobile forensic experts.

So, what do you think? Have mobile computing devices, such as smartphones and tablets, been material to your eDiscovery work? Have other mobile operating systems, such as Blackberry or Android, presented challenges that differ from iOS? 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 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.