Close
Enter your
text here

Collection

eDiscovery Trends: EDRM and Statistical Sampling
I’ve been proud to be a member of The Electronic Discovery Reference Model (EDRM) for the past six years (all but the first year) and I’m always keen to report on activities and accomplishments of the various working groups within EDRM.  Since this blog was founded, we’ve reported on 1) the unveiling of the EDRM Data Set, which has become a standard for useful eDiscovery test and demo data, 2) the EDRM Metrics Privilege Survey (which I helped draft), to collect typical volumes and percentages of privileged documents throughout the industry, 3) Model Code of Conduct which focuses on the ethical duties of eDiscovery service providers, and 4) the collaboration between EDRM and ARMA and subsequent joint Information Governance white paper.  EDRM’s latest announcement yesterday is a new guide, Statistical Sampling Applied to Electronic Discovery, which is now available for review and comment.

As EDRM notes in their announcement, “The purpose of the guide is to provide guidance regarding the use of statistical sampling in e-discovery contexts. Most of the material is definitional and conceptual, and is intended for a broad audience. The later material and the accompanying spreadsheet provide additional information, particularly technical information, to people in e-discovery roles who become responsible for developing further expertise in this area.”

The Guide is comprised of six sections, as follows:

  1. Introduction: Includes basic concepts and definitions, alludes to mathematical techniques to be discussed in more detail in subsequent sections, identifies potential eDiscovery situations where sampling techniques may be useful and identifies areas not covered in this initial guide.
  2. Estimating Proportions within a Binary Population: Provides some common sense observations as to why sampling is useful, along with a straightforward explanation of statistical terminology and the interdependence of sample size, margin of error/confidence range and confidence level.
  3. Guidelines and Considerations: Provides guidelines for effective statistical sampling, such as cull prior to sampling, account for family relationships, simple vs. stratified random sampling and use of sampling in machine learning, among others.
  4. Additional Guidance on Statistical Theory: Covers mathematical concepts such as binomial distribution, hypergeometric distribution, and normal distribution.  Bring your mental “slide-rule”!
  5. Examples Using the Accompanying Excel Spreadsheet: Describes an attached workbook (EDRM Statistics Examples 20120427.xlsm) that contains six sheets that include a notes section as well as basic, observed and population normal approximation models and basic and observed binomial methods to assist in learning these different sampling methods.
  6. Validation Study: References a Daegis article that provides an empirical study of sampling in the eDiscovery context.  In addition to that article, consider reading our previous posts on determining an appropriate sample size to test your search, how to generate a random selection and a practical example to test your search using sampling.

Comments can be posted at any of the EDRM Statistical Sampling pages, or emailed to the group at mail@edrm.net.  As a big proponent of statistical sampling as an effective and cost-effective method for verifying results, I’m very interested to see where this guide goes and how people will use it.  BTW, EDRM’s Annual Kickoff Meeting is next week (May 16 and 17) in St. Paul, MN – it’s not too late to become a member and help shape the future of eDiscovery with other industry leaders!

So, what do you think?  Do you perform statistical sampling to verify results within your eDiscovery process?  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: After Production, Your eDiscovery Obligations Are Not Necessarily Over
While a number of attorneys have yet to still embrace and fully understand eDiscovery best practices, most at least understand that there are (since 2006) Federal Rules of Civil Procedure that address discovery of electronically stored information (ESI) and (for most, but not all) similar rules at the state level.  More are learning to conduct an initial discovery conference (a.k.a., “meet and confer”) with opposing counsel to address eDiscovery requirements at the beginning of a case and more now not only understand the requirements to preserve potentially responsive data once it is clear that litigation is imminent but also how to conduct the review and production in a defensible manner.  However, as noted in this Texas Lawyer article, How to Prepare for E-Discovery Supplementation Obligations (written by Ross Cunningham and published in Law Technology News), an attorney’s eDiscovery obligations are not necessarily over after production.

As the author notes, “six months to a year into the process, most lawyers forget a key obligation. Under Texas and federal rules, all parties have an ongoing duty to supplement discovery responses.”  Failure to meet ongoing obligations to continue to preserve data and periodically update searches to retrieve new information could – like any other failure to meet obligations – result in sanctions.

