Document discovery is where most civil cases are actually won or lost. Long before a jury is empaneled or a summary-judgment motion is briefed, the parties exchange the paper and the data that will become the evidence at trial, and the single most powerful tool for forcing that exchange is the request for production of documents — usually abbreviated "RFP," and governed in federal court by Rule 34 of the Federal Rules of Civil Procedure. An RFP is simply a written demand that the other side hand over designated documents, electronically stored information, and tangible things that are within its possession, custody, or control. It sounds mundane. In practice, responding to RFPs is one of the most consequential, expensive, and ethically fraught tasks a litigator performs — and one of the few where a careless paragraph can forfeit a client's substantive rights or hand the adversary a case-ending sanction.

This article explains, from the ground up, how to object and respond to requests for production the right way. It is written for three audiences at once. A judge reading it should find the rules and authorities stated accurately. A practicing lawyer should find practical strategy, model language, and the traps to avoid. A business owner, paralegal, or self-represented litigant should be able to follow every step without a law degree, because every term of art is explained in plain English the first time it appears. Throughout, invented parties — we will use Acme Corp. and Beta Industries — illustrate the mechanics with concrete, clearly labeled hypotheticals.

By the end, you will understand the scope of discovery and the 2015 proportionality amendments that reshaped it; the precise structural requirements of a Rule 34 response, including the now-mandatory duty to say whether you are withholding documents; why "boilerplate" objections can forfeit your client's rights; how electronically stored information ("ESI") changes everything about form of production, native files, and metadata; how privilege logs and Federal Rule of Evidence 502 protect confidential material from waiver; the preservation and litigation-hold duties that run beneath the whole process; the meet-and-confer duty that the rules require before you run to the judge; the sanctions available under Rule 37, including the special spoliation regime of Rule 37(e); and how third-party subpoenas under Rule 45 fit into the picture. For a broader orientation to the discovery toolbox, this article is a companion to our practical discovery refresher, and it pairs naturally with our guides to interrogatories and requests for admission.

What a Request for Production Is — and Where It Fits

Discovery is the formal, pretrial process by which each side obtains information from the other and from third parties. The Federal Rules give litigants several discovery devices: depositions (live, sworn questioning, addressed in our guide to depositions in federal civil litigation), interrogatories (written questions a party must answer under oath), requests for admission (demands that a party admit or deny specific facts), and requests for production of documents and things. Each device has its niche. Interrogatories are good for nailing down identities, dates, and contentions. Requests for admission narrow what must be proved at trial. Depositions test witnesses in real time. But the request for production is the device that moves the evidence itself — the emails, contracts, spreadsheets, text messages, Slack threads, design files, and records that the case will ultimately turn on.

Rule 34(a) authorizes a party to serve on any other party a request to produce — and to permit inspection, copying, testing, or sampling of — designated documents or electronically stored information "stored in any medium," as well as tangible things and even entry onto land or property. The breadth of "any medium" is deliberate: it captures not only Word documents and PDFs but databases, voicemails, instant messages, workplace-collaboration threads, social-media activity, data from "Internet of Things" devices, and information that exists only as bits on a server. The Federal Rules define ESI broadly to include "writings, drawings, graphs, charts, photographs, sound recordings, images, and other data or data compilations." Rule 34(a) also limits the universe to items within the responding party's possession, custody, or control — a phrase that matters enormously and that we examine below.

Critically, Rule 34 reaches only parties to the lawsuit. To obtain documents from a non-party — a former employee, a bank, a vendor, a cloud-storage provider — a litigant must use a subpoena under Rule 45, which we discuss near the end of this article. Confusing the two is a common rookie error: you cannot "Rule 34" a stranger to the litigation, and you cannot subpoena your own adversary for documents you should have requested under Rule 34. For the bigger picture of how RFPs fit alongside pleadings, motions, and the rest of the federal docket, see our overview of the federal civil litigation paper trail.

The Scope of Discovery: Relevance and Proportionality Under Rule 26(b)(1)

Everything in document discovery flows from a single sentence in Rule 26(b)(1), which defines what is discoverable. As amended, it provides that parties may obtain discovery regarding "any nonprivileged matter that is relevant to any party's claim or defense and proportional to the needs of the case." Two independent gatekeepers live in that sentence: relevance and proportionality. A request must clear both, and a response that ignores either one is incomplete.

Relevance is broad — but no longer boundless

Relevance in discovery is broader than relevance at trial. Information need not be admissible to be discoverable; the 2015 amendments deleted the old "reasonably calculated to lead to the discovery of admissible evidence" phrasing precisely because lawyers had twisted it into a near-limitless license to demand anything. (The phrase was meant only to clarify that inadmissibility is not a bar to discovery; it had metastasized into a freestanding definition of scope.) What survives is the requirement that the matter be relevant to a claim or defense — that is, tied to the actual issues framed by the pleadings, not to the subject matter of the lawsuit at large. If Acme sues Beta for breach of a single supply contract, Beta's unrelated dealings with other customers are generally outside the scope, however interesting they might be.

A useful discipline for both requesting and responding counsel is to map each request to a specific element of a claim or defense. If you cannot articulate which element a category of documents bears on, the request is probably overbroad — and the response can say so with specificity rather than reflex. This mapping exercise pays off twice: it sharpens the requests you draft and supplies the precise, factual objections that survive a motion to compel.

Proportionality: the 2015 amendments' center of gravity

The 2015 amendments did more than trim the relevance language; they elevated proportionality from a buried provision into the operative test, listing six factors that courts and parties must weigh:

  1. the importance of the issues at stake in the action;
  2. the amount in controversy;
  3. the parties' relative access to relevant information (often called "information asymmetry");
  4. the parties' resources;
  5. the importance of the discovery in resolving the issues; and
  6. whether the burden or expense of the proposed discovery outweighs its likely benefit.

The drafters were explicit about their intent. As Chief Justice John Roberts emphasized in his 2015 Year-End Report on the Federal Judiciary, the amendments were meant to end the era in which discovery was used as "a weapon" to coerce settlement through expense rather than to find the truth. The Advisory Committee Note to the 2015 amendment stresses that proportionality is not a new concept — the factors had long lived in Rule 26(b)(2)(C) — but that moving them into the definition of scope makes proportionality a shared responsibility of both parties, not merely a defense to be raised after the fact. The Committee was equally explicit that the change "does not place on the party seeking discovery the burden of addressing all proportionality considerations" or permit a responding party "to refuse discovery simply by making a boilerplate objection that it is not proportional."

