Responding to Rule 34 Document Requests: A Practical Checklist

Litigation > Discovery | Published 15 December 2024 - Updated 17 December 2024 | UpLaw - uplaw.us

A Rule 34 response is the highest-stakes routine task in litigation: a single careless paragraph can waive a client's objections, hand the other side a document dump they will punish, or seed a spoliation motion. This checklist gives responding counsel the disciplined sequence, the doctrine behind each step, and the model language courts reward.

Keywords: Rule 34, requests for production, litigation hold, proportionality, ESI protocol, form of production, metadata, privilege log, FRE 502(d) clawback, Rule 37(e) spoliation, meet and confer, duty to supplement, possession custody or control.

Every civil case of any size runs on documents. The complaint frames the dispute, the depositions test the witnesses, but the paper — the emails, the Slack threads, the spreadsheets, the contract drafts with tracked changes — is where cases are usually won or lost. Under Federal Rule of Civil Procedure 34, the mechanism for extracting that paper is the request for production: a written demand that an opposing party turn over designated documents, electronically stored information (ESI), and tangible things within its possession, custody, or control, and permit their inspection or copying. Serving good requests is a craft. Responding to them well is a discipline, and it is the discipline that gets lawyers into trouble.

The trouble is structural. A responding party is asked to hunt through its own client's files for evidence that will often be used against the client, to do so within thirty days, to assert every good objection without asserting the frivolous ones, to preserve everything relevant from the moment litigation became foreseeable, and to certify under Rule 26(g) that the whole exercise was reasonable. Miss the deadline and you may waive objections, including — in many courts — privilege. Preserve too little and you invite a spoliation motion under Rule 37(e). Object with a wall of boilerplate and you expose the client to a motion to compel and yourself to sanctions. Produce in the wrong form and you may have to do it twice. The margin for improvisation is thin.

This checklist reduces that risk to a repeatable process. It reflects the architecture Congress and the Advisory Committee built into the Rules, especially the 2015 amendments, which moved proportionality to the center of the scope inquiry and — in the single most overlooked reform of that cycle — required a responding party that objects to state whether it is withholding anything on the basis of that objection. For the doctrinal deep dive that sits behind this operational guide, read the companion treatment, Requests for Production: A Comprehensive Guide to Objecting and Responding. This checklist is the field manual; that guide is the treatise.

A note on method before the phases begin. Throughout, we track a hypothetical to keep the doctrine concrete. Nimbus Analytics, Inc. v. Cirrus Data Labs, LLC is an invented trade-secret and breach-of-contract action in which Nimbus, the plaintiff, has served sixty-eight document requests on Cirrus, a mid-size software company. You represent Cirrus. The requests reach engineering repositories, executive email, a company Slack workspace, and — Nimbus suspects — a set of Signal messages among Cirrus's founders. Nothing about Nimbus v. Cirrus is real; everything about the rules governing your response is.

How to use this checklist

The phases below run in rough chronological order, but discovery is iterative, not linear. Preservation begins before the requests arrive and never stops. The meet-and-confer that shapes your ESI protocol should happen before you collect a single file, yet you will return to it repeatedly. Treat the phases as a loop you traverse with each new set of requests, each new custodian, and each new dispute, rather than a track you run once.

Each phase carries a checklist, a short why it matters, and — where useful — a worked example drawn from Nimbus v. Cirrus. A condensed master checklist appears near the end for quick reference, followed by the primary and secondary authority and the related UpLaw resources.

The statutory architecture in one page

Rule 34 does not operate alone. Five other provisions do most of the real work, and you cannot respond well without holding all six in your head at once.

• Rule 26(b)(1) sets the scope of all discovery: matter that is (a) nonprivileged, (b) relevant to a claim or defense, and (c) proportional to the needs of the case, measured by six factors. The 2015 amendments elevated proportionality into the definition of scope and deleted the old, much-abused phrase permitting discovery "reasonably calculated to lead to the discovery of admissible evidence." That phrase is gone; do not quote it, and be wary of any adversary who does.
• Rule 34 supplies the mechanics: the 30-day response window, the requirement to respond to each request separately, the duty to object with specificity, the duty to state whether material is withheld, and the rules governing the form in which ESI is produced.
• Rule 26(b)(5) governs privilege: how you claim it and the log you must provide so the requesting party and the court can test the claim.
• Rule 26(g) is the certification rule — the discovery analog of Rule 11. Signing a response certifies, after reasonable inquiry, that it is warranted, not interposed for delay, and neither unreasonable nor unduly burdensome. It is the hook for most objection-abuse sanctions.
• Rule 37 enforces everything: 37(a) for motions to compel and their fee-shifting, 37(b) for violating discovery orders, and 37(e) for the loss of ESI that should have been preserved.
• Rule 45 governs documents held by non-parties, which a Rule 34 request cannot reach.

Overlaying all of this is Federal Rule of Evidence 502, the privilege-waiver statute, whose subsection (d) is the most valuable single order a document-heavy defendant can obtain. Keep this map in view. Nearly every judgment call in a Rule 34 response is really a question about which of these provisions controls.

Phase 1: Calendar the deadline and lock down preservation

Checklist.

