Posts By :

Doug Austin

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

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

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

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

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

So, what do you think?  How important are self-documentation features in a review solution to you?  Can you think of other important self-documentation features in a review solution?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

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

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

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

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

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

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

So, what do you think?  How important are self-documentation features in a review solution to you?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

New eDiscovery Guidelines for Northern District of California – eDiscovery Trends

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

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

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

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

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

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

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

So, what do you think?  Should all District courts adopt similar standards and provide similar guidelines and checklists?  If not, why not?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

Another Major eDiscovery Acquisition: DTI Acquires Fios – eDiscovery Trends

As reported by Law Technology News and the Litigation Support News and Information Blog, Document Technologies Inc. (DTI), the nation’s largest independent provider of discovery services, facilities management, and knowledge process outsourcing has acquired Fios Inc., one of the electronic discovery industry’s most recognized brands.  The new company will be known as “Fios, A DTI Company.”

Atlanta-based DTI said that Fios was purchased to gain clients and staff. Based in Portland, Ore. and founded in 1999 , Fios also brings software development skills and workflow expertise to the DTI portfolio.

“We felt the opportunity to bring Fios into the DTI family was quite attractive,” said DTI CEO John Davenport Jr. “They have exactly what we look for — an exceptional group of high-performing employees, a respected name, strong relationships with an impressive list of Am Law 100 and Fortune 500 corporate clients, and most importantly, similar values and corporate cultures.”

Terms of the current deal were not disclosed.  DTI has been busy this year – this is its third acquisition of the year, after acquiring Los Angeles computer forensics specialist Data Forté in July and Houston-based legal staffing company Provius in September.

Industry consolidation continues.  This latest acquisition makes at least 44 eDiscovery industry deals so far this year, with companies such as Applied Discovery, CaseCentral, Sanction Solutions, Lateral Data and Digital Reef having been acquired.  Of course, not all acquisitions work out, as we saw recently with the HP/Autonomy purchase.  It will be interesting to see how this acquisition works out and how well DTI integrates all of its recent acquisitions.

So, what do you think?  Will the accelerated pace of eDiscovery acquisitions continue?  If so, who’s next?  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.

Plaintiff Hammered with Case Dismissal for “Egregious” Discovery Violations – eDiscovery Case Law

Apparently, destroying your first computer with a sledgehammer and using Evidence Eliminator and CCleaner on your second computer (when you have a duty to preserve both) are not considered to be best practices for preservation.  Who knew?  😉

In Taylor v. Mitre Corp., (E.D. Va. Nov. 8, 2012), Virginia District Court Judge Liam O’Grady upheld the findings by the Magistrate Judge for dismissal of the plaintiff’s claims and payment of the defendant’s reasonable attorney’s fees and costs due to “egregious” discovery conduct.  Here’s why:

  • The plaintiff hired counsel back in 2009 “in anticipation of bringing this lawsuit against Mitre for violations of the FMLA and failure to accommodate his disabilities.  Mr. Taylor’s lawyer immediately put him on clear notice that he was required to maintain all files and documents (electronic and otherwise) related to his claim, and that deleting or discarding such files could result in sanctions including dismissal of his claim.”;
  • The plaintiff filed his EEOC claim in November 2010;
  • Sometime in 2011, the plaintiff “wiped” his work desktop, then “took a sledgehammer to it” and disposed of it in the local landfill (as noted in the footnote: “Mr. Taylor has given varying accounts of the size and type of the hammer he used to wreck the computer, but does not deny that he smashed it with some nature of mallet.”);
  • Before destroying his work computer, the plaintiff “attempted” to back up files from it “but was only partially successful”;
  • In November 2011, the plaintiff filed his complaint;
  • On July 1, the Magistrate Judge “ordered Mr. Taylor to submit his current computer, a laptop, to inspection within a week.”  The plaintiff “had represented that whatever documents he maintained during the partially successful backup operation described above had been transferred to the laptop, and the Defendant won permission to inspect the laptop”;
  • A few days later, the defendant’s forensic expert examined the laptop and determined that the plaintiff had “run a program called Evidence Eliminator, a program whose express purpose is removing ‘sensitive material’ from one’s hard drive and defeating forensic software.”  The plaintiff admitted that “he downloaded the program the same day he learned of the Court’s inspection order”;
  • The plaintiff also ran another program CCleaner (which also erases files from the computer so that they cannot be recovered) “at least twice between the time of the Court’s inspection order and the actual inspection.”

