Requests for Production in U.S. Litigation

Requests for Production (RFPs) are a formal discovery mechanism through which one party in litigation compels another party — or, in certain circumstances, a non-party — to produce documents, electronically stored information (ESI), and tangible things for inspection, copying, or testing. Governed primarily by Rule 34 of the Federal Rules of Civil Procedure, RFPs sit at the center of the discovery process in US litigation and are among the most consequential tools for building or defending a case. Mishandled production obligations carry significant legal risk, including court-imposed sanctions.

Definition and Scope

Under Federal Rule of Civil Procedure 34, a Request for Production permits any party to request that another party produce designated documents, electronically stored information in any form, or tangible things — or permit entry onto land or other property for inspection. The scope of what may be requested is tied directly to the general discovery standard in Rule 26(b)(1), which limits permissible discovery to material that is "relevant to any party's claim or defense and proportional to the needs of the case."

The phrase "documents and things" encompasses a broad range of materials: paper records, contracts, emails, spreadsheets, photographs, video recordings, physical objects, and metadata. The 2015 amendments to the Federal Rules of Civil Procedure, implemented through Supreme Court order and Congressional review, sharpened the proportionality requirement. Courts applying these amendments weigh factors including the importance of the issues, the amount in controversy, and the relative access each party has to relevant information.

In state court systems, each jurisdiction maintains parallel rules. California's Code of Civil Procedure §§ 2031.010–2031.320 establishes a comparable framework, while New York's CPLR Article 31 governs document demands in New York state courts. The structural mechanics differ slightly — for example, California imposes a 35-document-set limit in certain contexts — but the foundational logic mirrors the federal model.

How It Works

The RFP process follows a structured sequence governed by procedural rules and court-specific local rules.

  1. Drafting: The requesting party identifies categories of documents relevant to claims or defenses. Each request must describe items with "reasonable particularity" under Rule 34(b)(1)(A), meaning the responding party can identify what is being sought without guessing.

  2. Service: RFPs are served on the responding party, typically after the Rule 26(f) conference in federal court. The responding party has 30 days to respond under Rule 34(b)(2)(A), unless the court orders otherwise or the parties stipulate to a different timeline.

  3. Response: The responding party must state whether it will comply with each request, object to it, or state that it lacks the responsive documents. Under Rule 34(b)(2)(C), objections must be stated with specificity — a blanket "overly broad and burdensome" objection is insufficient on its own.

  4. Production: Documents may be produced as kept in the ordinary course of business or organized according to the categories in the request. For ESI, the producing party may specify a form of production (e.g., native format, TIFF with load files); if no form is specified, Rule 34(b)(2)(E) requires production in the form in which the ESI is "ordinarily maintained."

  5. Meet and Confer: When disputes arise over adequacy of responses, Rule 37(a) requires parties to confer in good faith before filing a motion to compel. A motion to compel under Rule 37 is the standard enforcement mechanism when a party fails to produce.

  6. Privilege Review: Before producing, the responding party reviews materials for privilege. Documents withheld on privilege grounds must be identified on a privilege log (attorney-client privilege in litigation and the work product doctrine are the two primary shields), which must describe each withheld document with enough detail to allow the requesting party to assess the claim.

Common Scenarios

RFPs arise in virtually every category of civil litigation, but the volume and complexity vary significantly by case type.

Commercial litigation: Contract disputes frequently center on RFPs targeting internal communications, draft agreements, financial records, and board minutes. In a breach-of-contract action, requests directed at the opposing party's understanding of contract terms at the time of execution are routine.

Employment cases: Title VII claims under the Civil Rights Act of 1964 regularly generate RFPs seeking personnel files, performance evaluations, HR complaint records, and comparator employee records. The Equal Employment Opportunity Commission (EEOC) guidance on recordkeeping informs what employers are expected to retain.

Products liability and mass tort: In multidistrict litigation (MDL), defendants frequently face coordinated RFPs targeting design documents, safety testing records, regulatory submissions to the FDA or EPA, and post-market surveillance data. The volume of responsive ESI in these cases routinely reaches into the millions of documents.

Third-party subpoenas: Rule 45 governs document subpoenas directed at non-parties. The standard is the same relevance and proportionality test, but non-parties may invoke undue burden objections with greater force. A non-party served with a Rule 45 subpoena must comply or move to quash within 14 days of service under Rule 45(d)(2)(B).

Decision Boundaries

Understanding the limits of RFPs requires distinguishing them from related discovery tools and recognizing where court discretion applies.

RFPs vs. Interrogatories: Interrogatories in US litigation elicit narrative explanations in response to written questions and are capped at 25 in federal court under Rule 33 absent leave of court. RFPs target documents and things, not verbal explanations. When a party needs both the documents and the factual context surrounding them, both tools are typically deployed together.

RFPs vs. Depositions: Depositions in US litigation generate testimonial evidence through oral examination. RFPs generate documentary evidence. In practice, document production is often completed before key depositions so that counsel can question witnesses about specific documents.

Proportionality limits: Courts have denied or limited RFPs where the cost of production is disproportionate to the stakes. In Zubulake v. UBS Warburg, 217 F.R.D. 309 (S.D.N.Y. 2003), Judge Scheindlin articulated a cost-shifting framework for ESI that became foundational to electronic discovery (eDiscovery) practice. Although the Federal Rules were subsequently amended to codify proportionality directly, Zubulake remains widely cited.

Sanctions for non-compliance: Rule 37(b) authorizes sanctions ranging from adverse inference instructions to default judgment for willful failure to produce. Rule 37(e) specifically governs spoliation of ESI — courts may impose curative measures or adverse inference instructions where ESI was lost because a party failed to take reasonable steps to preserve it and the loss causes prejudice. Litigation holds and document preservation obligations trigger before litigation commences, at the point when litigation is "reasonably anticipated."

Privilege waiver risk: Producing privileged documents inadvertently does not automatically waive privilege in federal court. Rule 26(b)(5)(B) establishes a "clawback" process, and Federal Rule of Evidence 502(b) limits subject-matter waiver when inadvertent disclosure occurs. Parties routinely negotiate Rule 502(d) orders — court-endorsed agreements — to allow faster production without full pre-production privilege review.

References

📜 1 regulatory citation referenced  ·  🔍 Monitored by ANA Regulatory Watch  ·  View update log

Explore This Site

Regulations & Safety Regulatory References Tools & Calculators Attorney Fee Estimator