The Federal Discovery Toolkit: A Roadmap From Rule 26(f) to Sanctions

Litigation > Discovery | Published 8 January 2026 - Updated 4 June 2026 | UpLaw - uplaw.us

Discovery is where most federal cases are actually won, lost, and priced. This toolkit walks the full arc, planning, disclosures, written discovery, ESI, privilege, depositions, experts, subpoenas, and sanctions, and connects each move to the rule that governs it and the deeper resource that works it.

Keywords: discovery, Federal Rules of Civil Procedure, Rule 26(f), proportionality, initial disclosures, interrogatories, requests for production, requests for admission, ESI, e-discovery, litigation hold, spoliation, privilege log, work product, depositions, Rule 30(b)(6), expert discovery, motion to compel, Rule 37 sanctions, Sedona Conference

---

How to read this toolkit

Trials are rare. The overwhelming majority of federal civil cases resolve on the strength of the record built during discovery, on a summary-judgment motion, or in a settlement priced against the evidence each side has amassed. That makes discovery the longest, most expensive, and most outcome-determinative phase of a typical lawsuit, and the phase where disciplined lawyering separates itself most visibly from careless lawyering. The rules interlock, the deadlines are unforgiving, the volume of electronically stored information can dwarf everything else in the case, and the penalties for getting it wrong run from a fee award to the loss of a claim.

This document is a map, not a manual for any one task. It is written for the litigation associate and paralegal who execute discovery day to day, for the partner supervising the machine, and for in-house counsel and business clients who need to understand what their outside team is doing and why the invoices look the way they do. Each stage below states the governing rule, explains the doctrine and its traps, gives a concrete worked example, and points to the UpLaw guide or checklist that treats the task in depth. The connective tissue is the Federal Rules of Civil Procedure, principally Rules 26 through 37 plus Rule 45, as supplemented by the assigned court's local rules, the judge's standing orders, and any case-specific ESI protocol.

Two ideas govern everything that follows, and nearly every discovery fight eventually collapses back into one of them. First, discovery must be relevant and proportional to the needs of the case under Federal Rule of Civil Procedure 26(b)(1). Second, every party carries an affirmative duty to preserve and disclose, and the breach of that duty is punished with real teeth. Hold those two ideas in mind as you read; they explain the design of almost every rule in the set. For the broader procedural context in which discovery sits, from complaint to appeal, see the UpLaw Federal Civil Litigation roadmap and the companion narrative on federal civil litigation filings.

The roadmap at a glance

1. Plan the discovery. Confer under Rule 26(f), build the discovery plan, and paper the protective order and clawback.
2. Make initial disclosures. Serve Rule 26(a)(1) disclosures and keep them current under Rule 26(e).
3. Run written discovery. Serve and answer interrogatories (Rule 33), requests for production (Rule 34), and requests for admission (Rule 36).
4. Handle ESI and e-discovery. Preserve, collect, review, and produce electronically stored information.
5. Protect privilege. Withhold and log privileged and work-product material under Rule 26(b)(5).
6. Take and defend depositions. Work Rule 30, including the distinct discipline of a Rule 30(b)(6) corporate designee.
7. Disclose and depose experts. Meet the Rule 26(a)(2) report deadlines and the Rule 26(b)(4) protections.
8. Reach non-parties. Use Rule 45 subpoenas for documents and testimony from people outside the case.
9. Enforce and defend. Meet and confer, move to compel under Rule 37(a), and litigate sanctions under Rule 37(b), (c), and (e).

A recurring hypothetical will make the abstractions concrete. Throughout, imagine Meridian Robotics, Inc. v. Halcyon Dynamics, LLC, an invented federal suit in which Meridian, a warehouse-automation company, sues a former engineering partner for breach of a joint-development agreement and misappropriation of trade secrets after Halcyon allegedly used shared source code to launch a competing product. It is entirely fictional, but it is the kind of medium-stakes commercial case where discovery decides the outcome.

---

The two master principles

Relevance and proportionality under Rule 26(b)(1)

Rule 26(b)(1) sets the outer boundary of all discovery. A party may obtain discovery of "any nonprivileged matter that is relevant to any party's claim or defense and proportional to the needs of the case." Two features of that sentence deserve emphasis.

First, "relevant" in discovery is broader than "admissible." The Supreme Court framed the discovery relevance standard generously in Oppenheimer Fund, Inc. v. Sanders, 437 U.S. 340, 351 (1978), and Rule 26(b)(1) now says expressly that information "need not be admissible in evidence to be discoverable." A document can be inadmissible hearsay and still be squarely discoverable if it might lead to admissible proof or illuminate a claim or defense. What the 2015 amendments deleted was the old, much-abused phrase permitting discovery "reasonably calculated to lead to the discovery of admissible evidence," which litigants had misread as an independent, near-limitless charter. The standard is relevance to a claim or defense, full stop.