The author has created a clever acronym to address a party’s supplementation obligations: PREPARE.  Here are the components of that acronym:

  • Preserve: It’s not just important to issue the hold correctly, but also to periodically follow up on hold notices to keep custodians on notice of their obligation to continue to preserve the data in question until they are instructed that they can release it (which is also very important to ensure that information no longer subject to hold doesn’t continue to be preserved outside of the organization’s document retention policies).  Sometimes, the hold may need to be expanded to additional custodians as they case continues.
  • Research: The more the attorney knows about the case and the client, the better he/she will be able to assess whether custodians are continuing to create discoverable information throughout the case and manage supplementary eDiscovery obligations accordingly.
  • Execute: As the author notes, “[t]his means drafting an e-discovery plan — and sticking to it.”  Up front planning to meet with the client to identify all sources of ESI will help ensure a complete preservation and collection process and also create a “road map” for supplemental discovery.  However, it’s also important to periodically re-assess the plan and update it where appropriate as new custodians may be identified (or even hired).
  • Proactive: Educating the client on what goes into an eDiscovery plan and best practices for conducting that plan, along with education on the consequences for failing to comply (including sanctions) will help ensure a smooth eDiscovery process.  After all, the client knows their data better than the attorney ever will.
  • Ally: By allying with trusted providers who are involved from the planning stages, that provider should be reliable to support the supplemental eDiscovery process.
  • Recalibrate: No matter how prepared you are, you cannot always anticipate every situation, so you need to be prepared to adjust (“recalibrate”) the plan when unforeseen occurrences happen.  When you have a well thought out eDiscovery plan that is executed well, courts tend to be more forgiving of anomalies.
  • Expectations: Setting expectations with opposing counsel during the initial discovery conference will help determine whether discoverable information will continue to be created over the course of discovery and hopefully obtain agreement as to how often supplemental searches will be performed.

Of course, the order of these items might not fit the actual order of execution.  Research, Execute, Proactive, Expectations, Ally, Preserve, Recalibrate might be more appropriate.  But, REPEAPR doesn’t make nearly as catchy an algorithm!

So, what do you think?  Have you dealt with supplementary eDiscovery in any of your cases?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

eDiscovery Case Law: Court Orders eDiscovery Evidentiary Hearing When Parties Are Unable to Cooperate
A month ago, in Chura v. Delmar Gardens of Lenexa, Inc., No. 11-2090-CM-DJW, 2012 U.S. Dist. LEXIS 36893 (D. Kan. Mar. 20, 2012), 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.

The case involved an employment dispute with claims of sexual harassment, hostile work environment and other employment-based causes of action.  At a status conference, the parties had agreed to create a list of search terms in an attempt to resolve outstanding eDiscovery issues. However, the parties were unable to reach a consensus, and the plaintiffs filed a motion to compel the defendant to search for and produce ESI.

The plaintiffs’ Request for Production 1 requested the defendant to produce information from 10 individuals identified by the defendants with knowledge of the facts concerning the allegations in the complaint or answer; however, the defendants’ reply merely referred the plaintiffs to the complaints and personnel files of the plaintiffs.  In their motion to compel, the plaintiffs asserted that the defendant “failed to produce their written complaints, any emails or phone logs, the investigation files, and their personnel files”.  The plaintiffs also claimed that the defendant also “failed to produce responsive documents that one would expect to find in this type of litigation”, such as:

  • “emails between Defendant’s managers and witnesses regarding Plaintiffs’ allegations or Defendant’s defenses”;
  • “notes by the human resource director from the investigation she conducted as a result of Plaintiffs’ complaints about the alleged harasser and the environment at the nursing facility where Plaintiffs worked”; and
  • “reports and emails to the corporate office regarding the complaints”.

The plaintiffs noted that, “It does not make any sense that in response to numerous complaints from employees about the work environment that a corporate human resources manager would be sent to investigate and not create a single document reporting her findings to Defendant’s corporate managers.”  They also suggested that the defendant had searched for the agreed-upon search terms in Microsoft Outlook on the alleged harasser’s computer only and argued that the defendant should run a forensically sound search of “all computers used by employees of the facility and corporate office who participated in or were involved in Defendant’s investigation of the allegations”.

