A request for production (RFP) under Federal Rule of Civil Procedure 34 is a written demand that the other side hand over designated documents, electronically stored information (ESI), and tangible things within its possession, custody, or control. 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 rights or hand the adversary a case-ending sanction. This checklist gives you the disciplined sequence.

For the full treatment, see mastering document discovery. It pairs with the responding to interrogatories checklist and the responding to requests for admission checklist.

Phase 1: Calendar and preserve

  • Docket the deadline the instant the requests arrive: 30 days after service (Rule 34(b)(2)(A)), unless served with the complaint or before the Rule 26(f) conference (clock runs from that conference) or extended by stipulation/order.
  • Issue or confirm the litigation hold: written instruction to custodians, suspension of auto-deletion, and preservation across email, collaboration tools (Slack/Teams), personal devices reached by company policy, and any system with auto-purge.
  • Confirm preservation reaches ephemeral/disappearing-message apps, because their continued use after a duty attaches can supply the intent Rule 37(e)(2) requires.

Why this matters. An untimely response can waive objections (in many courts, even privilege). And spoliation cannot be cured retroactively — Zubulake IV/V established counsel's affirmative, ongoing duty to ensure preservation, and DR Distributors, LLC v. 21 Century Smoking, Inc., 513 F. Supp. 3d 839 (N.D. Ill. 2021), shows how chat and webmail data slips through an inadequate hold.