Second, and more consequentially, the December 1, 2015 amendments moved proportionality from a buried limitation in old Rule 26(b)(2)(C) to the front line of the scope definition itself. Courts now weigh six express factors: the importance of the issues at stake in the action, the amount in controversy, the parties' relative access to relevant information, the parties' resources, the importance of the discovery in resolving the issues, and whether the burden or expense of the proposed discovery outweighs its likely benefit. No single factor controls, and the burden of showing proportionality is shared rather than dumped on the party resisting discovery. Treat proportionality as both a sword and a shield: invoke it to trim a sprawling request, and expect it to be turned against your own demands.

Hypothetical. Meridian serves a request for every email in Halcyon's possession "concerning software" over an eight-year window. Halcyon objects that the request sweeps in years predating the parties' relationship and a workforce of hundreds, at a review cost it estimates in the high six figures against a claim worth roughly two million dollars. On a Rule 26(b)(1) analysis, a court is likely to narrow the request by custodian, date range, and search terms rather than order the whole haystack produced. The proportionality factors do the work: the marginal benefit of the oldest, most attenuated emails is small next to the review burden.

The duty to preserve

The obligation to preserve evidence does not wait for a complaint. It attaches when litigation is reasonably anticipated, which is frequently months before suit and sometimes turns on a single event: a demand letter, a credible threat, a serious internal investigation, or an executive's decision to sue. Federal courts have developed this trigger through the common law, and the leading formulations are consistent even where the circuits phrase them differently. See Silvestri v. Gen. Motors Corp., 271 F.3d 583, 590-91 (4th Cir. 2001) (the duty arises when a party knows or should know that evidence may be relevant to future litigation); West v. Goodyear Tire & Rubber Co., 167 F.3d 776, 779 (2d Cir. 1999).

The practical response to the trigger is a prompt, documented litigation hold: suspend routine deletion and auto-purge policies, identify the custodians and data sources likely to hold relevant material, issue written hold notices, and, critically, follow up to confirm compliance rather than assuming a one-time email did the job. The Southern District of New York's Zubulake line remains the canonical treatment of what counsel and client must actually do. In the decision practitioners call Zubulake V, the court held that counsel must oversee compliance with the hold, communicate directly with key players, and make certain that all sources of potentially relevant information are identified and preserved. Zubulake v. UBS Warburg LLC, 229 F.R.D. 422, 432 (S.D.N.Y. 2004); see also Zubulake v. UBS Warburg LLC, 220 F.R.D. 212 (S.D.N.Y. 2003) (preservation and adverse-inference framework). The point is repeated across the case law: a preservation program is a process, not a memo. Pension Comm. of the Univ. of Montreal Pension Plan v. Banc of Am. Sec., LLC, 685 F. Supp. 2d 456 (S.D.N.Y. 2010), abrogated on other grounds by Chin v. Port Auth. of N.Y. & N.J., 685 F.3d 135 (2d Cir. 2012).

Getting preservation right is the first thing on the list and the most dangerous thing to get wrong, because the consequence of failure is measured under Rule 37(e), covered in the ESI stage below. A litigation hold also sits at the intersection of pre-suit strategy and discovery; the moment a party sends or receives a serious demand letter, both sides should assume the preservation clock has started.

---

Stage 1: Plan the discovery (Rule 26(f) and Rule 16)

Discovery opens with a conversation, not a stack of paper. Rule 26(f) requires the parties to confer "as soon as practicable" and in any event at least 21 days before the Rule 16(b) scheduling conference. They must discuss the nature and basis of the claims and defenses, the possibilities for prompt settlement, arrangements for the initial disclosures, any issues about preserving discoverable information, and, in a provision that now drives the whole enterprise, the disclosure, discovery, and preservation of electronically stored information. The product is a written discovery plan submitted to the court, which the judge typically folds into a Rule 16(b) scheduling order that fixes the deadlines the parties will live under for the next year.

Three instruments should come out of this stage, and each pays for itself many times over:

• An ESI protocol. Negotiate the format of production, the custodians and date ranges, the search terms or the use of technology-assisted review, de-duplication and email threading, and how the parties will handle metadata. Deferring these questions guarantees a fight later, usually after each side has already spent money doing it their own way.
• A protective order. Confidential business information, trade secrets, and personal data need a governing order that defines confidentiality tiers, "attorneys' eyes only" treatment, and the mechanics for challenging designations. In Meridian, where the disputed source code is the entire case, no meaningful production happens until the protective order is entered.
• A clawback order under Federal Rule of Evidence 502(d). A 502(d) order is the single most cost-effective document in modern discovery. It provides that disclosure of privileged material in the litigation does not waive the privilege in that proceeding or any other, and it does so without the fact-intensive reasonableness inquiry that Rule 502(b) otherwise requires. With a 502(d) order in hand, a party can review at a defensible pace without betting the privilege on catching every stray document.

