1---2name: draft-discovery-plan-memorandum3task_id: litigation-dispute-resolution/draft-discovery-plan-memorandum4description: A Rule 26(f) discovery plan memorandum should map claims and defenses to discoverable evidence categories, identify custodians and data sources, assess litigation-hold adequacy and any spoliation risks, and propose ESI and discovery protocols for the conference.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/draft-discovery-plan-memorandum8---910# Skill: Draft Discovery Plan Memorandum for Breach of Contract and Fraud Defense1112## 1. Subject-matter triage1314- Treat this as a pre-conference litigation planning memo, not a merits brief.15- Start from the pleadings, disclosures, and file materials to identify what must be proved, what must be disproved, and what can be obtained efficiently.16- If the file contains multiple claims, defenses, counterclaims, or custodians, enumerate them before analysis and assign each a separate discovery lane.17- Flag immediately any preservation, collection, privilege, confidentiality, or timing issue that could affect the Rule 26(f) conference.1819## 2. Failure modes the skill is correcting2021- Listing generic discovery topics without tying each topic to a claim element, defense element, or damages theory.22- Naming custodians without identifying the systems, repositories, and third-party channels likely to hold responsive data.23- Missing preservation problems, including delayed hold issuance, incomplete implementation, or gaps between the preservation trigger and actual compliance.24- Treating ESI logistics as boilerplate instead of proposing concrete production, search, deduplication, privilege, and format terms.25- Failing to surface proportionality limits, inaccessible sources, or sequencing concerns that should shape the conference position.26- Writing a memo that describes issues but does not convert them into concrete proposals and next steps.2728## 3. Legal frameworks / domain conventions that apply2930- Rule 26(f): the parties must confer in good faith and develop a discovery plan addressing preservation, ESI, privilege, protection, and scheduling.31- Rule 26(a)(1): initial disclosures frame the baseline universe of people, documents, damages, and insurance materials.32- Rule 26(b)(1): discovery must be relevant and proportional to the needs of the case.33- Rule 26(b)(2)(B): inaccessible sources may be limited where the burden or expense is undue.34- Rule 37(e): preservation failures involving ESI can create serious sanctions exposure if reasonable steps were not taken.35- Rule 502(d) of the Federal Rules of Evidence: a clawback order can reduce inadvertent-waiver risk.36- Rule 26(c): protective orders should address confidentiality, use restrictions, and challenge procedures.37- If the source materials identify a governing authority, use it; otherwise cite the applicable Federal Rules and standard discovery practice directly.38- Do not state preservation, privilege, or proportionality conclusions without tying them to the governing rule.3940## 4. Analytical scaffolds4142- Build a claims-to-evidence map:43 - identify each claim, counterclaim, and affirmative defense;44 - isolate the elements or factual propositions that matter;45 - list the document, testimony, ESI, and third-party evidence needed for each.46- Build a custodian-and-source inventory:47 - separate decision-makers, operational personnel, finance personnel, technical personnel, and outside actors;48 - for each custodian, identify likely repositories such as email, messaging, shared drives, cloud storage, ERP/CRM systems, mobile devices, and paper files;49 - note where collection can be centralized and where it must be targeted.50- Review preservation timing:51 - identify the preservation trigger from the dispute timeline;52 - compare it to hold issuance and implementation dates;53 - note any gaps, missing acknowledgments, deleted data risk, or backup retention issues.54- Assess source accessibility and burden:55 - distinguish active, readily searchable systems from legacy, archived, or other harder-to-access sources;56 - note whether phased discovery, sampling, or search-term testing is appropriate.57- Design ESI protocols:58 - propose production format, metadata fields, native or near-native treatment where needed, Bates handling, deduplication, and family-level grouping;59 - recommend a defensible search methodology with an iterative validation step;60 - include privilege review and clawback mechanics.61- Address confidentiality and case management:62 - propose a protective order structure if sensitive business, personal, or technical information is likely to be exchanged;63 - identify whether a staged schedule, phased discovery, or discovery priorities would make the plan more efficient.64- If a source document provides dates, volumes, categories, or other hard facts, use them to anchor the memo; if not, state the need to confirm them through the conference process rather than inventing them.6566## 5. Vertical / structural / temporal relationships6768- Show how alleged breach conduct, fraud allegations, notice, reliance, damages, and mitigation relate to the discovery sequence.69- Separate pre-dispute, dispute-onset, notice, hold, collection, review, and production phases so timing risks are visible.70- Where the dispute spans business units, affiliates, or systems, explain which records sit upstream, which are transactional, and which are custodial.71- Make clear when one category of evidence depends on another, such as damages discovery following liability-focused collections or fraud-related intent evidence depending on communications and drafts.72- If there are multiple custodians or source types, present them in a structured inventory before drawing conclusions.7374## 6. Output structure conventions7576- Use an industry-standard memorandum shape with clear headings that cover:77 - claims and defenses mapped to evidence needs;78 - custodians and data sources;79 - preservation and litigation-hold assessment;80 - ESI collection and production proposals;81 - privilege, clawback, and protective-order proposals;82 - proposed discovery sequencing and conference positions.83- Keep the tone practical and conference-ready: identify issues, then state what the party should propose.84- Use an ordinal severity label only if you are also flagging issues for immediate attention; apply it consistently and define it once.85- End with a concise recommended-actions section that assigns each action to a role and ties it to the Rule 26(f) timing or another concrete milestone.86- Match the final document filename exactly to the task instruction: `discovery-plan-memorandum.docx`.