Sample Request for Production of Documents: Format, Timing, and Objections

A sample Request for Production of Documents is a formal written demand served on another party in a civil case, built around four parts — a caption, definitions, instructions, and a numbered list of individual requests — and drafted under Rule 34 of the Federal Rules of Civil Procedure.¹ Get the structure and the specificity right and the other side has 30 days to produce. Get them wrong and you invite objections that can stall the case for weeks.

What the Document Must Contain

Every Request for Production follows the same skeleton. Courts expect the structural formality of any litigation filing, and missing pieces give the responding party easy grounds to object.

Caption and Introductory Statement

Start with the legal caption: the court, the full names of the parties, and the case number. Below the caption, a short introductory paragraph names the party making the request, identifies the party who must respond, cites Rule 34(a) as the authority, and states the 30-day response deadline.

Definitions

The definitions section locks down the terms that recur in your numbered requests. At minimum, define “document” broadly enough to cover electronically stored information — emails, text messages, databases, metadata, and files in any format. Define “you” or “your” to include the responding party along with their employees, agents, and representatives. Specify the date range that applies across the requests. Keep this section tight. Some courts have criticized boilerplate definitions as unnecessarily burdensome, so don’t pad with terms you never use.

Instructions

The instructions tell the responding party how to produce. Under Rule 34, documents must be produced either as they are kept in the ordinary course of business or organized and labeled to correspond with each numbered request.¹ State which method you want. Also instruct that any document withheld on privilege grounds must appear on a privilege log.

Privilege Log Instructions

The log isn’t optional. Rule 26(b)(5)(A) requires any party withholding otherwise discoverable material on privilege grounds to expressly state the claim and describe the withheld documents in enough detail for the other side to evaluate the privilege, without revealing the privileged content itself.² A typical entry includes date, author, recipients, subject matter, and the specific privilege claimed. Amendments effective December 1, 2025, encourage parties to negotiate the format and scope of privilege logging during the Rule 26(f) conference, which can save both sides time and expense.

The Numbered Requests

Below the instructions comes the numbered list. This is the heart of the document, and it is where drafting choices decide whether the production is useful or useless.

Writing Individual Requests That Hold Up

Rule 34 requires that each request describe the items or category of items with “reasonable particularity.” The responding party should be able to read the request and know, without guessing, what to look for.¹

Compare two versions of the same request. “All documents related to the project” invites an objection and probably gets one. “All contracts and amendments between Party A and Party B concerning the Elm Street project, dated between January 1, 2021, and the present” tells the responding party exactly what to pull.

A few habits make the difference:

Tie each request to a specific claim or defense in your case. Common categories include financial records, internal communications about a specific transaction or decision, personnel files, maintenance or inspection logs, and insurance policies.
Time-bound every request. Courts are far more likely to enforce a request covering a defined period than one demanding every document a company has ever created on a topic.
Identify the people or transactions involved by name. Generic categories draw overbreadth objections; named custodians and named projects don’t.

Specifying the Format for ESI

Rule 34(b)(1)(C) lets you specify the format you want electronically stored information produced in. If you don’t specify, the producing party can hand it over in whatever form they ordinarily maintain or in any “reasonably usable” form, which can mean a massive PDF dump with no search capability.¹ If you need native files with metadata intact or searchable text, say so in the request itself. Fighting about format after the fact is a losing use of time.

How Many Requests You Can Serve

Unlike interrogatories, which Rule 33 caps at 25, the Federal Rules impose no numerical limit on requests for production. Serve as many as the case needs. Proportionality still governs, though, and a court can limit discovery on its own or on motion if the requests are unreasonably cumulative or duplicative or if the burden outweighs the benefit.² Some districts impose their own caps by local rule, so check before you file.

Drafting Around the Objections You’ll Face

Objections to requests for production cluster in a few predictable categories. Knowing them lets you write past them in the first draft.

Overbreadth. The request sweeps too wide in time, subject, or scope. Narrow the date range, name the people or transactions, and target categories instead of asking for “all documents.”
Vagueness or ambiguity. The responding party claims they can’t tell what you want. Clear definitions and specific language in each request shut this down.
Undue burden. The effort to locate and produce is disproportionate to the case. Requests tightly focused on disputed issues are hard to challenge on burden grounds.
Privilege. The documents are protected by attorney-client privilege, work-product doctrine, or another recognized privilege. You can’t draft around a legitimate privilege claim, but requiring a privilege log lets you test overbroad assertions.
Relevance. The information has no bearing on any claim or defense. Tying each request explicitly to a pleaded claim or defense makes a relevance objection hard to sustain.

Scope is set by Rule 26(b)(1), which permits discovery into any nonprivileged matter relevant to a party’s claim or defense and proportional to the needs of the case. Proportionality turns on the importance of the issues, the amount in controversy, each side’s relative access to the information, the parties’ resources, and whether the burden outweighs the likely benefit.² Discoverable information doesn’t have to be admissible at trial. It just has to be relevant and proportional. The older “reasonably calculated to lead to the discovery of admissible evidence” phrasing was removed from the rules in 2015 because courts were using it to expand discovery beyond its intended scope.

Draft every request as though a judge will read it. If the other side objects, one will.

When You Can Serve and When They Must Respond

You generally cannot serve discovery requests until after the parties have held their Rule 26(f) conference, where they discuss claims, defenses, and a discovery plan.² Rule 34 does let a party deliver requests before the conference, but the response clock doesn’t start running until 30 days after the conference happens.¹ Some courts exempt certain case types from initial disclosure requirements, so check local rules and any scheduling order.

Service is usually accomplished by mail, email, or hand delivery on the opposing party or their attorney. Keep proof of service in case the other side later claims they never received it.

The responding party has 30 days from the date of service to respond in writing. The court can shorten or extend that period, and the parties can agree to a different deadline in writing. The response must address each request individually, either confirming production or stating with specificity the grounds for objection, and any objection must state whether responsive materials are being withheld on that basis.¹

If They Object or Don’t Respond

A missed deadline or a wall of objections doesn’t go straight to the judge. Rule 37(a)(1) requires any motion to compel to include a certification that the moving party “in good faith conferred or attempted to confer” with the non-complying party to resolve the dispute without court involvement.³ Skip that step and the motion is denied before the judge reads it.

The federal rule doesn’t dictate a format. A phone call, letter, or email can satisfy it, though many districts have local rules with more specific requirements. Explain what you believe is deficient, listen to the other side, and try to find middle ground. Document every communication.

If the meet-and-confer fails, a motion to compel under Rule 37(a) asks the court to order production. The specificity you built into the original requests pays off here, because the judge evaluates each disputed request against the scope of permissible discovery. There is a financial incentive to cooperate: if the court grants the motion, it must generally order the non-complying party or their attorney to pay the moving party’s reasonable expenses, including attorney’s fees, unless the non-compliance was substantially justified.³ The reverse is also true. A denied motion can leave you paying the other side’s costs. Disobeying an order compelling production opens the door to the full ladder of Rule 37(b) sanctions, up to and including default judgment.

1
Legal Information Institute. Federal Rules of Civil Procedure Rule 34
2
Legal Information Institute. Federal Rules of Civil Procedure Rule 26
3
Legal Information Institute. Federal Rules of Civil Procedure Rule 37