While noting that it “cannot determine whether Defendant met its duty to both preserve relevant evidence” (based upon the limited information provided in the parties’ briefing), the Court found that “Defendant’s failure to produce any ESI, such as emails, attachments, exhibits, and word processing documents, raises justifiable concerns that Defendant may have 1) failed to preserve relevant evidence, or 2) failed to conduct a reasonable search for ESI responsive to Plaintiffs’ discovery requests.”  Therefore, the court set an evidentiary hearing for April 30, at which the defendant was instructed “to be prepared to present evidence on the following topics”:

  1. At the time of the initial charge of discrimination, what did Defendant’s system of creating and storing ESI consist of;
  2. When and how a litigation hold was instituted;
  3. What employees were notified of the litigation hold;
  4. What efforts were made to preserve ESI;
  5. What or whose computers or components of the computer systems were searched for responsive ESI;
  6. How the computers of computer information systems were searched (e.g., keyword searches, manual review, computer-assisted coding); and
  7. Who performed the searches.

So, what do you think?  Was the evidentiary hearing an appropriate next step?  Should more cases conduct eDiscovery evidentiary hearings when there are disputes?  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: Tips for Saving Money in Litigation
A recent article on The National Law Journal (entitled Top 12 tips for saving money in litigation, authored by Damon W.D. Wright) had some good tips for – you guessed it – saving money during litigation.  I thought it would be worth discussing some of these, especially those that relate to eDiscovery cost savings practices.
  1. Conduct targeted preservation and collection: As the author notes, the duty to preserve is “not supposed to cause business operations to grind to a halt” and “the focus should be on the specific subject matter, evidence and likely witnesses in the case”.  If you promptly investigate and quickly identify those likely custodians and act to preserve their data, you’re probably satisfying your duty to preserve.  Just don’t lose sight of organization-wide processes that affect those likely witnesses, such as automated deletion policies, and suspend them for those witnesses, at least.  Don’t make the same mistake that EchoStar did.
  2. Calibrate the budget to the amount and importance of the case:  Ralph Losey, in his interview with eDiscovery Daily, spoke about bottom line proportional review and the idea of setting a budget based on the size and potential exposure of each case.  It simply doesn’t make sense to spend the same amount of effort in routine cases as it does for the “bet your company on the outcome” cases.
  3. File in a fast-moving court: Or pursue transfer if you’re the defendant.  Certainly, the longer a case drags out, the more expensive it is, and that includes for eDiscovery.
  4. Know the court: The author addresses this from a general perspective, but it could be important from an eDiscovery perspective, as a part of that.  Enough case law related to eDiscovery exists now that many judges have started to establish at least some track record with regard to issues such as spoliation, proportionality and sharing of eDiscovery costs.  It’s important to know how your judge views those issues.
  5. Have a key client liaison: Nobody knows the client better than the client themselves, so identifying the right person to serve as a liaison between the client and counsel can not only improve communications, but also streamline process and save costs.  As the author noted, the ideal client liaison will “know the organization well and have the authority, perseverance and communication skill needed to get the attention of others.”
  6. Select vendors and experts with care: The author notes that “you should always obtain price estimates (comparing ‘apples to apples’)” when considering eDiscovery vendors.  As a part of that, it’s important to make sure those comparisons are truly “apples to apples” and comprehensive.  Are per GB processing charges for the original (compressed) GB size or expanded?  Do hosting charges include per user fees or other ancillary charges or are they strictly per GB?  It’s important to make sure those distinctions are clear when comparing.
  7. Try to get along with opposing counsel: While some are easier to get along with than others, the ability to cooperate with opposing counsel and discuss various discovery issues in the Fed.R.Civ.P. 26(f) conference (such as limits to discovery, form of production, privilege, etc.) will save considerable costs up front if the parties can agree.
  8. Allow opposing counsel to inspect and copy documents at their expense: Although most collections are predominantly in electronic form, there are still paper documents to be addressed and if you can make a non-privileged collection available for them to go through and select and copy the documents they want, that saves on your production costs.
  9. Limit e-mail production by custodians, search terms and date range: As the author noted and eDiscovery Daily previously noted, it’s not only a good idea for producing parties to limit production scope, but model orders to limit scope in patent cases are now being adopted in various jurisdictions, including Texas.
  10. Seek agreement on a narrowed privilege log and a no-waiver order: If you’re successful in #7 above, this should be part of what you try to negotiate.  It helps if both parties have similar concerns regarding the effort and cost to determine privilege and prepare a privilege log.
  11. Pursue cost-shifting for discovery: As yesterday’s post reflects, courts are more often expecting requesting parties to share in the discovery costs when the requests for information result in an undue burden or cost for the producing party.  And, as the author noted, the model order establishes specific parameters for patent cases and the expectation for requesting parties to pay for additional discovery.
  12. Stipulate to facts not in dispute: Why conduct discovery on facts not in dispute?  The author’s recommendation for early stipulations is a great idea for eliminating discovery in areas where it’s not necessary.