The plaintiff claimed “that CCleaner was set to run automatically, and so even if it did delete relevant documents, the deletion was not intentional.” – a claim that the court found to be “highly suspicious”.  However, when it came to the installation of Evidence Eliminator, Judge O’Grady did not mince words:

“For Mr. Taylor to download and run a program whose express purpose is deletion of evidence in direct response to the Magistrate Judge’s order that his computer be produced for inspection was to blatantly disregard his duties in the judicial system under which he sought relief. The Court finds Mr. Taylor’s conduct to be egregious and highly contemptuous of the inspection order. Mr. Taylor has forfeited his right to pursue his claims with this Court any further.”

So, what do you think?  Is this the most egregious example of spoliation you’ve ever seen?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

The Grossman-Cormack Glossary of Technology Assisted Review – eDiscovery Resources

Do you know what a “Confidence Level” is?  No, I’m not talking about Tom Brady completing football passes in coverage.  How about “Harmonic Mean”?  Maybe if I hum a few bars?  Gaussian Calculator?  Sorry, it has nothing to do with how many Tums you should eat after a big meal.  No, the answer to all of these can be found in the new Grossman-Cormack Glossary of Technology Assisted Review.

Maura Grossman and Gordon Cormack are educating us yet again with regard to Technology Assisted Review (TAR) with a comprehensive glossary that defines key TAR-related terms and also provides some key case references, including EORHB, Global Aerospace, In Re: Actos:, Kleen Products and, of course, Da Silva Moore.  The authors of the heavily cited article Technology-Assisted Review in E-Discovery Can Be More Effective and More Efficient Than Exhaustive Manual Review have provided a new reference document that may help many in the industry understand key TAR concepts better.  Or, at least recognize key terms associated with TAR.  This is version 1.01, published just this month and clearly intended to evolve over time.  As the authors note in the Preamble:

“The introduction of TAR into the legal community has brought with it much confusion because different terms are being used to refer to the same thing (e.g., ‘technology assisted review,’ ‘computer-assisted review,’ ‘computer-aided review,’ ‘predictive coding,’ and ‘content based advanced analytics,’ to name but a few), and the same terms are also being used to refer to different things (e.g., ‘seed sets’ and ‘control sample’). Moreover, the introduction of complex statistical concepts, and terms-of-art from the science of information retrieval, have resulted in widespread misunderstanding and sometimes perversion of their actual meanings.

This glossary is written in an effort to bring order to chaos by introducing a common framework and set of definitions for use by the bar, the bench, and service providers. The glossary endeavors to be comprehensive, but its definitions are necessarily brief. Interested readers may look elsewhere for detailed information concerning any of these topics. The terms in the glossary are presented in alphabetical order, with all defined terms in capital letters.

In the future, we plan to create an electronic version of this glossary that will contain live links, cross references, and annotations. We also envision this glossary to be a living, breathing work that will evolve over time. Towards that end, we invite our colleagues in the industry to send us their comments on our definitions, as well as any additional terms they would like to see included in the glossary, so that we can reach a consensus on a consistent, common language relating to technology assisted review. Comments can be sent to us at mrgrossman@wlrk.com and gvcormac@uwaterloo.ca.”

Live links, with a Table of Contents, in a (hopefully soon) next iteration will definitely make this guide even more useful.  Nonetheless, it’s a great resource for those of us that have bandied around these terms for some time.

