Draft Litigation Discovery Responses

Skill: Draft Discovery Responses and Objections to RFAs and RFPs in Breach of Supply Agreement Litigation

1. Subject-matter triage

• Identify the governing discovery set, the request numbering, the response deadline, and any stipulation or court order that changes timing, format, or privilege-log requirements.
• Separate requests for admission from requests for production before drafting; each has a different response posture and different risk if handled reflexively.
• Review the pleadings, the supply agreement, and any precedent responses before deciding what can safely be admitted, denied, qualified, or objected to.
• If the source set includes multiple requests, enumerate them first and analyze each one individually; do not use a generic response strategy across dissimilar requests.
• Preserve the possibility that a single request may require a mixed response: objection as to part, admission or denial as to the rest, or production subject to limitations.

2. Failure modes the skill is correcting

• Denying an RFA that concerns an undisputed fact, which can create needless expense exposure under Rule 36 of the Federal Rules of Civil Procedure or the applicable state analogue.
• Failing to distinguish between a request for a fact, a request for a legal conclusion, and a compound request that bundles several propositions together.
• Answering an RFP with objections only, without saying whether responsive materials will be produced, withheld, or produced in part.
• Using boilerplate objections that do not track the actual request, the actual burden, or the actual privilege issue.
• Missing the litigation rationale behind each response, so the formal response and the strategy memo do not support each other.
• Forgetting that admissions can conclusively establish a matter, making careless admissions harder to unwind later.
• Omitting the controlling authority for the objection or response position, which weakens the memo and makes the response look conclusory.

3. Legal frameworks / domain conventions that apply

• For RFAs, apply Federal Rule of Civil Procedure 36 or the governing state rule: after reasonable inquiry, the responding party must admit, deny, or state that it cannot truthfully admit or deny, and must fairly respond to the substance of the request.
• For RFAs, a denial should not be evasive; if only part of a request is supportable, qualify the response and admit the undisputed portion.
• For RFAs, a request that seeks a legal conclusion may be objectionable, but the objection should be tied to the governing rule and the request should still be answered to the extent it seeks facts.
• For RFAs, a compound request may be objected to as compound, ambiguous, or confusing, while still responding to any separable factual component.
• For RFPs, apply Federal Rule of Civil Procedure 34 or the governing state rule: state whether responsive documents or ESI will be produced, identify any scope limits, and say if materials are withheld on the basis of an objection.
• For RFPs, if materials are withheld, the response should preserve the objection and describe the nature of the withheld material with enough specificity to be meaningful.
• For privilege issues, use the attorney-client privilege, work-product doctrine, or any applicable confidentiality protection, and reference a privilege log or similar log where required.
• For all legal propositions stated in the memo or the formal responses, cite the controlling rule, statute, regulation, or doctrine by name rather than relying on conclusory phrasing.

4. Analytical scaffolds

• Start with the request text, then ask: what exactly is being sought, what is undisputed, what is disputed, what is privileged, and what is burdensome or overbroad.
• For each RFA, decide whether to admit, deny, qualify, object, or state inability to admit or deny after reasonable inquiry.
• Favor admissions on noncontroversial facts that help narrow the case and do not concede the disputed breach, causation, damages, or defenses issues.
• For each RFA denial, ensure the denial fairly meets the substance of the request and does not leave an implied admission.
• For each RFP, decide whether the objection is total or partial, whether production will occur subject to the objection, and whether a privilege log or confidentiality designation is needed.
• If a request is overbroad or ambiguous, identify the defect specifically and tie it to the request’s wording, scope, or time period.
• Use precedent responses only as a formatting and phrasing aid; adapt them to the present requests and facts rather than copying them mechanically.
• Draft the strategy memo as the explanation layer for the responses: why each request is answered the way it is, what risk the position avoids, and what factual or legal issue remains preserved.

5. Vertical / structural / temporal relationships

• Track the relationship between the request, the pleadings, the supply agreement, and any scheduling order; a response that is technically plausible can still be wrong if it ignores a deadline, a defined term, or a governing limitation.
• If the request turns on whether a fact is pre-breach, post-breach, or tied to performance under a specific contractual period, anchor the response to that temporal frame.
• If a request reaches across multiple periods, products, shipments, notices, or performance events, analyze each discrete slice separately before deciding whether a single response can safely cover them.
• Where a request intersects with privilege, confidentiality, or trade-secret concerns, state the limitation in the response and align it with any protective-order procedure in the source materials.
• Keep the memo and the formal responses synchronized: the memo should explain the same positions that appear in the written responses, not a different strategy.

6. Output structure conventions

• Produce two distinct deliverables: a discovery-response-plan memo and a separate set of formal RFA/RFP responses.
• The discovery-response-plan memo should be organized by request type, then by individual request number, with a short recommendation and litigation rationale for each.
• The memo should conclude with a concise Recommended Actions section that tells counsel or the relevant business owner what to do next and on what timing.
• The formal responses should be captioned, numbered to match the requests, and drafted in a standard discovery-response style suitable for filing or service after local formatting is checked.
• Each formal response should clearly state: admitted, denied, unable to admit or deny after reasonable inquiry, objected to, or produced/withheld in part, as appropriate.
• When an objection is asserted, pair it with a substantive response to any non-objectionable portion whenever possible.
• When production is promised, identify the category of documents or ESI to be produced and avoid leaving the response ambiguous.
• When materials are withheld, say so expressly and maintain the objection consistently across the response set.
• Before finishing, confirm that each requested output file is fully drafted and non-empty, and that the responses are operative text rather than a mere summary of what would be done.