So, what do you think?  Did you get some good ideas?  Please share any comments you might have or if you’d like to know more about a particular topic.

eDiscovery Daily will resume with new posts on Tuesday after the Easter holiday.  Have an eggs-cellent weekend!

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 Eighteen! (Months Old, That Is)
Eighteen months ago yesterday, eDiscovery Daily was launched.  A lot has happened in the industry in eighteen months.  We thought we might be crazy to commit to a daily blog each business day.  We may be crazy indeed, but we still haven’t missed a business day yet.

The eDiscovery industry has grown quite a bit over the past eighteen months and is expected to continue to do so.   So, there has not been a shortage of topics to address; instead, the challenge has been selecting which topics to address.

Thanks for noticing us!  We’ve more than doubled our readership since the first six month period, had two of our biggest “hit count” days in the last month and have more than quintupled our subscriber base since those first six months!  We 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.  And, as always, please share any comments you might have or if you’d like to know more about a particular topic!

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, Atkinson-Baker (depo.com), Litigation Support Technology & News, Next Generation eDiscovery Law & Tech Blog, InfoGovernance Engagement Area, Justia Blawg Search, Learn About E-Discovery, Ride the Lightning, Litigation Support Blog.com, ABA Journal, Law.com and any other publication that has picked up at least one of our posts for reference (sorry if I missed any!).  We really appreciate it!

As we’ve done in the past, 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!

eDiscovery Trends: Is Email Still the Most Common Form of Requested ESI?

eDiscovery Trends: Sedona Conference Provides Guidance for Judges

eDiscovery Trends: Economy Woes Not Slowing eDiscovery Industry Growth

eDiscovery Law: Model Order Proposes to Limit eDiscovery in Patent Cases

eDiscovery Case Law: Court Rules ‘Circumstantial Evidence’ Must Support Authorship of Text Messages for Admissibility

eDiscovery Best Practices: Cluster Documents for More Effective Review

eDiscovery Best Practices: Could This Be the Most Expensive eDiscovery Mistake Ever?

eDiscovery 101: Simply Deleting a File Doesn’t Mean It’s Gone

eDiscovery Case Law: Facebook Spoliation Significantly Mitigates Plaintiff’s Win

eDiscovery Best Practices: Production is the “Ringo” of the eDiscovery Phases

eDiscovery Case Law: Court Grants Adverse Inference Sanctions Against BOTH Sides

eDiscovery Trends: ARMA International and EDRM Jointly Release Information Governance White Paper

eDiscovery Trends: The Sedona Conference International Principles

eDiscovery Trends: Sampling within eDiscovery Software

eDiscovery Trends: Small Cases Need Love Too!

eDiscovery Case Law: Court Rules Exact Search Terms Are Limited

eDiscovery Trends: DOJ Criminal Attorneys Now Have Their Own eDiscovery Protocols

eDiscovery Best Practices: Perspective on the Amount of Data Contained in 1 Gigabyte

eDiscovery Case Law: Computer Assisted Review Approved by Judge Peck in New York Case

eDiscovery Case Law: Not So Fast on Computer Assisted Review

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 History: A Look Back at Zubulake
Yesterday, we discussed a couple of cases within a month’s time where the New York Appellate Division has embraced the federal standards of Zubulake v. UBS Warburg LLC, 220 FRD 212.  Those of us who have been involved in litigation support and discovery management for years are fully aware of the significance of the Zubulake case and its huge impact on discovery of electronic data.  Even if you haven’t been in the industry for several years, you’ve probably heard of the case and understand that it’s a significant case.  But, do you understand just how many groundbreaking opinions resulted from that case?  For those who aren’t aware, let’s take a look back.

The plaintiff, Laura Zubulake, filed suit against her former employer UBS Warburg, alleging gender discrimination, failure to promote, and retaliation. Southern District of New York Judge Shira Sheindlin’s rulings in this case are the most often cited in the area of electronic discovery, and were issued prior to the 2006 amendments to the Federal Rules of Civil Procedure. That’s somewhat like establishing laws before the Ten Commandments!  The important opinions related to eDiscovery are commonly known as Zubulake I, Zubulake III, Zubulake IV and Zubulake V.  Here is a summary of each of those opinions:

