Draft Written Discovery Responses and Objections From the Requests and Client Documents
Turn a served set of interrogatories, document requests and requests for admission into a request-specific objection matrix, source-mapped draft responses and a plain-English verification checklist for the client.
When to use this
Use this when your client has been served with written discovery and you need a first draft of responses and objections before the deadline. Claude works request by request: it proposes objections tied to the specific wording of each request, maps each request to facts and documents you supply, drafts the responses with every factual statement marked for client confirmation, and builds the questionnaire the client must complete before signing a verification. It works the same whether you represent a plaintiff, a defendant, or a company responding through in-house counsel.
Written discovery responses are repetitive and unforgiving at the same time. Every set needs the same structure, but each answer binds the client, each objection has to fit the request it is made to, and a sloppy response to a request for admission can concede a fact. The temptation is to recycle a prior set of general objections, and many courts have made clear they do not accept boilerplate.
This workflow keeps Claude anchored to the documents. You paste the requests exactly as served and the client materials you actually have. Claude proposes objections only where the wording of a particular request supports them, explains why, and labels its confidence. It then drafts responses using only facts it can quote from your materials, lists what it could not answer, and marks every factual statement for client verification.
Claude does not know your client's facts beyond what you paste, and it does not know your court's local practice. The response deadline, the governing rule, the protective order, privilege calls and the final wording of every objection are for the responsible attorney. The client must confirm every fact before signing any verification.
The Workflow
Set the context and paste the requests as served
Tell Claude who you represent, the claims, and what governs (court, rules, protective order). Calculate and calendar the response deadline yourself. Paste each set in its own document tags with the numbering exactly as served, including definitions and instructions, since those often drive objections.
PromptI represent [RESPONDING PARTY], the [PLAINTIFF / DEFENDANT], in a [TYPE OF CASE] pending in [COURT]. The claims are [CLAIMS]. Discovery is governed by [APPLICABLE RULES, e.g., the Federal Rules of Civil Procedure and Local Rules of COURT / STATE RULES], and [there is / is not] a protective order (summary of key terms: [TERMS]). I have calendared the response deadline separately. <document title="[PROPOUNDING PARTY]'s First Set of Interrogatories"> [PASTE, INCLUDING DEFINITIONS AND INSTRUCTIONS] </document> <document title="[PROPOUNDING PARTY]'s First Requests for Production"> [PASTE] </document> <document title="[PROPOUNDING PARTY]'s First Requests for Admission"> [PASTE] </document> First, list every request by set and number with a one-line paraphrase. Then flag: any numbering gaps or duplicates, interrogatories with discrete subparts that may count separately, definitions or instructions that are unusually broad (quote them), and anything that looks cut off. Do not draft objections or responses yet.
What you get: A numbered inventory plus flags on definitions, subparts and missing text. Confirm the inventory matches the served sets before moving on, since a skipped request is a skipped response.
Build the request-specific objection matrix
Ask Claude to propose objections request by request, each tied to the language of that request. Make clear that general or boilerplate objections may be disfavored or ineffective in your court, so an objection only belongs where it fits.
PromptFor each request, build a table: Set and No. | Request (short quote) | Candidate objection(s) | Language in the request that supports the objection (quoted) | Why it fits this request | Proposed narrowing or what we will answer despite the objection | Confidence (strong / arguable / weak). Consider only objections the wording actually supports: vague or ambiguous terms, overbreadth in time or subject matter, undue burden, proportionality, privilege or work product, privacy or confidentiality, calls for a legal conclusion, and duplicative requests. Cite the governing rule as [APPLICABLE RULE] unless I give you the rule. Rules: - Do not propose a general objection that applies to the whole set. - If no objection fits a request, write "none" rather than reaching for one. - For any objection, say whether we will still answer or produce within a narrowed scope, and state that scope. - Flag any request where withholding on privilege would require a privilege log entry.
What you get: A matrix where every objection is tied to quoted language. Delete the weak ones. Where the governing rule requires the response to say whether anything is being withheld on the basis of an objection (as Federal Rule of Civil Procedure 34(b)(2)(C) does in federal court), the narrowed scope column feeds that statement.
Map client facts and documents to each request
Paste the client's documents and your interview notes, each in labeled document tags. Claude maps every request to the facts and documents that answer it, quotes its source, and lists what it cannot answer from what you provided.
PromptBelow are the client materials I have so far. <document title="Client interview notes, [DATE]"> [PASTE] </document> <document title="[DOCUMENT NAME OR BATES RANGE]"> [PASTE] </document> [ADD MORE DOCUMENT TAGS AS NEEDED] For each request, give: Set and No. | Responsive facts (each with a quote and the source document) | Responsive documents (title or Bates range) | Gaps: what the request asks that these materials do not answer | People likely to have the missing information. Rules: use only facts that appear in these materials. Do not fill gaps with assumptions or typical facts for this kind of case. Where two sources conflict (for example, the notes say one date and an email says another), list both and do not choose.
What you get: A request-by-request map with quoted support and an explicit gaps list. The gaps list becomes your follow-up request to the client.
Draft the responses
Have Claude draft each response in the required form, using the objection matrix and the fact map. Every factual statement is marked for client verification, and nothing is stated that the materials do not support.
PromptDraft responses to every request using the objection matrix and fact map above. Follow this format for each: REQUEST NO. [N]: [restate the request verbatim] RESPONSE: [specific objections, if any, stated with the reason] [the substantive response] Requirements: - Interrogatories: answer fully within any narrowed scope. Mark every factual statement [VERIFY WITH CLIENT]. Where information is unknown, say what inquiry was made, marked [CONFIRM INQUIRY]. - Requests for production: state whether responsive documents will be produced, are being withheld on the basis of a stated objection (and what is withheld), or do not exist after a reasonable search [CONFIRM], and when production will be made [CONFIRM DATE]. - Requests for admission: admit, deny, or admit in part and deny in part, stating which part. If the answer is lack of knowledge, mark it [CONFIRM REASONABLE INQUIRY] and do not use it where the materials show the client knows the answer. - Do not add facts beyond the fact map. Mark any open item [OPEN]. - Leave the caption, signature block and verification as placeholders.
What you get: A full draft response set with verification flags. Pay special attention to the requests for admission: an unanswered or late RFA can be deemed admitted under many rules, so these go to the top of the review.
Build the client verification questionnaire
Turn every [VERIFY WITH CLIENT], [CONFIRM] and gap into a plain-English list the client can work through. This is what makes the verification meaningful rather than a signature on a draft the client has not read.
PromptUsing the draft responses, write a client questionnaire in plain English for [CLIENT NAME / CLIENT CONTACT]. Group it by topic, not by request number, and for each item give: the question, the draft answer we currently have (quoted), the request numbers it affects, and what documents we need from them, if any. Open with a short explanation that the client will be verifying the interrogatory answers under oath and that every response must be accurate, that "I don't know" is acceptable only after they have checked, and that they should tell us about any documents they have not yet given us. End with a list of documents to send by [DATE]. Keep the tone direct and avoid legal jargon. Do not include our objection strategy or internal assessments in this document.
What you get: A client-facing questionnaire that tracks back to request numbers. Keep internal strategy out of it; the questionnaire goes to the client, and internal notes stay in the attorney file.
Attorney review, privilege log and calendar
The responsible attorney checks each objection against [APPLICABLE RULE] and local practice, confirms every fact with the client, prepares a privilege log for anything withheld on privilege, and calendars service, any meet-and-confer, and supplementation obligations.
What you get: Final responses with only objections the attorney will defend, verified facts, a privilege log where needed, and calendared follow-up. Claude's draft is a starting point for that review, not a substitute for it.
Example Output
Illustrative example — names, facts, and figures are fictional.
DRAFT RESPONSES (ILLUSTRATIVE / FICTIONAL)
Matter: Okafor v. Meridian Fabrication Co. We represent the defendant employer.
INTERROGATORY NO. 4: Identify every person involved in the decision to terminate Plaintiff's employment.
RESPONSE: Defendant objects to the term "involved" as vague because it could include employees who only processed paperwork after the decision was made. Defendant construes "involved" to mean participated in making or approving the decision, and on that basis identifies: Lena Haverford, Plant Manager, and Corbin Ash, Human Resources Director. [VERIFY WITH CLIENT]
Source: interview notes, March 2 ("Lena made the call, Corbin signed off"); termination memo, MF-000112.
REQUEST FOR PRODUCTION NO. 9: All communications concerning Plaintiff from January 1, 2015 to the present.
RESPONSE: Defendant objects that the request is overbroad in time and subject matter: it reaches more than a decade of communications on any subject "concerning" Plaintiff, while the claims concern events in the 12 months before the termination. Defendant will produce non-privileged communications concerning Plaintiff's performance, discipline or termination dated [START DATE] through [END DATE]. Defendant is withholding communications outside that scope. [CONFIRM]
REQUEST FOR ADMISSION NO. 3: Admit that Plaintiff received no written warning before termination.
RESPONSE: [OPEN] Draft: Denied. [VERIFY WITH CLIENT]
Source: written warning dated October 14, MF-000098. Note: interview notes say "verbal only." Conflict listed in the fact map; resolve with the client before serving.
OPEN ITEMS
- Interrogatory No. 7 (comparators): no materials provided. Need the list from HR.
DRAFT for attorney review. Objections to be confirmed against [APPLICABLE RULE] and local practice; all facts to be verified by the client before the verification is signed.Tips
- •Paste the definitions and instructions with the requests. A definition of 'document' or 'you' that sweeps in affiliates or counsel is often the real source of overbreadth, and Claude needs to see it to make a specific objection.
- •Let Claude write 'none' in the objection column. A response set with fewer, well-supported objections is easier to defend in a meet-and-confer than one that objects to everything.
- •Treat requests for admission as their own review pass. Read every RFA response against the fact map yourself, because a careless denial or a failure to respond can have consequences that interrogatory answers do not.
- •Never let Claude fill a factual gap. If the fact map has no source for an answer, the answer is [OPEN] until the client provides it.
- •Keep the client questionnaire separate from the internal draft. The client should see questions and draft answers, not your objection strategy or confidence ratings.
A note on confidentiality
This workflow puts client interview notes, internal business documents and sometimes privileged communications into Claude, along with the opponent's requests. Use a Claude plan whose terms exclude your inputs from model training (such as Team or Enterprise), check the protective order before including any material the other side designated confidential, and redact personal identifiers (employee medical details, Social Security numbers, account numbers) that the drafting does not require. Keep the objection matrix and fact map in the attorney file. Every response is a draft for attorney review, every fact must be confirmed by the client before verification, and any rule or authority cited must be verified.
Frequently Asked Questions
Can Claude draft discovery responses without the client documents?
It can draft objections and a response structure from the requests alone, but not substantive answers. The workflow requires every factual statement to come from materials you paste, and anything without a source is marked open. Responses built on assumed facts create verification and credibility problems later.
Will Claude include general objections?
Not in this workflow. The prompts ask for objections tied to the specific language of each request and allow 'none' where no objection fits. Many courts have criticized boilerplate general objections, so check your jurisdiction's rules and case law before adding any back.
Does this work for state court discovery?
Yes. The structure (objection matrix, fact map, draft responses, verification) is the same. Supply your court's rules as the governing rule, or leave [APPLICABLE RULE] placeholders and confirm requirements such as response format, numbering limits and verification rules yourself.
Who should sign off before the responses are served?
The responsible attorney signs the responses and objections, and the client (or a corporate representative) verifies interrogatory answers under oath where the rules require it. Claude's draft feeds that review; it does not replace either signature.
Prompts used in this workflow
Get New Workflows Like This Every Week
Join the free Claude for Lawyers newsletter — practical workflows, prompts, and guides for everyday practice.