Request for Production: Drafting, Responding, and ESI Format

A request for production is the main discovery tool in federal civil litigation for getting documents, electronically stored information, tangible items, and property access from the opposing party. Federal Rule of Civil Procedure 34 governs the process. It lets one party demand that the other produce, allow inspection of, copy, test, or sample anything relevant that falls within the party’s possession, custody, or control. The responding party has 30 days to answer in writing, and mistakes in drafting, timing, preservation, or objections can waive rights or trigger sanctions.¹

What You Can Actually Request

Rule 34 covers three categories. Documents and electronically stored information in the responding party’s possession, custody, or control: contracts, invoices, personnel files, insurance policies, internal memos, emails, text messages, spreadsheets, database records, social media posts, voicemails. Tangible things, like a defective product, a piece of machinery, or a physical sample. And entry onto land or property to inspect, measure, photograph, or test it.¹

“Possession, custody, or control” is broader than it sounds. A party can be compelled to produce documents it does not physically hold, as long as it has a legal right to obtain them. Records stored with a third-party vendor or a cloud provider are still within the party’s control for discovery purposes. Parking documents with an outside entity does not shield them.

Relevance, Proportionality, and Privilege

Every request has to fall within the scope defined by Rule 26(b)(1): relevant to any party’s claim or defense and proportional to the needs of the case. Courts weigh six factors on proportionality: the importance of the issues, the amount in controversy, each party’s relative access to the information, the parties’ resources, how important the discovery is to resolving the dispute, and whether the burden or expense outweighs the likely benefit.²

Proportionality cuts both ways. A party pursuing a multi-million dollar claim will struggle to argue that broad document requests are excessive. In a smaller case, demanding years of company-wide email archives may legitimately be too much. Courts regularly limit discovery when retrieval costs dwarf the likely value of the information, especially for ESI held on backup tapes or legacy systems requiring forensic recovery.

If a party identifies sources of ESI that are not reasonably accessible because of undue burden or cost, it does not have to produce from those sources automatically. The requesting party can still pursue the data by showing good cause, and the court may shift retrieval costs or impose other conditions on the production.²

Material that clears relevance and proportionality is still off-limits if it is privileged. The two most common protections are attorney-client privilege, covering confidential communications between client and lawyer made to obtain legal advice, and the work-product doctrine under Rule 26(b)(3), which protects documents and tangible things prepared by or for a party’s attorney, consultant, or agent in anticipation of litigation.²

A party withholding responsive documents on privilege grounds has to say so expressly and give the other side enough detail to evaluate the claim. In practice, that means a privilege log identifying each withheld document by date, author, recipients, subject matter, and the specific privilege asserted. A vague entry saying only “attorney-client communication” is usually insufficient, and courts routinely order supplementation of inadequate logs.²

How to Draft a Request

Rule 34 requires that each request describe the items or categories “with reasonable particularity.”¹ The responding party should be able to read the request and know what to look for. “All documents relating to the project” is almost certainly too broad. “All emails between John Smith and Jane Doe regarding the Elm Street construction project from January 2024 through June 2025” gives a clear target.

Each request must also specify a reasonable time, place, and manner for the inspection or production.¹ Most productions happen digitally now, but inspections of physical items or property still need proposed dates and logistics. If you want electronic files in a particular format, like native Excel rather than static PDF, state that in the request. Otherwise the responding party chooses.

A well-drafted set typically opens with a definitions section. Defining “document” to include drafts, attachments, and non-identical copies prevents the responding party from producing only final versions. Defining “you” to include the party’s agents, subsidiaries, and representatives closes another common loophole. These definitions are not required by Rule 34, but experienced litigators treat them as essential.

Local court rules often add formatting requirements for captions, font size, page limits, and numbering. Check the local rules in the specific district before filing. Many clerks’ offices post templates.

Serving Requests Before the Rule 26(f) Conference

A party can serve requests for production before the parties hold their initial Rule 26(f) planning conference. The responding party’s 30-day clock does not start until after that conference happens.¹ Early service puts your requests in front of the other side so they can begin identifying responsive material while the discovery plan is still being negotiated.

Responding to a Request

The responding party has 30 days after service to provide a written response. If the request was served early under Rule 26(d)(2), the 30-day period begins after the first Rule 26(f) conference. The parties can agree to a different deadline, or the court can set one.¹

