How to Draft Discovery Requests That Actually Get Answers

Discovery is where most cases are won or lost, yet too many practitioners treat it as a box-checking exercise. They copy boilerplate from a prior matter, fire off vague demands, and then wonder why they receive pages of objections instead of useful information. The truth is that drafting discovery requests is a skill, and well-crafted requests are far harder to dodge than sloppy ones. This article walks through how to write interrogatories, requests for production, and requests for admission that produce real, usable answers rather than evasion.

Why Do So Many Discovery Requests Fail?

Most discovery requests fail for one of three reasons: they are too broad, too vague, or too compound.

A request that asks for "all documents relating to the incident" invites an objection that the demand is overbroad and unduly burdensome. A request that uses undefined terms like "communications" without specifying form or participants leaves room for a narrow, self-serving interpretation. And a request that crams five questions into one sentence gives the responding party an easy excuse to answer only the part they like.

When you understand why requests fail, you can reverse-engineer requests that succeed. The goal is to leave the opposing party with no legitimate ground to object and no honest way to claim confusion about what you are asking.

What Should You Do Before You Write a Single Request?

Effective discovery begins long before you open a template. It starts with your claims and defenses.

Pull up the elements of every cause of action and every affirmative defense in the case. Each element is something you must prove or disprove, and each one should map to specific discovery. If you cannot tie a request back to an element of a claim or defense, ask yourself why you are sending it.

Next, build a chronology of the facts as you understand them. Identify the gaps. Discovery exists to fill those gaps, not to restate what you already know. A focused list of factual questions will guide far better requests than any generic form.

Finally, think about the documents and witnesses that likely exist. Knowing that a company uses a particular system or that a transaction generated certain records lets you ask for those items by name, which is much harder to evade.

How Do You Write Interrogatories That Get Straight Answers?

Interrogatories work best when they ask for specific facts, identities, and contentions.

Use them to pin down names, dates, account numbers, and positions. Ask the responding party to identify every person with knowledge of a specific event, or to state the factual basis for a particular affirmative defense. Contention interrogatories are especially powerful because they force your opponent to commit to a theory early, which limits their ability to shift positions later.

Keep each interrogatory focused on a single piece of information. Instead of asking the party to "describe the accident and identify all witnesses and explain any contributing factors," break that into three separate interrogatories. Compound questions invite partial answers.

Define your terms with care. If you use a word like "agreement," specify whether you mean written, oral, or both. Precise definitions remove wiggle room and make non-responsive answers stand out clearly to a judge if you later move to compel.

Watch your numerical limits. Many jurisdictions cap the number of interrogatories, so spend them wisely. Reserve them for information that is hard to get any other way, and use document requests for the underlying records.

How Should You Draft Requests for Production?

Requests for production are where specificity pays the biggest dividends.

Describe the categories of documents with enough particularity that the responding party cannot plausibly claim confusion, but not so narrowly that they can withhold a key file on a technicality. The sweet spot is a request that names a clear category, a relevant time frame, and a connection to the issues in the case.

For example, rather than demanding "all financial records," ask for "all monthly bank statements for the business checking account from January 2021 through December 2022." That request is specific, bounded, and tied to a relevant period.

Address electronically stored information directly. Specify the form of production, whether native files with metadata or searchable images, and consider whether you need email, text messages, or data from specific applications. If you do not ask for metadata, you may not receive it.

Anticipate privilege objections by requesting a privilege log when documents are withheld. A detailed log lets you challenge improper claims and signals that you intend to hold the other side accountable. For practitioners who want to see how polished production sets are structured, you can explore this service to understand how organized, defensible requests come together.

When Are Requests for Admission Most Effective?

Requests for admission are the most underused tool in discovery, and that is a mistake.

Their purpose is to narrow the issues by establishing facts that are not genuinely in dispute. Use them to authenticate documents, confirm dates, and lock down facts that the other side cannot honestly deny. Every admission you obtain is one less thing you must prove at trial.

Draft each request so it addresses a single, simple fact. A request like "admit that the contract attached as Exhibit A is a true and accurate copy of the agreement signed on June 1, 2022" is hard to deny in good faith. A compound or argumentative request, by contrast, gives the responding party room to deny the whole thing.

Remember that an unanswered request for admission is typically deemed admitted, and that a party who denies something later proven true may face cost-shifting consequences. That pressure makes carefully drafted admissions a quiet but potent source of leverage.

How Do You Phrase Requests to Limit Objections?

The way you phrase a request often determines whether you get an answer or an objection.

Avoid the words that trigger reflexive objections, such as "any and all" and "relating to in any way." These phrases practically beg for a burden objection. Replace them with bounded language that names specific categories and time frames.

Tie each request to the subject matter of the litigation so that relevance is obvious on its face. When relevance is self-evident, an objection looks like obstruction, which helps you if you later go before the court.

Include reasonable definitions and instructions at the front of your discovery, but do not bury an unreasonable demand inside a definition. Courts dislike gamesmanship, and an overreaching definition can taint otherwise valid requests.

Calibrate proportionality. Discovery rules increasingly require that requests be proportional to the needs of the case. Framing your requests in proportionate terms, with sensible limits, deprives your opponent of the argument that you are simply fishing.

What Should You Do After You Send the Requests?

Drafting is only half the battle. Follow-through determines whether your careful work produces answers.

Calendar the response deadline and track it. When you receive responses, read every objection and answer closely. Identify evasive answers, improper objections, and any documents that should exist but were not produced.

Meet and confer promptly and in good faith. A specific, well-documented letter that points to particular deficient responses lays the foundation for a motion to compel if the dispute cannot be resolved. The clearer your original requests, the stronger your position in that meet-and-confer process.

If you must move to compel, your precise drafting becomes your best evidence. A judge who sees a narrow, relevant request paired with an evasive answer is far more likely to rule in your favor.

Conclusion

Discovery requests that get answers are not the product of luck or volume. They come from preparation, precision, and discipline. When you anchor each request to an element of your case, write in specific and bounded language, and follow through diligently, you make evasion difficult and useful responses likely. Treat discovery as the strategic heart of your case rather than a clerical chore, and the answers you need will follow.