No single factor controls. A modest amount in controversy does not automatically defeat discovery if the issues are important (think civil-rights cases) or if one party holds nearly all the relevant information (think an individual plaintiff suing a corporation that controls the records). Conversely, even a high-stakes case does not justify discovery whose burden swamps its benefit. The art of a modern proportionality objection lies in marshaling concrete facts about each factor — actual cost estimates, data volumes, the availability of the same information from cheaper sources — rather than chanting the word "disproportionate." We return to this below in the discussion of drafting effective objections. Our guide to evaluating and assessing a civil case explains how early case budgeting feeds directly into credible proportionality positions.

Possession, custody, or control

Rule 34 obligates a party to produce only what is within its possession, custody, or control. Possession and custody are intuitive — documents in your own files or your lawyer's. "Control," however, is a legal concept that varies by circuit. The majority "legal right" test asks whether the party has the legal right, on demand, to obtain the documents from the entity that physically holds them. Under that test, a corporation generally controls documents held by its wholly owned subsidiaries, by its agents, and by employees acting within the scope of employment. A minority of courts apply a broader "practical ability" test, asking whether the party has the practical ability to obtain the documents regardless of any legal entitlement. The boundaries matter: if Acme is sued and the requested documents sit only with an independent third-party vendor that Acme has no legal right to command, Acme can properly object that the documents are outside its control — and the requesting party must reach them by Rule 45 subpoena instead.

A modern wrinkle: employees' personal devices and personal accounts. Whether a company "controls" text messages on an employee's personal phone, or messages in a personal email account used for business, is heavily litigated and fact-specific. Courts increasingly find control where a company has a "bring your own device" policy, reimburses for the device, or otherwise has the practical and legal ability to obtain the data; they are more skeptical where the device is purely personal and the company has no policy reaching it. Ephemeral and disappearing-message applications — Signal, Snapchat, Telegram's secret chats, auto-deleting Slack channels — present a related and growing danger: their use after a preservation duty attaches has drawn sanctions in several high-profile cases, on the theory that affirmatively choosing a tool designed to destroy evidence can itself supply the intent that Rule 37(e)(2) requires. The safest course for a responding party is to address device and messaging-app issues candidly in the response and in meet-and-confer, to disable auto-deletion on relevant accounts the moment a hold issues, and never to stay silent and risk a later motion.

The Mechanics of a Rule 34 Response

Rule 34(b)(2) sets out the procedural skeleton every response must follow. Get the skeleton wrong and even meritorious objections can be deemed waived.

Timing

A party served with requests for production must respond in writing within 30 days after being served (Rule 34(b)(2)(A)). When requests are served with the summons and complaint or before the parties' Rule 26(f) conference — an early planning meeting the rules require — the clock instead runs from the first Rule 26(f) conference. The 30-day period can be extended by stipulation or court order, and reasonable extensions are routinely granted in document-heavy cases. (State practice varies: New Jersey, for example, generally allows 35 days, with a longer window for a defendant served at the outset of the case — a reminder always to check the forum's rules.) But the deadline is real: an untimely response can forfeit objections, including, in many courts, objections based on privilege. Calendar the date the instant requests arrive.

Respond to each request, separately

Rule 34(b)(2)(B) requires that, "for each item or category," the responding party either state that inspection and production will be permitted as requested or state with specificity the grounds for objecting to the request, including the reasons. The response is request-by-request. A single global paragraph purporting to answer 75 separate requests does not satisfy the rule, and a court asked to rule on it will struggle to tell which objection applies to which request — a fact that almost always cuts against the responding party.

The 2015 amendments' three structural commands

The 2015 amendments rewrote Rule 34(b)(2) to cure three chronic abuses. Every practitioner should commit these to memory.

First — specificity (Rule 34(b)(2)(B)). Objections must state the grounds "with specificity." Generic recitals — "overly broad, unduly burdensome, vague, and not reasonably calculated to lead to admissible evidence" — do not comply. The objection must explain what about the request is objectionable and why.

Second — and this is the single most important and most overlooked rule — the duty to state whether documents are being withheld (Rule 34(b)(2)(C)). The rule provides: "An objection must state whether any responsive materials are being withheld on the basis of that objection." This was the headline fix of 2015. Before it, a party could lodge an objection, produce some documents "subject to and without waiving" the objection, and leave the requesting side guessing whether anything had actually been held back. Now the response must affirmatively say so. The Advisory Committee Note explains the goal plainly: to end "the practice of objecting to discovery requests reflexively — but not in fact withholding any responsive materials — out of a fear that documents will be 'overlooked.'" The Committee also offered a practical safe harbor: a party need not provide a detailed, document-by-document description of what is withheld; "an objection that states the limits that have controlled the search for responsive and relevant materials qualifies as a statement that the materials have been 'withheld.'" In other words, if you tell the requesting party the search you actually ran — the custodians, the date range, the search terms — and they can see what you left out, you have satisfied the duty.

Third — production timing and rolling production (Rule 34(b)(2)(B)). When a party states it will produce, the production must be completed no later than the time specified in the request or another reasonable time stated in the response. This codified the common practice of rolling productions — producing documents in batches as review proceeds — but it also requires the responding party to commit to a date rather than leaving production open-ended. A response that says "documents will be produced" without a deadline is incomplete and invites a motion to compel.

A worked example of a compliant response

Hypothetical. Suppose Beta serves Acme with this request:

Request No. 14: All documents and communications concerning the design, testing, and manufacture of the Model X widget from January 1, 2019 to the present.

A compliant, modern response might read:

Response to Request No. 14: Acme objects to this Request to the extent it seeks documents protected by the attorney-client privilege or the work-product doctrine; such documents will be identified on a privilege log as provided in the parties' ESI protocol. Acme further objects to the phrase "concerning . . . manufacture" as overbroad and not proportional to the needs of the case insofar as it would encompass routine, voluminous shop-floor production records that bear on no claim or defense; the parties' dispute concerns the design of the Model X, not the volume or cost of its manufacture. Acme also objects to the time period to the extent it predates the first commercial sale of the Model X in March 2020.

