Checklist · Litigation

Serving Written Discovery Requests: A Practical Checklist

Type
Checklist
Jurisdiction
National
Date
2024-06-27
Topic
Litigation

This checklist is for the propounding side of written discovery in federal court — the party asking the questions, demanding the documents, and forcing admissions. It walks you from a discovery plan mapped to the elements you must prove, through drafting interrogatories under Rule 33 (including the 25-count cap and contention interrogatories), requests for production under Rule 34 (with ESI form-of-production traps), and requests for admission under Rule 36. It grounds every request in the scope-and-proportionality standard of Rule 26(b)(1) and the certification duty of Rule 26(g), then covers timing and sequence around the Rule 26(f) conference. Finally it shows how to drive compliance through the meet-and-confer process to a motion to compel under Rule 37(a), with cost-shifting leverage under Rule 37(c)(2). A running patent hypothetical illustrates contention interrogatories and document requests served on an accused infringer.

Serving Written Discovery Requests: A Practical Checklist

Litigation > Discovery | Published 27 June 2024 - Updated 14 April 2025 | UpLaw - uplaw.us

Discovery is not a fishing expedition and it is not a scavenger hunt — it is an argument you build one request at a time. Every interrogatory, document demand, and admission you serve should trace back to an element you must prove or a defense you must defeat. Serve with that discipline and the record writes itself; serve carelessly and you fund your opponent's motion practice.

Keywords: written discovery, interrogatories, Rule 33, requests for production, Rule 34, requests for admission, Rule 36, proportionality, Rule 26(b)(1), Rule 26(g) certification, motion to compel, Rule 37(a), ESI, contention interrogatories

How to use this checklist

This is a doing document for the propounding party — the side serving written discovery, not the side responding to it. If you are on the receiving end, work from the companion checklists on Answering Rule 33 Interrogatories: A Practical Checklist, Responding to Rule 34 Document Requests: A Practical Checklist, and Answering Rule 36 Requests for Admission: A Practical Checklist instead. For the whole machine — how the three written tools fit alongside depositions, disclosures, and sanctions — see Federal Civil Discovery: Mastering the Tools, Rules, and Pitfalls and The Federal Discovery Toolkit: A Roadmap From Rule 26(f) to Sanctions.

The phases below run in the order you should actually work them: plan, scope, draft each instrument, time the service, certify, and enforce. Each phase carries real check items and a short "Why it matters, and the traps" note. A running hypothetical follows a fictional patentee, Talus Dynamics, Inc., which has sued Northgate Systems, LLC for infringing a patent on a warehouse-robot navigation module.

Phase 1 — Start from the elements: a discovery plan mapped to what you must prove

Before you write a single request, write out the elements. Discovery is a means, not an end; the end is admissible proof of each element of each claim (or each defense you must rebut). Build a proof chart, and every request will earn its place.

  • [ ] List each cause of action and each element you bear the burden on, plus each affirmative defense you must defeat.
  • [ ] For each element, identify the facts you must establish and where those facts likely live (documents, witnesses, data systems, third parties).
  • [ ] Mark which facts you already have from Rule 26 Initial Disclosures and the Discovery Plan: A Practical Checklist and pre-suit investigation, so you do not spend requests re-proving the undisputed.
  • [ ] Assign each remaining fact to the right tool: interrogatories for identities, contentions, and computations; document requests for the paper and the data; admissions to lock down the uncontested.
  • [ ] Sketch a sequencing plan — what you serve first, what you hold for after depositions, and what you reserve to close gaps before the discovery cutoff.
  • [ ] Confirm the operative complaint frames the claims you are now trying to prove; if the pleading is thin, fix it first (see Drafting a Federal Civil Complaint: A Practical Checklist).

Why it matters, and the traps. The single most common defect in propounded discovery is that it is written from a form file instead of from the case. Boilerplate interrogatories ("Identify all persons with knowledge of the facts alleged in the Complaint") produce boilerplate objections and almost no usable proof. When you map requests to elements, three good things happen: you can defend every request as relevant "to any party's claim or defense" under Fed. R. Civ. P. 26(b)(1); you avoid burning your limited interrogatory count on trivia; and, at the motion-to-compel stage, you can tell the judge exactly what element the withheld material goes to. The classic trap is the opposite — serving everything you can imagine and hoping something sticks. That approach invites proportionality objections, wastes your Rule 26(g) credibility, and buries the responses you actually need. For the strategic frame on which battles are worth fighting, see Federal Civil Litigation for Small Businesses: A Patent-Focused Field Guide.

