Generate Litigation Hold Notice
Skill: Convert matter facts into a court-defensible litigation hold notice
Region: United States Category: Legal / eDiscovery Does: Takes the trigger facts of a dispute and a custodian roster and generates a structured litigation hold (legal hold) notice — the preservation directive that suspends routine deletion and instructs custodians to preserve relevant ESI, scoped to meet the FRCP 37(e) spoliation-avoidance standard. Authority: FRCP 37(e) · Zubulake v. UBS Warburg (SDNY 2004) · The Sedona Principles, 3rd ed. (2017)
The duty to preserve attaches when litigation is reasonably anticipated — often before a complaint is filed. The hold notice is the primary defensible record that the duty was met; FRCP 37(e) lets a court impose sanctions (up to an adverse-inference instruction) for ESI lost through failure to take reasonable preservation steps. This produces the notice and tracking structure; legal counsel owns scope and timing decisions.
When this applies
- A complaint, demand letter, government inquiry, or any credible indication of a dispute makes litigation reasonably anticipated → the preservation duty triggers and a hold should issue promptly.
- Holds are living: new custodians get added, the matter scope evolves, and the hold is released only when the matter and any appeal/limitations period closes.
Input data required
| Group | Fields |
|---|---|
| Matter | matter name/number, trigger event + date, anticipated claims, preservation duty date |
| Legal basis | brief statement of the dispute and why preservation is required (privileged-but-discoverable framing) |
| Custodians | name, role, department, email, manager; relationship to the issues |
| Scope | in-scope data types (email, files, chat/Teams/Slack, texts, voicemail, databases, physical docs), date range, key topics/terms |
| Sources | systems and devices per custodian (laptop, mailbox, shared drives, phone, cloud apps) |
| IT actions | auto-deletion/retention suspensions, journaling, mailbox holds to apply |
| Process | acknowledgment requirement, reminder cadence, escalation contact |
Notice structure
1. Subject + CONFIDENTIAL / ATTORNEY WORK PRODUCT header
2. Purpose — a legal matter requires you to preserve information
3. Trigger & scope — what the matter is about; date range; topics
4. What to preserve — in-scope data types and example sources (non-exhaustive)
5. Affirmative duties — DO NOT delete, alter, overwrite, or move in-scope ESI;
suspend auto-delete / do-not-disturb retention; preserve devices
6. Specific instructions — mailboxes, drives, chat, texts, removable media, cloud
7. Questions / contact — named in-house or outside counsel contact
8. Acknowledgment — required confirmation, with a deadline
9. Consequences — preservation is mandatory; failure can harm the company and the individual
Drafting rules
- Scope to the matter, not the world: identify in-scope data types, a defined date range, and the topics/issues — over-broad holds are unenforceable in practice and under-broad holds risk spoliation. Iterate scope with counsel.
- Plain, directive language: custodians are non-lawyers; the affirmative "do not delete / suspend auto-deletion / preserve your device" instructions must be unambiguous.
- Pair the notice with IT/system holds: custodian self-preservation alone is not "reasonable steps" for systems with auto-deletion — record the journaling/retention-suspension/in-place hold actions applied centrally (Microsoft Purview, Google Vault, archive).
- Track acknowledgments and send periodic reminders; document new-custodian additions and the eventual release notice. The audit trail is the defense to a future spoliation motion.
- Mark the notice privileged / work product, but write it expecting it may be discoverable on a preservation challenge.
Worked example (outline)
Matter: Acme Corp v. Beta LLC — breach of supply contract (Matter 2025-014)
Trigger: Demand letter received 2025-03-01 → duty to preserve as of 2025-03-01
Date range: 2023-01-01 → present
Topics: Beta supply agreement, pricing disputes, delivery delays, related emails/chats
Custodians: J. Doe (VP Procurement), R. Roe (Contracts Mgr), team distribution list
Data types: Outlook mail + calendar, OneDrive/SharePoint, Teams chat, mobile texts, contract DB
IT actions: Purview In-Place Hold on the 3 mailboxes + Teams; suspend 90-day auto-delete
Acknowledge: Reply-to-confirm within 5 business days; reminders at 30/60 days
This becomes a complete hold notice (sections 1–9) plus an acknowledgment-tracking row per custodian.
Validation checklist
- Trigger event and preservation-duty date identified; hold issued promptly thereafter
- In-scope data types, date range, and topics defined with counsel (not over/under-broad)
- All known custodians listed with role and contact; method to add custodians later
- Affirmative "do not delete / suspend auto-deletion / preserve device" instructions in plain language
- Modern sources covered (email, files, chat/Teams/Slack, mobile texts, cloud apps, databases)
- Central IT/system holds (Purview/Vault/archive) recorded — not custodian self-preservation alone
- Acknowledgment required with a deadline; reminder cadence and escalation set
- Marked privileged/work product; release process defined for matter close
Last updated: 2026-05-31 — this generates a hold notice and tracking structure; scope, timing, and release are legal judgments. Confirm against current FRCP 37(e), controlling case law in your jurisdiction, and the Sedona Principles before issuing.