• [ ] Docket the response deadline the instant the requests arrive: 30 days after service under Rule 34(b)(2)(A), adjusted for the method of service, unless the requests were delivered with the summons and complaint or before the Rule 26(f) conference (in which case the 30 days run from the first Rule 26(f) conference) or the parties stipulate to a different date.
• [ ] Calendar an internal draft deadline at least ten days before the real one, because collection and review always take longer than counsel expect.
• [ ] Issue or confirm a written litigation hold: a plain-language instruction to every custodian who may hold relevant material, identifying the subject matter, directing preservation, and suspending routine deletion.
• [ ] Suspend auto-delete and retention-purge settings across email, document management systems, collaboration platforms (Slack, Teams), ticketing systems, voicemail, and backup rotation.
• [ ] Extend the hold to modern and non-obvious sources: text messages, personal devices reachable under a bring-your-own-device policy, cloud storage, and ephemeral or disappearing-message applications.
• [ ] Document the hold: who received it, when, what it said, and how compliance was monitored.

Why it matters. Two independent risks converge in this phase. The first is waiver by tardiness. A response served late can forfeit objections; many courts treat even the privilege objection as waived when a party blows the deadline without seeking an extension or showing good cause. The 30-day clock is not a suggestion, and "we were still collecting" is not, by itself, cause.

The second risk is spoliation, and it cannot be cured after the fact. The duty to preserve attaches when litigation is reasonably anticipated — often well before a complaint is filed, sometimes the moment a credible demand letter lands (a link worth following: Drafting an Effective Demand Letter: The Basics explains why sending or receiving one can trigger the duty). The foundational articulation remains Judge Scheindlin's Zubulake opinions: Zubulake v. UBS Warburg LLC, 220 F.R.D. 212 (S.D.N.Y. 2003) ("Zubulake IV"), which fixed the trigger and scope of the preservation duty, and Zubulake v. UBS Warburg LLC, 229 F.R.D. 422 (S.D.N.Y. 2004) ("Zubulake V"), which held that counsel bear an affirmative, ongoing obligation to ensure that clients actually preserve and collect — not merely to send a memo and move on. A generation later, DR Distributors, LLC v. 21 Century Smoking, Inc., 513 F. Supp. 3d 839 (N.D. Ill. 2021), showed how the same failure metastasizes with modern data: counsel who never learned that key custodians used personal webmail and chat, and who let that data vanish, produced a 256-page sanctions opinion and a cautionary tale about competence with ESI.

The 2015 amendment to Rule 37(e) reworked the consequences. For ESI that should have been preserved but was lost because a party failed to take reasonable steps, and that cannot be restored or replaced, a court may order curative measures no greater than necessary to cure the prejudice (37(e)(1)); the severe sanctions — an adverse-inference instruction, dismissal, or default — require a finding that the party acted with the intent to deprive another of the information's use (37(e)(2)). The Advisory Committee was explicit that this intent requirement forecloses the older approach of some circuits, which permitted an adverse inference on a mere showing of negligence. See Fed. R. Civ. P. 37(e) advisory committee's note to 2015 amendment (rejecting Residential Funding Corp. v. DeGeorge Financial Corp., 306 F.3d 99 (2d Cir. 2002)). The practical lesson has not changed: the way to win a spoliation fight is to never have one, and that means a real hold, monitored, from the earliest moment the duty could plausibly have attached.

Modern sources deserve a paragraph of their own. Preservation used to mean not shredding paper and not wiping the email server. It now means understanding where a business actually communicates. Slack and Teams messages are documents. Text messages are documents. And ephemeral messaging — Signal, disappearing Slack messages, auto-expiring channels — is the sharpest edge. Continued use of a disappearing-message app after the duty to preserve has attached can itself supply the "intent to deprive" that Rule 37(e)(2) requires, because a factfinder may infer that the party chose a self-destructing channel precisely to keep evidence from surfacing. Turning off disappearing messages, or exporting them, is not optional once litigation is foreseeable.

Worked example. In Nimbus v. Cirrus, you learn on intake that Cirrus's three founders coordinate on Signal with disappearing messages set to seven days, and that the engineering team uses a Slack workspace with a ninety-day retention policy. Before you draft a single response, you: (1) instruct the founders in writing to disable disappearing messages on any thread touching Nimbus, the disputed code, or the parties' contract, and to export existing threads; (2) direct Cirrus's IT lead to place a legal hold flag on the Slack workspace so the ninety-day purge stops; and (3) log all of it. If Nimbus later moves under Rule 37(e), the story Cirrus tells is one of prompt, documented preservation — not the DR Distributors story of a client left to police itself. For the front-end mechanics of preservation, initial disclosures, and the discovery plan, see Rule 26 Initial Disclosures and the Discovery Plan: A Practical Checklist.

Phase 2: Read each request against the pleadings

Checklist.

