Professional Documents
Culture Documents
SANCTIONED
Like These Parties!
INTERPRETING RECENT CASE
LAW TO ENSURE E-DISCOVERY
DEFENSIBILITY
TABLE OF CONTENTS
Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Key Takeaways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
With e-discovery practices maturing, and more than six years removed from the
last changes to the Federal Rules of Civil Procedure (FRCP), it seems some of us
are ready for a refresher in the fundamentals. A few years ago, we were hearing
about seeing fewer e-discovery sanctions from the bench. Fast forward to 2022,
and it seems not everyone got the memo.
E-Discovery sanctions are still an important tool for judges, as ten recent cases
demonstrate. This white paper from Exterro’s E-Discovery Case Law Project
covers five cases where judges granted e-discovery sanction motions and five
cases where one of the parties narrowly escaped sanctions. To help ensure you
stay on the right side of e-discovery sanctions, we’ve also included an FRCP Rule
37 (e) Flowchart and some advice in the form of actionable key takeaways.
The bedrock underlying all these cases, of course, is the concept that parties
to a potential lawsuit have an obligation to preserve relevant documents and
electronically stored information (ESI) as soon as they have “a reasonable
anticipation of litigation.” That means organizations must have defensible legal
hold and preservation processes in place. Without the ability to ensure you’re
preserving responsive data, you’re running the risk of e-discovery sanctions.
FRCP 37 (e) explains what happens when parties allow the spoliation of ESI.
Use this handy flowchart to determine what actions the court may take regarding
the spoliation of ESI?
RULE 37(e)(1)
THE COURT MAY…
Order measures no greater than necessary
to cure the prejudice.
YES
RULE 37(e)(2)
Can the “lost” ESI be
restored or replaced? NO THE COURT MAY…
A) Presume the information loss was unfavorable;
YES
B) Issue mandatory or permissive adverse
inference instruction; or
C) Enter dismissal or default
Restore or replace
the “lost” ESI and produce
SANCTIONS
DO NOT
APPLY!
Overview • Notice.
The defendants had notice, via the cease
and desist letter that there was a reasonably
In this copyright infringement case, the U.S. 4th Circuit
anticipated likelihood of litigation. This action
Court of Appeals was asked to review a district court
should’ve triggered the defendants’ duty to
judgement which sanctioned the defendants with a
preserve all potentially relevant information,
permanent injunction for data spoliation.
which they didn’t.
The plaintiffs contended that the defendants stole
source code from the plaintiffs. After the plaintiffs sent
• Severity of the Ruling.
a cease and desist letter, the defendants destroyed
To justify the severe punishment of a permanent
his computer that retained relevant information about
injunction the court stated, “No less drastic
the case. When the plaintiffs requested information
sanction would adequately address the prejudice
regarding the source code, the defendants initially
suffered by QueTel (plaintiffs) or adequately deter
contended that they had no relevant information.
the type of spoliation that occurred in the case.
Subsequently the defendants admitted during a
deposition that his computer had been destroyed.
As a result, the plaintiff motioned for sanctions. This case is another example of
the problems that can arise when
counsel and the IT department are
not sufficiently coordinated. It also
Ruling demonstrates the importance of
contemporaneous notes as to what
• Spoliation Occurred. was done to preserve and why
The court ruled that “discoverable ESI existed those decisions were made. Finally, it is curious that
at the time the duties to preserve the evidence the Court nowhere mentions Rule 37(e). The court
arose, that defendant’s efforts to preserve the reached the correct conclusion not to enter a default,
ESI were deficient, that defendant took but Rule 37(e)(2) reserves default judgments or serious
affirmative and intentional steps to destroy sanctions for when there is an “intent to deprive”
relevant evidence that it knew or should have which was absent here.
known had not been preserved, and that the
evidence is now irretrievably lost. Thus, plaintiffs
have shown that spoliation occurred.”
Based on these events, the plaintiffs filed for spoliation An important take away is that
sanctions, specifically an adverse inference about the no sanctions were imposed for
key custodian’s role in the case. the company issued phone which
automatically backs up to the
company’s survey. “No party has
Ruling suggested that the back up would
not include text messages.” I am not
• Motion for Spoliation Sanctions Granted. sure that that would be true for all device management
The court ordered that the proposed sanction systems, but to the extent that can be done, it will make
precluding the defendant “from introducing any preservation and production in discovery so much easier.
DON’T:
һ Optimized Workflows
һ Custodian Notifications and Reminders
һ Technology Integrations
һ In-Place Preservation
GET A DEMO