Worked example. Talus Dynamics must prove, for its infringement claim, that Northgate's "PathPilot" robots practice each limitation of claim 1. Talus's proof chart lists the claim limitations down the left column and, across the top, the sources: source code (document request), the accused product's technical specifications (document request), Northgate's own internal claim-charts or design docs (document request), sales volumes for damages (interrogatory plus documents), and Northgate's non-infringement and invalidity positions (contention interrogatories). Nothing gets served that is not on the chart.

Phase 2 — Scope and proportionality: Rule 26(b)(1) and the 2015 amendments

Rule 26(b)(1) is the gate every request must pass through. Since the 2015 amendments, the rule permits discovery of any nonprivileged matter "relevant to any party's claim or defense and proportional to the needs of the case." Proportionality is now text, not atmosphere.

  • [ ] Confirm each request seeks matter relevant to a claim or defense — not merely relevant to "the subject matter" (that broader phrase was deleted in 2015).
  • [ ] Run each request through the six proportionality factors: the importance of the issues, the amount in controversy, the parties' relative access to the information, the parties' resources, the importance of the discovery in resolving the issues, and whether the burden outweighs the likely benefit.
  • [ ] Narrow the time period, custodians, and subject matter to what the elements actually require; a tightly scoped request is far harder to resist.
  • [ ] Note where information is uniquely in the opponent's control (asymmetry cuts in your favor on burden) versus equally available to you (which weakens your position).
  • [ ] Preserve privilege issues on your own side, and anticipate the log you will demand — see Building a Privilege Log: A Practical Checklist.

Why it matters, and the traps. Proportionality is a sword and a shield. As the propounding party you want to frame requests so that the burden-versus-benefit math is obviously in your favor, because you know the responding party will invoke Rule 26(b)(1) to cut them down. Two traps recur. First, over-breadth as a "negotiating position" — lawyers deliberately serve sweeping requests intending to settle for less. Post-2015, that tactic backfires: courts increasingly treat facially disproportionate requests as sanctionable overreach and may deny the motion to compel outright rather than blue-pencil it. Second, forgetting that relevance is measured against the claims and defenses, so if you want broader discovery you may need to broaden the pleadings first. The doctrinal deep dive lives in Interrogatories in Civil Litigation: A Comprehensive Guide to Objecting and Responding and Requests for Production: A Comprehensive Guide to Objecting and Responding; both explain the objections you are trying to preempt.

Phase 3 — Drafting interrogatories under Rule 33

Interrogatories are written questions answered under oath by the party. Rule 33 limits each party to 25 interrogatories, including all discrete subparts, absent stipulation or leave of court. Use them for what only sworn party answers can give you: identities, computations, and the other side's contentions.

  • [ ] Count your interrogatories honestly — a question with genuinely separate subparts (e.g., "identify each sale, and for each state the date, quantity, price, and customer") counts the subparts if they are not logically related to a single subject.
  • [ ] Reserve capacity: do not blow 25 on preliminaries. Front-load identity and computation interrogatories, and hold slots for contention interrogatories after documents come in.
  • [ ] Use contention interrogatories to pin down the opponent's theories — e.g., "State each basis on which you contend claim 1 of the '842 patent is invalid, and identify all documents supporting each contention."
  • [ ] Ask for the computation and support behind any damages number, affirmative defense, or denial.
  • [ ] Define terms precisely and incorporate a short, fair set of definitions and instructions — but do not smuggle extra questions into "instructions."
  • [ ] Where a document search would answer the question, consider whether Rule 33(d) (option to produce business records) will let the responder dump files on you instead of answering; if so, phrase the interrogatory to demand a narrative, not a record set.

