Build a litigation hold runbook: triggers, custodian identification, preservation…
- User
Build a litigation hold runbook: triggers, custodian identification, preservation notices, and release process.
Assistant
The user wants a "Litigation Hold Runbook." A runbook needs to be actionable, structured, and comprehensive. The specific components requested are:
- Triggers (When to start).
- Custodian Identification (Who is involved).
- Preservation Notices (The formal communication).
- Release Process (When to end).
Target Audience: Legal Operations, General Counsel, IT, Compliance, HR. The tone should be professional, procedural, and authoritative but easy to follow.
Structure of the Runbook:
- Header/Metadata: Purpose, Scope, Owner.
- Phase 1: Trigger & Assessment: Defining the "Triggering Event."
- Phase 2: Scoping & Custodian Identification: Who has the data?
- Phase 3: Issuance & Preservation (The "Hold"): Drafting and sending notices.
- Phase 4: Monitoring & Compliance: Ensuring people actually do it.
- Phase 5: Release: Ending the hold.
- Appendix/Templates: To make it a real tool.
Drafting Content - Section by Section:
-
Phase 1: Triggers
- Need to define "Reasonable anticipation of litigation."
- Examples: Demand letters, subpoena, government investigation, employee termination (sometimes), significant contract breach.
- Action: "Intake Interview" to assess duty to preserve.
-
Phase 2: Custodians & Data Sources
- Who? (Key players, supervisors, IT admins).
- What? (Email, Slack/Teams, shared drives, cloud storage, physical docs, phones/texts).
- Crucial Step: The "Data Map" concept (even a simple one).
-
Phase 3: The Notice
- This is the core output.
- What goes in the letter? Explanation of the matter, specific instructions (don't delete), scope (date range/topics), and contact info.
- Method: Email + Read Receipts + Acknowledgement form.
-
Phase 4: Preservation (Technical)
- It's not just a letter; IT needs to act.
- Stop auto-deletion (this is a big one for legal holds).
- Freeze mailboxes (Litigation Hold in M365/Google).
- Image hard drives if necessary.
-
Phase 5: Release
- Often overlooked.
- Trigger: Case settled, dismissed, or investigation closed.
- Process: Notify custodians they can go back to normal. Delete preserved data only if it was created solely for the hold (careful here with retention policies).
Refining the Content:
- Formatting: Use bolding, lists, and clear headers.
- Tone: Professional, step-by-step.
- Key Terminology: Spoliation, Custodian, ESI (Electronically Stored Information).
Self-Correction/Review during drafting:
- Initial thought: Should I include eDiscovery collection?
- Correction: The user asked for a Litigation Hold runbook, not a full eDiscovery workflow. Keep collection distinct (usually the next step after the hold is in place), but mention that the hold protects data for future collection.
- Emphasis: Make sure to mention the "legal hold software" aspect vs. manual spreadsheets, as modern companies often use tools like Relativity One, Zapproved, etc.
Final Polish:
- Add a disclaimer that this isn't legal advice.
- Create a clear "Lifecycle" visualization (text-based).
Let's write the runbook. (Proceeding to generate the structured response based on these steps). This Litigation Hold Runbook provides a standardized workflow for legal teams to fulfill their duty to preserve relevant Electronically Stored Information (ESI) and physical documents when litigation or an investigation is reasonably anticipated.
Litigation Hold Runbook
Objective: Establish a defensible process to identify, preserve, and collect relevant data, minimizing the risk of spoliation (destruction of evidence) and sanctions.
Owner: Legal Department (General Counsel/Litigation Support) Stakeholders: IT, HR, Records Management, Key Business Units
Phase 1: Trigger & Assessment
Goal: Determine if a "litigation hold" is required based on the "reasonable anticipation of litigation."
1.1 Common Trigger Events
- Formal: Receipt of a demand letter, subpoena, complaint, or government inquiry.
- Informal: Verbal threats of litigation from a significant partner/vendor, internal complaints of harassment/discrimination, or a significant data breach.
- Operational: Notice of a whistleblower claim or significant regulatory audit.
1.2 Initial Triage (The "Preservation Interview")
Before issuing a hold, conduct a brief interview with the business owner of the relevant department to answer:
- What is the core dispute about?
- When did the relevant events occur (date range)?
- Who are the key players involved (custodians)?
- Where is the data likely stored?
Phase 2: Custodian Identification & Data Mapping
Goal: Identify all potential "Custodians" (individuals with control over relevant data) and the systems they use.
2.1 Identify Custodians
Create a list of individuals fitting the following criteria:
- Primary: Direct participants in the dispute (e.g., the fired employee, the project manager).
- Secondary: Supervisors, HR representatives handling the file, direct reports.
- IT/Tech: System administrators who maintain relevant server logs or backups (often treated as a "System Custodian").
2.2 Identify Data Sources (The Scope)
Identify where these custodians store data.
- Standard: Email (O365/Gmail), Network Drives (SharePoint/Box), Local Hard Drives.
- Modern: Slack/Teams, Mobile devices (SMS/WhatsApp), Cloud apps (Salesforce, Jira).
- Physical: Paper files in desk drawers, printed contracts, notebooks.
2.3 Action Item: IT Preservation Request
Issue a "Tech Hold" to IT immediately upon triggering.
- Action: Suspend automatic deletion policies (e.g., 30-day email trash deletion, auto-archiving) for the identified custodians.
- Action: Preserve backup tapes relevant to the date range (do not overwrite).
Phase 3: Preservation Notices (The "Legal Hold")
Goal: Formally notify custodians of their obligation to preserve evidence.
3.1 The Notice Workflow
- Drafting: Customize the template hold notice. It must be specific enough to be understood but broad enough to cover the scope.
- Review: Have outside counsel (if retained) review the scope.
- Issuance: Send via email with a read-receipt or through a Legal Hold Management software (e.g., Relativity, Zapproved, Exterro).
3.2 Notice Content Requirements
The notice must clearly state:
- The Matter: Brief description of the lawsuit/investigation.
- The Obligation: Federal/State rules requiring preservation.
- The Action: DO NOT DELETE, SHRED, or ALTER any relevant data.
- The Scope: Specific date ranges and key search terms (if known).
- The Contact: Who to ask for help (Paralegal/Inside Counsel).
3.3 The "Litigation Hold Questionnaire"
Attach a short survey to the notice asking custodians to confirm:
- I have read the notice.
- I understand the instructions.
- I have data in the following non-standard locations: (e.g., Personal Dropbox, Home Computer).
Phase 4: Monitoring & Compliance
Goal: Ensure custodians are actually preserving data.
4.1 Acknowledgement Tracking
- T + 24 Hours: Custodian opens email.
- T + 48 Hours: If no acknowledgement is received, send an automated reminder.
- T + 72 Hours: If still no response, escalate to the custodian’s manager.
4.2 The "Exit Interview" (for departing employees)
If a custodian under a legal hold resigns or is terminated:
- HR/Legal must intervene before IT deactivates accounts.
- Collect a forensic image of the hard drive.
- Export email to a PST/Mbox file.
- Do not wipe the machine until the image is verified.
Phase 5: Release Process
Goal: Release the hold and restore normal data governance procedures when the duty to preserve ends.
5.1 Trigger for Release
- Settlement agreement signed.
- Court dismissal (and statute of limitations expired).
- Final judgment entered and appeals period exhausted.
5.2 The Release Workflow
- Draft Release Notice: Inform custodians that the hold is lifted. Instruct them they may resume normal deletion practices (but are not required to delete).
- Notify IT: Inform IT to re-enable auto-deletion policies for the specific custodians.
- Data Disposition:
- If data was collected and stored in a "Legal Hold Repository," confirm with outside counsel whether it should be destroyed or retained for business purposes.
- Crucial: Do not delete backup tapes if they are subject to retention schedules for other reasons.
Appendix: Templates
A. Custodian Acknowledgement Form
Subject: IMPORTANT: Legal Hold Notice - [Matter Name]
I, [Custodian Name], acknowledge receipt of the Litigation Hold Notice regarding [Matter Name]. I understand my obligation to preserve all documents, emails, and electronic files related to [Scope/Keywords]. I agree not to delete, modify, or destroy any such information until further notice.
[ ] I have relevant data. [ ] I do not have relevant data.
B. IT Preservation Ticket Template
Ticket Type: Legal Hold Preservation Priority: High Affected Users: [List of Email Addresses] Action Required:
- Place mailboxes on "Litigation Hold" (Stop Journaling/Deletion).
- Preserve home directory drives on Server X.
- Suspend overwrite of Backup Tape #452. Date Range: [Start Date] to [End Date]
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.