The written response must address each request individually, either stating that the party will comply or stating a specific objection. A party that fails to respond within the 30-day window risks waiving its objections entirely. Some courts will excuse a minor, non-prejudicial delay, but relying on judicial mercy is poor strategy.

The actual document production usually follows the written response by days or weeks, depending on volume. The responding party must organize the production either in the order the documents are kept in the ordinary course of business or in the categories matching the requests.¹ Dumping thousands of unorganized files to bury the important ones is sanctionable.

The duty does not end with the initial production. Under Rule 26(e), a party that has responded has an ongoing obligation to supplement or correct the response if it later learns the response was materially incomplete or incorrect, and the supplementation must be timely.² A batch of responsive emails discovered six weeks after production has to be disclosed promptly, not held until trial.

Common Objections and the Withholding Rule

The responding party can object on several recognized grounds:

Overbreadth or vagueness: the request fails to describe items with reasonable particularity, or sweeps in far more material than could be relevant.
Undue burden or expense: the cost or effort of locating and producing the material outweighs its value to the case.
Irrelevance: the requested items are not relevant to any claim or defense.
Privilege or work product: the material is protected by attorney-client privilege, the work-product doctrine, or another recognized privilege.
Documents do not exist: a party cannot be compelled to create documents that do not already exist. Discovery covers existing records, not new analyses or compilations.
Already provided or equally available: the requesting party already has the documents or can get them just as easily from another source.

An objection has to state whether any responsive materials are being withheld on the basis of that objection. The responding party can no longer object and leave the other side guessing. The response must be transparent: either “we object and are withholding 200 documents on this basis” or “we object but are producing all responsive documents despite the objection.”¹

Boilerplate objections (“overly broad, unduly burdensome, and not proportional to the needs of the case”) inserted reflexively into every response carry little weight with most judges. Courts increasingly treat generic objections as no objection at all.

When objections create a stalemate, the parties have to try resolving the dispute themselves before involving the court. Rule 37(a) requires any motion to compel to include a certification that the moving party conferred or attempted to confer in good faith.³ Most discovery disputes settle in these discussions, and judges notice when a party runs to court without a genuine attempt first.

ESI Format and Metadata

Electronic documents raise questions paper never did. The requesting party can specify the format it wants, such as native files, searchable PDFs, or TIFF images with extracted text. If the request does not specify, the responding party must produce either in the form the information is ordinarily maintained or in a reasonably usable form.¹

The rules do not explicitly require metadata by default, but a responding party cannot convert electronic files into a format that strips out useful features. If a spreadsheet is ordinarily maintained with formulas and sort functions, producing it as a flat PDF that removes those features is not a reasonably usable form. When metadata matters to the case, such as timestamps, authorship data, or editing history, request it explicitly and specify the production format. Leaving the choice to the responding party is where disputes start.

Preservation and Spoliation

The obligation to preserve relevant evidence begins before any request arrives. It starts the moment litigation is reasonably anticipated, whether from a demand letter, a complaint, or a credible verbal threat. Preservation means suspending automatic deletion policies, issuing a litigation hold to employees who may have responsive material, and identifying the specific types of information to be preserved.

A litigation hold notice should be in writing, explain why the hold is being issued, identify the categories of information to preserve, and instruct recipients to suspend any routine destruction. Instructions like “save everything important” are not enough. The hold should reach every person in the organization who may hold relevant documents, not just the records custodian.

When ESI that should have been preserved is lost because a party failed to take reasonable steps, and the information cannot be recovered through other discovery, Rule 37(e) authorizes the court to intervene. If the loss caused prejudice, the court can order measures to cure it. If the court finds the party intentionally destroyed the information to deprive the other side of its use, the consequences escalate: the court can presume the lost information was unfavorable, instruct the jury to draw that inference, or dismiss the case or enter a default judgment.³

The distinction between negligent and intentional destruction matters enormously. Negligent loss may draw a curative order. Intentional destruction can end the case.

Protective Orders for Sensitive Material

Discovery sometimes forces production of legitimately sensitive material: trade secrets, proprietary formulas, customer lists, financial data, personal health information. Rule 26(c) allows a party to ask the court for a protective order limiting how produced information can be used or who can see it. The party seeking protection must show good cause, which means a concrete risk of harm, not a general preference for secrecy.²