Phase 2: Read each request against the pleadings

  • Map each request to a specific element of a claim or defense; if you cannot, it is probably overbroad and you can say so with specificity.
  • Flag overbreadth, irrelevance, vagueness, privilege exposure, and proportionality concerns request by request.
  • Confirm scope under Rule 26(b)(1): relevant to a claim or defense and proportional (weigh the six factors — importance of issues, amount in controversy, relative access, parties' resources, importance of the discovery, and burden vs. benefit).
  • Assess possession, custody, or control: object where documents are genuinely beyond your legal right to obtain, and point the requester to a Rule 45 subpoena.

Why this matters. The 2015 amendments made proportionality a shared, affirmative obligation, but a credible proportionality objection needs concrete facts (custodians, data volumes, cost estimates tied to the factors), not the word "disproportionate."

Phase 3: Negotiate scope and an ESI protocol

  • Meet and confer on custodians, date ranges, search terms or TAR methodology, de-duplication, production format, and metadata fields — ideally before collecting a single document.
  • Address collaboration-tool data and "modern attachments" (cloud links) explicitly, so linked files and the version that existed when a message was sent are not lost.
  • Obtain a Rule 502(d) order (often combined with a clawback provision) so inadvertent production does not waive privilege in this or any other federal or state proceeding.
  • Memorialize every agreement in writing.

Why this matters. A 502(d) order eliminates the costly after-the-fact fight over whether your precautions were "reasonable" under 502(b); many judges consider it close to malpractice not to seek one in a document-intensive case. The best practice, strongly favored by courts, is to lock the ESI protocol down at the Rule 26(f) conference.

Phase 4: Collect, review, and log

  • Collect ESI defensibly, preserving metadata from the outset (even opening a native file can alter its "last accessed" date).
  • Review for responsiveness, privilege, and confidentiality, building the privilege log as you go (date, author, recipients, type, privilege asserted, subject-matter description sufficient to assess the claim under Rule 26(b)(5)(A)).
  • Negotiate categorical logging up front where document-by-document logging would be unduly burdensome.
  • Watch the recurring trap: communications that merely copy a lawyer or mix business and legal content — make the legal purpose visible without disclosing the advice.

Why this matters. An inadequate log is itself a waiver risk. Produce native files for spreadsheets and dynamic file types (converting them to images destroys formulas), and use TIFF/PDF images with load and text files for ordinary documents so they remain Bates-stamped, redactable, and searchable.

Phase 5: Draft request-by-request responses

  • Respond to each request separately — no global paragraph answering 75 requests at once.
  • Object with specificity (Rule 34(b)(2)(B)): explain what about the request is objectionable and why; abandon the deleted "reasonably calculated to lead to admissible evidence" language.
  • State whether responsive materials are being withheld on the basis of each objection (Rule 34(b)(2)(C)) — you can satisfy this by disclosing the limits that controlled the search (custodians, date range, search terms).
  • Commit to a completion date for production (rolling productions are fine, but state a date).
  • Narrow constructively where a request is overbroad rather than refusing wholesale.

Why this matters. Boilerplate, copy-pasted objections can waive your client's rights and expose counsel to Rule 26(g) sanctions, as Fischer v. Forrest, 2017 WL 773694 (S.D.N.Y. 2017), Liguria Foods v. Griffith Laboratories, 320 F.R.D. 168 (N.D. Iowa 2017), and Mancia v. Mayflower Textile Services, 253 F.R.D. 354 (D. Md. 2008), all make clear. The duty to state whether documents are withheld was the headline fix of 2015 and is the single most overlooked rule.

Phase 6: Produce and supplement

  • Produce in the agreed format with appropriate confidentiality designations under the protective order (Confidential / Attorneys' Eyes Only).
  • Supplement under Rule 26(e) as new material surfaces — the duty is ongoing, and a stale "no responsive documents" answer that later proves false invites sanctions.
  • Document everything: the hold, the searches, the conferral, the productions.

Why this matters. The party that can show the court a clean, reasonable, well-documented process almost always fares better than the party defending a black box.

Phase 7: Use substantive objections correctly and confer

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

  • Relevance/scope: when a request reaches beyond any claim or defense, explain the gap ("this is a trademark action; pre-dispute tax filings bear on no issue, and damages are measured by the defendant's profits").
  • Overbreadth (distinct from relevance): 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 with evidence: a sworn declaration estimating, say, 4.2 terabytes from 60 custodians at $900,000 in review cost against $250,000 in controversy, tied factor by factor to Rule 26(b)(1).
  • Vagueness: reserve it for genuine ambiguity, adopt a reasonable construction, and produce on that basis.
  • Duplication / "equally available": if the requester already has the documents or can get them as easily, say so (relative access is now part of the proportionality calculus).
  • Meet and confer in good faith before any motion to compel (Rule 37(a)(1) and local rules), addressing specific requests rather than vague complaints, and memorialize every agreement in writing.
  • Remember non-party documents require a Rule 45 subpoena, with its geographic limits, 14-day objection window, and the serving party's duty to avoid undue burden.

Why this matters. Objections that succeed read as though a reasonable lawyer wrote them after actually thinking about the request, not as though a template was dropped onto every line — and because discovery rulings are reviewed only for abuse of discretion, the trial judge's first impression of who is being reasonable tends to harden into the law of the case. A genuine meet-and-confer is where most disputes are actually solved, and the fee-shifting presumption of Rule 37(a)(5) cuts both ways: a requesting party that moves without conferring, or that loses, can be ordered to pay the responding party's fees.

Common mistakes

  • A wall of "General Objections" used as a substitute for specific, request-by-request objections.
  • Objecting "subject to and without waiving" while staying silent on whether anything is withheld.
  • "Documents will be produced" with no completion date.
  • Skipping the 502(d) order in a document-intensive case.
  • An inadequate litigation hold that misses collaboration tools and personal devices.

Primary authority

  • Fed. R. Civ. P. 26(b)(1) (scope and proportionality); 34 (RFP mechanics, including 34(b)(2)(B)–(C)); 26(b)(5) (privilege log); 26(g) (certification); 37(a) (motion to compel) and 37(e) (ESI spoliation); 45 (non-party subpoenas).
  • FRE 502 (waiver and clawback, especially 502(d)).
  • Key cases: Fischer v. Forrest, 2017 WL 773694 (S.D.N.Y. 2017); Liguria Foods v. Griffith Labs., 320 F.R.D. 168 (N.D. Iowa 2017); Mancia v. Mayflower Textile Servs., 253 F.R.D. 354 (D. Md. 2008); Zubulake v. UBS Warburg, 217 F.R.D. 309 & 220 F.R.D. 212 (S.D.N.Y. 2003); DR Distributors v. 21 Century Smoking, 513 F. Supp. 3d 839 (N.D. Ill. 2021).

Related resources

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.