So, what do you think?  Will this glossary help educate the industry and help standardize use of the terms?  Or will it lead to one big “Confusion Matrix”? (sorry, I couldn’t resist)  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.

Sedona Conference Updates Guide for Judges – eDiscovery Trends

Last year, The Sedona Conference® made a public comments version of the Cooperation Proclamation: Resources for the Judiciary available on the Sedona Conference website. The Resources for the Judiciary document aims to provide judges with a foundation for creating a collaborative and non-adversarial approach to managing eDiscovery.  Now, its Judicial Resources guide has been updated and the free version is available on the Sedona Conference web site.

In addition to a Preface that outlines the Vision, Mission and Goal for the Resources, the guide includes the following sections:

  • I. Introduction: Discusses the difference between “active case management” (proactive) and “discovery management” (reactive), while urging judges to take an active case management model approach;
  • II. Review of Existing Literature on E-Discovery for Judges: A compilation of various resources for judges to become more familiar with eDiscovery, including everything from the 2006 amendments to the Federal Rules to local rules and pilot projects, such as the Model Order for Patent eDiscovery;
  • III. General Recommendations for Judges: A list of seven recommendations for how judges handle eDiscovery issues in their cases, along with supporting information and resources;
  • IV. The Stages of Litigation from a Judge’s Perspective: Sections for twenty different stages, ranging from Preservation to Post-Judgment Costs.

Creation of the new edition was led by senior editors Ronald Hedges (a retired magistrate judge from the U.S. District Court for the District of New Jersey, now a consultant) and Kenneth Withers (Sedona’s director of judicial education) with Karen Van Allen serving as editorial coordinator.  Judicial Reviewers were:

  • Hon. Ralph Artigliere, 10th Judicial Circuit Court, Florida (ret.)
  • Hon. John M. Facciola, U.S. Magistrate Judge, District of the District of Columbia
  • Hon. Peter Flynn, Circuit Court of Cook County, Illinois
  • Hon. Elizabeth D. Laporte, U.S. Magistrate Judge, Northern District of California
  • Hon. Elizabeth M. Schwabedissen, General Magistrate, 11th Judicial Circuit Court, Florida
  • Hon. Craig B. Shaffer, U.S. Magistrate Judge, District of Colorado

Apparently, the web site will also have a special password-protected collaboration area exclusively for judges to comment, suggest resources or even submit sample orders, enabling those judges to freely communicate without concern about eavesdropping from outside parties.  And, as always, to submit a public comment, you can download a public comment form here, complete it and fax (yes, fax) it to The Sedona Conference® at 928-284-4240.  You can also email a general comment to them at tsc@sedona.net.

So, what do you think?  Will this guide make for a smoother discovery 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.

Perspective on the HP/Autonomy Fiasco – eDiscovery Trends

It’s not exactly Dr. Evil’s $100 billion, but it’s not “chump change” either…

By now, you’ve probably heard that, on Tuesday, Hewlett-Packard (HP) took an $8.8 billion charge resulting from its acquisition of Autonomy back in 2011, one of the largest acquisitions in the eDiscovery industry in history.  HP has called on US and British authorities to investigate what it called “serious accounting improprieties, disclosure failures and outright misrepresentations at Autonomy” before the acquisition in a developing scandal that also involves accounting firms Deloitte and KPMG, who audited the sale.

In a statement, HP said “HP is extremely disappointed to find that some former members of Autonomy’s management team used accounting improprieties, misrepresentations, and disclosure failures to inflate the underlying financial metrics of the company, prior to Autonomy’s acquisition by HP”.  The deal was brokered by former HP CEO Leo Apotheker and Autonomy founder Mike Lynch – both are no longer with HP.

Some notable stats:

  • The $8.8 billion charge is 85% of the widely reported $10.3 billion purchase price that HP paid for Autonomy in October 2011;
  • On Tuesday, HP’s shares traded down $1.74, or 13%, at $11.56 in morning trading – just after the open, they hit $11.35, the lowest level since 2002;
  • HP’s net loss for the fiscal fourth quarter (which ended Oct. 31) was $6.85 billion, compared with net income of $239 million in the same period in 2011.