The tone set at the Rule 26(f) conference matters beyond the checklist. The Sedona Conference Cooperation Proclamation urges counsel to treat the mechanics of discovery, as distinct from the merits, as a cooperative rather than adversarial exercise, and many judges now expect exactly that. Decisions made in this first hour shape the cost and risk of everything downstream. For a task-level walkthrough of the conference and the plan, see the UpLaw checklist on Rule 26 initial disclosures and the discovery plan, and for the wider toolset, the refresher on mastering the tools, rules, and pitfalls of federal civil discovery.

---

Stage 2: Make initial disclosures (Rule 26(a)(1))

Rule 26(a)(1) requires each party, early and without waiting for a request, to disclose four categories of information: the individuals likely to have discoverable information the party may use to support its claims or defenses, with the subjects of that information; a copy or description by category and location of the documents, ESI, and tangible things the party may use to support its claims or defenses; a computation of each category of damages claimed, with the supporting materials made available for inspection; and any insurance agreement that might satisfy a judgment. Absent a stipulation or court order, these are due within 14 days after the Rule 26(f) conference.

Two features are easy to underrate. The first is the phrase "may use to support." Initial disclosures are not a neutral inventory of everything a party knows; they are a disclosure of the ammunition the party intends to fire. That framing narrows the obligation but also sets a trap, because a party generally may not use, at a hearing, on a motion, or at trial, information or a witness it failed to disclose. The second is the duty to supplement under Rule 26(e): disclosures and discovery responses must be corrected and completed in a timely manner as new information surfaces. A disclosure that was complete in month one and stale by month six, left uncorrected, is a disclosure failure.

The consequence lives in Rule 37(c)(1), and it is unusually automatic. A party that fails to disclose or supplement "is not allowed to use that information or witness to supply evidence on a motion, at a hearing, or at a trial, unless the failure was substantially justified or is harmless." The sanction operates by its own force, without a prior court order, and the burden of proving substantial justification or harmlessness sits on the party that failed to disclose. Because a precluded witness or document is often the very proof an element depends on, this quiet rule can be quietly dispositive. UpLaw treats it at length in the guide to Rule 37(c)(1) and the preclusion of undisclosed evidence. Treat initial disclosures as the opening move in a preservation-and-disclosure discipline that runs unbroken to the verdict.

---

Stage 3: Run written discovery (Rules 33, 34, and 36)

Written discovery is the workhorse of the case. Three tools do most of the labor, each with its own mechanics, its own deadline, and its own strategic personality.

Interrogatories (Rule 33)

Interrogatories are written questions a party must answer under oath. Rule 33 presumptively caps them at 25, "including all discrete subparts," per party, absent leave of court or a stipulation, and answers are due within 30 days of service. The subpart limit is a frequent battleground: a single numbered interrogatory that bundles several genuinely distinct inquiries can be counted as multiple interrogatories, and courts apply a "related question" or "common theme" test to decide. Interrogatories excel at identifying the universe of a case, the who, the what, the when, the identities of witnesses, the location of documents, and the party's contentions and their factual bases. Rule 33(d) offers a useful option where the answer can be derived from business records: the responding party may produce the records instead of narrating the answer, provided the burden of locating the answer is substantially the same for both sides. The UpLaw comprehensive guide to objecting and responding to interrogatories and the companion Rule 33 answering checklist work the details, including verification and contention interrogatories.

Requests for production (Rule 34)

Rule 34 is how a party obtains documents, ESI, and tangible things, and how it inspects premises. Responses are due in 30 days. Two features of modern Rule 34 practice deserve special attention because they are the most common source of motions to compel.

First, the 2015 amendments require that objections "state whether any responsive materials are being withheld on the basis of that objection." Rule 34(b)(2)(C). The days of lodging an objection and silently sitting on documents behind it are over; a responding party must reveal that it is withholding and on what basis, so the requesting party can decide whether to fight. Second, boilerplate is now openly disfavored and increasingly sanctionable. A string of unexplained adjectives, "vague, overbroad, unduly burdensome, and not reasonably calculated," attached indiscriminately to every request fails to satisfy Rule 34(b)(2)(B)'s command that objections be stated "with specificity," and courts across the country have treated such responses as effective waivers. Rule 34 also governs the form of production of ESI through Rule 34(b)(2)(E): a party must produce ESI in the form in which it is ordinarily maintained or in a reasonably usable form, and need not produce the same ESI in more than one form. That is where fights over native files, TIFF-plus-load-file, and metadata are resolved. For depth, see UpLaw's comprehensive guide to objecting and responding to requests for production and the operational Rule 34 response checklist.

Hypothetical. Halcyon responds to Meridian's document requests with "Objection: overbroad and unduly burdensome" on all forty requests and produces 300 pages, saying nothing about what it is holding back. Under Rule 34(b)(2)(C), the objections are deficient because they do not state whether responsive materials are being withheld, and under Rule 34(b)(2)(B) they lack specificity. Meridian's meet-and-confer letter will quote both provisions, and if Halcyon does not cure, a motion to compel with a fee request under Rule 37(a)(5) is the predictable next step.

Requests for admission (Rule 36)

