Build a litigation hold runbook: triggers, custodian identification, preservation…
- User
Build a litigation hold runbook: triggers, custodian identification, preservation notices, and release process.
- Assistant
Litigation Hold Runbook
1. Purpose
This runbook provides a standardized process for implementing, managing, and releasing litigation holds (also known as legal holds) to preserve relevant electronically stored information (ESI) and physical records in anticipation of or during litigation, investigations, regulatory inquiries, or audits. Compliance ensures defensibility, avoids spoliation sanctions, and minimizes risk.
Key Principles:
- Preserve all potentially relevant data "as is" – no deletion, alteration, or overwriting.
- Scope: Emails, documents, chats, databases, cloud storage, devices, etc.
- Legal team owns the hold; IT/Records Management executes technically.
2. Roles and Responsibilities
Role Responsibilities Legal Department Trigger holds, identify custodians, draft/issue notices, monitor compliance, authorize release. IT/Information Governance Suspend auto-deletion, collect/secure data, track holds, provide reports. Department Leads/HR Assist in custodian identification, distribute notices internally. Custodians Preserve data, acknowledge notices, report issues. Compliance Officer Oversee process, audit compliance. 3. Triggers for Litigation Hold
Initiate a hold immediately upon any of the following (notify Legal within 24 hours):
- Lawsuit/Service of Process: Complaint, summons, or notice of claim received.
- Government Inquiry: Subpoena, CID, grand jury subpoena, audit notice.
- Internal Investigation: Triggered by whistleblower, ethics hotline, or executive directive.
- Anticipated Litigation: Threatened suit, demand letter, or board directive.
- Regulatory/Compliance Events: Data subject request (e.g., GDPR), merger scrutiny.
- Data Breach/Incident: If litigation risk exists.
Process on Trigger:
- Legal assesses scope (matter ID, keywords, date range).
- Create hold record in tracking system (e.g., Matter #LH-YYYY-###).
- Notify IT/Compliance within 1 business day.
4. Custodian Identification
Identify custodians within 48 hours of trigger. Custodians are individuals with custody/control of potentially relevant data.
Steps:
- Initial Review (Legal): Review triggering documents for names, roles, departments.
- Keyword/Organizational Mapping:
Criteria Examples Named Parties Plaintiffs, defendants, witnesses. Involved Roles Project leads, executives, HR for employee matters. Departments Sales for contract disputes; IT for data breaches. Data Sources Email aliases, shared drives, Slack channels. - Interviews/Questionnaires: Send to key stakeholders: "Who else was involved? What systems used?"
- Data Mapping Tools: Use eDiscovery tools (e.g., Relativity, Everlaw) for custodian reports.
- Expand as Needed: Iterative; add custodians if new info emerges.
- Cap at Viable Number: Prioritize top 20-50; use proportionality.
Output: Custodian list with contact info, roles, data sources (e.g., email, laptop, OneDrive).
5. Preservation Notices
Issue notices within 72 hours of trigger. Two-tiered: Initial (quick) and Detailed (formal).
5.1 Initial Notice (Email – Template Below)
- Sent by Legal to custodians via tracked email.
- CC: Department lead, IT.
Template: Initial Preservation Notice
Subject: URGENT LEGAL HOLD – Matter [Matter ID/Description] – PRESERVE ALL DATA Dear [Custodian], You are required to IMMEDIATELY preserve all records related to [brief description, e.g., "Project X contract dispute from 2022-2024"]. WHAT TO PRESERVE: - Emails, docs, chats (incl. deleted items). - Devices: Laptop, phone, external drives. - DO NOT delete, alter, or overwrite. Stop personal deletions. Acknowledge receipt by replying ALL within 24 hours. Detailed notice follows. Legal Team [Contact Info]5.2 Detailed Preservation Notice (Formal Letter – Template Below)
- Sent via certified mail/email with read receipt.
- Includes scope, duration, escalation.
Template: Detailed Preservation Notice
[Legal Letterhead] Re: Litigation Hold Notice – Matter [ID/Description] Dear [Custodian], Pursuant to [trigger, e.g., FRCP 37(e)], you must preserve all relevant ESI and records. SCOPE: - Timeframe: [e.g., Jan 1, 2022 – present]. - Keywords/Topics: [list]. - Sources: [email, Slack, SharePoint, etc.]. INSTRUCTIONS: 1. Suspend auto-delete on all accounts. 2. Identify/search for data. 3. Forward to IT for collection if requested. 4. Report any issues to [Legal contact]. Duration: Until released in writing. Violation may result in sanctions. Acknowledge: Sign and return attached form within 5 days. Sincerely, [Legal Counsel]Tracking:
- Use spreadsheet/tool: Custodian, Date Sent, Acknowledgment Date, Compliance Notes.
- Follow-up: 48 hours if no ack; escalate to manager.
5.3 Technical Actions (IT)
- Suspend backups/deletion policies for custodians.
- Quarantine data if high-risk.
- Log all actions for audit trail.
6. Monitoring and Compliance
- Quarterly Check-Ins: Legal surveys custodians.
- Reporting: Monthly hold status to executives.
- Audits: Annual review of holds >1 year.
- Escalation: Non-compliance → Manager notification → Discipline.
7. Release Process
Lift hold only when risk ends. Goal: Release within 30 days post-resolution.
Triggers for Release:
- Case dismissal/settlement.
- Investigation closed.
- Court order.
- Legal determination no further risk.
Steps:
- Legal Review: Confirm all collections complete, no appeals.
- Release Notice (Template Below): Sent to all custodians.
- IT Confirmation: Resume normal deletion policies.
- Archive Hold File: Retain for 7 years.
Template: Release Notice
Subject: LITIGATION HOLD RELEASE – Matter [ID] Dear [Custodian], The legal hold for [description] is LIFTED effective [date]. - Resume normal data management. - Questions? Contact Legal. Thank you, Legal TeamPost-Release:
- Update tracking system.
- Notify executives of closed holds.
8. Appendices
- Acknowledgment Form: Signed PDF confirming receipt/understanding.
- Escalation Matrix: Level 1: Email reminder; Level 2: Manager call; Level 3: HR.
- Tools: [e.g., Microsoft Purview, OpenText eDiscovery].
- Training: Annual for employees; simulate drills.
Version: 1.0 | Last Updated: [Date] | Review Annually
This runbook is a template; customize to your organization's policies and consult counsel.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.