For his part, Lynch fiercely denies allegations that Autonomy falsified its financial statements. In a statement to the Guardian on Tuesday, his spokesperson said: “HP has made a series of allegations against some unspecified former members of Autonomy Corporation PLC’s senior management team. The former management team of Autonomy was shocked to see this statement today, and flatly rejects these allegations, which are false…HP’s due diligence review was intensive, overseen on behalf of HP by KPMG, Barclays and Perella Weinberg. HP’s senior management has also been closely involved with running Autonomy for the past year…It took 10 years to build Autonomy’s industry-leading technology and it is sad to see how it has been mismanaged since its acquisition by HP.”

Additional articles discussing the HP/Autonomy controversy are available here, here, here and here.  As for what will become of HP and its Autonomy division (that previously acquired Zantaz, Interwoven and Iron Mountain, among others), remains to be seen.  Expect a long legal battle.

So, what do you think?  How will this affect future acquisitions of eDiscovery companies?  Will we all be working with the HP/Autonomy public domain data set someday?  😉  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.

Defendant Compelled to Produce Additional Discovery to Plaintiff – 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!

Where the facts of the case led a court to conclude that certain electronically stored information (ESI) could contain evidence relevant to the case, the court ordered a party to comply with its discovery obligations related to that ESI.

In Freeman v. Dal-Tile Corp., No. 5:10-CV-00522-BR, 2012 U.S. Dist. (E.D.N.C. Oct. 2, 2012), 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.

Specifically, the plaintiff sought to compel a keyword search of preserved e-mails belonging to certain individuals for a time frame that began two months after the plaintiff left Dal-Tile. The defendant objected, arguing that because the plaintiff had already left the company during the time frame for e-mails requested, any such e-mails “could not be relevant to Plaintiff’s harassment claims, because ‘the sole issue is whether Dal-Tile knew or should have known of the harassment and failed to take appropriate steps to halt it.’”

North Carolina Magistrate Judge William A. Webb disagreed, stating that it was “reasonable to expect” that e-mails written or received during that time period “could contain historical e-mails, i.e., an e-mail chain, given that the requested search period begins only two months after Plaintiff resigned.” Moreover, the plaintiff’s request hit the mark for other reasons: “The custodians whose e-mail Plaintiff requests to have searched are . . . the human resource officer who investigated Plaintiff’s complaints, and . . . the regional vice-president to whom [the human resources officer] reported her investigation findings.” In addition, the search terms that the plaintiff requested were “appropriately limited in number and scope and, thus, reasonably calculated to lead to the discovery of admissible evidence.”

Moreover, Judge Webb noted, Dal-Tile did “not assert[ ] that it would be unduly burdensome to search the e-mail[s requested]” or the hard drive of the human resources officer, a search of which the plaintiff had included in her request.

Therefore, the plaintiff’s motion was granted.

So, what do you think?  Should the plaintiff’s motion have been granted?  Please share any comments you might have or if you’d like to know more about a particular topic.

From All of Us at CloudNine Discovery and eDiscovery Daily, Happy Thanksgiving!  eDiscovery Daily will resume with new posts next Monday.

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.

Rambus’ “Shred Days” Result in Sanctions Yet Again – 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!

By the way, the Rambus cases are among the most “famous” from an eDiscovery spoliation standpoint.  As you’ll see from the description below, Rambus is still paying for activities way back in 1998 that have been ruled to be spoliation of data.

In Hynix Semiconductor Inc. v. Rambus, Inc., No. C-00-20905 RMW, 2012 U.S. Dist. (N.D. Cal. Sept. 21, 2012), California District Judge Ronald Whyte used his discretion to fashion an appropriate fact-specific sanctions award after it found a party willfully destroyed evidence despite reasonably foreseeable litigation, it destroyed such evidence in bad faith, and the opposing party suffered prejudice.