Requests for admission are a precision instrument, and the most misunderstood of the three. A party serves written statements and asks the opponent to admit or deny them or the genuineness of documents. The federal rule imposes no numerical cap (unlike many state analogues), but it imposes a brutal default: a matter is deemed admitted unless the party answers or objects within 30 days. Rule 36(a)(3). Miss the deadline, and facts you would have contested are established. And a matter admitted under Rule 36 is "conclusively established" unless the court permits withdrawal or amendment, Rule 36(b), which is a stronger effect than the impeachable weight of a deposition admission. The best practice is to serve RFAs late in discovery, after the productions and depositions have shown which facts are genuinely uncontested, and to use them to authenticate documents and lock down undisputed elements so they need not be proven at trial. UpLaw's strategic guide to answering Rule 36 requests and the Rule 36 answering checklist address the response forms, the narrow permissible objections, and the cost-shifting mechanism of Rule 37(c)(2), under which a party that wrongly denies an RFA can be made to pay the cost of proving the point.

Coordinating the three

The tools are strongest in sequence and combination. Interrogatories map the terrain; requests for production pull in the documents that populate it; requests for admission fence off the ground no longer worth fighting over. A common cadence is to serve interrogatories and RFPs early, mine the productions and depositions through the middle of the discovery period, then deploy targeted RFAs near the close to shrink the case for summary judgment and trial. Watch two limits that trip up even experienced litigators: the 25-interrogatory ceiling, and the timing rule that every written request must be served far enough before the discovery cutoff that the response comes due before discovery closes, because courts routinely refuse to compel answers to requests served too late to be answered in time. The mechanics of these disputes, from deficiency letters to the motion itself, are the same across all three tools; the analytical work is knowing which tool answers which question.

---

Stage 4: Handle ESI and e-discovery

Most discoverable information now lives in electronic form, and it arrives in volumes and varieties that paper never did: email and chat, collaboration platforms and ticketing systems, structured databases, cloud storage, mobile-device data, and the metadata that describes all of it. E-discovery has its own lifecycle, commonly organized around the Electronic Discovery Reference Model (EDRM): information governance, identification, preservation, collection, processing, review, analysis, production, and presentation. The governing legal standards are the same proportionality principle from Rule 26(b)(1), the form-of-production rules in Rule 34(b)(2)(E), and, when things go wrong, the spoliation remedies in Rule 37(e).

Preservation and the litigation hold, revisited

Everything in the ESI lifecycle rests on preservation, which is why the duty to preserve was flagged at the top of this toolkit. The moment litigation is reasonably anticipated, routine deletion and auto-purge must be suspended for potentially relevant sources. The reasonableness of the effort is judged as a process. Counsel who issue a hold and never confirm that IT actually paused the 90-day email purge, or who overlook a departed engineer's laptop or a Slack channel, have not discharged the duty merely by sending a memo. Some courts have imported proportionality into preservation itself, declining to require a party to preserve every conceivable byte where the burden dwarfs the likely value. Victor Stanley, Inc. v. Creative Pipe, Inc., 269 F.R.D. 497 (D. Md. 2010). But proportionality is a defense to over-preservation, not a license to under-preserve the obvious.

Form of production and technology-assisted review

Rule 34(b)(2)(E) resolves most format disputes: ESI is produced as ordinarily maintained or in a reasonably usable form, and not in multiple forms. In practice the parties negotiate this in the ESI protocol, choosing among native files, near-native, and imaged formats accompanied by extracted text and a load file carrying the agreed metadata fields. On the review side, technology-assisted review (also called predictive coding or TAR) is now an accepted, and in large matters often expected, method of culling and prioritizing documents; courts have approved defensible TAR protocols where the parties are transparent about the methodology. The Sedona Conference's Principles remain the leading practical guidance across all of this, and its Glossary supplies the vocabulary courts and vendors use.

The Rule 37(e) framework for lost ESI

When ESI that should have been preserved is lost because a party failed to take reasonable steps to preserve it, and it cannot be restored or replaced through additional discovery, Rule 37(e) supplies a carefully tiered remedy that the 2015 amendment designed to replace a chaotic body of inconsistent circuit law. The structure is worth memorizing because it dictates strategy on both sides:

• Rule 37(e)(1) authorizes curative measures only "upon finding prejudice to another party from loss of the information," and only "measures no greater than necessary to cure the prejudice." This is the ordinary path, and it covers everything from allowing evidence and argument about the loss to more tailored remedies.
• Rule 37(e)(2) authorizes the severe sanctions, a mandatory or permissive adverse-inference instruction, dismissal, or default, "only upon finding that the party acted with the intent to deprive another party of the information's use in the litigation." Intent, not mere negligence, is the gate. That drafting choice was deliberate: it abrogated the line of authority, associated with Residential Funding Corp. v. DeGeorge Financial Corp., 306 F.3d 99 (2d Cir. 2002), and Pension Committee, under which negligence could support an adverse inference, and it now requires a finding of intent before the jury is told to presume the worst.

