1---2name: assess-litigation-hold-scope-for-custodian-identification3task_id: litigation-dispute-resolution/assess-litigation-hold-scope-for-custodian-identification4description: A litigation hold memo should identify likely custodians of potentially relevant information, map the principal sources of their data, and flag preservation risks such as auto-deletion, off-boarding, or system migrations that may affect collection.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/assess-litigation-hold-scope-for-custodian-identification8---910# Skill: Assess Litigation Hold Scope for Custodian Identification — Custodian Recommendation Memorandum1112## 1. Subject-matter triage13- Treat the record set as a preservation-assessment problem: identify who likely has relevant information, where that information lives, and what could cause it to disappear before collection.14- Start from the trigger materials to fix the preservation onset and the subject-matter boundary of the hold.15- If the materials point to multiple groups, time periods, systems, or entities, enumerate them first and analyze each separately rather than collapsing them into a single generalized hold scope.16- Distinguish between likely custodians, data stewards, and third parties; each may require a different preservation step.1718## 2. Failure modes the skill is correcting19- Limiting custodians to named parties and missing decision-makers, operational personnel, communications personnel, IT personnel, and other data owners with non-duplicative information.20- Naming custodians without tying them to concrete sources, so the hold cannot be implemented in practice.21- Ignoring retention settings, auto-deletion, migrations, device turnover, or off-boarding that can destroy relevant ESI before collection.22- Failing to coordinate with business and IT teams on preservation steps, especially for departing employees and shared systems.23- Overlooking outside holders of relevant materials, including vendors, consultants, and other counterparties who may need separate notice.24- Stating preservation conclusions without identifying the governing duty to preserve or the authorities that support the action.2526## 3. Legal frameworks / domain conventions that apply27- The duty to preserve arises when litigation is reasonably anticipated; in practice, that may occur before suit is filed after a demand, dispute escalation, internal claim assessment, or regulatory inquiry.28- Preservation analysis should be tied to relevance and proportionality, using the dispute themes, known actors, and document systems in the source materials as the scope boundary.29- Custodian identification should prioritize people with firsthand knowledge, approval authority, operational responsibility, or communications about the disputed conduct.30- Common source categories include corporate email, chat and collaboration tools, cloud storage, shared drives, mobile devices, enterprise applications, and paper files.31- Departing or terminated employees require prompt preservation coordination because device return, account closure, and record transfer can create spoliation risk.32- Third-party preservation may be necessary where vendors, consultants, or partners hold unique information.33- Preservation failures can trigger sanctions under the court’s inherent authority and the federal ESI framework, including Federal Rule of Civil Procedure 37(e) where electronically stored information is lost.34- The memo should reflect the applicable retention and hold controls identified in the materials, including any corporate records policy, IT hold protocol, or account-suspension process.35- When citing a legal proposition, name the controlling rule, statute, regulation, or recognized authority rather than stating the conclusion abstractly.3637## 4. Analytical scaffolds38- Build the hold scope from four linked questions: who knows, what they used, where it sits, and what could delete it.39- For each likely custodian, record name if known, role/title, why the person matters, likely data sources, and the immediate preservation steps needed.40- Separate custodians into practical categories such as leadership/decision-makers, operational participants, communications participants, IT/data stewards, and outside holders.41- For each category, identify whether the person is active, departed, or likely to depart soon, and adjust the preservation recommendation accordingly.42- Review system and records materials for hold-relevant controls: auto-delete settings, retention overrides, backup limitations, migration schedules, and account deactivation workflows.43- Identify whether forensic imaging, export, or suspension of deletion should occur before ordinary collection.44- If a source document names a specific legal or policy authority for preservation, use that authority; otherwise anchor the recommendation in the general duty to preserve and standard ESI preservation practice.45- Convert each risk into an action: issue notice, suspend deletion, preserve devices, coordinate with IT, confirm receipt, or extend notice to a third party.4647## 5. Vertical / structural / temporal relationships48- Structure the memo by custodian category first, then individual custodian or holder within each category.49- For each entry, move from role to source systems to risk to required action so the reader can implement the hold without inference.50- Track temporal sensitivity explicitly: immediate actions for departing employees or expiring systems, near-term actions for active custodians, and follow-up actions for third parties.51- Where systems interact, note dependencies, such as account deactivation affecting email retention or migrations affecting shared-drive integrity.52- Where one custodian’s information overlaps with another’s, identify the overlap so the preservation plan avoids gaps and redundant steps.5354## 6. Output structure conventions55- Prepare the document as a litigation hold memorandum suitable for external circulation or internal approval.56- Use conventional memo headings rather than a rigid rubric-derived checklist; keep the presentation operational and implementation-oriented.57- Include a short opening that states the preservation trigger, the hold purpose, and the scope assumptions.58- Include a custodian analysis section with one entry per identified custodian or holder, each entry covering role, rationale, data sources, and immediate preservation actions.59- Include a systems and records section addressing deletion controls, backups, migrations, device management, and off-boarding risks.60- Include a third-party preservation section where outside holders of relevant information are identified.61- End with a concise action plan that assigns responsibility to counsel, business leads, or IT and gives a timing anchor tied to the urgency shown in the materials.62- Keep the output aligned to the required file name: `litigation-hold-memo.docx`.