In this discovery dispute over spoliation and sanctions in a patent lawsuit, the district court reconsidered this case after its previous decision was vacated by the Federal Circuit and remanded. Previously, in this court, Hynix Semiconductor Inc. et al. (Hynix) had “unsuccessfully urged” that Rambus, Inc. (Rambus) had engaged in the spoliation of evidence, and “its ‘unclean hands’ warranted dismissal of its patent infringement claims.” On appeal, however, the Federal Circuit remanded the case so that the district court could consider it under a different spoliation test, which had been applied in another case presenting an identical spoliation issue, Micron Technology, Inc. v. Rambus Inc., 645 F.3d 1311 (Fed. Cir. 2011) (Micron II).

Therefore, the court had to analyze whether “Rambus destroyed records at a time when litigation was reasonably foreseeable. If so, the court will determine whether Rambus acted in bad faith. Next, the court will determine the nature and extent of any prejudice suffered by Hynix as a result of the spoliation. Finally, the court will decide what sanction is appropriate, if any.”

The court found that Rambus engaged in spoliation of evidence when it destroyed documents on “Shred Days” in 1998, 1999, and 2000 when it invited an outside company to Rambus to shred documents that employees provided for shredding in accordance with the company’s document retention policy. The court found that on those Shred Days, litigation was reasonably foreseeable. Noting that the “important question” was not when Rambus’s duty to preserve arose, “but rather the binary question of whether litigation was reasonably foreseeable by the date on which documents were destroyed,” the court found that although litigation was not foreseeable when Rambus destroyed some of its back-up tapes in July 1998, it was reasonably foreseeable by the time of Shred Day 1998.

At the time the back-up tapes were destroyed in July, the court pointed to numerous questions that existed about the success of Rambus’s patented product and what features the existing patents covered. Management had only held hypothetical discussions about potential targets of litigation, and they had not discussed in depth budgeting for litigation. Destruction of back-up tapes was done “primarily” for “housekeeping” purposes.

By the time Shred Day 1998 occurred, however, Rambus “anticipated instituting litigation.” A Rambus officer, Joel Karp, whom the company hired in 1997 to assess whether competitors were infringing on Rambus’s patents, had advised employees of the company’s documentation retention policy, and “the fact that he advised them to discard documents that questioned the patentability of ideas suggests he had litigation on his mind.” Moreover, a litigation strategy was being “aggressively developed,” and Rambus was turning its attention heavily toward a certain part of its business, which it believed it had to fight to protect.

Thus, finding that Rambus had engaged in spoliation beginning with Shred Day 1998, the court turned to analyze whether Rambus acted with “unclean hands.” The court set forth the applicable standard: “To find bad faith in the spoliation context, ‘the district court must find that the spoliating party intended to impair the ability of the potential defendant to defend itself.’” While Rambus asserted that it conducted document destruction only to execute its “neutral” document retention policy, Hynix argued that regardless of Rambus’s compliance with its own document retention policy, Rambus knew litigation was reasonably foreseeable and destroyed documents in bad faith “to gain a litigation advantage.” In addition, Hynix argued that Karp ordered Rambus employees to destroy documents selectively, keeping ones that would protect their patents and destroying ones that would cause difficulty in litigation.

Parsing the evidence, the court found:

“Although the evidence does not support a conclusion that Rambus deliberately shredded documents it knew to be damaging, the court concludes that Rambus nonetheless spoliated evidence in bad faith or at least willfully. This conclusion is based upon the facts that: (1) Rambus destroyed records when litigation was reasonably foreseeable; (2) Karp, the officer in charge of the destruction, was experienced in litigation and undoubtedly knew that relevant documents should not be destroyed when litigation is reasonably foreseeable; (3) the destruction was part of a litigation plan; (4) one of the motives of the destruction was to dispose of potentially harmful documents; and (5) Rambus shredded a huge number of documents without keeping any records of what it was destroying.”