Subject to and without waiving the foregoing objections, Acme will produce non-privileged design specifications, engineering test reports, and internal communications concerning the design and testing of the Model X for the period March 1, 2020 to the date of this response, located through a reasonable search of the files of the four engineers and two project managers identified in Acme's initial disclosures, using the search terms set forth in Exhibit A. Acme is withholding documents responsive to this Request on the basis of the overbreadth and time-period objections stated above (specifically, manufacturing-volume records and pre-March 2020 materials), and on the basis of privilege. Acme will substantially complete this production within 30 days.

Notice what this response does. It objects with specificity, not boilerplate. It explains the search it ran. It states affirmatively that documents are being withheld and identifies the limits that controlled the search — satisfying Rule 34(b)(2)(C). It commits to a completion date. And it preserves privilege with a promise of a log. That is the template.

The Death of the Boilerplate Objection

For decades, lawyers responded to document requests with a wall of reflexive, copy-pasted objections, often headed by a page of "General Objections" incorporated by reference into every individual response. The 2015 amendments, and a wave of judicial decisions enforcing them, have made that practice dangerous.

The leading cautionary opinion is Fischer v. Forrest, 2017 WL 773694 (S.D.N.Y. Feb. 28, 2017), in which Magistrate Judge Andrew Peck — one of the most influential voices in modern e-discovery — issued a "wake-up call" to the bar. Reviewing responses that still recited the pre-2015 "reasonably calculated" language and laid down a slab of general objections, Judge Peck held that such responses violated Rule 34 as amended and warned that "any discovery response that does not comply with Rule 34's requirement to state objections with specificity (and to clearly indicate whether responsive material is being withheld on the basis of objection) . . . may be deemed a waiver of all objections (except as to privilege)." That warning has teeth: courts across the country have overruled boilerplate objections and ordered production, and some have found objections waived entirely. See, e.g., Liguria Foods, Inc. v. Griffith Laboratories, Inc., 320 F.R.D. 168 (N.D. Iowa 2017), in which Chief Judge Mark Bennett — visibly exasperated by competent lawyers on both sides serving pages of "obstructionist" boilerplate — declined to impose sanctions only because the practice was so endemic, while warning that future offenders would not be spared.

Why are general objections so perilous? Several reasons. They are not "specific" as Rule 34 demands. They almost never say whether documents are actually being withheld, in violation of Rule 34(b)(2)(C). And the maneuver of producing documents "subject to and without waiving" a pile of unexplained objections leaves both the requesting party and the court unable to tell what, if anything, has been held back — the precise mischief the 2015 amendments targeted. Many courts now treat an objection that asserts burden or overbreadth but produces everything anyway as either meaningless or, worse, as evidence of bad faith. There is also a deeper, often-ignored point made years before the 2015 amendments in Mancia v. Mayflower Textile Services Co., 253 F.R.D. 354 (D. Md. 2008): then-Magistrate Judge Paul Grimm explained that Rule 26(g) — which requires that every discovery response be signed, and that the signature certify the response is consistent with the rules and not interposed for any improper purpose — makes reflexive boilerplate a certification problem, not merely a stylistic one. Each unfounded objection is, in effect, a signed representation to the court that the lawyer cannot honestly make.

This does not mean general objections are categorically forbidden. A short, genuinely applicable set of preliminary statements — for example, that the response is based on a reasonable search to date and that the party reserves the right to supplement under Rule 26(e) — is fine. What is forbidden is using "General Objections" as a substitute for the request-specific, fact-based objections the rule requires. The discipline is simple to state and hard to practice: object only to what you actually object to, say why with specificity, and say whether you are withholding anything. A useful internal checklist before serving responses is to ask, for every objection, three questions: Is it specific? Is it true (are we really limiting our search because of it)? Have we stated whether we are withholding? If the answer to any is "no," fix the response before it goes out.

Substantive Objections, Used Correctly

With the boilerplate cleared away, several substantive objections remain genuinely useful when supported by facts and tied to a specific request.

Relevance / scope. When a request reaches beyond any claim or defense, say so and explain the gap. "Request No. 22 seeks Acme's tax returns for 2015–2018. This is a trademark-infringement action; Acme's pre-dispute tax filings bear on no issue of liability or the requested injunctive relief, and damages are measured by Beta's profits, not Acme's tax position." That is a relevance objection a court can evaluate.

Overbreadth. Overbreadth differs from relevance: the request may seek some relevant material but is drawn too widely — an unbounded time period, every custodian in the company, "any and all" documents "relating to" a sprawling topic. The fix in the response is to identify the overbroad component and propose the reasonable scope you will honor instead. Courts reward responding parties who narrow constructively rather than refuse wholesale.

Proportionality. As discussed, proportionality is now the heavyweight objection — but only with evidence. A bare assertion that production is "unduly burdensome" is worthless; a sworn declaration from an IT director estimating that the request would require collecting and reviewing 4.2 terabytes from 60 custodians at an estimated review cost of $900,000 in a case with $250,000 in controversy is powerful. Tie the burden estimate to the Rule 26(b)(1) factors explicitly, factor by factor. Courts have shown they will quantify proportionality when given the numbers and will reject it when given only adjectives.

Vagueness and ambiguity. Reserve this for genuine ambiguity, and explain it. "The term 'sales materials' in Request No. 9 is undefined and could mean anything from final marketing brochures to internal pricing analyses; Acme will interpret it to mean customer-facing marketing materials and produce on that basis unless Beta clarifies." Note that this response does the work courts want: it does not hide behind the ambiguity but adopts a reasonable construction and produces.

Duplication and "equally available." If the requesting party already has the documents, or can obtain them as easily from public sources or its own files, say so. This factor (relative access) is now part of the proportionality calculus.

Possession, custody, or control. As above, object when the documents are genuinely beyond the party's legal right to obtain, and point the requester toward the proper source (often a Rule 45 subpoena).

A word on tone and credibility. The objections that succeed share a common quality: they read as though a reasonable lawyer wrote them after actually thinking about the request, not as though a template was dropped onto every line. Judges develop a fast instinct for the difference. An objection that concedes the relevant core of a request, narrows the overbroad fringe, and explains the narrowing in two sentences signals good faith; a wall of identical objections signals obstruction. Because discovery rulings are reviewed only for abuse of discretion, the trial judge's first impression of which side is being reasonable tends to harden into the law of the case. Spend your credibility carefully: object hard where you genuinely have grounds, and produce graciously where you do not.

