Discovery Request Example: What Do Sample Requests for Production Look Like?

You filed your lawsuit, or you were served with one, and now the other side holds the documents that prove your case. That gap is exactly what a discovery request example solves. A request for production is the tool that forces an opponent to hand over emails, contracts, records, and files that sit outside your reach. This article shows you what sample requests for production look like, how they are built, and how to draft them so a court will enforce them. You will see worked examples, the governing rules, the objections you will face, and where to get court-ready drafting help if you are representing yourself.

What You Need to Know

A request for production is a written discovery demand that compels an opposing party to produce documents, electronically stored information (ESI), and tangible things relevant to a lawsuit. Federal Rule of Civil Procedure 34 governs it in federal court. Each request must be specific, proportional, and tied to a claim or defense. The responding party has 30 days to answer, object, or produce.

1. A request for production demands documents and ESI, such as emails, contracts, invoices, and photographs, held by an opposing party.
2. Rule 34 of the Federal Rules of Civil Procedure (FRCP) controls the form, scope, and timing in federal court.
3. Each request must define a specific category and state a reasonable manner and form of production.
4. The responding party owes a written response within 30 days of service, either producing, objecting, or stating no responsive documents exist.
5. State courts follow their own discovery codes, so confirm the rule and deadline in your jurisdiction before you serve.

What is a request for production of documents?

A request for production of documents is a formal written demand that requires an opposing party to turn over documents, electronically stored information, and tangible things that relate to the claims or defenses in a case. It operates as a core discovery device that moves evidence from the party who holds it to the party who needs it.

Discovery is the pretrial phase where each side exchanges information before trial. A request for production, often shortened to RFP, targets tangible proof rather than testimony. You can demand paper records, digital files, spreadsheets, text messages, and physical objects. The requesting party defines categories of items, and the responding party gathers and produces everything responsive within its possession, custody, or control.

The reach is broad. You can request emails between managers, a signed lease, repair invoices, insurance policies, or metadata attached to a digital file. Our attorneys use these requests to build the documentary record that supports a settlement demand or a trial exhibit list.

What governs requests for production under the Federal Rules of Civil Procedure?

Requests for production in federal court are governed by Federal Rule of Civil Procedure 34, which authorizes a party to demand documents, ESI, and tangible things, and to inspect land or property. Rule 34 works together with Rule 26, which sets the scope and limits of all discovery.

Rule 26(b)(1) defines the scope. Discovery reaches any nonprivileged matter relevant to a claim or defense and proportional to the needs of the case. Courts weigh the importance of the issues, the amount in controversy, and the burden of production against its likely benefit. That proportionality standard, added in the 2015 amendments, gives responding parties a real basis to resist sweeping demands.

State courts apply their own rules. California uses Code of Civil Procedure sections 2031.010 and following. New York applies its Civil Practice Law and Rules. Deadlines, formatting, and numerical limits differ by jurisdiction, so confirm your local rule before serving. Our guide on how the Federal Rules of Civil Procedure shape discovery requests breaks the framework down further.

Anatomy of a Request for Production: The Core Parts

A request for production contains five core parts: a caption, an introductory statement, definitions and instructions, the numbered requests themselves, and a signature block. Each part carries a distinct function, and skipping one weakens enforceability.

The caption names the court, the parties, and the case number. The introductory statement identifies who serves the request and cites the governing rule. Definitions clarify recurring terms, such as "document," "you," and "relevant period," so the responding party cannot claim ambiguity. Instructions state the form of production, the manner of identifying privileged items, and the treatment of ESI and metadata.

The numbered requests are the heart of the document. Each request states one clear category of items. The signature block certifies that the requests comply with Rule 26(g), which requires a good-faith basis and prohibits requests served to harass or cause delay. A well-built request reads as precise, self-limiting, and tied to a specific fact in dispute.

Sample Requests for Production: Worked Examples

Sample requests for production read as numbered, single-category demands that name the documents sought, the time period, and the parties involved. Strong examples avoid vague catch-all language and instead target a defined class of records tied to a disputed fact.

Consider a breach of contract case. A clean request states: "Produce all written communications between Plaintiff and Defendant concerning the March 2023 supply agreement, including emails, letters, and text messages, from January 1, 2023 to December 31, 2023." That request names the topic, the format, the parties, and the date range.