Why it matters, and the traps. The 25-count cap is the discipline that makes interrogatories valuable. The trap that ends most interrogatory campaigns is the "discrete subpart" miscount: a party thinks it served 20 interrogatories, the responder counts 41 by unpacking subparts, answers 25 and objects to the rest, and the propounding party discovers too late that its most important questions fell outside the count. Draft with the count in mind and, when you truly need more, seek a stipulation or leave early rather than litigating the count later. The second trap is timing contention interrogatories: served too early, they draw a legitimate objection that they are premature before document discovery, and courts often defer answers until the close of fact discovery. Serve the identity and factual interrogatories first; serve contention interrogatories once the record can support a real answer. The mechanics of answering — and the objections you will face — are laid out in Answering Rule 33 Interrogatories: A Practical Checklist.

Worked example. Talus serves twelve interrogatories on Northgate. Numbers 1–6 seek identities and computations: the persons who designed PathPilot's navigation firmware, the total units sold, the revenue and gross margin per unit, and the identity of any supplier of the accused module. Talus holds the rest. After it receives Northgate's source code and design documents, it serves contention interrogatories 7–12: "Identify each claim limitation of claim 1 you contend is absent from the PathPilot product, and state the complete factual basis for that contention," and a parallel set on Northgate's invalidity theory. Because Talus sequenced them, Northgate cannot credibly call them premature.

Phase 4 — Drafting requests for production under Rule 34

Requests for production reach documents, electronically stored information (ESI), and tangible things in the responding party's "possession, custody, or control." There is no numerical cap, but Rule 26(b)(1) proportionality still governs, and Rule 34's form-of-production rules are where careless propounders lose leverage.

  • [ ] Define document categories by subject and by custodian, not by open-ended catchalls; "all documents relating to PathPilot" invites an over-breadth objection, while "PathPilot navigation firmware source code, revision history, and design specifications" does not.
  • [ ] Specify the form of production for ESI. Under Rule 34(b)(1)(C) you may state the form(s) in which ESI is to be produced. Demand native files with metadata for anything where the metadata matters (spreadsheets, databases, source repositories) and searchable text/load files for documents.
  • [ ] Identify the custodians and data sources you want searched, and, where useful, propose search terms or date ranges to head off a "we'll produce what we deem responsive" runaround.
  • [ ] Demand production as the documents are "kept in the usual course of business" or organized to correspond to the categories, per Rule 34(b)(2)(E).
  • [ ] Coordinate with the preservation record — confirm your opponent's litigation-hold obligations attached, and be ready to raise spoliation if data is missing (see Issuing a Litigation Hold and Preserving ESI: A Practical Checklist).
  • [ ] Note Rule 34's 30-day response window and the requirement that objections be stated with specificity and that the responder state whether anything is being withheld on the basis of an objection.

Why it matters, and the traps. The form-of-production fight is the one propounders most often forget until it is too late. If you do not specify a form, Rule 34(b)(2)(E) lets the responder produce in the form in which the information is "ordinarily maintained" or in a "reasonably usable form" — which can mean a stack of unsearchable TIFF images stripped of metadata, or a flattened PDF of a spreadsheet whose formulas you needed. Once produced, you generally cannot demand a re-production in a different form. Specify native-with-metadata up front for the data that matters. The second trap is the vague catchall request, which hands the responder a specificity objection and lets it decide unilaterally what is "responsive." Precision in the request forecloses that discretion. For the full landscape of objections you are drafting against, see Requests for Production: A Comprehensive Guide to Objecting and Responding.

Worked example. Talus's document requests to Northgate demand: (1) the complete source code and version-control history for the PathPilot navigation module, produced in native form on a secured review computer; (2) design specifications, test reports, and internal engineering presentations, produced as searchable PDFs with load files preserving custodian and date metadata; and (3) sales and financial records sufficient to show units sold, revenue, and cost, produced as native spreadsheets. Each request names a subject and, where relevant, the custodians (the named firmware engineers) — so Northgate cannot answer with a metadata-stripped image dump.

Phase 5 — Drafting requests for admission under Rule 36

Requests for admission (RFAs) are not really a discovery device — they are a case-narrowing device. Under Rule 36, a matter is admitted unless the responding party timely answers or objects, and anything admitted is "conclusively established" for the case. Use RFAs to remove the undisputed from trial and to authenticate documents.

  • [ ] Draft each RFA as a single, self-contained factual proposition or a genuineness-of-document request — not a compound sentence and not a legal argument.
  • [ ] Use RFAs to authenticate documents and establish foundational facts (dates, corporate identity, chain of custody) so you need not prove them at trial.
  • [ ] Use RFAs to lock down concessions the opponent has effectively already made in pleadings or interrogatory answers.
  • [ ] Track the 30-day deadline (Rule 36(a)(3)) and calendar it hard — an untimely response admits the request by operation of the rule.
  • [ ] Preserve your cost-shifting leverage: if the opponent denies something you later prove true, you can move under Rule 37(c)(2) to recover the reasonable expenses, including attorney's fees, of proving it.