Zubulake v. UBS Warburg, 217 F.R.D. 309 (Zubulake I) and Zubulake v. UBS Warburg, 216 F.R.D. 280 (S.D.N.Y. 2003) (Zubulake III)

The plaintiff argued that key evidence was located in various emails exchanged among employees of UBS, the defendant. Initially, the defendant produced about 350 pages of documents, including approximately 100 pages of email, but the plaintiff produced approximately 450 pages of email correspondence on her own. To address the discrepancy, the plaintiff requested for UBS to locate the documents that existed in backup tapes and other archiving media.

The defendant, arguing undue burden and expense, requested the court to shift the cost of production to the plaintiff, citing Rowe Entertainment v. The William Morris Agency, 205 F.R.D. 421 (S.D.N.Y. 2002). In May 2003, the court ruled stating that whether the production of documents is unduly burdensome or expensive “turns primarily on whether it is kept in an accessible or inaccessible format”. The court determined that the issue of accessibility depends on the media on which data are stored. It described five categories of electronic media, as follows:

  1. Online data, including hard disks;
  2. Near-line data, including optical disks;
  3. Offline storage, such as magnetic tapes;
  4. Backup tapes;
  5. Fragmented, erased and damaged data.

The last two categories were considered inaccessible as they were not readily available and thus subject to cost-shifting. Discussing the Rowe decision, the court concluded that it needed modification and created a new seven factor balance test for cost-shifting:

  1. The extent to which the request is specifically tailored to discover relevant information;
  2. The availability of such information from other sources;
  3. The total cost of production, compared to the amount in controversy;
  4. The total cost of production, compared to the resources available to each party;
  5. The relative ability of each party to control costs and its incentive to do so;
  6. The importance of the issues at stake in the litigation; and
  7. The relative benefits to the parties of obtaining the information.

The defendant was ordered to produce, at its own expense, all responsive email existing on its servers, optical disks, and five backup tapes as selected by the plaintiff. The court would only conduct a cost-shifting analysis after the review of the contents of the backup tapes.

In July 2003, Zubulake III applied the cost-shifting test outlined in Zubulake I based on the sample recovery of data from five backup tapes.  After the results of the sample restoration, both parties wanted the other to fully pay for the remaining backup email. The sample cost the defendant about $19,003 for restoration but the estimated costs for production was $273,649, including attorney and paralegal review costs. After applying the seven factor test, it determined that the defendant should account for 75 percent of the restoration and searching costs, excluding attorney review costs.

Zubulake v. UBS Warburg, 220 F.R.D. 212 (S.D.N.Y. 2003) (Zubulake IV)

During the restoration effort, the parties discovered that some backup tapes were no longer available. The parties also concluded that relevant emails created after the initial proceedings had been deleted from UBS’s email system and were only accessible on backup tapes. The plaintiff then sought an order requiring UBS to pay for the total costs of restoring the remaining backup tapes and also sought an adverse inference instruction against UBS and the costs for re-deposing some individuals required because of the destruction of evidence.

In October 2003, Judge Scheindlin found that the defendant had a duty to preserve evidence since it should have known that it would be relevant for future litigation. However, at the time, she concluded that the plaintiff failed to demonstrate that the lost evidence supported the adverse inference instruction claim. But, she did order the defendant to cover the costs as claimed by the plaintiff.

Zubulake v. UBS Warburg, 2004 WL 1620866 (S.D.N.Y. July 20, 2004) (Zubulake V)

In July 2004, Judge Scheindlin ruled that UBS had failed to take all necessary steps to guarantee that relevant data was both preserved and produced, and granted the plaintiff’s motion for adverse inference instruction sanctions, sought in Zubulake IV, due to the deleted evidence (emails and tapes) and inability to recover key documents during the course of the case.

The court also indicated that defense counsel was partly to blame for the document destruction because it had failed in its duty to locate and preserve relevant information. In addressing the role of counsel in litigation, the court stated that “[c]ounsel must take affirmative steps to monitor compliance so that all sources of discoverable information are identified and searched” by ensuring all relevant documents are discovered, retained, and produced and that litigators must guarantee that relevant documents are preserved by instituting a litigation hold on key data, and safeguarding archival media.