A personal injury case offers another model: "Produce all medical records, bills, and diagnostic images reflecting treatment of Plaintiff for injuries alleged in the Complaint from the date of the incident to the present." An employment case might request: "Produce Defendant's personnel file for Plaintiff, including performance reviews, disciplinary records, and termination documents." For deeper templates across practice areas, review our library of sample requests for production in civil litigation.

Each example shares three traits. It targets one category. It fixes a time frame. It connects to a pleaded claim. Those traits keep the request enforceable and hard to object to.

How to Draft a Request for Production Step by Step

Drafting a request for production follows a repeatable six-step process that moves from your claims to enforceable numbered demands. Follow the sequence in order, and your requests will survive objection.

1. Identify each element of your claim or defense that documents can prove.
2. List the specific records that would prove each element, such as contracts, invoices, or emails.
3. Draft one numbered request per category, using precise nouns and a defined date range.
4. Add definitions and instructions that fix the meaning of recurring terms and the form of production.
5. Review each request against Rule 26 proportionality so no demand looks overbroad or harassing.
6. Serve the requests under your jurisdiction's rule and calendar the 30-day response deadline.

Draft narrow first, then broaden if the response reveals gaps. A tightly scoped request forces production; a bloated one invites a motion to quash. When you need help building a complete set, our professional discovery request drafting service prepares court-ready demands tailored to your jurisdiction.

Common Mistakes to Avoid in Requests for Production

The most damaging mistakes in requests for production are overbreadth, vagueness, and missing time limits. Each defect hands the opposing party a valid objection and delays the evidence you need.

Overbroad requests demand "all documents relating to the business" without limits. Courts routinely narrow or strike such requests. Vague requests use undefined terms that let the responder produce nothing of value. Requests without a date range sweep in decades of irrelevant records, which triggers a proportionality objection.

Other frequent errors include compound requests that bundle several categories into one number, requests that ignore ESI and metadata format, and requests that seek privileged material without a plan to handle the privilege log. Serving duplicative requests wastes leverage and can prompt a motion to strike. Our guide on how to object to overbroad discovery requests shows how the other side attacks these defects, which tells you what to avoid.

How Does the Other Side Respond to Requests for Production?

The responding party answers each request in writing within 30 days of service, and the response either produces the documents, states an objection, or confirms no responsive documents exist. Rule 34(b)(2) requires a specific response to each numbered request.

A proper response addresses every request individually. The party produces responsive documents as they are kept in the ordinary course of business, or organized to correspond with the categories requested. For ESI, the party produces files in the form specified or in a reasonably usable form. When the party withholds documents on privilege grounds, it must produce a privilege log describing each withheld item without revealing the protected content.

A responding party cannot stay silent. Failure to respond waives most objections and exposes the party to a motion to compel under Rule 37. Our attorneys prepare professional responses to discovery requests that meet these standards and preserve every valid objection.

How do you object to overbroad or improper requests?

Yes, you can object to an overbroad or improper request, and you do it by stating a specific written objection in your response within the 30-day window. Rule 34(b)(2)(B) requires that the objection state the grounds with particularity and confirm whether any responsive materials are withheld on that basis.

Valid grounds include overbreadth, undue burden, lack of relevance, disproportionality, privilege, and vagueness. A boilerplate objection that recites "overbroad and burdensome" without explanation fails under current federal practice. State the exact defect. For example: “Defendant objects to Request No. 4 as overbroad because it seeks documents without any time limitation and unrelated to the transactions pleaded in the Complaint.”

Attorney-client privilege protects confidential legal communications, and the work-product doctrine shields materials prepared in anticipation of litigation. Assert both in the objection and log the withheld items. When a dispute stalls production, a party moves to compel or moves for a protective order. Our resource on the role of protective orders in discovery requests explains that path.

Requests for Production vs. Interrogatories vs. Requests for Admission

The three written discovery devices differ by what each one demands. A request for production demands documents and tangible things. An interrogatory demands written answers to questions. A request for admission demands that a party admit or deny a specific fact.

Requests for production, governed by Rule 34, produce the documentary record: contracts, emails, and financial statements. Interrogatories, governed by Rule 33, extract narrative answers, and federal practice caps them at 25 including subparts. Requests for admission, governed by Rule 36, narrow the issues by locking in facts, so an admitted fact needs no proof at trial.

The three tools work together. You use interrogatories to identify who holds which records, requests for production to obtain those records, and requests for admission to authenticate them. That sequence builds a trial-ready file efficiently. Requests for admission carry a sharp edge, because an unanswered request is deemed admitted after 30 days.