Why it matters, and the traps. RFAs have a unique and underused enforcement mechanism. If a party denies a request and you then prove the matter true at trial, Rule 37(c)(2) directs the court to award you the costs of proof — including attorney's fees — unless the denial was substantially justified or the request was of no substantial importance. That turns a well-drafted, unassailably-true RFA into a trap for an opponent who reflexively denies. The corresponding trap for you as propounder is drafting RFAs that are compound, argumentative, or freighted with legal conclusions; those draw legitimate objections and forfeit the cost-shifting leverage, because a court will find the denial substantially justified. Keep them atomic and factual. The responder's playbook — and the narrow grounds for a good-faith denial or qualification — is set out in Answering Rule 36 Requests for Admission: A Practical Checklist and, in more depth, Answering Requests for Admission Under Rule 36: A Strategic Practitioner's Guide.

Worked example. Talus serves RFAs asking Northgate to admit that "PathPilot units sold after January 1, 2023 include the navigation firmware identified in Exhibit A," that "Exhibit A is a true and correct copy of Northgate's PathPilot firmware source repository as of March 2023," and that "Northgate sold at least 4,000 PathPilot units in 2023." If Northgate denies the sales figure and Talus later proves it with Northgate's own financials, Talus moves under Rule 37(c)(2) for the cost of proving it.

Phase 6 — Timing, sequence, and the Rule 26(f) conference

Written discovery has a starting gun and a finish line, and serving out of turn wastes the requests. Rule 26(d)(1) generally bars a party from seeking discovery from any source before the parties have conferred under Rule 26(f).

  • [ ] Confirm the Rule 26(f) conference has occurred (or that an exception applies) before serving anything — premature requests are a nullity and signal inexperience.
  • [ ] Note that Rule 26(d)(2) lets you deliver Rule 34 requests 21 days after service of the summons and complaint, with the response clock running from the first Rule 26(f) conference — a way to get document requests teed up early.
  • [ ] Fold your discovery plan into the Rule 26(f) report: number of interrogatories, ESI protocol, form of production, and any phasing.
  • [ ] Sequence the tools: identity interrogatories and core document requests first; depositions after key documents; contention interrogatories and RFAs toward the close of fact discovery.
  • [ ] Back-calculate from the discovery cutoff so that a response (30 days) plus a meet-and-confer plus a motion to compel can all finish before the deadline — serve final requests at least 45–60 days before the cutoff.
  • [ ] Confirm the scheduling order's limits (many courts cap interrogatories or depositions beyond the default) and honor them.

Why it matters, and the traps. The finish-line trap is fatal and common: a party serves an important document request 25 days before the discovery cutoff, the response is due after the cutoff, and the court refuses to compel because the request was, in effect, untimely. Written discovery must be served early enough that the entire enforcement cycle fits inside the discovery period. The starting-line trap is subtler — serving before the Rule 26(f) conference, which draws a clean objection and forces re-service, resetting your clock. For where written discovery sits in the full pretrial arc, see The Civil Pretrial Toolkit: From Pleadings to Summary Judgment and the roadmap in The Federal Discovery Toolkit: A Roadmap From Rule 26(f) to Sanctions.

Phase 7 — The Rule 26(g) certification and avoiding abusive requests

Every discovery request, response, and objection must be signed, and that signature is a certification under Rule 26(g). It is the discovery analogue of Rule 11 — and it applies to you as the propounding party, not just to the responder.

  • [ ] Confirm every set of requests is signed by an attorney of record (or the party if unrepresented).
  • [ ] Satisfy yourself that each request is (a) consistent with the rules and warranted by existing law, (b) not interposed for any improper purpose such as harassment or needless delay, and (c) neither unreasonable nor unduly burdensome given the needs of the case — the three prongs of Rule 26(g)(1)(B).
  • [ ] Keep a contemporaneous record of the reasonable inquiry behind your requests, so you can show the certification was well founded if challenged.
  • [ ] Avoid the hallmarks of abuse: purely duplicative requests, requests aimed at driving up the opponent's costs, and requests untethered to any pleaded claim or defense.
  • [ ] Remember that a Rule 26(g) violation carries mandatory sanctions — the court "must" impose an appropriate sanction on the signer, the party, or both.