In the final instructions to the jury Judge Scheindlin instructed in part, “[i]f you find that UBS could have produced this evidence, the evidence was within its control, and the evidence would have been material in deciding facts in dispute in this case, you are permitted, but not required, to infer that the evidence would have been unfavorable to UBS.” In addition, monetary sanctions were awarded to the plaintiff for reimbursement of costs of additional re-depositions and of the motion leading to this opinion, including attorney fees. The jury found in the plaintiff’s favor on both claims awarding compensatory and punitive awards totaling $29.2 million.

Judge Scheindlin’s opinions in Zubulake, including definitions of accessible and inaccessible data, the seven factor balance test for cost shifting and definition of counsel’s obligation for preserving data, have been referenced in numerous cases since and have provided guidance to organizations preparing for litigation.  For any of you who may not have fully understood the significance of the case, I hope this look back was helpful.

So, what do you think?  Did you learn something new about Zubulake?  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: Who’s On Your Team?
When beginning a new eDiscovery project, a good place so start is to estimate the various tasks that will need to be performed and identify the type of personnel that will be needed. Every project is different and unique, so the requirements of each project must be assessed. As the project unfolds, the tasks required to complete it may change – not just in terms of tasks added, but also tasks removed if the work is deemed to be unnecessary.  So, it is important to revisit the project tasks and assignments to determine whether additional personnel are needed or if you can cut back. Here are the types of roles that could be associated with a typical eDiscovery project:

Client Contact(s): It’s important for the client to be involved in the process, so the team should include at least one client representative that can serve as the link between the internal and external teams, providing guidance on internal company workings and contact personnel. Typically, the client contact is from the in-house legal department, usually either a paralegal (to handle routine tasks) or an attorney (to discuss issues and coordinate decision making).  When preservation and collection are required, the client contact(s) generally assist with litigation hold procedures, locating and collecting ESI, and conducting interviews of custodians. It is up to the client contact(s) to involve key managers and custodians as needed to provide guidance during this process.

IT Personnel: When responding to requests for ESI, let’s face it – you need your trusty geek.  Or geeks.  It’s important to include personnel who understand technical details about the client’s various computer systems and data.  Depending on the case, you need one or more individuals who understand any and all of the above: email and email archiving, storage of employee ESI, servers, clients, intranets, and databases. It’s typical for IT personnel in larger organizations to specialize; for example, to have one or more that is more knowledgeable about structured data (i.e. database programs) while others may understand and have access to email systems.

IT personnel should be involved in all issues related to the technology for the responding party to increase efficiency and optimize the approach to each new case. For many corporations, this is typically one or more individuals already employed as a member of the IT staff.  It’s important for IT personnel to have at least a basic understanding of the legal processes and requirements of discovery.  If they don’t have that, it may be necessary to provide some training before a case arises or employ an outside consultant.

Forensic Collection Personnel: In some cases, it’s necessary to perform forensic analysis on various types of ESI (or at least collect the ESI in a forensic manner in the event that’s required). Examples of cases that may require forensic collection of electronic data include internal integrity investigations, situations where fraud and data deletion are suspected (such as trade secret cases) and government civil or criminal investigations. To enable the forensic specialist to testify (if required) to the work that was performed and exactly how it was done, companies often use a vendor not employed by the company or by the outside law firm.

See at least one critical team component missing?  Tomorrow, we’ll talk about the rest of the team.  Same bat time, same bat channel!

So, what do you think?  Do you estimate the team members needed for your project before it begins?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

eDiscovery Case Law: 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 a woman must produce an unencrypted version of her Toshiba laptop’s hard drive to prosecutors in a mortgage fraud case for police inspection.  The woman, Ramona Fricosu, had argued that the Fifth Amendment’s privilege against self-incrimination protected her from having to disclose the password to her hard drive, which was encrypted using PGP Desktop and seized when investigators served a search warrant on her home.

In providing his ruling, Judge Blackburn referenced In re Grand Jury Subpoena to Boucher in which a password protected laptop was seized. After an initial magistrate judge ruling finding that the defendant could not be compelled to reveal the contents of his mind (via the password), the grand jury requested (which a Vermont District judge granted) to require the defendant to produce, not the password itself, but rather an unencrypted version of the drive.

