Practical guidance on FRCP compliance, data preservation strategy, and modern legal hold operations for in-house legal teams.
Rule 37(e) fundamentally changed how courts approach sanctions for lost ESI. The two-tier framework — curative measures under 37(e)(1), severe sanctions under 37(e)(2) — creates a direct line between your hold process and your litigation exposure.
If your legal hold process relies on email chains, shared spreadsheets, or calendar reminders to track custodian responses, you already have a problem. The question is whether you find out in a deposition or before it.
Issuing a hold notice is the beginning of your preservation obligation, not the end. Defensible preservation in 2026 means documented custodian acknowledgment, in-place preservation for cloud data sources, and a complete chain of custody for anything collected.
A migration isn't just a data transfer — it's a compliance event. Acknowledgment records, event history, and matter relationships all need to move intact or you lose the audit trail that makes your historical holds defensible.
Your legal hold platform processes litigation-sensitive employee data, attorney-client privileged communications, and regulatory records. A vendor's security questionnaire isn't a substitute for third-party attestation. Here's what the Type II designation actually tells you.
Every issuance, acknowledgment, reminder, and release in Citelock is written to an append-only event log. Here is exactly what that log records, how it is protected from tampering, and how you export it for counsel or opposing parties.