Why it matters, and the traps. Propounding lawyers tend to think of sanctions as something that happens to the other side. Rule 26(g) says otherwise: serving discovery that is harassing, disproportionate, or interposed to run up costs exposes you to a mandatory sanction. The proportionality analysis you did in Phase 2 is also your Rule 26(g) defense — document it. The practical trap is the "form file" set of 50 requests copied from an unrelated case, signed without thought; if the opponent shows the requests bear no relation to this case's claims, your certification is exposed. Sign only what you have actually vetted against the elements.

Phase 8 — Meet and confer, and the motion to compel under Rule 37(a)

Requests are only as good as the compliance they produce. When responses arrive full of objections, non-answers, and "documents will be produced" promises that never ripen, the enforcement machinery is Rule 37(a).

  • [ ] Read the responses against your requests and build a deficiency chart: request number, response, specific defect (evasive answer, unsupported objection, withholding without a basis stated, incomplete production).
  • [ ] Treat an evasive or incomplete answer as a failure to answer — Rule 37(a)(4) says so expressly.
  • [ ] Meet and confer in good faith before moving — Rule 37(a)(1) requires a certification that you conferred or attempted to confer. Do it in writing and by phone/video, and memorialize it.
  • [ ] Narrow the dispute in the meet-and-confer: concede the requests you can, so the motion presents the court a tight set of genuinely contested items.
  • [ ] If it does not resolve, move to compel under Rule 37(a)(3), attaching the requests, the responses, and the meet-and-confer correspondence.
  • [ ] Seek your expenses: Rule 37(a)(5)(A) makes fee-shifting to the prevailing movant the default when a motion to compel is granted, unless the opposition was substantially justified.
  • [ ] Preserve the follow-on remedy: if the court orders production and the party still refuses, escalate to Rule 37(b) sanctions.

Why it matters, and the traps. The meet-and-confer is not a formality — it is a jurisdictional-feeling prerequisite that judges enforce strictly. A motion to compel filed without a genuine, documented conferral effort is routinely denied on that ground alone, regardless of the merits. Confer in good faith, in writing, and specifically; a two-line email demanding "supplement everything" is not a conferral. The second point of leverage most propounders leave on the table is fees: Rule 37(a)(5) makes fee-shifting the default for a granted motion, so a well-supported motion to compel is not just a way to get the documents — it is a way to make the opponent pay for the obstruction. For how these tools sit within the sanctions ladder and the preclusion consequences under Rule 37(c), see Rule 37(c)(1) and the Preclusion of Undisclosed Evidence: A Practical Guide and the sanctions map in The Federal Discovery Toolkit: A Roadmap From Rule 26(f) to Sanctions.

Worked example. Northgate answers Talus's contention interrogatories with "Discovery is ongoing; Northgate reserves the right to supplement," produces its source code as a metadata-stripped PDF, and objects to the sales interrogatory as "overly broad." Talus builds a deficiency chart, writes a detailed meet-and-confer letter tying each deficiency to a claim element, and holds a video conference. Northgate agrees to re-produce the code in native form but stands on the contention non-answers. Talus moves to compel only the contention answers and the financial data, attaches the correspondence, and requests fees under Rule 37(a)(5). Because the requests were tightly drafted and sequenced, the court grants the motion and orders substantive answers within fourteen days.

Patent-case note: infringement and invalidity contentions