• [ ] Map every request to a specific element of a claim or defense in the operative pleadings. If you cannot connect a request to any element, that is your relevance objection — stated with specificity, not as a reflex.
• [ ] Flag, request by request, the grounds that genuinely apply: overbreadth (in time, custodian, or subject), irrelevance, undue burden, vagueness or ambiguity, privilege exposure, and disproportion.
• [ ] Run each request through Rule 26(b)(1)'s two gates: is the material relevant to a claim or defense, and is production proportional to the needs of the case?
• [ ] For proportionality, work the six factors deliberately: (1) the importance of the issues at stake, (2) the amount in controversy, (3) the parties' relative access to the information, (4) the parties' resources, (5) the importance of the discovery in resolving the issues, and (6) whether the burden or expense outweighs the likely benefit.
• [ ] Assess possession, custody, or control for each category, and note where responsive material sits with a third party beyond your client's legal right or practical ability to obtain.

Why it matters. The 2015 amendments made proportionality a shared, affirmative obligation rather than a defensive afterthought, and Chief Justice Roberts devoted his 2015 Year-End Report on the Federal Judiciary to the point. But proportionality is a factual argument, not an incantation. A court will not credit the bare word "disproportionate." It will credit custodian counts, data volumes, review-hour estimates, and dollar figures tied factor by factor to Rule 26(b)(1). Relevance, likewise, is anchored in the pleadings: the Supreme Court's classic statement that relevance for discovery is broad but not boundless, Oppenheimer Fund, Inc. v. Sanders, 437 U.S. 340, 351-52 (1978), still frames the inquiry, and the deletion of the "reasonably calculated" language narrowed, not widened, the field.

Possession, custody, or control carries a hidden circuit split worth knowing. Rule 34 reaches only what the responding party controls, but "control" is defined two ways. Some courts apply a legal-right test: a party controls documents it has a legal right to obtain on demand. Others apply a broader practical-ability test: a party controls documents it has the practical ability to obtain, even absent a legal right — a standard that can sweep in materials held by affiliates, agents, or foreign parents. Compare the practical-ability formulation discussed in In re NTL, Inc. Securities Litigation, 244 F.R.D. 179 (S.D.N.Y. 2007), with the narrower legal-right approach many courts prefer. Which test your forum uses can determine whether your client must produce a sister company's files or can point the requester to a Rule 45 subpoena. Know the answer before you object.

Worked example. Nimbus's Request No. 41 seeks "all documents concerning any product Cirrus has ever developed." Cirrus makes four products; only one is accused. You map the request against the complaint, which pleads misappropriation of a single trade secret embodied in one product line, and you object that the request is overbroad and disproportionate to the extent it reaches three unrelated products, while agreeing to produce responsive documents for the accused product. That is a relevance-and-overbreadth objection a court will respect because it is tethered to the pleadings and paired with a reasonable production. Request No. 52 seeks financials held only by Cirrus's Irish parent. If your forum uses the legal-right test and Cirrus has no contractual right to demand those files, you say so and direct Nimbus to Rule 45 and the Hague framework — a topic that quickly grows complicated when the custodian is abroad. For early-case scoping of what a matter will demand in discovery, see Assessing a Civil Lawsuit: A Comprehensive Early-Case Framework and the companion Evaluating a New Civil Case: A Practical Checklist.

Phase 3: Negotiate scope and an ESI protocol

Checklist.

• [ ] Meet and confer — ideally at or before the Rule 26(f) conference and before collecting a single document — on custodians, date ranges, data sources, and the mechanics of ESI.
• [ ] Negotiate the search methodology: agreed keyword terms, or technology-assisted review (TAR / predictive coding), plus de-duplication, email threading, and how disputes over the search will be resolved.
• [ ] Address collaboration-tool data and "modern attachments" (cloud links rather than attached files) expressly, so that linked files and the version that existed when a message was sent are captured.
• [ ] Agree on the form of production: native files for dynamic formats, images (TIFF or PDF) with load files and extracted text for the rest, and the specific metadata fields to be produced.
• [ ] Obtain a Rule 502(d) order — usually combined with a clawback provision — so that inadvertent production of privileged material does not waive privilege in this or any other federal or state proceeding.
• [ ] Reduce every agreement to writing, and propose an entered ESI protocol and protective order rather than a handshake.

Why it matters. The single highest-leverage move a document-heavy defendant can make is to lock the ESI protocol down early and to secure a Rule 502(d) order. Here is the distinction that makes 502(d) indispensable. Under FRE 502(b), when a privileged document is produced inadvertently, waiver is avoided only if the holder took reasonable steps to prevent disclosure and reasonable steps to rectify the error — a fact-intensive, expensive, after-the-fault inquiry that has produced its share of harsh results. See Victor Stanley, Inc. v. Creative Pipe, Inc., 250 F.R.D. 251 (D. Md. 2008) (Grimm, J.) (finding waiver where the producing party could not defend the keyword search it used to screen for privilege). A Rule 502(d) order, by contrast, lets the court decree in advance that production in the litigation does not waive privilege, full stop — and, by the statute's terms, that non-waiver is enforceable in every other federal and state proceeding. Many judges consider it close to malpractice to litigate a document-intensive case without one. Ask for it at the Rule 26(f) conference; most courts will sign a short, standalone 502(d) order on the spot.