Worked example: turning a boilerplate response into a defensible one

Hypothetical. Consider a request and two responses. Request No. 31: "All documents relating to your company's finances." A boilerplate response reads: "Objection. This request is overly broad, unduly burdensome, vague and ambiguous, and not reasonably calculated to lead to the discovery of admissible evidence." That response violates the current rule three times over: it is not specific, it uses deleted pre-2015 language, and it never says whether anything is withheld. A defensible response reads: "Acme objects to Request No. 31 as overbroad and not proportional to the needs of the case because 'all documents relating to . . . finances,' without limitation as to time, subject, or relevance to any claim or defense, would sweep in decades of routine accounting records bearing on no issue in this breach-of-warranty action, where the only financial issue is the amount Beta paid for the Model X units. Subject to that objection, Acme will produce the invoices, purchase orders, and payment records reflecting Beta's purchases of the Model X for 2020 through 2022. Acme is withholding other financial documents on the basis of this objection." The second version objects with specificity, ties the burden to proportionality, narrows constructively, and states what is withheld. It is the version a court will sustain.

Privilege, Work Product, and the Privilege Log

Some material is discoverable in the sense of being relevant and proportional, yet still protected from disclosure because it is privileged. The two protections that dominate document discovery are the attorney-client privilege and the work-product doctrine. Asserting them correctly — and not waiving them carelessly — is among the highest-stakes tasks in litigation.

Attorney-client privilege

The attorney-client privilege protects confidential communications between a lawyer and client made for the purpose of obtaining or providing legal advice. It is the oldest privilege known to the common law, and its purpose is to encourage candor between client and counsel. The protection is robust but narrow and easily lost. It covers the communication, not the underlying facts; a client cannot shield a fact from discovery merely by mentioning it to a lawyer. It requires confidentiality, so looping in a third party (other than one whose presence furthers the legal advice, such as an interpreter or, under the right circumstances, a consultant) can destroy it. In the corporate setting, Upjohn Co. v. United States, 449 U.S. 383 (1981), held that the privilege can extend to communications between counsel and lower-level employees gathered to enable legal advice — but the privilege belongs to the corporation, not the individual employees, and only the corporation can waive it. Communications that are predominantly business advice rather than legal advice fall outside the privilege, a recurring problem for in-house counsel who wear both hats; courts often ask whether legal advice was the "primary purpose" of the communication.

Work-product doctrine

The work-product doctrine, rooted in Hickman v. Taylor, 329 U.S. 495 (1947), and codified at Rule 26(b)(3), protects documents and tangible things prepared in anticipation of litigation or for trial by or for a party or its representative (including consultants, insurers, and agents, not just lawyers). Work product comes in two strengths. "Fact" or "ordinary" work product — e.g., a compiled set of witness statements — is discoverable only on a showing of substantial need plus an inability to obtain the substantial equivalent without undue hardship. "Opinion" work product — the lawyer's mental impressions, conclusions, opinions, and legal theories — receives near-absolute protection and is rarely discoverable at all. The doctrine is broader than the attorney-client privilege in some respects (it covers materials prepared by non-lawyers and protects more than communications) but, unlike the privilege, it can be overcome by the right showing. A perennial fight is the "anticipation of litigation" line: documents prepared in the ordinary course of business — routine incident reports, regular audits — generally are not work product even if litigation later ensues.

The privilege log

When a party withholds responsive documents as privileged, Rule 26(b)(5)(A) requires it to (i) expressly make the claim and (ii) describe the nature of the withheld documents in a manner that, without revealing the protected information, "will enable other parties to assess the claim." The vehicle for this is the privilege log — a document-by-document (or, increasingly, category-by-category) listing that typically includes the date, author, recipients (including anyone copied), document type, the privilege asserted, and a description of the subject matter sufficient to evaluate the claim.

Privilege logs are notoriously expensive and time-consuming — in large matters they can cost more than the production of non-privileged documents — and they are a frequent battleground. Three practical points. First, categorical logging is increasingly accepted: where a custodian-by-custodian, document-by-document log would be unduly burdensome, parties may agree (or a court may order) to log by categories of documents, a practice the Sedona Conference and many courts endorse. Negotiate this in the ESI protocol up front. Second, an inadequate log is itself a waiver risk: courts have found privilege forfeited where the log was so threadbare that the opposing party could not assess the claim, or where the party logged plainly non-privileged materials in bad faith. Third, watch for the recurring trap of communications that merely copy a lawyer or that combine business and legal content — these are the entries most often challenged, and the description should make the legal purpose visible without disclosing the advice itself. Describe enough to justify the claim; reveal nothing that gives the privilege away.

Waiver, Federal Rule of Evidence 502, and Clawback Orders

In a world of million-document productions, the nightmare scenario is inadvertent waiver — accidentally producing a privileged email and thereby losing the privilege not only for that email but potentially for every related communication on the same subject. Before 2008, the consequences of a slip were governed by inconsistent state and federal common law, and the risk drove up review costs because parties felt compelled to review every document by hand. The problem has only intensified as ESI volumes have grown, because privileged material can hide in metadata, embedded files, and email threads no human reviewer ever opens.

Federal Rule of Evidence 502, enacted in 2008, was designed to tame that risk, and every litigator handling document discovery must understand its three operative subsections.

Rule 502(a) — scope of waiver. When a disclosure does waive the privilege, the waiver extends to undisclosed communications only if (1) the waiver was intentional, (2) the disclosed and undisclosed communications concern the same subject matter, and (3) fairness requires them to be considered together. This curtails the old "subject-matter waiver" doctrine, under which one voluntary disclosure could blow privilege across an entire topic.

Rule 502(b) — inadvertent disclosure. An inadvertent disclosure in a federal proceeding does not operate as a waiver if the holder (1) took reasonable steps to prevent disclosure and (2) promptly took reasonable steps to rectify the error once discovered, including (where applicable) following Rule 26(b)(5)(B)'s clawback procedure. This is a fault-based standard: reasonable precautions plus prompt correction generally preserve the privilege — but it invites a fact-intensive, after-the-fact fight over whether the precautions really were "reasonable," which is exactly the fight a 502(d) order avoids.