In patent cases, the general written-discovery machinery is overlaid by court-specific rules — many districts have Local Patent Rules (modeled on the Northern District of California's) that require the patentee to serve Infringement Contentions and the accused infringer to serve Invalidity Contentions on a set schedule, independent of interrogatory answers.

  • [ ] Check whether the district (or the judge's standing order) imposes Patent Local Rules and calendar the contention deadlines separately from Rule 33/34 deadlines.
  • [ ] Serve infringement contentions with an element-by-element claim chart mapping each asserted claim limitation to the accused product.
  • [ ] Use contention interrogatories to probe the bases behind the other side's contentions, but do not expect them to substitute for the local-rule disclosures.
  • [ ] Coordinate source-code review procedures early — most patent cases run on a protective order with a source-code-review protocol, and your Rule 34 requests should track it.

Why it matters, and the traps. Patent litigators who treat contentions as ordinary interrogatory fodder get whipsawed: the local rules often lock in the asserted claims and theories, and amending contentions later requires a showing of good cause. Serve them with the care of a pleading. For the broader arc of a patent suit and where contentions and written discovery fit, see The Patent Infringement Lawsuit From Filing to Appeal: A Comprehensive Guide and Litigating Patent Infringement: A Roadmap and Research Guide.

Common mistakes to avoid

  • Serving form-file requests. Boilerplate untethered to the elements draws boilerplate objections and, post-2015, risks a Rule 26(g) sanction. Draft from the proof chart.
  • Miscounting interrogatory subparts. Believing you served 20 when the responder counts 45; your key contention interrogatories fall outside the 25-count cap and go unanswered.
  • Forgetting to specify the ESI form of production. You receive metadata-stripped images of documents whose metadata was the point, and you generally cannot demand a do-over.
  • Serving contention interrogatories too early. They draw a legitimate "premature" objection; courts defer the answers until the close of fact discovery.
  • Compound or argumentative RFAs. They forfeit your Rule 37(c)(2) cost-of-proof leverage because the denial becomes substantially justified.
  • Serving too late. A request whose 30-day response lands after the discovery cutoff cannot be compelled — serve final requests 45–60 days out.
  • Skipping a genuine meet-and-confer. A motion to compel without documented good-faith conferral is denied on that ground alone.
  • Leaving fees on the table. Not requesting expenses under Rule 37(a)(5) when you move to compel, or not invoking Rule 37(c)(2) when a denied admission proves true.
  • Ignoring proportionality. Facially over-broad requests now risk outright denial rather than judicial narrowing.
  • Serving before the Rule 26(f) conference. Premature requests are a nullity and reset your clock.

Consolidated one-glance checklist

Plan

  • [ ] Element-by-element proof chart built; each fact assigned to a tool.
  • [ ] Sequencing plan set (identity/documents → depositions → contentions/RFAs).

Scope

  • [ ] Every request relevant to a claim or defense and defensible on the six proportionality factors.
  • [ ] Time periods, custodians, and subjects narrowed.

Interrogatories (Rule 33)

  • [ ] 25-count cap respected; subparts counted honestly; slots reserved for contention interrogatories.
  • [ ] Contention interrogatories drafted to draw out bases, timed after documents.

Requests for production (Rule 34)

  • [ ] Categories defined by subject and custodian, not catchalls.
  • [ ] ESI form of production specified (native + metadata where it matters).
  • [ ] Preservation/litigation-hold coordination confirmed.

Requests for admission (Rule 36)

  • [ ] Atomic, factual, or document-genuineness propositions only.
  • [ ] Authentication and undisputed facts locked down; Rule 37(c)(2) leverage preserved.

Timing

  • [ ] Rule 26(f) conference held before service.
  • [ ] Final requests served 45–60 days before the discovery cutoff.

Certification

  • [ ] Every set signed; Rule 26(g)(1)(B) prongs satisfied; reasonable-inquiry record kept.

Enforcement

  • [ ] Deficiency chart built; good-faith meet-and-confer documented.
  • [ ] Motion to compel under Rule 37(a) with a fee request; escalation to Rule 37(b) preserved.

Primary authority

Secondary sources

  • Wright & Miller, Federal Practice and Procedure (Civil) — authoritative treatment of Rules 26, 33, 34, 36, and 37.
  • The Sedona Conference, Principles and Commentary on ESI and proportionality — persuasive authority on form of production and cost-benefit analysis.

Related UpLaw Resources

Related Guides & Articles

Related Checklists

Related Toolkits

This checklist is general legal information from UpLaw (uplaw.us), not legal advice, and does not create an attorney-client relationship. The Federal Rules of Civil Procedure, local rules, and standing orders change and vary by district and judge; verify current requirements and consult qualified counsel before serving discovery or moving to compel.