Search methodology is its own discipline. Keyword searching feels simple and is treacherous: poorly chosen terms miss responsive documents and over-capture junk, and courts have warned against lawyers guessing at search terms "in the dark." See William A. Gross Construction Associates, Inc. v. American Manufacturers Mutual Insurance Co., 256 F.R.D. 134 (S.D.N.Y. 2009) (Peck, M.J.) (a "wake-up call" urging careful, cooperative, tested keyword design). Technology-assisted review — training a classifier on attorney-coded examples — is now judicially blessed for large collections: Da Silva Moore v. Publicis Groupe, 287 F.R.D. 182 (S.D.N.Y. 2012) (Peck, M.J.) was the first federal opinion approving predictive coding, and Rio Tinto PLC v. Vale S.A., 306 F.R.D. 125 (S.D.N.Y. 2015), confirmed that "the case law has developed to the point that it is now black letter law" that TAR is an acceptable method. But acceptance runs one direction: a court will allow you to use TAR; it generally will not force your opponent to. See Hyles v. New York City, No. 10 Civ. 3119, 2016 WL 4077114 (S.D.N.Y. Aug. 1, 2016) (Peck, M.J.) ("the responding party is best situated to decide how to search for and produce" its own ESI). The governing consensus on all of this is collected in The Sedona Conference, The Sedona Principles, Third Edition: Best Practices, Recommendations & Principles for Addressing Electronic Document Production, 19 Sedona Conf. J. 1 (2018) — the secondary authority courts cite most often on ESI.

Worked example. For Nimbus v. Cirrus, the collection will run to several million documents across engineering repositories and email. At the Rule 26(f) conference you propose: eight custodians on each side; a two-year date range keyed to the alleged misappropriation; TAR for the bulk email review with a validation protocol; native production of source code and spreadsheets; TIFF-plus-load-file for everything else; a defined metadata field list; and an entered Rule 502(d) order. You memorialize all of it in a stipulated ESI protocol submitted with the discovery plan. Doing this now converts a dozen future fights into one negotiated document. The mechanics of that Rule 26(f) conference and the plan it produces are laid out in Rule 26 Initial Disclosures and the Discovery Plan: A Practical Checklist, and the whole discovery arc is mapped in The Federal Discovery Toolkit: A Roadmap From Rule 26(f) to Sanctions.

Phase 4: Collect, review, and log defensibly

Checklist.

• [ ] Collect ESI defensibly, preserving metadata from the outset — remember that merely opening a native file can alter its "last accessed" or "last modified" timestamps, so collection should be forensically sound, not a paralegal double-clicking through folders.
• [ ] Review for three things at once: responsiveness, privilege, and confidentiality (which documents need a "Confidential" or "Attorneys' Eyes Only" designation under the protective order).
• [ ] Build the privilege log as you review, not after: date, author, all recipients (including cc/bcc), document type, the privilege asserted, and a subject-matter description detailed enough to let the court assess the claim under Rule 26(b)(5)(A) without disclosing the privileged content.
• [ ] Negotiate categorical logging up front where a document-by-document log would be unduly burdensome; the Rules and many local rules permit logging by category.
• [ ] Watch the recurring privilege traps: an email that merely copies a lawyer is not automatically privileged, and communications mixing business and legal advice are privileged only as to the legal advice. Make the legal purpose visible without disclosing the advice itself.

Why it matters. An inadequate privilege log is itself a waiver risk, and the sanction for a late or deficient log can be forfeiture of the privilege for the documents it fails to describe. The leading cautionary authority is Burlington Northern & Santa Fe Railway Co. v. United States District Court, 408 F.3d 1142 (9th Cir. 2005), which held that boilerplate objections and a tardy, deficient log can waive privilege, and instructed courts to weigh the log's timeliness and specificity rather than apply a mechanical thirty-day rule. Subject-matter waiver looms behind the whole exercise: once privilege is genuinely waived as to a communication, the waiver can extend to the entire subject matter, an old and unforgiving doctrine reflected in cases like Diversified Industries, Inc. v. Meredith, 572 F.2d 596 (8th Cir. 1978) (en banc). The 502(d) order you secured in Phase 3 is your insurance against the inadvertent-production version of this disaster, but it does not excuse a sloppy log for documents you intend to withhold.