Rule 502(d) — court orders, the practitioner's best friend. This is the provision sophisticated litigators rely on most. A federal court may enter an order providing that disclosure of privileged material in the litigation does not waive the privilege — and that order is enforceable against non-parties and in any other federal or state proceeding. A well-drafted 502(d) order (often combined with a "clawback" provision in the protective order) means that an accidental production does not waive privilege regardless of whether the producing party took "reasonable steps," eliminating the costly fight over whether precautions were adequate under 502(b). Judge Peck and other courts have gone so far as to say it is "akin to malpractice" not to seek a 502(d) order in a document-intensive case. Pair it with a clawback procedure specifying how a party demands return of inadvertently produced material and how the recipient must sequester or destroy it. Rule 26(b)(5)(B) supplies a default clawback mechanism, but an explicit, agreed protocol is far preferable. As a model, a typical 502(d) order states in substance that the production of privileged or protected information "is not a waiver of any privilege or protection in this or any other federal or state proceeding," and then layers the return-and-sequester mechanics on top.

A caution: a 502(d) order protects against waiver by inadvertent production; it does not authorize indiscriminate "quick peek" or "data dump" productions with no review, and parties still owe candor obligations to the court and each other. Use it as a safety net, not a license to abandon review.

Electronically Stored Information: Where Modern Discovery Lives

The overwhelming majority of discoverable material today is electronically stored information — email, text and chat messages, documents, spreadsheets, databases, social-media content, collaboration-tool threads, and metadata. The volume of discoverable ESI in a typical matter now dwarfs the volume of paper, and finding, preserving, and reviewing it requires technical expertise that paper never demanded. The Federal Rules treat ESI as a first-class subject of discovery, and Rule 34 contains special provisions for it. ESI introduces three recurring issues that paper never did: form of production, native versus image formats, and metadata.

Form of production under Rule 34(b)(1)(C) and 34(b)(2)(E)

Rule 34(b)(1)(C) lets the requesting party specify the form in which it wants ESI produced. If the request specifies a form, the responding party must either produce in that form or object and state the form it intends to use (Rule 34(b)(2)(D)). If the request does not specify a form, Rule 34(b)(2)(E) supplies defaults: the responding party must produce ESI either in the form "in which it is ordinarily maintained" or in a form "that is reasonably usable," and it need not produce the same ESI in more than one form. A frequently litigated rule is that a party may not "downgrade" usability — for example, by converting searchable, sortable native files into flat, non-searchable images stripped of metadata — when that would make the production materially less usable than how the data is kept. The best practice, strongly favored by courts, is to negotiate an ESI protocol (often entered as an order) at the Rule 26(f) conference, specifying formats, metadata fields, de-duplication, and search methodology before any production occurs. The same rules apply, with parallel citations, to ESI produced under a Rule 45 subpoena.

Native files versus TIFF/PDF images

There are, broadly, four production formats, and the choice drives both cost and usability. The trade-offs come down to who bears the processing cost, whether the documents can be Bates-stamped and redacted, and whether the receiving party can search, sort, and print them:

  • Native production delivers the file in its original application format (the actual .xlsx, .docx, .pst). It preserves full functionality, embedded formulas, and metadata, and it is cheap for the producing party because no conversion is required. Its drawbacks: native files cannot have Bates numbers or confidentiality stamps embossed on their face (the identifier must live in the file name or an accompanying load file), and they cannot be redacted without first converting the redacted document to an image.
  • Image production (TIFF or PDF) converts each document to a static picture of each page. Images print uniformly, accept Bates stamps and confidentiality legends, and can be redacted — which is why partially privileged documents are usually produced as images. But a raw image is not text-searchable and carries no metadata.
  • Image production with load and text files — the modern default in most large cases — pairs TIFF/PDF images with (1) a load file containing extracted metadata (custodian, dates, author, recipients, file path) and (2) a text file containing the document's extracted searchable text. This combination gives the receiving party Bates-stamped, redactable, and searchable, sortable documents, at the cost of more processing by the producing party.
  • Paper or static PDF without load files — the least useful for any sizeable case, because it strips searchability and metadata entirely; reserve it for small volumes or documents that exist only on paper.

Spreadsheets and other dynamic file types are typically produced natively even within an image-based protocol, because converting a spreadsheet to an image destroys formulas and renders large sheets incomprehensible. The practical takeaway: parties usually agree on a hybrid — images with load and text files for ordinary documents, native production for spreadsheets, presentations, audio, video, and other file types that images mangle. Spell this out in the ESI protocol.

Metadata

Metadata is "data about data" — the hidden fields a file carries, such as author, creation and modification dates, sender and recipient, file path, and (for email) subject and time stamps. Metadata can be decisive: a modification date can reveal when a contract was actually altered; email header metadata can establish who knew what and when. But not all metadata is relevant, and collecting and preserving it can add cost. The Federal Rules do not squarely resolve the discoverability of metadata; absent a directive from the forum court, the relevant fields should be negotiated in the ESI protocol. Two cautions for producing parties: first, collect ESI in a forensically sound way that preserves metadata from the outset, because metadata is easily and irreversibly altered by careless copying (even opening a native file can change its "last accessed" date); and second, remember that producing native files transmits all embedded metadata, including potentially privileged or embarrassing tracked changes and comments — another reason sensitive documents are produced as redacted images.

For the related problem of proving that ESI is authentic once produced — a question that arises at summary judgment and trial, not just in discovery — see our discussion of authenticating website screenshots as evidence. Federal Rules of Evidence 902(13) and 902(14), added in 2017, now allow certain electronic records and copies to be self-authenticated by a written certification, easing the path from production to admission.

Collaboration tools and "modern attachments"

A fast-growing headache is ESI generated by workplace-collaboration tools — Slack, Microsoft Teams, Google Chat — and the "modern attachments" (cloud links rather than embedded files) those platforms produce. Chat data is conversational, threaded, and constantly updated; it does not map neatly onto the email-and-document paradigm that the production-format rules were built around. Linked documents create a special trap: an exported chat may show a hyperlink to a file stored elsewhere, and unless the protocol addresses it, the linked file's contents — and the version that existed when the message was sent — can be lost. Counsel should raise collaboration-tool and modern-attachment issues explicitly at the Rule 26(f) conference, agree on how threads will be grouped and how linked files will be collected, and confirm that the company's preservation steps actually capture these systems, which often sit outside the email archive.