Many cases operate under a stipulated protective order negotiated at the start of discovery. These orders typically create tiered confidentiality designations. A “Confidential” designation restricts use of the information to the litigation and prevents public disclosure. A higher tier, often called “Attorneys’ Eyes Only,” limits access to outside counsel and their staff, keeping the information from the parties’ own business employees who might use it for competitive advantage. Before filing a motion for a protective order, the moving party must certify that it attempted to resolve the dispute with the other side first.²

Inadvertent Disclosure and Clawback

In productions involving thousands or millions of files, mistakes happen. A privileged email gets buried in a chain of routine correspondence and goes out the door. Without protection, that accidental production could waive the privilege, not just for that document but potentially for the entire subject matter.

Rule 26(b)(5)(B) provides a safety net. When a producing party realizes it has inadvertently disclosed privileged material, it can notify the receiving party of the claim and its basis. After receiving notice, the other side must promptly return, sequester, or destroy the information and any copies, and cannot use or disclose it until the privilege claim is resolved. If the receiving party already shared the document with someone else before being notified, it must take reasonable steps to retrieve it.²

For stronger protection, parties can ask the court to enter an order under Federal Rule of Evidence 502(d), which provides that disclosure connected with the litigation does not waive privilege, with that protection extending to any other federal or state proceeding.⁴ A 502(d) order lets both sides produce documents more quickly and with less expense on privilege review, because an accidental disclosure cannot be weaponized. Negotiating this order at the start of the case, before any production, is the smart move.

Documents from Non-Parties

Rule 34 only applies between parties to the lawsuit. To obtain documents from a non-party, such as a bank, employer, internet provider, or former business partner, you need a subpoena under Rule 45. A subpoena for document production, sometimes called a subpoena duces tecum, must issue from the court where the action is pending and can be signed by the clerk or by any attorney authorized to practice in that court.⁵

The geographic reach is limited. The subpoena can only require production at a location within 100 miles of where the non-party lives, works, or regularly conducts business in person.⁵ Before serving the subpoena on the non-party, you must serve a notice and a copy on every other party in the case. That notice requirement gives the other side a chance to object before the non-party turns over records that may include privileged or confidential material.

The non-party can push back. A person commanded to produce may serve a written objection before the earlier of the compliance date or 14 days after receiving the subpoena. The issuing party also has an independent obligation to avoid imposing undue burden or expense on the non-party.⁵ Courts take that duty seriously. Non-parties did not choose to be in the litigation, and judges are less tolerant of broad fishing expeditions aimed at them.

Sanctions for Non-Compliance

A party that ignores a request for production or defies a court order to produce faces escalating consequences under Rule 37. The first step is usually a motion to compel. If granted, the court typically awards the requesting party its reasonable attorney fees for bringing the motion.³

If a party then disobeys the court’s order to produce, Rule 37(b)(2) gives the court a menu of increasingly severe sanctions:

The court can deem certain facts established for purposes of the case, taking the disputed issue out of the non-compliant party’s hands.
The non-compliant party can be prohibited from introducing designated evidence or supporting certain claims or defenses.
The court can strike claims or defenses from the non-compliant party’s filings.
In extreme cases, the court can dismiss the case entirely or enter a default judgment against the disobedient party.
The court may treat the failure as contempt of court.

Courts impose these sanctions regularly when parties stonewall. The practical lesson is simple. If you have a legitimate reason not to produce something, raise a proper objection. If the court orders production anyway, comply. The cost of producing documents you would rather keep private is almost always less than the cost of sanctions.³

1
Legal Information Institute. Federal Rule of Civil Procedure 34 – Producing Documents, Electronically Stored Information, and Tangible Things, or Entering onto Land, for Inspection and Other Purposes
2
Legal Information Institute. Federal Rules of Civil Procedure Rule 26 – Duty to Disclose; General Provisions Governing Discovery
3
Legal Information Institute. Federal Rules of Civil Procedure Rule 37 – Failure to Make Disclosures or to Cooperate in Discovery; Sanctions
4
Legal Information Institute. Federal Rule of Evidence 502 – Attorney-Client Privilege and Work Product; Limitations on Waiver
5
Legal Information Institute. Federal Rules of Civil Procedure Rule 45 – Subpoena