Identify Issues In Counterparty Discovery Responses

Skill: Identify Issues in Counterparty Discovery Responses

1. Subject-matter triage

• Treat the assignment as a request to compare discovery responses against the underlying requests and supporting materials, then isolate enforceable deficiencies.
• Build the memo request-by-request; do not generalize from one deficient response to the entire set unless the same defect repeats across multiple requests.
• If the source set includes interrogatories, document requests, responses, objections, privilege claims, log entries, or production metadata, analyze each as a distinct input stream and reconcile them.
• If the discovery universe spans more than one party, custodian, time period, or data source, enumerate those categories first and run the same deficiency check across each.
• Where only one party, custodian, or period is actually at issue, state that limitation expressly before analyzing.

2. Failure modes the skill is correcting

• Analyst flags an objection as boilerplate but does not tie the critique to the governing discovery rule requiring specific grounds.
• Analyst treats outdated discovery language as controlling and misses the current proportionality framework.
• Analyst assumes a privilege claim is valid without testing whether the material was created for legal advice, whether business or HR functions drove the process, and whether the log supports the claim.
• Analyst notes a privilege log problem without reconciling withheld materials against logged entries or the production set.
• Analyst overlooks ESI preservation issues when production gaps appear in a relevant date range.
• Analyst accepts a records-reference response without checking whether the records are identified with sufficient particularity and whether the burden allocation is satisfied.
• Analyst identifies a defect in isolation but does not explain its scale, interaction with other discovery materials, or practical consequence for the client.
• Analyst gives legal conclusions without naming the rule, case, or standard that supports them.
• Analyst lists problems without assigning a uniform severity level or recommending the next step.

3. Legal frameworks / domain conventions that apply

• Interrogatory objections must be stated with specificity under Federal Rule of Civil Procedure 33; boilerplate objections that do not explain the defect in the particular interrogatory are vulnerable to waiver.
• Discovery scope is governed by Federal Rule of Civil Procedure 26(b)(1), including relevance and proportionality; objections should be tested against the current proportionality framework rather than obsolete formulations.
• Privilege claims must be anchored in the attorney-client privilege or work-product doctrine as applicable; communications or materials created for nonlegal business, operational, or HR purposes may fall outside those protections.
• A privilege log should identify withheld materials with enough detail to test the claim; an incomplete log can be attacked as facially insufficient under the applicable discovery rules and local practice.
• Preservation and spoliation concerns arise when electronically stored information that should have been preserved is missing or partially produced; the analysis should track the duty to preserve, the relevant time window, and any remedial implications.
• Interrogatory answers that refer to business records are governed by Federal Rule of Civil Procedure 33(d); the responding party must identify records with sufficient particularity and only shift the burden when deriving the answer would be substantially the same for both sides.
• Any legal proposition in the memo should be tied to a named authority, such as a federal rule, controlling case, local rule, or recognized privilege doctrine.

4. Analytical scaffolds

• Request-by-request deficiency analysis: compare each request to the response and separate objection problems, incomplete answers, privilege issues, and production deficiencies.
• Authority-backed issue statement: for each deficiency, state the governing rule or doctrine and explain why the response fails under that authority.
• Scale-and-impact framing: for each issue, note the magnitude using the source documents themselves, cross-reference the related response, log, or production record, and explain the downstream effect on the client.
• Privilege-log reconciliation: compare the number and type of withheld materials referenced in the responses with the log entries and identify any mismatch or missing detail.
• ESI-gap review: check whether the production range leaves unexplained gaps in the relevant period and whether those gaps coincide with a preservation duty.
• Cross-response consistency check: identify contradictions between interrogatory answers, document responses, and supporting documents.
• Burden-shift check for record references: test whether the response actually permits the requesting party to derive the answer from identified records without disproportionate effort.
• If a deficiency cannot be quantified from the documents, say so and identify the missing data needed to complete the analysis instead of guessing.

5. Vertical / structural / temporal relationships

• Track how each response relates vertically to the original request, any supplemental response, any privilege log, and the production set.
• Track how objections evolve over time; note whether later productions or amended responses cure, narrow, or repeat the original defect.
• Track the relevant temporal window for each request, then compare that window to the dates covered by production and any identified gaps.
• Track document hierarchy: request, response, objection, withholding statement, log entry, production item, and any cited business record should be reconciled in that order.
• If a response relies on another document or dataset, verify whether that referenced source is actually produced and whether it resolves the question asked.

6. Output structure conventions

• Produce a partner-ready discovery deficiency memorandum in conventional memo form.
• Start with a short executive summary, then a table of issues, then numbered deficiency sections.
• Define a uniform ordinal severity scale once near the top and use it consistently for every issue.
• For each deficiency, include: request number or topic, concise deficiency statement, governing authority, why the response fails, scale/interaction/consequence, recommended next step, and severity.
• Include a summary table that maps each issue to its severity, affected request, and recommended action.
• Close with a Recommended Actions section that uses imperative verbs, assigns the responsible role, and includes timing tied to the litigation schedule or other source milestone when available.
• Recommend motion-to-compel or related relief only where the record supports it, and tailor the requested relief to the specific defect identified.
• Keep the memo focused on concrete deficiencies; avoid reciting compliant responses at length unless needed to show the gap.