# Compare Document Production Against Grand Jury Subpoena

> Gap analysis memorandum comparing a rolling document production set against subpoena request categories, identifying collection gaps, coding guide deficiencies, privilege log completeness issues, and potential bad-faith or obstruction risk from non-responsive classification of plainly responsive documents.

- Skill: `finchipaiorg/compare-document-production-against-grand-jury-subpoena` (Agent Skill)
- Install (CLI): `npx skillmds@latest add finchipaiorg/compare-document-production-against-grand-jury-subpoena`
- Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/compare-document-production-against-grand-jury-subpoena/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/finchipaiorg/compare-document-production-against-grand-jury-subpoena

---


# Skill: Gap Analysis — Document Production Set vs. Grand Jury Subpoena Request Categories

## 1. Subject-matter triage (only if applicable)

- This skill applies when the task is to compare a rolling production against subpoena request categories and explain gaps, likely causes, and remediation.
- First determine whether the source set includes multiple subpoena categories, multiple custodians, multiple collection sources, or multiple production rounds; if so, analyze each separately rather than treating the set as a single undifferentiated corpus.
- If the materials reflect a negotiated narrowing or expansion, distinguish the original subpoena scope from any meet-and-confer adjustment before assessing completeness.

## 2. Failure modes the skill is correcting

- A narrow review definition can cause responsive materials to be coded non-responsive; treat that as a systematic process defect when the pattern suggests it, not only as isolated reviewer error.
- A production gap can stem from collection failure, review/coding failure, privilege withholding, or scope misunderstanding; do not collapse distinct causes into one generalized “missing documents” label.
- Non-production of plainly responsive materials can support an adverse inference, bad-faith, or obstruction-risk argument depending on volume, centrality, and context; the analysis should surface that risk when supported by the record.
- Privilege withholding is not a substitute for responsive production; if documents are withheld, the analysis must check whether the privilege log is complete enough to permit review.
- A remediation memo that stops at diagnosis is incomplete unless it translates each gap into a concrete corrective step.

## 3. Legal frameworks / domain conventions that apply

**Subpoena-category analysis**
- Treat each numbered request category as its own scope unit, with its own subject matter, date range, and custodian reach.
- Assess whether the production is complete, partial, or absent for each category, and whether any apparent deficiency is due to source omission, review coding, or privilege withholding.

**Responsiveness and coding conventions**
- Review coding should map documents to the subpoena category they fairly fall within, not only to the narrowest textual reading of a reviewer note.
- If a definition is too restrictive, identify whether re-review should extend to adjacent coding buckets, parent topics, or document families that were likely excluded by the same definition.

**Collection adequacy**
- Confirm that all relevant repositories and devices were collected for each custodian implicated by the request.
- Common gaps include secondary email accounts, messaging platforms, personal devices used for business, and departed custodians whose data was not preserved.

**Privilege log conventions**
- Withheld documents should be logged with enough information to test the claim, typically including date, author, recipients, non-privileged description, and asserted privilege basis.
- Missing log fields or vague descriptions are actionable deficiencies even where the underlying withholding may be valid.

**Bad-faith / obstruction-risk framing**
- Risk analysis should focus on the pattern: whether the gap is isolated or systematic, whether the documents are central, and whether the coding explanation is plausible in light of the document set.
- A coding defect does not itself establish misconduct, but it can increase risk if plainly responsive materials were repeatedly excluded.

**Meet-and-confer record**
- Any agreed narrowing, exclusion, or timing accommodation should be incorporated into the completeness assessment and remediation plan.

## 4. Analytical scaffolds

1. **Enumerate the scope first**
   - List each subpoena category, custodian group, and production tranche before analysis.
   - If only one exists in a given dimension, state that explicitly and explain why no subdivision is needed.

2. **Category-by-category production status**
   - For each request category, state whether the production appears complete, partial, or absent.
   - Identify the likely cause of any gap: collection, coding, privilege, or scope mismatch.

3. **Gap attribution**
   - For each gap, explain whether it reflects missing sources, a narrow coding guide, a privilege hold, or a production sequencing issue.
   - Separate documentary absence from temporary rolling-production timing when the record supports that distinction.

4. **Coding-guide adequacy review**
   - Test whether the category definition is so narrow that it would systematically exclude responsive documents.
   - If so, identify the re-review universe by document family, topic cluster, or adjacent code bucket rather than by isolated exemplars only.

5. **Miscoded-document review**
   - Flag documents that appear plainly responsive but were coded non-responsive.
   - Trace each to the likely coding-defect source and assess whether the issue appears isolated or recurring.

6. **Collection-gap review**
   - For each custodian, check whether all relevant sources were collected and preserved.
   - Flag secondary accounts, personal devices, collaboration tools, and departed-employee data where relevant.

7. **Privilege-log sufficiency review**
   - Confirm that withheld items are logged with date, sender/recipient information, a non-privileged description, and privilege basis.
   - Identify missing fields, ambiguous entries, or insufficiently granular descriptions.

8. **Risk and consequence assessment**
   - For each material gap, state the likely litigation or investigative consequence, including whether it may support a completeness challenge, motion practice, adverse inference argument, or additional meet-and-confer pressure.
   - Where supported by the source set, note whether the issue is likely to be viewed as a process defect or a more troubling non-production pattern.

9. **Remediation recommendations**
   - Convert each identified gap into a concrete next step, including supplemental collection, targeted re-review, privilege-log supplementation, or rolling production supplementation.
   - Tie the recommendation to the responsible role and the next milestone in the production process.

## 5. Vertical / structural / temporal relationships (only if applicable)

- If the production is rolling, distinguish what is missing because it has not yet been collected or reviewed from what is missing after review and withholding.
- If categories overlap, explain the hierarchy: broad topic requests, subtopic requests, and custodian-specific requests may all capture the same documents, but each must be checked for completeness on its own terms.
- If the gap concerns a time window, identify whether the omission is pre-period, post-period, or a hole within the period, because the remedial scope differs.

## 6. Output structure conventions

- Draft as a gap analysis memorandum organized by subpoena category, using conventional memorandum headings rather than a rigid rubric list.
- Define a simple ordinal severity scale once at the top and apply it consistently to each issue entry.
- For each category, include: scope reference, production status, gap description, apparent cause, severity, risk assessment, and recommended remediation.
- Include a distinct section for coding-guide deficiencies and the re-review scope they require.
- Include a distinct section for privilege-log deficiencies and the missing fields or vague descriptions to be cured.
- Include a short section summarizing any meet-and-confer adjustments that affect the completeness analysis.
- End with a Recommended Actions section that names the responsible role and a timing anchor for each step.
- Keep the memo operational: describe the gap, its cause, its consequence, and the next action; do not stop at abstract characterization.