Inaccessible ESI and cost-shifting

Rule 26(b)(2)(B) provides a specific safety valve for ESI: a party need not provide discovery of ESI from sources it identifies as "not reasonably accessible because of undue burden or cost" — think disaster-recovery backup tapes or legacy systems. The responding party must still identify those sources. If the requesting party moves to compel, the responding party bears the burden of showing inaccessibility; even then, the court may order production for good cause and may shift costs to the requesting party. The influential framework for cost-shifting comes from Zubulake v. UBS Warburg LLC, 217 F.R.D. 309 (S.D.N.Y. 2003) ("Zubulake I"), whose seven factors — including the specificity of the request, the availability of the information elsewhere, the total cost compared to the amount in controversy and to each party's resources, and each party's ability and incentive to control costs — courts still cite. The Zubulake line of opinions is also foundational to modern preservation and spoliation law, discussed below.

Technology-assisted review and search methodology

A final ESI topic deserves real attention because it increasingly drives both cost and disputes: how a producing party actually finds responsive documents in a haystack of millions. The traditional approach is keyword searching — agreeing on a list of search terms and producing the documents that hit. Keywords are cheap and transparent but blunt: they miss responsive documents that use synonyms or shorthand, and they over-capture irrelevant documents that happen to contain a common term. A more sophisticated approach is technology-assisted review (TAR), also called predictive coding, in which lawyers train a machine-learning model on a sample of documents they have coded as responsive or not, and the model then ranks the remaining population by likely responsiveness. Beginning with Da Silva Moore v. Publicis Groupe, 287 F.R.D. 182 (S.D.N.Y. 2012) — the first federal opinion to approve TAR — courts have repeatedly endorsed TAR as an acceptable, and sometimes superior, methodology. In Rio Tinto PLC v. Vale S.A., 306 F.R.D. 125 (S.D.N.Y. 2015), Judge Peck observed that "the case law has developed to the point that it is now black letter law that where the producing party wants to utilize TAR for document review, courts will permit it."

Equally important is the limit courts have placed on the requesting party's ability to dictate the producing party's process. The general rule — flowing from Sedona Principle 6, which most courts treat as persuasive — is that the responding party is best situated to choose how to preserve and produce its own ESI, so long as the result is a reasonable, good-faith search. The practical points for a responding party are to negotiate search methodology in the ESI protocol where possible, to document the validation of whatever method is used (so the search can be defended as reasonable if challenged), and to resist a requesting party's demand to dictate the internal review process absent a real showing that the chosen method is deficient. Generative-AI review tools are now entering this space; the same principles apply — defensibility and validation matter more than the brand of technology.

Preservation, the Litigation Hold, and Spoliation Under Rule 37(e)

The duty to produce documents presupposes a prior duty to preserve them. That duty arises when litigation is reasonably anticipated — which can be well before suit is filed, the moment a party knows or should know that evidence may be relevant to future litigation. Once the duty attaches, the party must suspend ordinary document-destruction practices (auto-delete settings, recycling of backup tapes, routine email purges) and issue a litigation hold: a written instruction to relevant custodians to preserve potentially relevant material. Zubulake v. UBS Warburg LLC, 220 F.R.D. 212 (S.D.N.Y. 2003) ("Zubulake IV"), and the later Zubulake V opinion, 229 F.R.D. 422 (S.D.N.Y. 2004), established that counsel has an affirmative, ongoing duty to ensure preservation — to issue the hold, monitor compliance, and follow up with key custodians, not merely to send one email and forget it. A defensible hold identifies the custodians and data sources, describes the categories to preserve in plain language, suspends auto-deletion on the relevant systems, and is reissued and re-confirmed as the case develops and new custodians emerge.

When ESI that should have been preserved is lost, the governing rule in federal court is Rule 37(e), comprehensively rewritten in the 2015 amendments to replace a chaotic patchwork of circuit standards. Understanding its structure is essential because it deliberately raises the bar for the most severe sanctions.

Rule 37(e) applies only when ESI (1) should have been preserved in anticipation or conduct of litigation, (2) was lost because a party failed to take reasonable steps to preserve it, and (3) cannot be restored or replaced through additional discovery. If those threshold conditions are met, the rule provides two tiers of consequence:

  • Rule 37(e)(1) — prejudice-based curative measures. Upon a finding of prejudice to another party from the loss, the court "may order measures no greater than necessary to cure the prejudice." These are remedial, not punitive — for example, permitting evidence and argument about the loss, ordering further discovery, or excluding certain evidence.
  • Rule 37(e)(2) — intent-based severe sanctions. The harshest sanctions — an adverse-inference instruction telling the jury it may or must presume the lost information was unfavorable, dismissal, or default judgment — are available only upon a finding that the party "acted with the intent to deprive another party of the information's use in the litigation." This is a demanding, near-bad-faith standard. Crucially, under (e)(2) the court need not separately find prejudice; the intent finding supplies it. Mere negligence, or even gross negligence, is not enough for an adverse-inference instruction under the federal rule — a significant change from pre-2015 law in circuits like the Second, which had permitted adverse inferences for gross negligence under Residential Funding Corp. v. DeGeorge Financial Corp., 306 F.3d 99 (2d Cir. 2002).

Courts applying the rewritten rule have not hesitated to impose severe sanctions where the intent standard is met. In DR Distributors, LLC v. 21 Century Smoking, Inc., 513 F. Supp. 3d 839 (N.D. Ill. 2021), the court issued a lengthy, widely cited opinion sanctioning a party (and faulting counsel) after relevant chat and webmail data was lost through a failure to identify and preserve the right sources — a cautionary tale about how easily collaboration-tool and personal-account data slips through an inadequate hold.

The practical lesson for responding parties is unambiguous: preserve early and document your preservation. Issue the hold in writing, identify custodians and data sources, suspend auto-deletion, confirm compliance, and keep records of every step. If a court later asks whether you took "reasonable steps," a contemporaneous paper trail is the difference between a curative measure and a case-ending sanction. For requesting parties, Rule 37(e)(2)'s intent requirement means that proving negligence alone will not yield an adverse inference; the focus must be on evidence of deliberate destruction — the use of disappearing-message apps after a duty attaches, the wiping of devices, the suspicious timing of "routine" deletions.