Hypothetical. Halcyon's engineering lead wipes and re-images his laptop three weeks after Meridian's demand letter, deleting the local repository that would show whether Meridian's code was copied. If Meridian shows only that Halcyon was careless, a court may permit evidence and argument about the loss under Rule 37(e)(1), and perhaps a tailored instruction. If Meridian shows the wipe was done to keep the code out of the case, Rule 37(e)(2) opens the door to an adverse-inference instruction or even a default, either of which likely ends the litigation. The difference between those outcomes is the difference between negligence and intent, which is exactly what the parties will fight about.

Capturing and authenticating web-based and social-media evidence is a recurring sub-problem inside the ESI stage, and it carries its own foundation requirements under the Rules of Evidence. UpLaw addresses it in the practitioner's guide to authenticating website screenshots and web evidence in federal court and the paired authentication checklist.

---

Stage 5: Protect privilege (Rule 26(b)(5) and FRE 502)

Privileged and work-product material is withheld and logged, not produced, and the withholding must be done in a way the rules recognize. Rule 26(b)(5)(A) provides that when a party withholds otherwise discoverable information on a claim of privilege or trial-preparation protection, it must expressly make the claim and describe the nature of the withheld documents or communications in a manner that, without revealing the protected content, enables other parties to assess the claim. In practice that description is a privilege log.

Two distinct protections

Practitioners routinely conflate two protections that behave very differently.

The attorney-client privilege protects confidential communications between a client and counsel made for the purpose of obtaining or providing legal advice. In the corporate setting, the privilege extends beyond the "control group" to communications with employees gathering information at the direction of counsel to enable legal advice, the framework the Supreme Court adopted in Upjohn Co. v. United States, 449 U.S. 383 (1981). The privilege is powerful but fragile: it protects only communications, not underlying facts; it can be lost by disclosure to third parties; and it does not attach to business advice dressed up as legal advice.

The work-product doctrine, codified at Rule 26(b)(3) and rooted in Hickman v. Taylor, 329 U.S. 495 (1947), protects documents and tangible things prepared in anticipation of litigation or for trial by or for a party or its representative. It is qualified, not absolute. An opponent can reach fact work product on a showing of substantial need and an inability to obtain the substantial equivalent without undue hardship, Rule 26(b)(3)(A)(ii), but opinion work product, an attorney's mental impressions, conclusions, opinions, and legal theories, receives near-absolute protection under Rule 26(b)(3)(B). The two doctrines also waive differently: disclosure to an adversary generally waives both, but sharing work product with a third party that does not increase the risk of disclosure to the adversary (say, a co-defendant under a common-interest arrangement) may not waive it, whereas the same disclosure would waive the attorney-client privilege.

Waiver, clawback, and the privilege log

Federal Rule of Evidence 502 governs waiver in federal proceedings and is the practitioner's best friend. Rule 502(b) provides that an inadvertent disclosure does not waive privilege if the holder took reasonable steps to prevent disclosure and promptly took reasonable steps to rectify the error. Rule 502(d) goes further and lets a court order that disclosure in the litigation is not a waiver in that proceeding or any other, cutting off the reasonableness inquiry entirely, which is why the 502(d) order negotiated back at Stage 1 is so valuable. Guard against subject-matter waiver under Rule 502(a): a voluntary disclosure that is used to gain an advantage can waive privilege as to all communications on the same subject, so a party cannot disclose the helpful half of a privileged analysis and withhold the rest.

Build the log with care. Entries that are too thin, a bare "email re: legal advice," invite challenges and, in the worst case, a finding of waiver for failure to substantiate the claim. Entries that quote the privileged content defeat the purpose. Many courts now permit categorical logging by agreement, grouping like documents rather than listing each one, which can save enormous effort in a large ESI case; negotiate that in the ESI protocol. UpLaw's privilege log checklist walks the categorical-versus-document decision, the required fields, and the clawback mechanics.

---

Stage 6: Take and defend depositions (Rule 30)

Depositions are where the paper record becomes live, sworn testimony, and where cases are frequently made or broken. Rule 30 governs oral depositions and sets the presumptive limits: each side may take 10 depositions, a deposition is limited to one day of seven hours, and leave of court or a stipulation is needed to exceed either. A party notices a deposition; a non-party is compelled by subpoena under Rule 45 (Stage 8).

Taking a deposition

Taking a deposition well is a discipline built on preparation. The examiner needs a theory of the case, a document plan keyed to the exhibits, and a questioning strategy that pins the witness to specific facts, closes off escape routes, and locks in testimony that can be used on summary judgment or read at trial. Depositions taken before the key productions are reviewed usually have to be redone, and depositions crammed in after the discovery cutoff invite motions. Sequence them so the documents come first and the witnesses second. The UpLaw comprehensive guide to taking depositions and the deposition-taking checklist cover technique, exhibits, and the use of transcripts.

Defending a deposition