The court then turned to the issue of whether Rambus’s bad faith spoliation of evidence had prejudiced Hynix. The Micron II court set forth the applicable standard for evaluating prejudice: “‘Prejudice to the opposing party requires a showing that the spoliation materially affect[s] the substantial rights of the adverse party and is prejudicial to the presentation of his case.’ (citation omitted) ‘In satisfying that burden, a party must only come forward with plausible, concrete suggestions as to what [the destroyed] evidence might have been.’” Moreover, if the spoliation had already been determined to have been in bad faith, the spoliating party had a heavy burden to show its document destruction had not prejudiced the other party. Yet, the court cautioned, “the alleged misconduct by the spoliator . . . must relate directly to an issue concerning which the complaint is made.”

Here, Hynix had claimed that Rambus’s patents were invalid, and the court explained, “the invalidity defenses of anticipation and obviousness depend upon how one of ordinary skill in the art would have understood the prior art.” In this case, all prior art was accessible to Hynix and therefore the document destruction did not prejudice Hynix. The other defense of “inadequate written description” similarly turned on information that was available to Hynix. As such, the court found that Hynix’s invalidity defenses were not prejudiced by Rambus’s spoliation of evidence.

On the other hand, however, the court found that Rambus did not overcome Hynix’s allegations of prejudice based on its unenforceability complaint against Rambus. The court found that “it appear[ed] plausible that spoliated evidence might have shed additional light on the scope” of certain disclosure obligations that Rambus had with respect to its patents. Because this allegation offered a concrete suggestion for Hynix as to what the destroyed evidence could have been, Rambus had a heavy burden to disprove prejudice, which the court found it could not overcome.

Having concluded that Rambus “spoliated documents in bad faith and that Hynix has established prejudice,” the court then considered sanctions, noting it had “wide discretion whether to hold the patents-in-suit unenforceable pursuant to Hynix’s unclean hands defense, or to impose a different sanction.”

The court used the following analysis to evaluate the appropriateness of sanctions:

“In gauging the propriety of the sanction, the district court must take into account

“(1) the degree of fault of the party who altered or destroyed the evidence; (2) the degree of prejudice suffered by the opposing party; and (3) whether there is a lesser sanction that will avoid substantial unfairness to the opposing party and, where the offending party is seriously at fault, will serve to deter such conduct by others in the future.” (citation omitted) The sanction ultimately imposed must be commensurate with the analysis of these factors.”

In examining the Rambus’s degree of fault, the court found that

“Rambus’s fault was significant but not as great as that of a spoliator who knows of adverse evidence and specifically alters, hides or destroys that evidence. There is a possibility that Rambus did not destroy any evidence that would have been beneficial to Hynix’s litigation position. However, because Rambus is the party that destroyed documents by the box and bag without keeping any record of what was destroyed, Rambus must suffer the consequences of that uncertainty.”

Hynix’s degree of prejudice was significant, the court held, because it “was arguably prejudiced in its ability to litigate its equitable claims and defenses,” and if it had been able to better litigate them, it possibly could have avoided a royalty fee that was awarded against it based on a previous determination that Rambus’s patents were valid.

Therefore, the court “conclude[d] that the sanction most commensurate with Rambus’s conduct and [the fact that a royalty rate was previously awarded] is to strike from the record evidence supporting a royalty in excess of a reasonable, nondiscriminatory royalty. Such a remedy recognizes that Rambus’s patents have been determined to be valid while at the same time recognizing that Rambus’s spoliation of evidence should preclude it from entitlement to a royalty that places Hynix at a competitive disadvantage.” The court decided to use its discretion to fashion a sanction, noting that “a retrial of the case with either an adverse jury instruction or an evidentiary exclusion order would involve considerably more delay and expense,” and there had already been great delay in reaching a final determination in the case.

So, what do you think?  Was it appropriate to issue sanctions at this point and, if so, were they harsh enough?  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.