While Judge Blackburn ruled that Fricosu was required to provide the government in this case with an unencrypted copy of the Toshiba laptop computer’s hard drive, he also ruled that the government would be “precluded from using Ms. Fricosu’s act of production of the unencrypted contents of the computer’s hard drive against her in any prosecution”.

Still, 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.  “They must have used or found successful one of the passwords the co-defendant (Scott Whatcott) provided them,” Fricosu’s attorney, Philip Dubois, said in a telephone interview.  Dubois said the authorities delivered to him a copy of the information they discovered on the drive, but he said he had not examined it.

So, what do you think?  Will disclosure of the password preclude a later appeal?  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: Brian Schrader of Business Intelligence Associates (BIA)
This is the fifth of the 2012 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 do you consider to be the emerging trends in eDiscovery that will have the greatest impact in 2012?
  2. Which trend(s), if any, haven’t emerged to this point like you thought they would?
  3. What are your general observations about LTNY this year and how it fits into emerging trends?
  4. What are you working on that you’d like our readers to know about?

Today’s thought leader is Brian Schrader. Brian is Co-Founder and President of Business Intelligence Associates, Inc. (BIA).  Brian is an expert and frequent writer and speaker on eDiscovery and computer forensics topics, particularly those addressing the collection, preservation and processing functions of the eDiscovery process.

What do you consider to be the emerging trends in eDiscovery that will have the greatest impact in 2012?

Well, I think you don’t have to walk around the floor very much to see that this year everybody is talking about predictive coding.  I think you’re going to see that shake out a lot over the next year.  We’ve been doing predictive coding for about a year and a half now, and we have our own algorithms for that.  We have our review teams, and they’ve been using our algorithms to do predictive coding.  We like to call it “suggestive coding”.

What I expect you’ll find this year is a standard shakeout among providers because everybody talks about predictive coding.  The question is how does everybody approach it?  It’s very much a black-box solution.  Most people don’t know what goes on inside that process and how the process works.  So, I think that’s going to be a hot topic for a while.  We’re doing a lot of predictive coding and BIA is going to be announcing some cool things later this year on our predictive coding offerings.

Every provider that you talk to seems to have a predictive coding solution.  I’m really looking forward to seeing how things develop, because we have a lot of input on it and a lot of experience.  We have our review team that is reviewing millions and millions of documents per year, so we can compare various predictive coding engines to real results.  It gives us the ability to review the technology.  We look forward to being part of that conversation and I hope to see a little bit more clarity from the players and some real standards set around that process.

The courts have now also started to look at these algorithmic methods, Judge Peck in particular.  Everybody agrees that key word searching is inadequate.  But, people are still tentative about it – they say “it sounds good, but how does it work?  How are we going to approach it?”

Which trend(s), if any, haven’t emerged to this point like you thought they would?

Frankly, I thought we’d see a lot more competition for us in data collection.  A huge pain point for companies is how to gather all their data from all over the world.  It’s something we’ve always focused on.  I started to see some providers focus on that, but now it looks like everybody, even some of the classic data collection providers, are focusing more on review tools.  That surprises me a bit, though I’m happy to be left with a wide-open field to have more exposure there.

When we first came out with TotalDiscovery.com last year, we thought we’d see all sorts of similar solutions pop up out there, but we just haven’t.  Even the traditional collection companies haven’t really offered a similar solution.  Perhaps it’s because everybody has a “laser focus” on predictive coding, since document review is so much more expensive.  I think that has really overpowered the focus of a lot of providers as they’ve focused only on that.  We have tried to focus on both collection and review.

I think data processing has become a commodity.  In talking to customers, they don’t really ask about it anymore.  They all expect that everybody has the same base level capabilities.  Everybody knows that McDonald’s secret sauce is basically Thousand Island dressing, so it’s no longer unique, the “jig is up”.  So, it’s all about the ends, the collection, and the review.

What are your general observations about LTNY this year and how it fits into emerging trends?

Well, predictive coding again.  I think there’s an awful lot of talk but not enough detail.  What you’re seeing is a lot of providers who are saying “we’ll have predictive coding in six months”.  You’re going to see a huge number of players in that field this year.  Everybody’s going to throw a hat in the ring, and it’s going to be interesting to see how that all works out.  Because how do you set the standards?  Who gets up there and really cooperates?