How do deadlines and timing work for requests for production?

The core deadline is 30 days. The responding party must serve its written answers and objections within 30 days after being served with the requests in federal court under Rule 34(b)(2)(A). A defendant served with requests before its Rule 26(f) conference gets a longer runway, because the response is not due until 30 days after that conference.

Discovery cannot start until the parties hold their Rule 26(f) planning conference, which shapes the discovery schedule. Our overview of Rule 26(f) conferences and discovery planning explains that step. The court then issues a scheduling order under Rule 16 that sets the discovery cutoff.

Timing rules vary by jurisdiction. California allows 30 days plus extensions for mailed service. Some state courts require a demand only after a set period following service of the complaint. Add mailing time under Rule 6(d) when service is by mail. Calendar every deadline the day you serve or receive requests, because a missed deadline waives objections and can trigger default consequences.

Where can pro se litigants get help drafting requests for production?

Pro se litigants can get help drafting requests for production from LegalHusk, where our legal professionals prepare court-ready discovery tailored to your jurisdiction and your claims. You keep control of your case while experienced attorneys build demands that comply with Rule 34 and your local rules.

Representing yourself does not mean drafting alone. Our lawyers translate your facts into precise, proportional requests, prepare the definitions and instructions, and structure the document so a court will enforce it. We serve pro se plaintiffs pursuing evidence and pro se defendants responding to demands, across civil, employment, and commercial disputes. Where full representation fits, it is available on a retainer basis, subject to your jurisdiction, its applicable rules, and the availability of a licensed attorney in your state.

Attorneys and law firms rely on our drafting for overflow capacity and cost-effective support, and our documents are built to withstand objection. Learn why litigants hire LegalHusk to draft discovery requests and responses, then order your requests for production today so you meet every deadline with confidence.

Frequently Asked Questions

1. What is a discovery request example in plain terms?

A discovery request example is a sample of a formal demand one party serves on another during litigation. The most common type, a request for production, asks the opposing side to hand over documents, emails, and records tied to the case. It shows the exact wording and structure a court will enforce.

2. How many requests for production can I serve?

The Federal Rules of Civil Procedure set no numerical cap on requests for production, unlike the 25-interrogatory limit under Rule 33. Rule 26 proportionality still limits the total volume. Many state courts and individual judges impose their own caps, so confirm your local rule and any standing order before you serve.

3. What happens if the other side ignores my request for production?

No response within 30 days waives most objections and lets you file a motion to compel under Rule 37. The court can order production, award your costs, and impose sanctions for continued noncompliance. Persistent refusal exposes the party to evidentiary sanctions and, in severe cases, default.

4. Can I request electronically stored information and metadata?

Yes, Rule 34 expressly covers electronically stored information, including emails, spreadsheets, text messages, and metadata. You specify the form of production, such as native files with metadata intact. The responding party must produce ESI in the requested form or a reasonably usable form.

5. What is the difference between possession, custody, and control?

Possession means the party physically holds the document. Custody means the party keeps it. Control means the party has the legal right to obtain it, even from a third party such as an agent or affiliate. A request reaches all documents within any of the three, which is why control matters for records held by related entities.

6. Do I need to define terms in my requests?

Yes, defining recurring terms such as "document," "communication," and "relevant period" prevents the responding party from claiming ambiguity. Clear definitions close the door on evasive responses. A definitions section keeps each numbered request short while still capturing the full scope you intend.

7. How is a request for production different in state court?

State courts follow their own discovery codes, so deadlines, formats, and limits differ from the federal 30-day standard. California, New York, and Texas each set distinct rules and response times. Always confirm the governing statute and local rule in your jurisdiction before drafting or serving.

8. Can requests for production help settle a case?

Yes, documents obtained through production often reveal the strength or weakness of each side's position, which drives settlement. Financial records, contracts, and internal emails can expose liability or damages exposure. Our guide on using discovery requests to identify settlement opportunities explains that strategy.

Conclusion

A well-drafted discovery request example turns hidden evidence into a documentary record you can use to settle or win. A request for production under Rule 34 compels documents, ESI, and tangible things, and its power depends on precise categories, defined terms, fixed time frames, and strict deadline discipline. Draft narrow, tie each request to a claim, and calendar the 30-day clock. Self-represented litigants gain the most from getting the wording right the first time. Order court-ready requests for production from LegalHusk today, and put professional drafting behind your case.