Draft Litigation Hold Notice

Skill: Litigation Hold Notice and Preservation Action-Items Memo

1. Subject-matter triage

• Treat the task as a two-document preservation package: a custodian-facing litigation hold notice and a separate IT/records preservation action-items memo.
• Identify the triggering matter, the preservation duty window, all relevant custodians, and all data sources before drafting either document.
• If the source materials suggest international custodians, foreign-hosted data, mobile devices, cloud systems, or scheduled deletion, elevate those items early in the preservation plan.

2. Failure modes the skill is correcting

• Drafts address employees generally but fail to create a separate operational memo that gives IT and records teams concrete preservation steps, owners, and deadlines.
• Drafts instruct custodians to “preserve documents” but omit platform-level holds, retention freezes, and vendor-side suspension steps for cloud and third-party systems.
• Drafts delay device preservation until after ordinary coordination, even when devices are exposed to removal, tampering, reassignment, or travel.
• Drafts ignore foreign privacy and transfer constraints when preservation reaches custodians or data outside the primary forum.
• Drafts recite preservation concepts without mapping them to the actual systems, custodians, and timelines in the source file set.
• Drafts fail to separate legal advice from operational instructions, causing confusion over who must act and by when.
• Drafts omit privilege markings and other conventions that signal attorney-client and work-product treatment.

3. Legal frameworks / domain conventions that apply

• Duty to preserve: Once litigation is reasonably anticipated, preservation obligations attach under the governing litigation-hold and spoliation doctrine recognized in the forum. Anchor the notice to the event that made litigation foreseeable, not merely to filed pleadings.
• Spoliation risk: The hold should address routine deletion, overwriting, migration, recycling, and device replacement that can destroy relevant evidence.
• Custodian-directed notice: A valid notice should identify the matter, the categories of likely relevant information, the date range, the preservation instructions, the prohibition on deletion or alteration, and the contact for questions.
• IT and records implementation: Operational preservation requires more than custodian notice; administrators must disable auto-delete, place holds in enterprise systems, preserve backup or archive workflows as needed, and document completion.
• Cloud and third-party systems: Cloud email, collaboration tools, file repositories, messaging platforms, and vendor-hosted archives often require administrator-side legal hold actions under the provider’s own controls and retention settings.
• Forensic preservation: When a device is exposed to loss, reassignment, travel, repair, confiscation, or tampering, emergency forensic imaging is the preferred preservation step and should be prioritized over ordinary collection.
• Cross-border data handling: Where preservation implicates personal data of individuals outside the primary forum, assess collection and transfer constraints under applicable data-protection law and involve local counsel before cross-border transfer if needed.
• Privilege and work product: Both documents should be marked and drafted as privileged attorney-client communications and attorney work product to the extent supported by the facts and governing law.

4. Analytical scaffolds

• Trigger analysis: State the event or sequence that made litigation reasonably anticipated and use that as the anchor for the preservation obligation.
• Custodian map: Build a complete custodian list from the source files, including the subject matter owner, direct supervisors, witnesses, assistants, IT administrators, records personnel, and anyone likely to hold responsive communications.
• Data-source inventory: Identify every plausible repository of relevant information: email, shared drives, collaboration platforms, messaging tools, HR files, devices, local files, cloud storage, archives, backup systems, and paper records.
• Preservation scope: Define the document categories, communications, and date range in practical terms so custodians can act without needing legal interpretation.
• System-specific action items: Translate preservation obligations into discrete steps for each system owner, including legal hold placement, retention freeze, export/collection where appropriate, and confirmation back to counsel.
• Urgency sorting: Separate immediate device-imaging or hold steps from standard preservation tasks; do not bury time-sensitive actions in a general list.
• Cross-border screen: Flag foreign custodians, foreign-hosted systems, and international transfer issues; determine whether local privacy review is needed before collection or transfer.
• Destruction-cycle review: Look for ordinary retention runs, auto-purge rules, device refresh, offboarding, or vendor rotation cycles that could erase relevant materials before the hold takes effect.
• Acknowledgment mechanics: Include a practical acknowledgment or compliance-confirmation mechanism so counsel can verify receipt and implementation.

5. Vertical / structural / temporal relationships

• Two-document architecture: The custodian notice and the preservation action-items memo should be distinct documents with different audiences, but consistent scope and terminology.
• Priority sequencing: Emergency imaging and platform holds should occur before or at the same time as custodian circulation when delay would increase spoliation risk.
• Role separation: The custodian notice should tell people what to preserve and not to delete; the operational memo should tell administrators how to preserve it.
• Temporal precision: Use relative or fixed deadlines tied to the matter’s urgency, device risk, or system ownership, and distinguish immediate steps from follow-up validation.
• Cross-jurisdiction sequencing: Where foreign privacy issues exist, identify them before collection or transfer, not after data has already been moved.

6. Output structure conventions

• Document one: Litigation hold notice. Draft as a formal privileged memorandum or notice to custodians. Include the matter description, why litigation is anticipated, the preservation duty, the scope of materials and systems, the prohibition on deletion or alteration, the duty to preserve devices and documents, the contact person, and an acknowledgment request.
• Document two: Preservation action-items memo. Draft as a privileged operational memo to IT, records, and other technical owners. Organize by urgency and owner. For each action item, state the responsible role, the specific preservation step, and the deadline or urgency level.
• Use implementation language. Prefer instructions that can be executed directly by administrators, such as placing holds, disabling retention rules, suspending overwrite cycles, preserving inboxes and shared drives, and initiating forensic imaging where required.
• Separate legal framing from technical execution. Do not let the custodian notice become a systems checklist, and do not let the technical memo omit the legal rationale for the hold.
• If foreign data issues exist, add a short consultation instruction. Direct the relevant team to coordinate with local counsel before cross-border collection or transfer.
• If a device is at risk, elevate it visibly. Put emergency imaging or seizure-preservation steps first so they cannot be overlooked.
• Mark both documents privileged. Use a clear privilege/work-product designation consistent with the source materials and firm practice.