Defending a witness is a different craft. Most objections are reserved for trial and simply preserved on the record; the objections actually made are to the form of the question and to privilege. Rule 30(c)(2) permits an instruction not to answer only in three narrow circumstances: to preserve a privilege, to enforce a court-ordered limitation, or to present a Rule 30(d)(3) motion to terminate or limit an abusive deposition. Coaching the witness through speaking objections and improper conferences is sanctionable, and "form" objections must be stated concisely and non-suggestively. The defending lawyer's real work happens before the deposition, in preparing the witness to tell the truth clearly, concisely, and without volunteering. See UpLaw's guide to defending depositions in federal court and the defending-the-witness checklist.

The Rule 30(b)(6) corporate deposition

Deposing an organization is its own discipline. Under Rule 30(b)(6), a party names the organization and describes the matters for examination "with reasonable particularity," and the organization must designate one or more people to testify about information "known or reasonably available" to it. Two consequences follow. First, the designee speaks for the entity, not merely for personal knowledge; the organization must prepare the witness on the noticed topics even if that means educating a designee on facts he did not personally live through. An under-prepared designee, one who repeatedly answers "I don't know" on a properly noticed topic, can itself be sanctionable and can expose the entity to a motion to compel a further, better-prepared witness. Second, since the December 1, 2020 amendment, the noticing party and the organization must confer in good faith about the number and description of the topics before (or promptly after) the notice, a requirement designed to head off the recurring fights over topic overbreadth. In Meridian, the corporate-designee deposition of Halcyon on topics like "the development history of the accused product" is likely to be the single most important deposition in the case, and both sides will invest accordingly. For a life-cycle view from notice through trial testimony, see the Federal Deposition Toolkit.

---

Stage 7: Disclose and depose experts (Rules 26(a)(2) and 26(b)(4))

Expert discovery runs on its own track and its own clock, usually set by staggered deadlines in the scheduling order for opening, rebuttal, and sometimes reply reports.

The disclosure obligation and the two categories of expert

Rule 26(a)(2)(A) requires disclosure of the identity of any witness who will offer expert testimony. From there the rule splits experts into two categories with very different obligations:

• Retained or specially employed experts (and employees whose duties regularly involve giving expert testimony) must serve a written report under Rule 26(a)(2)(B). The report must contain a complete statement of all opinions and their bases and reasons, the facts or data considered, any exhibits, the witness's qualifications and publications from the last ten years, a list of other cases in which the witness testified in the last four years, and the compensation for the study and testimony. The report is meant to be comprehensive; opinions not fairly disclosed in it are vulnerable to exclusion.
• Non-retained experts, most commonly treating physicians and other percipient experts, require only the lighter disclosure of Rule 26(a)(2)(C): the subject matter on which the witness will testify and a summary of the facts and opinions. Mislabeling a retained expert as non-retained to dodge the full report is a common and dangerous shortcut.

Protection for drafts and attorney-expert communications

The 2010 amendments to Rule 26(b)(4) changed expert practice for the better by protecting most draft reports (Rule 26(b)(4)(B)) and most communications between counsel and a retained expert (Rule 26(b)(4)(C)), with three narrow exceptions for communications about compensation, facts or data the attorney provided that the expert considered, and assumptions the attorney provided that the expert relied on. The practical effect is that counsel and expert can collaborate on the analysis without every draft becoming a deposition exhibit, which is why expert depositions now focus on the final opinions, the data, and the assumptions rather than the drafting process.

Timing, admissibility, and the stakes

Missed expert deadlines run straight into Rule 37(c)(1) preclusion, and because expert opinion is frequently essential to an element, causation, damages, technical infringement, exclusion of the expert can be effectively dispositive. The discovery built here also feeds directly into the admissibility fight under Federal Rule of Evidence 702 and the Daubert trilogy: Daubert v. Merrell Dow Pharmaceuticals, Inc., 509 U.S. 579 (1993), General Electric Co. v. Joiner, 522 U.S. 136 (1997), and Kumho Tire Co. v. Carmichael, 526 U.S. 137 (1999), under which the trial judge acts as a gatekeeper assessing the reliability and fit of expert testimony. The 2023 restyling of Rule 702 reinforced that the proponent must show reliability by a preponderance and that the opinion reflects a reliable application of the methodology. A deposition that pins the expert to a shaky methodology or an unsupported assumption is the raw material of a successful motion to exclude. For the mechanics of a Daubert challenge in a representative context, see UpLaw's treatment of Daubert and the expert-exclusion framework.

---

Stage 8: Reach non-parties (Rule 45 subpoenas)

Much of the evidence in a commercial case sits with people who are not parties: former employees, vendors, banks, cloud providers, accountants, and the like. Rule 45 is the tool that reaches them, and it has traps that catch even careful lawyers.

A subpoena can command a non-party to produce documents or ESI, to permit inspection, or to appear for a deposition. Rule 45 builds in territorial limits: a subpoena may command a person to attend a trial, hearing, or deposition only within 100 miles of where the person resides, is employed, or regularly transacts business, and, for a deposition, within the state. It requires the serving party to take reasonable steps to avoid imposing undue burden or expense, and it arms the recipient with the ability to serve written objections and to move to quash or modify, on grounds that include undue burden, insufficient time to comply, and the disclosure of privileged or protected matter. A non-party responding to a document subpoena gets the benefit of the same proportionality analysis a party enjoys, and courts are often more protective of non-parties precisely because they have no stake in the fight.