I think it’s really up to the individual companies to get together and cooperate on this. This particular field is so critical to the legal process that I don’t think you can have everybody having individual standards and processes.  The most successful companies are going to be the ones that step up and work together to set those standards.  And, I don’t know for sure, but I wouldn’t be surprised if The Sedona Conference already has a subcommittee on this topic.

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

Our biggest announcement is around data collection – we’ve vastly expanded it.  Our motto is to collect “any data, anytime, anywhere”.  We’ve been providing data collection services for over a decade, and our collection guys like to say they’ve never met a piece of data they didn’t like.

Now, we’ve brought that data collection capability direction to TotalDiscovery.com.  The latest upgrade, which we’re previewing at the show to be released in March, will offer the ability to collect data from social media sites like Facebook, Twitter, as well as collections from Webmail and Apple systems.  So, you can collect pretty much anything through TotalDiscovery.com that we have historically offered in our services division. It gives you a single place to manage data collection and bring it all together in one place, and then deliver it out to the review platform you want.

We’re on a three-week development cycle, which doesn’t always mean new features every three weeks, but it does mean we’re regularly adding new features.  Mid-year in 2011, we added legal hold capabilities and we’ve also recently added other components to simplify search and data delivery.  Now, we’ve added expanded collection for social media sites, Webmail and Apple.  Later this year, we expect to release our predictive coding capabilities to enable clients to perform predictive coding right after collection instead of waiting until the data is in the review tool.

Thanks, Brian, 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!

eDiscovery Case Law: Court Rules Exact Search Terms Are Limited
In Custom Hardware Eng’g & Consulting v. Dowell, 2012 U.S. Dist. LEXIS 146, 7-8 (E.D. Mo. Jan. 3, 2012), the plaintiff and defendant could not agree on search terms to be used for discovery on defendant’s forensically imaged computers.  The court directed each party to submit a proposed list of search terms and indicated that each party would be permitted to file objections to the opposing party’s proposed list.  After reviewing the proposals, 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.

Plaintiff alleged the defendants formed a competing company by “illegally accessing, copying, and using Plaintiff’s computer software and data programming source code systems” and sued defendants for copyright infringement, trade secret misappropriation, breach of contract and other claims.  The court ordered discovery of ESI on defendants’ computers through use of a forensic process to recover and then search the ESI.  In July 2011, the plaintiffs provided a request for production to defendants that requested “any and all documents which contain, describe, and/or relate in any manner to any of the words, phrases and acronyms, or derivatives thereof, contained in the list [provided], irrespective of whether exact capitalization, alternative spelling, or any other grammatical standard was used.”  The defendants submitted their own proposed list, which “excludes irrelevant information by requiring precise matches between search terms and ESI”.

Referencing Victor Stanley (previous blog posts regarding that case here, here, here and here), Missouri District Court Judge Richard Webber noted in his ruling that “While keyword searches have long been recognized as appropriate and helpful for ESI search and retrieval, there are well-known limitations and risks associated with them.”  Quoting from The Sedona Conference Best Practices Commentary on the Use of Search & Information Retrieval Methods in E-Discovery, the court noted that keyword searches “capture many documents irrelevant to the user’s query…but at the same time exclude common or inadvertently misspelled instances” of the search terms.

The defendant issued three objections to the plaintiff’s terms, which the court addressed as follows:

  • Plaintiffs’ Terms would Include an Unreasonable Number of Irrelevant Results: Assuming that the argument was based on a contention by the defendants that the discovery would be overly burdensome, the court noted that the “burden or expense of conducting such a search must be low, and Defendants have presented the Court with no evidence that suggests otherwise.”
  • Plaintiffs’ Terms would Produce Privileged Results: The Court noted that a producing party can create a privilege log to exclude documents that would otherwise fit the search term results.
  • Some of Plaintiffs’ terms will Encompass Only Irrelevant Information: Noting that the defendants’ “objection is a conclusory statement, stated without any argumentation or other support”, the Court found that a search of these terms may produce “matter that is relevant to any party’s claim or defense”.

The Court also found that the defendants’ proposed list would be “problematic and inappropriate” and “would fail to produce discoverable ESI simply because of an inexact match in capitalization or phrasing between a search term and the ESI” and rejected that list, ordering use of the plaintiff’s list for searching.

So, what do you think?  Was that the right call, or was the plaintiff’s request overbroad?  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.