Sanctions for Discovery Misconduct Under Rule 37

Beyond spoliation, Rule 37 is the general enforcement engine for discovery. When a party fails to respond to RFPs, responds evasively or incompletely, or stonewalls, the requesting party's remedy is a motion to compel under Rule 37(a). An evasive or incomplete response "must be treated as a failure to . . . respond" (Rule 37(a)(4)). If the motion is granted, Rule 37(a)(5) creates a presumption that the losing party pays the movant's reasonable expenses, including attorney's fees, unless the position was substantially justified or an award would be unjust. That fee-shifting presumption is a powerful deterrent — and a powerful reason to take a defensible position rather than a reflexive one. It cuts both ways: a requesting party that files a motion to compel without first conferring, or that loses, can be ordered to pay the responding party's fees.

If a party then disobeys an order compelling production, Rule 37(b) authorizes escalating sanctions: deeming facts established, prohibiting the disobedient party from supporting or opposing designated claims, striking pleadings, staying proceedings, dismissing the action, rendering default judgment, and treating the disobedience as contempt. These tools, combined with the spoliation regime, mean that discovery abuse can lose the case outright — not on the merits, but as a sanction. And as Mancia underscored, Rule 26(g)'s certification requirement gives courts an independent basis to sanction lawyers personally for objections and responses that were not the product of a reasonable inquiry.

The Meet-and-Confer Duty: You Must Try Before You Sue

Federal courts do not want to referee discovery disputes that the parties could resolve themselves. Both Rule 37(a)(1) and virtually every district's local rules require that, before filing a motion to compel, the movant confer or attempt in good faith to confer with the opposing party to resolve the dispute without court action. Many courts require a certification describing those efforts, and judges routinely deny motions — sometimes with irritation — when the certification is perfunctory or the "conference" was a single boilerplate letter.

A genuine meet-and-confer is not a formality; it is where most document-discovery disputes are actually solved. Effective conferral starts early, addresses specific requests rather than vague complaints ("Request 14 is too broad" is useless; "Request 14's undefined ten-year period and inclusion of manufacturing-volume records is the problem, and here is the narrower scope we propose" is productive), and is documented in writing. Reach agreements on time periods, custodians, search terms, and production formats, and memorialize every agreement in writing — a confirming email is fine — to avoid later disputes about what was decided. Professional, reasonable conduct in conferral also pays dividends later: judges remember which side was cooperative when they exercise their broad discretion over discovery, and over the fee-shifting that accompanies a granted or denied motion to compel. The Mancia court framed the meet-and-confer duty as a natural extension of the parties' shared obligation to make discovery cooperative and proportionate rather than adversarial theater.

Protective Orders and Confidentiality