Hypothetical. Meridian suspects Halcyon uploaded the shared code to a third-party cloud repository. A Rule 45 subpoena to the cloud provider can reach the access logs and version history, but Meridian must give the provider reasonable time, must avoid a demand so broad it sweeps in unrelated customers' data, and should expect the provider to negotiate scope and cost. If Halcyon believes the subpoena reaches its confidential material, Halcyon, though the code sits with a non-party, may have standing to move to quash to protect its own privilege or trade secrets.

Where the non-party or the evidence sits abroad, Rule 45 gives way to the machinery of international discovery, the Hague Evidence Convention, letters rogatory, and the recurring complications of serving and compelling foreign entities. UpLaw addresses that terrain in the toolkit on litigating IP across borders and the guide to serving process on a Chinese defendant under the Hague Convention.

---

Stage 9: Enforce and defend (Rule 37 motions to compel and sanctions)

When discovery breaks down, Rule 37 supplies the enforcement machinery, and it is built as a ladder from gentle to severe.

Meet and confer, then move to compel

Before invoking the court, a party must meet and confer in a good-faith effort to resolve the dispute without judicial intervention. Rule 37(a)(1) requires it, most local rules add their own certification requirements, and many judges add informal pre-motion procedures, a letter, a conference, a phone call, that must be exhausted before a motion is entertained. A motion to compel filed without a genuine meet-and-confer effort is routinely denied on that ground alone. When the effort fails, Rule 37(a) authorizes a motion to compel an answer, a designation, a production, or an inspection, and Rule 37(a)(4) provides the crucial rule that an evasive or incomplete disclosure, answer, or response is treated as a failure to respond, which is how a party gets relief against the opponent who technically "responded" with objections and nothing else.

The motion carries a fee-shifting default that surprises litigants who treat discovery motions casually. Under Rule 37(a)(5), if the motion is granted, the court must ordinarily require the losing party (or its counsel) to pay the movant's reasonable expenses, including attorney's fees, unless the position was substantially justified or other circumstances make an award unjust; and if the motion is denied, the fees run the other way. The fee-shifting is presumptive, not discretionary in the ordinary sense, which raises the cost of both bad objections and bad motions.

The sanctions ladder for disobedience and spoliation

Failing to obey a discovery order escalates the stakes sharply. Rule 37(b)(2) authorizes a graduated menu of sanctions for disobeying a court's discovery order: directing that designated facts be taken as established, prohibiting the disobedient party from supporting or opposing designated claims or defenses, striking pleadings, staying the proceeding, dismissing the action in whole or in part, rendering a default judgment, and treating the disobedience as contempt. Courts choose the least severe sanction that will cure the harm and deter, reserving dismissal and default for willful, bad-faith, or repeated violations. Layered on top are the two self-executing consequences already discussed, Rule 37(c)(1) preclusion of undisclosed evidence and Rule 37(e)'s tiered remedies for lost ESI, and Rule 37(c)(2)'s cost-shifting for wrongful denials of requests for admission.

Hypothetical. The court orders Halcyon to produce its source-code repository by a date certain. Halcyon produces a scrubbed version stripped of the version history. Meridian moves under Rule 37(b). Because the disobedience is of a direct order and goes to the heart of the case, the court's menu runs from an order deeming the copying established, to precluding Halcyon from contesting misappropriation, to, if the court finds willfulness, entering a default. The escalation tracks the culpability, which is the lesson of the entire enforcement scheme.

The theme that has run through this toolkit lands here with full force: the duty to preserve and disclose is not aspirational, it is enforced with sanctions that can decide the case. Document the diligence, meet the deadlines, and treat every discovery obligation as if a judge will one day read the file. For the enforcement stage in its broader litigation context, and for early-case strategy that anticipates these fights, see UpLaw's frameworks for assessing a civil lawsuit and for navigating federal civil litigation as a small business.

---

Cross-cutting disciplines

A handful of practices run through every stage and deserve to be named on their own.

Cost control and proportionality as a live budget. Discovery cost is not a byproduct of the case; it is a variable the parties manage. Custodian selection, date ranges, search terms, de-duplication, email threading, and TAR are all levers, and the Rule 26(f) ESI protocol is where they are set. The proportionality factors of Rule 26(b)(1) give a resisting party the vocabulary to push back on disproportionate demands, and give a requesting party a check on its own over-asking.

Cooperation on process, adversarial on the merits. The Sedona Conference Cooperation Proclamation captures the modern judicial expectation: fight hard over what the evidence means, cooperate on the mechanics of exchanging it. Judges increasingly penalize gamesmanship over search terms and formats, and reward parties who resolve process disputes without motions.

