Esi Preservation In Corporate Litigation
1. Overview of ESI Preservation
Electronically Stored Information (ESI) refers to all digital data that corporations maintain, including:
Emails, instant messages, and chat logs
Documents and spreadsheets
Databases and cloud storage
Metadata associated with digital files
Social media content and enterprise collaboration tools
ESI preservation is the process of ensuring that relevant electronic evidence is maintained and protected from deletion, alteration, or destruction once litigation is reasonably anticipated or ongoing.
Failure to preserve ESI can lead to spoliation claims, adverse inferences, fines, or sanctions.
2. Legal Basis for ESI Preservation
Federal Rules of Civil Procedure (FRCP), Rule 26(f), 37(e)
Requires parties to preserve discoverable information once litigation is reasonably anticipated.
Rule 37(e) addresses failure to preserve ESI, providing for sanctions only if information was lost due to intentional or negligent conduct that prejudices another party.
State Law Equivalents
Many U.S. states have similar rules imposing duties to preserve ESI in litigation.
Corporate Governance Implications
Preservation duties extend to officers, IT personnel, and employees.
Requires policies and procedures to ensure defensible holds and proper data management.
3. Key Elements of ESI Preservation
Litigation Hold Notice
Formal notice to employees and IT staff to preserve all potentially relevant ESI.
Identification of Custodians and Systems
Determine which individuals, departments, and data systems may hold relevant information.
Suspension of Routine Deletion Policies
Temporarily suspend automatic email deletion, data purging, or backup overwriting.
Monitoring and Compliance
Track adherence to preservation instructions and provide follow-up reminders.
Documentation
Maintain records of litigation hold notices, custodian acknowledgments, and preservation actions.
4. Corporate Implications
Risk Mitigation: Preserving ESI reduces risk of sanctions and adverse inference in litigation.
Operational Management: Balances preservation with ongoing business operations.
IT Governance: Requires coordination between legal, IT, and compliance teams.
Insurance and Liability: Defensible preservation reduces exposure to claims and fines.
5. Illustrative Case Laws
1. Zubulake v. UBS Warburg LLC, 220 F.R.D. 212 (S.D.N.Y. 2003 – 2004)
Principle: Duty to preserve ESI begins when litigation is reasonably anticipated.
Impact: Corporations must issue litigation holds promptly and monitor compliance.
2. Pension Committee of the University of Montreal Pension Plan v. Banc of America Securities, 685 F. Supp. 2d 456 (S.D.N.Y. 2010)
Principle: Failure to implement litigation holds constitutes gross negligence.
Impact: Companies can face severe sanctions for non-compliance with ESI preservation.
3. Victor Stanley, Inc. v. Creative Pipe, Inc., 269 F.R.D. 497 (D. Md. 2010)
Principle: Spoliation occurs when ESI is destroyed after duty to preserve arises.
Impact: Courts may impose adverse inference instructions or monetary sanctions.
4. Residential Funding Corp. v. DeGeorge Financial Corp., 306 F.3d 99 (2d Cir. 2002)
Principle: Preservation duty extends to relevant email and electronic files.
Impact: IT and corporate personnel must proactively identify and preserve relevant digital evidence.
5. Qualcomm Inc. v. Broadcom Corp., 2008 WL 906309 (S.D. Cal.)
Principle: Sanctions for failure to preserve ESI even when inadvertent.
Impact: Highlights need for comprehensive, documented preservation policies.
6. Apple Inc. v. Samsung Electronics Co., 888 F. Supp. 2d 976 (N.D. Cal. 2012)
Principle: Failure to preserve technical data and communications can lead to adverse jury instructions.
Impact: Technical teams must coordinate with legal to ensure technical ESI is retained.
7. Rimkus Consulting Group, Inc. v. Cammarata, 688 F. Supp. 2d 598 (S.D. Tex. 2010)
Principle: Courts consider intent, scope, and prejudice when determining sanctions for ESI destruction.
Impact: Good faith efforts and documentation can mitigate liability.
6. Best Practices for Corporate ESI Preservation
Litigation Hold Policies: Formal written policies with templates for hold notices.
Identify Custodians Early: Employees, contractors, and IT systems likely to hold relevant data.
Suspend Routine Data Deletion: Suspend auto-deletion or backup overwriting for relevant custodians.
Training & Awareness: Educate employees on legal obligations to preserve ESI.
Documentation & Audit Trails: Record all actions taken to preserve and monitor ESI.
Coordination Between Legal and IT Teams: Ensure technical feasibility and compliance.
7. Summary Table of Case Laws
| Case | Principle | Corporate Takeaway |
|---|---|---|
| Zubulake v. UBS (2003–2004) | Duty arises when litigation anticipated | Issue litigation holds promptly |
| Pension Committee v. Banc of America (2010) | Gross negligence for failure | Implement and monitor preservation procedures |
| Victor Stanley v. Creative Pipe (2010) | Spoliation = destroyed ESI | Document preservation actions to avoid sanctions |
| Residential Funding v. DeGeorge (2002) | Email and files must be preserved | IT must proactively preserve relevant data |
| Qualcomm v. Broadcom (2008) | Sanctions even if inadvertent | Maintain comprehensive and documented policies |
| Apple v. Samsung (2012) | Technical data must be preserved | Ensure cross-team coordination for technical ESI |
| Rimkus v. Cammarata (2010) | Intent, scope, and prejudice matter | Good-faith efforts mitigate sanctions |
Conclusion:
ESI preservation in corporate litigation is legally mandated, operationally critical, and risk-sensitive. Corporations must:
Implement formal litigation hold policies
Identify custodians and systems
Suspend routine deletion of relevant data
Maintain documentation and audit trails
Proper ESI preservation protects corporations from sanctions, adverse inferences, and reputational harm while ensuring defensible litigation practices.
RELATED Blog
comments