On the form of the collection, defensibility is the watchword. Preserve metadata; document your collection method; and be able to describe, later and under oath if necessary, exactly how each source was collected. For dynamic files — spreadsheets with live formulas, databases, presentations with embedded data — collect and later produce the native file, because flattening a spreadsheet to a static image destroys the formulas and the very information that makes it useful. See Aguilar v. Immigration & Customs Enforcement Division, 255 F.R.D. 350 (S.D.N.Y. 2008) (Maas, M.J.) (surveying metadata's role in form-of-production disputes).

Worked example. As you review Cirrus's collection, you find a thread in which the general counsel is copied on an engineering email debating whether the disputed algorithm "borrows too much" from Nimbus. It is tempting to log the whole thread as privileged. But copying a lawyer does not privilege a business discussion; only the portion seeking or conveying legal advice qualifies. You produce the business discussion, redact and log the two sentences requesting the GC's legal assessment, and describe them on the log with enough specificity — "email seeking legal advice of counsel regarding IP-infringement risk of Product X module" — to survive a challenge. For a full treatment of log construction, categorical logging, and clawback, follow Building a Privilege Log: A Practical Checklist.

Phase 5: Draft request-by-request responses

Checklist.

• [ ] Respond to each request separately. No global paragraph purporting to answer sixty-eight requests at once, and no undifferentiated "General Objections" section doing the real work.
• [ ] Object with specificity under Rule 34(b)(2)(B): state what about the request is objectionable and why, in enough detail that the requester and the court can evaluate it.
• [ ] For every objection, state whether responsive material is being withheld on the basis of that objection — the affirmative command of Rule 34(b)(2)(C). You can satisfy it by disclosing the limits that governed your search: the custodians, the date range, the search terms, the scope you agreed to produce.
• [ ] Commit to a completion date for production. Rolling productions are fine and often necessary, but "documents will be produced" with no date is not a response.
• [ ] Narrow constructively. Where a request is overbroad, state the reasonable scope you will honor rather than refusing wholesale.
• [ ] Retire dead language: do not object that a request is not "reasonably calculated to lead to the discovery of admissible evidence." That phrase left Rule 26 in 2015.

Why it matters. This is where careers get dented. For decades, responding counsel copied a block of thirty "General Objections" onto every response, followed each request with "Objection; overbroad, unduly burdensome, vague, and not reasonably calculated," and then answered "subject to and without waiving the foregoing objections" — a formula that told the requester and the court exactly nothing. The 2015 amendments and a wave of judicial opinions declared that practice dead. Two provisions do the work. Rule 34(b)(2)(B) requires objections to be stated "with specificity." Rule 34(b)(2)(C) — the headline reform — requires that "[a]n objection must state whether any responsive materials are being withheld on the basis of that objection." Boilerplate violates both, and it draws Rule 26(g) sanctions.

The case law is emphatic and quotable. In Fischer v. Forrest, No. 14 Civ. 1304, 2017 WL 773694 (S.D.N.Y. Feb. 28, 2017), Judge Peck opened with a warning "to counsel in all cases" that boilerplate objections and the failure to state whether documents were withheld would no longer be tolerated, and that objections not stated with specificity "should be viewed as waived." In Liguria Foods, Inc. v. Griffith Laboratories, Inc., 320 F.R.D. 168 (N.D. Iowa 2017), Judge Bennett — who ordered the lawyers to show cause why they should not be sanctioned for reflexive boilerplate — canvassed the national consensus and called on the bar to "STOP" the practice. And the intellectual foundation is Mancia v. Mayflower Textile Services Co., 253 F.R.D. 354 (D. Md. 2008), where Judge Grimm traced boilerplate objections directly to Rule 26(g)'s certification requirement, explaining that signing a response certifies a reasonable inquiry and that generic objections are, by definition, unsupported by one.

The duty to state whether anything is withheld is the rule most often overlooked, so it deserves emphasis. Before 2015, a party could object, produce some documents, and leave the requester guessing whether the objection had actually caused anything to be held back. Now the objection must own its consequences. If you object that a request is overbroad and, on that basis, decline to search two of eight custodians, you must say so. If your objection is a pure legal reservation that withholds nothing, say that too — "Responding party will produce all responsive, non-privileged documents notwithstanding this objection" — because that sentence converts a landmine into a harmless notation.

Model response language (illustrative). For an overbroad-but-partly-legitimate request like Nimbus's No. 41, a defensible response reads roughly:

Request No. 41: All documents concerning any product Cirrus has ever developed.

Response: Cirrus objects to this Request as overbroad and disproportionate to the needs of the case to the extent it seeks documents concerning products other than [the accused Product X], which are not relevant to any claim or defense; the Complaint alleges misappropriation of a single trade secret embodied in Product X. Cirrus further objects to "concerning" as vague; Cirrus construes it to mean documents that reference or relate to the design, development, or source code of the identified product. Subject to and without waiving these objections, and pursuant to the parties' ESI protocol, Cirrus will produce non-privileged documents concerning the development and source code of Product X for the agreed custodians and date range. Cirrus is withholding responsive documents on the basis of the overbreadth objection, specifically documents concerning Products W, Y, and Z. Production will be substantially complete by [date], on a rolling basis.

Note the four moves: a specific, pleadings-anchored objection; a reasonable construction of a vague term; an affirmative commitment to produce within a defined scope; and — the sentence in bold — an explicit statement of what is being withheld and why, satisfying Rule 34(b)(2)(C). This is the paragraph that separates a response a court credits from one it sanctions. The same discipline governs the neighboring written-discovery devices; compare the parallel drills in Answering Rule 33 Interrogatories: A Practical Checklist and Answering Rule 36 Requests for Admission: A Practical Checklist, with the fuller analysis in Interrogatories in Civil Litigation: A Comprehensive Guide to Objecting and Responding.

Phase 6: Produce in the right form

Checklist.

• [ ] Produce in the form the parties agreed to in the ESI protocol. If there was no agreement and the request did not specify a form, produce ESI in the form in which it is ordinarily maintained or in a reasonably usable form, per Rule 34(b)(2)(E)(ii).
• [ ] Do not degrade usability: you may not convert searchable, metadata-rich ESI into a form that strips its searchability just to burden the requester. Rule 34(b)(2)(E) forbids production that is unreasonably unusable.
• [ ] Organize paper and static documents either as they are kept in the usual course of business or labeled to correspond to the categories in the request, per Rule 34(b)(2)(E)(i).
• [ ] You need not produce the same ESI in more than one form (Rule 34(b)(2)(E)(iii)) — so choose the form deliberately.
• [ ] Apply confidentiality designations under the protective order accurately; over-designating everything "Attorneys' Eyes Only" is its own sanctionable abuse.
• [ ] Bates-number the production, maintain a production log, and keep a defensible record of what was produced, when, and in what form.

Why it matters. Form-of-production disputes are avoidable and expensive. The default rules in Rule 34(b)(2)(E) exist precisely because parties fight about native versus image formats and about metadata. The practical rule of thumb: produce native files for anything dynamic (spreadsheets, databases, source code) so formulas and structure survive, and produce images (TIFF or PDF) with load files and extracted text for ordinary documents so they can be Bates-stamped, redacted, and still searched. Courts police both ends of this. A party that produces a searchable database as a mountain of flat images has degraded usability, and a court may order re-production at the producing party's expense. See Scott Hutchinson Enterprises, Inc. v. Cranberry Pipeline Corp., 318 F.R.D. 44 (S.D. W. Va. 2016) (ordering production in a usable form). Conversely, a party cannot demand a second form of the same documents merely because it prefers native after receiving images. See Ford Motor Co. v. Edgewood Properties, Inc., 257 F.R.D. 418 (D.N.J. 2009) (discussing the single-form limit and metadata expectations).

There is also a document-dump trap for the producing party. Rule 34(b)(2)(E)(i) permits producing documents "as they are kept in the usual course of business," and some parties treat that as license to bury a smoking gun in a shapeless mass. Courts are wise to it. A production that is deliberately disorganized to frustrate review can draw an order to re-produce in an organized form, and worse. See Williams v. Taser International, Inc., 274 F.R.D. 694 (N.D. Ga. 2011). The safe course is to produce as maintained and to preserve the metadata (custodian, file path, dates) that lets the requester make sense of it. Where produced ESI later becomes a trial exhibit — a screenshot, an archived web page, a chat export — the same metadata and chain-of-custody discipline pays off at the authentication stage; see Authenticating Website Screenshots and Web Evidence in Federal Court: A Practitioner's Guide and the operational Getting Website Evidence Admitted: A Practical Authentication Checklist.

Worked example. Cirrus's source code lives in a Git repository; its financial model is a live Excel workbook with dozens of linked sheets. You produce the code natively with its commit history intact and the Excel workbook natively with formulas preserved, both under an "Attorneys' Eyes Only" designation that the protective order reserves for competitively sensitive material. The tens of thousands of emails go out as TIFFs with a load file, extracted text, and the agreed metadata fields. Because the ESI protocol specified all of this, Nimbus has no form-of-production motion to bring — which is exactly the point of Phase 3.

Phase 7: Supplement, and deploy the surviving objections correctly

Once the boilerplate is gone, several substantive objections remain genuinely powerful — but only when supported by facts and tied to a specific request. This phase is where the reasonable-lawyer standard either protects your client or exposes it.

Checklist.

• [ ] Supplement under Rule 26(e) as new material surfaces. The duty is affirmative and ongoing; a stale "no responsive documents" answer that later proves false is a sanctions magnet, and undisclosed material can be excluded at trial under Rule 37(c)(1).
• [ ] Relevance / scope: when a request reaches beyond any claim or defense, explain the gap in a sentence a stranger could follow ("this is a single-trade-secret case about Product X; the tax returns of an unrelated subsidiary bear on no issue").
• [ ] Overbreadth (distinct from relevance): identify the overbroad component precisely and propose the reasonable scope you will honor instead.
• [ ] Proportionality with evidence: support the objection with a sworn declaration quantifying the burden — custodians, data volume, review hours, and dollar cost — mapped factor by factor onto Rule 26(b)(1).
• [ ] Vagueness / ambiguity: reserve it for genuine ambiguity, adopt and state a reasonable construction, and produce on that basis rather than using vagueness as a dodge.
• [ ] Duplication / equally available: if the requester already has the documents or can obtain them as easily (relative access is now part of the proportionality calculus), say so with specifics.
• [ ] Not reasonably accessible ESI: under Rule 26(b)(2)(B), you may decline to produce ESI from sources that are not reasonably accessible because of undue burden or cost (legacy backup tapes, decommissioned systems), if you identify those sources — but be ready to defend the claim, and remember the requester can still compel on a showing of good cause with cost-shifting.
• [ ] Meet and confer in good faith before any motion practice (Rule 37(a)(1) and local rules), addressing specific requests rather than vague grievances, and memorialize every agreement.
• [ ] Non-party documents: route them through a Rule 45 subpoena, with its geographic limits, its 14-day objection window, and the serving party's duty to take reasonable steps to avoid imposing undue burden.

Why it matters. Objections that succeed read as though a competent lawyer wrote them after actually thinking about the request, not as though a template landed on every line. Because discovery rulings are reviewed only for abuse of discretion, the trial judge's early read of who is being reasonable tends to harden into the law of the case. The proportionality declaration is the workhorse here: a court confronted with a request for "all documents" from sixty custodians is far more likely to grant relief when the responding party swears out concrete numbers — say, 4.2 terabytes across those custodians, an estimated 1.1 million documents after de-duplication, and roughly $900,000 in review cost against $250,000 in controversy — than when it merely intones "unduly burdensome." Numbers move courts; adjectives do not.

The meet-and-confer is where most discovery disputes are actually solved, and Rule 37 rewards those who take it seriously. Rule 37(a)(5) makes fee-shifting the default: a party that wins a motion to compel generally recovers its fees, and — crucially for responding counsel — a requesting party that moves without a good-faith conferral, or that loses, can be ordered to pay your fees. That presumption cuts both ways and gives even the responding party a reason to insist on a real conferral before anyone runs to the courthouse. When a dispute does reach a motion to compel, the fuller mechanics live in Federal Civil Discovery: Mastering the Tools, Rules, and Pitfalls, and the preclusion consequence of a blown supplementation duty is treated in Rule 37(c)(1) and the Preclusion of Undisclosed Evidence: A Practical Guide.

Worked example. Nimbus's Request No. 7 demands "all communications, from any device, of every Cirrus employee, for a five-year period." You do not simply write "overbroad." You attach a declaration from Cirrus's IT director: 143 employees, an estimated 8.4 million messages across email, Slack, and text once you include the full five years, a projected review cost north of $1.4 million, and a case in which the disputed trade secret was accessed by at most nine people over eighteen months. You then propose the reasonable scope — nine custodians, an eighteen-month window keyed to the access logs — and produce on that basis. If Nimbus moves to compel the rest, it is arguing against arithmetic, and Rule 37(a)(5) now points its fee exposure the wrong way.

When it goes wrong: the sanctions map

Responding counsel should understand the full ladder of consequences, because the client's exposure scales with the nature of the failure.

• Rule 26(g) certification sanctions. Signing a response or objection without substantial justification, or interposing it to cause delay or needless cost, exposes the signer — the lawyer, personally — to sanctions "including a reasonable attorney's fee." This is the primary hook for boilerplate-objection sanctions, as Mancia and Liguria Foods illustrate.
• Rule 37(a) motion to compel. The mildest enforcement: the court orders production and, under 37(a)(5), usually shifts the fees of the prevailing side. An objection deemed unsupported can also be treated as waived.
• Rule 37(b) violation of an order. Once a court has ordered production and a party disobeys, the sanctions escalate sharply — from deeming facts established, to precluding claims or defenses, to striking pleadings, to default or dismissal. Courts also have inherent authority to shift the full cost of misconduct, including the fees an adversary spent chasing withheld ESI. See Klipsch Group, Inc. v. ePlus Inc., 880 F.3d 620 (2d Cir. 2018) (affirming a discovery sanction calibrated to the cost the misconduct imposed).
• Rule 37(e) ESI spoliation. As discussed in Phase 1, curative measures under 37(e)(1) require only prejudice; the case-ending sanctions under 37(e)(2) require intent to deprive.
• Rule 37(c)(1) preclusion. Information not timely disclosed or produced may be excluded from use at trial unless the failure was substantially justified or harmless — a self-executing sanction that can gut a case without any motion to compel ever being filed.

The through-line is that the party who can show the court a clean, documented, reasonable process almost always fares better than the party defending a black box. Preservation logs, ESI protocols, search-term validation, and specific objections are not bureaucratic overhead; they are the evidentiary record you will rely on when your adversary accuses your client of hiding the ball.

Common mistakes, in brief

• A wall of "General Objections" doing the work that specific, request-by-request objections should do.
• Objecting "subject to and without waiving" while staying silent on whether anything is actually withheld — a direct violation of Rule 34(b)(2)(C).
• "Documents will be produced" with no completion date.
• Skipping the Rule 502(d) order in a document-intensive case and gambling the client's privilege on the fact-bound 502(b) analysis.
• A litigation hold that misses collaboration tools, personal devices, and disappearing-message apps — the DR Distributors failure.
• Quoting the deleted "reasonably calculated to lead to admissible evidence" standard, which advertises that your discovery vocabulary froze in 2014.
• Producing a searchable collection as flat, unsearchable images to burden the requester, then acting surprised when the court orders a do-over.
• Over-designating everything "Attorneys' Eyes Only," which invites a challenge and erodes your credibility on the designations that actually matter.

The master checklist, condensed

1. Calendar the 30-day deadline (adjusted for service and the Rule 26(f) trigger) and set an internal draft date.
2. Preserve: issue and monitor a written litigation hold; suspend auto-deletion; reach collaboration tools, personal devices, and ephemeral apps.
3. Map each request to a claim or defense; flag overbreadth, irrelevance, burden, vagueness, privilege, and disproportion.
4. Confer early on custodians, date ranges, sources, search method, form, and metadata; get a Rule 502(d) order and a protective order.
5. Collect defensibly (metadata intact); review for responsiveness, privilege, and confidentiality; log privilege as you go.
6. Draft request-by-request: specific objections; state whether withholding; commit to a completion date; narrow constructively.
7. Produce in the agreed form (native for dynamic files, images-plus-text for the rest); designate accurately; Bates and log.
8. Supplement under Rule 26(e); deploy substantive objections with evidence; meet and confer before any motion.
9. Document everything — the hold, the searches, the conferrals, the productions — so the process is defensible from the outside.

Primary and secondary authority

Federal Rules of Civil Procedure. Rule 26(b)(1) (scope and proportionality); Rule 26(b)(2)(B) (not-reasonably-accessible ESI); Rule 26(b)(5) (privilege claims and log); Rule 26(e) (duty to supplement); Rule 26(f) (discovery-planning conference); Rule 26(g) (certification); Rule 34 (requests for production, including 34(b)(2)(A)-(E)); Rule 37(a) (motion to compel and fee-shifting), 37(b) (order-violation sanctions), 37(c)(1) (preclusion), and 37(e) (loss of ESI); Rule 45 (non-party subpoenas).

Federal Rules of Evidence. FRE 502, especially 502(b) (inadvertent-disclosure waiver) and 502(d) (court-ordered non-waiver).

Cases. Oppenheimer Fund, Inc. v. Sanders, 437 U.S. 340 (1978); Zubulake v. UBS Warburg LLC, 220 F.R.D. 212 (S.D.N.Y. 2003) and 229 F.R.D. 422 (S.D.N.Y. 2004); Diversified Industries, Inc. v. Meredith, 572 F.2d 596 (8th Cir. 1978) (en banc); Burlington Northern & Santa Fe Railway Co. v. U.S. District Court, 408 F.3d 1142 (9th Cir. 2005); Victor Stanley, Inc. v. Creative Pipe, Inc., 250 F.R.D. 251 (D. Md. 2008); Mancia v. Mayflower Textile Services Co., 253 F.R.D. 354 (D. Md. 2008); Aguilar v. ICE, 255 F.R.D. 350 (S.D.N.Y. 2008); William A. Gross Construction Associates, Inc. v. American Manufacturers Mutual Insurance Co., 256 F.R.D. 134 (S.D.N.Y. 2009); Ford Motor Co. v. Edgewood Properties, Inc., 257 F.R.D. 418 (D.N.J. 2009); In re NTL, Inc. Securities Litigation, 244 F.R.D. 179 (S.D.N.Y. 2007); Williams v. Taser International, Inc., 274 F.R.D. 694 (N.D. Ga. 2011); Da Silva Moore v. Publicis Groupe, 287 F.R.D. 182 (S.D.N.Y. 2012); Rio Tinto PLC v. Vale S.A., 306 F.R.D. 125 (S.D.N.Y. 2015); Hyles v. New York City, 2016 WL 4077114 (S.D.N.Y. 2016); Scott Hutchinson Enterprises, Inc. v. Cranberry Pipeline Corp., 318 F.R.D. 44 (S.D. W. Va. 2016); Fischer v. Forrest, 2017 WL 773694 (S.D.N.Y. 2017); Liguria Foods, Inc. v. Griffith Laboratories, Inc., 320 F.R.D. 168 (N.D. Iowa 2017); Klipsch Group, Inc. v. ePlus Inc., 880 F.3d 620 (2d Cir. 2018); DR Distributors, LLC v. 21 Century Smoking, Inc., 513 F. Supp. 3d 839 (N.D. Ill. 2021).

Secondary authority. The Sedona Conference, The Sedona Principles, Third Edition, 19 Sedona Conf. J. 1 (2018); Fed. R. Civ. P. 37(e) advisory committee's note to 2015 amendment; Chief Justice John Roberts, 2015 Year-End Report on the Federal Judiciary.

Related UpLaw Resources

Related Guides and Articles

• Requests for Production: A Comprehensive Guide to Objecting and Responding — the doctrinal companion to this checklist.
• Federal Civil Discovery: Mastering the Tools, Rules, and Pitfalls — the discovery system end to end, including the sanctions framework.
• Interrogatories in Civil Litigation: A Comprehensive Guide to Objecting and Responding
• Answering Requests for Admission Under Rule 36: A Strategic Practitioner's Guide
• Rule 37(c)(1) and the Preclusion of Undisclosed Evidence: A Practical Guide
• Assessing a Civil Lawsuit: A Comprehensive Early-Case Framework
• Authenticating Website Screenshots and Web Evidence in Federal Court: A Practitioner's Guide
• Federal Civil Litigation Filings: A Comprehensive Guide from Complaint to Appeal

Related Checklists

• Rule 26 Initial Disclosures and the Discovery Plan: A Practical Checklist
• Answering Rule 33 Interrogatories: A Practical Checklist
• Answering Rule 36 Requests for Admission: A Practical Checklist
• Building a Privilege Log: A Practical Checklist
• Evaluating a New Civil Case: A Practical Checklist
• Preparing to Take a Deposition: A Practical Checklist
• Discovery Before the TTAB: A Practical Checklist

Related Toolkits

• The Federal Discovery Toolkit: A Roadmap From Rule 26(f) to Sanctions
• Federal Civil Litigation: A Roadmap and Resource Guide
• The Federal Deposition Toolkit: From Notice to Trial Testimony

---

This checklist is provided for general informational purposes only and does not constitute legal advice. Discovery rules and their interpretation vary by jurisdiction and change over time. Consult qualified counsel licensed in your jurisdiction before acting.