Discovery on discovery. When a party suspects the other side's search or preservation was inadequate, it may seek "discovery on discovery," interrogatories and depositions about the opponent's collection and search methodology. Courts permit it where there is a specific, articulable basis to doubt the adequacy of the process, but not as a fishing expedition; a bare suspicion of a gap does not open the opponent's discovery process to examination.

Authentication downstream. Everything collected in discovery must eventually clear the Rules of Evidence to be used. Building the authentication foundation, especially for ESI, web pages, and social media, during discovery rather than on the courthouse steps is what separates a usable record from a pile of documents. The web-evidence resources cited above are the place to start.

Verify the current rules. The Federal Rules are amended on a rolling basis, typically effective December 1 of the year adopted, and local rules and standing orders vary widely by district and by judge. The 2015 amendments reshaped proportionality and Rule 37(e); the 2020 amendment reshaped Rule 30(b)(6); the 2023 restyling touched Rule 702. Before relying on any provision in this toolkit, confirm the operative text of the Federal Rule, the local rule, the judge's standing order, and any case-specific ESI protocol. Good case-law research habits apply with equal force to the procedural authorities that govern how the evidence is gathered in the first place.

---

A note on scope and use

This toolkit is a navigation and research resource for federal civil discovery, not advice on any specific matter. Discovery practice varies by district, by judge, and by case type, and the proportionality analysis, the local meet-and-confer rules, the ESI protocol, and the standing orders that apply to your case may differ from the general framework described here. The Meridian Robotics hypothetical is entirely invented and is used only to illustrate how the rules interact. Verify the operative rules, orders, and protocols in your court before acting.

---

Related UpLaw Resources

Related Toolkits

• Federal Civil Litigation: A Roadmap and Resource Guide
• The Federal Deposition Toolkit: From Notice to Trial Testimony
• Litigating IP Across Borders: A Roadmap and Resource Library for International Disputes

Related Guides and Articles

• Federal Civil Discovery: Mastering the Tools, Rules, and Pitfalls
• Federal Civil Litigation Filings: A Comprehensive Guide from Complaint to Appeal
• Interrogatories in Civil Litigation: A Comprehensive Guide to Objecting and Responding
• Requests for Production: A Comprehensive Guide to Objecting and Responding
• Answering Requests for Admission Under Rule 36: A Strategic Practitioner's Guide
• Taking Depositions in Federal Civil Litigation: A Comprehensive Guide
• Defending Depositions in Federal Court: A Comprehensive Guide
• Rule 37(c)(1) and the Preclusion of Undisclosed Evidence: A Practical Guide
• Authenticating Website Screenshots and Web Evidence in Federal Court: A Practitioner's Guide
• Assessing a Civil Lawsuit: A Comprehensive Early-Case Framework

Related Checklists

• Rule 26 Initial Disclosures and the Discovery Plan: A Practical Checklist
• Answering Rule 33 Interrogatories: A Practical Checklist
• Responding to Rule 34 Document Requests: A Practical Checklist
• Answering Rule 36 Requests for Admission: A Practical Checklist
• Building a Privilege Log: A Practical Checklist
• Preparing to Take a Deposition: A Practical Checklist
• Defending the Witness on the Record: A Practical Checklist
• Getting Website Evidence Admitted: A Practical Authentication Checklist

Primary and Secondary Authorities

• Federal Rules of Civil Procedure 16, 26, 30, 31, 32, 33, 34, 36, 37, and 45
• Federal Rules of Evidence 502 (waiver and clawback) and 702 (expert testimony)
• Oppenheimer Fund, Inc. v. Sanders, 437 U.S. 340 (1978); Hickman v. Taylor, 329 U.S. 495 (1947); Upjohn Co. v. United States, 449 U.S. 383 (1981)
• Zubulake v. UBS Warburg LLC, 217 F.R.D. 309, 220 F.R.D. 212, and 229 F.R.D. 422 (S.D.N.Y. 2003-2004); Silvestri v. Gen. Motors Corp., 271 F.3d 583 (4th Cir. 2001); Pension Comm. of the Univ. of Montreal Pension Plan v. Banc of Am. Sec., LLC, 685 F. Supp. 2d 456 (S.D.N.Y. 2010); Victor Stanley, Inc. v. Creative Pipe, Inc., 269 F.R.D. 497 (D. Md. 2010)
• Daubert v. Merrell Dow Pharmaceuticals, Inc., 509 U.S. 579 (1993); General Electric Co. v. Joiner, 522 U.S. 136 (1997); Kumho Tire Co. v. Carmichael, 526 U.S. 137 (1999)
• The Sedona Conference, The Sedona Principles, Third Edition; the Cooperation Proclamation; and the Sedona Conference Glossary (thesedonaconference.org); the Electronic Discovery Reference Model (EDRM)
• Charles Alan Wright & Arthur R. Miller, Federal Practice and Procedure (Civil), discovery volumes

This toolkit is general legal information, not legal advice. Discovery rules, the proportionality analysis, local rules, ESI protocols, and standing orders vary by court and by judge; verify the operative rules and orders in your case before acting.