# Discovery Production Gap Analysis

> Production gap analysis memorandum comparing document production against discovery request specifications, assessing the merits of each objection, identifying privilege log deficiencies, and recommending remediation to bring production into compliance.

- Skill: `finchipaiorg/discovery-production-gap-analysis` (Agent Skill)
- Install (CLI): `npx skillmds@latest add finchipaiorg/discovery-production-gap-analysis`
- Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/discovery-production-gap-analysis/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/finchipaiorg/discovery-production-gap-analysis

---


# Skill: Document Production Gap Analysis vs. Discovery Request Specifications

## 1. Subject-matter triage

- Identify the governing production record first: requests, deficiency correspondence, privilege log, production log, ESI protocol, clawback order, and any rolling supplementation notices.
- Separate asserted deficiencies into: missing production, overbroad objections, privilege-log defects, custodial gaps, format/metadata noncompliance, inadvertent production, and coding/logging errors.
- Enumerate each deficiency item and each self-identified issue before analysis; if only one item exists, say so expressly and explain why no broader set is in scope.
- Confirm the response deadline immediately and treat it as a live constraint on every recommendation.

## 2. Failure modes the skill is correcting

- Conceding a deficiency without testing whether the request actually reaches the withheld material, whether the objection is supported, and whether a narrower cure would suffice.
- Reviewing only the government-identified defects and missing obvious self-correctable production issues that will draw a second challenge.
- Treating litigation hold notices as categorically privileged without testing whether they are directive, factual, or reflective of legal advice.
- Accepting a work-product claim for ordinary-course compliance or regulatory materials without asking whether anticipation of litigation was the primary purpose of creation.
- Failing to scrutinize privilege logs for enough detail to evaluate the claim, which risks waiver and downstream production.
- Leaving date-range objections untested against the origin date of the underlying obligation or document category.
- Overlooking omitted custodians, protocol departures, or logging/coding errors that can be cured by supplemental collection or corrected metadata.
- Failing to identify what should be produced, what should be logged, what should be supplemented, and what can be defended.

## 3. Legal frameworks / domain conventions that apply

- Discovery scope: apply the governing civil discovery rules on relevance, proportionality, and responsive production; objections to entire categories must be narrow and supported.
- Work product doctrine: apply the governing rule protecting materials prepared in anticipation of litigation; ordinary-course documents are not protected merely because they later become useful in litigation.
- Attorney-client privilege: apply the controlling privilege rule requiring confidential legal advice communication; factual or ministerial notices may not qualify.
- Privilege log sufficiency: the log must permit assessment of the claim without revealing the privileged communication; include date, author, recipients, document type, privilege basis, and a meaningful subject description.
- Clawback / inadvertent production: follow any court order or agreed procedure governing return, sequester, or logging of inadvertently produced privileged material.
- ESI protocol compliance: check whether the production matches agreed format, metadata, load file, deduplication, and search/processing requirements.
- Custodian collection: relevant custodians identified in pleadings, interviews, or documents should ordinarily be in scope unless a defensible limitation exists.
- Date limits: pre-litigation documents can still be discoverable where the obligation, transaction, or compliance issue predates the suit.
- The analysis should cite the controlling authority relied on for each legal proposition, whether from the source record or general discovery doctrine.

## 4. Analytical scaffolds

- For each asserted deficiency:
  - state the requesting party’s position;
  - state the legal merit of the objection or criticism;
  - state the practical cure;
  - state the litigation or compliance consequence if uncured.
- Use a uniform ordinal severity scale for every issue, such as Critical / High / Medium / Low, and define the scale once at the top of the memo.
- For each issue, tie the concern to:
  - the volume or scope described in the source record;
  - any interacting request, log entry, protocol term, or prior production;
  - the downstream risk to the client, including waiver, sanctions, follow-on demands, or credibility harm.
- Treat litigation hold notices as presumptively not privileged unless a specific privilege theory is supported by the record; if withheld, explain why and determine whether a log entry is required.
- For withheld materials claimed as work product, ask whether the material was created in the ordinary course or because litigation was anticipated; recommend producing ordinary-course documents and logging only genuinely protected material.
- For each privilege-log entry, test whether the description is specific enough to support the claim without revealing the substance; flag generic labels, missing dates, missing recipients, missing authors, or conclusory privilege phrases.
- For each date objection, identify when the underlying obligation, event, or compliance duty arose and whether the requested period is reasonably tied to that timeline.
- For each custodial gap, determine whether supplemental collection is required and whether the gap affects completeness of the production set.
- For each ESI issue, distinguish between a true production defect and a mere coding or description error that can be fixed by a supplemental load or corrected log.
- For each inadvertent production, confirm the governing clawback mechanism, then list the affected items for return, sequester, or privilege-log supplementation.
- Independently inventory additional production problems apparent from the production record, even if not cited in the deficiency letter, to reduce the risk of a second challenge.

## 5. Vertical / structural / temporal relationships

- Privilege-log defects compound over time: an inadequate entry can weaken the privilege claim for the document and related materials.
- Custodian gaps can cascade into later deficiency letters because missing custodians often imply missing categories of responsive material.
- Date objections should be tested against the chronology of the underlying obligation, not just the litigation filing date.
- Self-initiated remediation is strategically valuable because it can neutralize issues before they harden into waiver disputes or sanctions arguments.
- Prioritize time-sensitive remediation so that supplementation, clawback, and log correction occur before the response deadline.

## 6. Output structure conventions

- Write the memo as a conventional issues memorandum, not a checklist.
- Open with a short executive summary identifying the overall production posture, the most material gaps, and the response deadline.
- Include a clear severity legend once, then apply it consistently to each issue.
- For each issue, use a compact substructure:
  - issue title;
  - severity;
  - requester’s position;
  - legal merit assessment with controlling authority named;
  - recommended response;
  - specific remediation steps, including whether to produce, withhold and log, supplement the log, reopen collection, correct metadata, or invoke clawback;
  - where available, identify the affected Bates range or production segment without inventing numbers.
- Organize the body first by the asserted deficiency items from the correspondence, then by self-initiated issues discovered in review.
- Include a distinct risk section addressing privilege-waiver exposure, custodian-gap exposure, ESI noncompliance, and deadline pressure.
- End with a standalone Recommended Actions block. Each recommendation should state the action in the imperative, identify the responsible role, and give a timing anchor tied to the response deadline or next production milestone.
- Use professional litigation-memo language; do not reproduce the deficiency letter verbatim except for brief quoted terms when necessary and permitted.