Much of what is produced in discovery is sensitive: trade secrets, pricing data, personnel files, customers' personal information. Rule 26(c) authorizes the court, for good cause, to issue a protective order to shield a party or person from "annoyance, embarrassment, oppression, or undue burden or expense." Protective orders can limit who may see produced material, restrict its use to the litigation, require return or destruction at the case's end, and create tiers of confidentiality — most commonly a "Confidential" tier and a more restrictive "Attorneys' Eyes Only" (AEO) tier for the most competitively sensitive material, which only outside counsel and retained experts (not the client's business personnel) may review. In practice, parties almost always negotiate a stipulated protective order early, frequently bundling in the Rule 502(d) clawback provision discussed above. For businesses worried about exposing trade secrets in litigation, a carefully drafted protective order is often the difference between producing and fighting to the death; our guide to building a trade secret protection program addresses the upstream measures that make confidentiality claims credible, and our overview of protecting trade secrets explains the substantive law those orders are meant to safeguard.

Third-Party Discovery: Rule 45 Subpoenas

Because Rule 34 reaches only parties, documents in the hands of non-parties must be obtained by subpoena under Rule 45. A Rule 45 document subpoena (technically a subpoena duces tecum) commands a non-party to produce designated documents or ESI. The scope of what may be sought is the same Rule 26(b)(1) standard — relevant and proportional — but Rule 45 layers on protections for the non-party, who, after all, did not choose to be dragged into someone else's lawsuit.

Several Rule 45 features matter. First, a subpoena commanding production may be served anywhere in the United States, but Rule 45(c) limits where compliance can be required — generally within 100 miles of where the person resides, works, or regularly transacts business. Second, the party serving the subpoena must "take reasonable steps to avoid imposing undue burden or expense" on the non-party (Rule 45(d)(1)), and the court must enforce that duty, including by imposing sanctions for breach. Third, the non-party may serve written objections within 14 days (or before the compliance date, if sooner) under Rule 45(d)(2)(B); doing so shifts the burden to the serving party to move to compel. Fourth, the court must quash or modify a subpoena that requires disclosure of privileged material, imposes undue burden, or fails to allow reasonable time to comply (Rule 45(d)(3)). The same form-of-production rules that govern Rule 34 ESI productions apply to Rule 45 subpoenas, and non-parties enjoy the same right to specify or object to formats and to assert that data is not reasonably accessible.

A practical note for responding non-parties: a duty to preserve is inherent in the subpoena process (Rule 45(g)), so even though you are not a party, you should issue a litigation hold and preserve responsive material once you receive — or reasonably anticipate — a subpoena or a preservation demand. You should also consider negotiating reimbursement of your production costs; non-parties have stronger cost-reimbursement claims than parties do, given Rule 45's explicit burden-avoidance command. But remember that a bare assertion of burden will not carry the day: courts have overruled non-party objections and denied fee requests where the non-party offered adjectives instead of specific evidence of its actual cost and effort. For litigants navigating cross-border production, our guides to serving defendants in China and serving Chinese defendants in IP litigation address how service and discovery mechanics shift when a witness sits abroad.

A Practical Workflow for Responding to RFPs

Drawing the threads together, here is a disciplined sequence for responding to a set of requests for production.

First, docket the deadline immediately — 30 days in federal court, subject to the Rule 26(f) trigger and any stipulated extension. Second, issue or confirm the litigation hold and verify preservation across all relevant custodians and data sources, including email, collaboration tools, personal devices reached by company policy, and any system with auto-deletion; if you have not done this already, do it before anything else, because spoliation cannot be cured retroactively. Third, read each request against the pleadings, mapping it to specific claims or defenses, and flag overbreadth, irrelevance, vagueness, privilege exposure, and proportionality concerns. Fourth, negotiate scope and an ESI protocol with opposing counsel — custodians, date ranges, search terms or TAR methodology, de-duplication, production format, metadata fields, treatment of collaboration-tool and linked-file data, and a Rule 502(d)/clawback order — ideally before you collect a single document, because doing this work up front prevents the most expensive disputes. Fifth, collect ESI defensibly, preserving metadata, and process it into a review platform. Sixth, review for responsiveness, privilege, and confidentiality, building your privilege log as you go. Seventh, draft request-by-request responses that object with specificity, state whether documents are withheld (Rule 34(b)(2)(C)), and commit to a completion date, producing in the agreed format with appropriate confidentiality designations. Eighth, supplement under Rule 26(e) as new material surfaces — the duty to supplement is ongoing, and a stale "no responsive documents" answer that later proves false invites sanctions. Throughout, document everything: the hold, the searches, the conferral, the productions. The party that can show the court a clean, reasonable, well-documented process almost always fares better than the party defending a black box.

Key Takeaways

Modern document discovery rewards precision and punishes reflex. The scope of discovery is relevance and proportionality under Rule 26(b)(1), and the 2015 amendments made proportionality a shared, affirmative obligation rather than an afterthought. A Rule 34 response must address each request specifically, commit to a production date, and — most importantly — state whether responsive documents are being withheld on the basis of each objection (Rule 34(b)(2)(C)); satisfying that duty can be as simple as disclosing the limits that controlled your search. Boilerplate, copy-pasted objections are not just ineffective; they can waive your client's rights and expose counsel to Rule 26(g) sanctions, as Fischer v. Forrest, Liguria Foods, and Mancia v. Mayflower make clear. ESI dominates discovery, so master form of production, the native-versus-image trade-offs, metadata, and the new headaches of collaboration tools and TAR, and lock them all down in an ESI protocol. Protect privilege with careful logs, an understanding of Federal Rule of Evidence 502, and — in any document-intensive case — a Rule 502(d) order. Preserve early and document it, because Rule 37(e) makes the harshest spoliation sanctions available only on proof of an intent to deprive, but also makes preservation failures unforgiving when they occur. Meet and confer in good faith before running to the judge. And remember that documents from non-parties require a Rule 45 subpoena, with its own burden-avoidance protections. Do these things well and document discovery becomes a source of advantage; do them carelessly and it becomes the place your case goes to die.

Frequently Asked Questions

How long do I have to respond to a request for production in federal court? Thirty days after service under Rule 34(b)(2)(A), unless the requests were served with the complaint or before the Rule 26(f) conference (in which case the clock runs from that conference), or unless the parties stipulate or the court orders a different time. State courts often differ — New Jersey, for example, generally allows 35 days — so always check the forum's rules. Missing the deadline can waive your objections, so calendar it the moment the requests arrive.

What does it mean that I must "state whether documents are being withheld"? Rule 34(b)(2)(C), added in 2015, requires that each objection say whether any responsive materials are actually being held back because of it. The point is to stop parties from objecting reflexively while quietly producing everything, or from withholding documents without telling anyone. You can satisfy the rule by describing the limits that controlled your search — for example, the custodians, date range, and search terms you used — so the other side can see what you left out.

Are general objections still allowed? A short set of genuinely applicable preliminary statements is acceptable, but using a block of "General Objections" as a substitute for specific, fact-based, request-by-request objections is not. Courts increasingly treat boilerplate objections as non-compliant with Rule 34 and may deem them waived, leaving only privilege intact; some also treat reflexive boilerplate as a violation of the Rule 26(g) certification that the responding lawyer signs.

What is the difference between native and TIFF production? Native production delivers the file in its original format (e.g., the actual spreadsheet), preserving functionality and metadata but resisting Bates-stamping and redaction. TIFF (or PDF) production converts each page to an image that can be stamped and redacted but is not searchable on its own; it is usually paired with load files (metadata) and text files (searchable text). Most cases use a hybrid: images-plus-load-files for ordinary documents and native production for spreadsheets and other dynamic file types.

How do I protect privileged documents from being waived if I accidentally produce one? Take reasonable review precautions, act promptly to claw back any inadvertent production, and — most importantly — obtain a Rule 502(d) order at the outset. A 502(d) order provides that disclosure does not waive privilege in that litigation or any other federal or state proceeding, eliminating the costly fight over whether your precautions were "reasonable" under Rule 502(b). Many judges consider it close to malpractice not to seek one in a document-intensive case.

Do I have to produce text messages and Slack or Teams chats? Generally yes, if they are relevant, proportional, and within your possession, custody, or control. Chat data and text messages are ESI like any other, and collaboration-tool threads and "modern attachments" (cloud links) are an increasingly common subject of motions. Address how this data will be preserved, collected, and produced in the ESI protocol, and make sure your litigation hold actually reaches these systems — losing chat data through an inadequate hold has produced serious sanctions.

What happens if my client deleted relevant documents before I got involved? That is a potential spoliation problem governed by Rule 37(e). If the data should have been preserved, was lost through a failure to take reasonable steps, and cannot be restored, a court may order curative measures on a showing of prejudice. The most severe sanctions — an adverse-inference instruction, dismissal, or default — require proof that someone acted with the intent to deprive the other side of the information. Move quickly to assess what was lost, whether it can be recovered, and how to document the circumstances honestly.

Can I get documents from someone who is not a party to the lawsuit? Yes, but not through Rule 34. You must serve a subpoena under Rule 45, which carries special protections for the non-party, including geographic limits on compliance, a duty on the serving party to avoid undue burden, a 14-day window to object, and a court's mandatory duty to quash subpoenas that seek privileged material or impose undue burden.

Related Articles

This article is provided by mclaw.io for general informational purposes only and does not constitute legal advice. Discovery rules and their interpretation vary by jurisdiction and change over time, and the application of any rule depends on the specific facts of your matter. You should consult qualified counsel licensed in your jurisdiction before acting on any information contained here.