Rule 26 Initial Disclosures and the Discovery Plan: A Practical Checklist

Litigation > Discovery | Published 2 August 2025 - Updated 9 October 2025 | UpLaw - uplaw.us

A field-tested, phase-by-phase checklist for the front end of federal discovery, pairing each step with the governing rule, the case law that gives it teeth, and worked examples, updated for the December 1, 2025 amendments to Rules 26(f) and 16(b).

Keywords: Rule 26, initial disclosures, Rule 26(a)(1), Rule 26(f) conference, discovery plan, Rule 16(b) scheduling order, proportionality, privilege log timing, FRE 502(d), litigation hold, ESI protocol, Rule 26(g), expert disclosures, duty to supplement, Rule 37(c)(1), Rule 37(e) spoliation

Most people picture discovery as the moment a document request lands in the inbox. By then, the important work is half over. Federal discovery opens with three obligations that arrive before anyone serves a single request: a duty to preserve evidence, a mandatory exchange of core information that no party has to ask for, and a face-to-face conference between adversaries designed to reduce the fights that follow. All three live in Rule 26 of the Federal Rules of Civil Procedure. Handle them well and a case runs on rails; handle them casually and the same lawyer who skipped the hold letter is later explaining to a magistrate judge why a key custodian's phone was wiped, or why the damages theory the client is counting on should not be struck for want of a computation.

This checklist converts the opening weeks into ordered, defensible steps. It follows the sequence a disciplined litigator actually works through, not the order in which the subsections happen to appear in the rulebook: preserve, map, disclose, confer, plan, and calendar what comes next. It reflects the Federal Rules as amended through December 1, 2025, including the amendments that move privilege-log method and timing to the front of every case. For the full architecture of discovery into which these front-end steps fit, keep our refresher on the tools, rules, and pitfalls of federal civil discovery and the federal discovery toolkit from Rule 26(f) to sanctions open in the next tab.

How the Front End Fits Together

Before the phases, a map. Rule 26's opening obligations are a relay, and each handoff has a deadline pinned to the one before it. Missing an early one compresses everything downstream.

The relay runs roughly like this. A complaint is filed and served. Within the earlier of 90 days after any defendant is served or 60 days after any defendant appears, the court must enter a scheduling order under Rule 16(b)(2). Working backward from that date, the parties must hold their Rule 26(f) conference "as soon as practicable" and in any event at least 21 days before the scheduling conference or the scheduling-order due date. Fed. R. Civ. P. 26(f)(1). Initial disclosures under Rule 26(a)(1) come due at or within 14 days after that conference. Fed. R. Civ. P. 26(a)(1)(C). The written discovery plan the parties produce out of the conference must reach the court within 14 days after they confer. Fed. R. Civ. P. 26(f)(2). The court folds that plan into its Rule 16(b) order, which then governs the rest of the case.

Two features of that choreography deserve emphasis at the outset. First, the duty to preserve evidence sits outside the timeline entirely, because it can attach months before the complaint is filed. Second, none of these obligations is self-canceling: a party cannot sit on its initial disclosures because it thinks the other side's are thin, and it cannot skip the hold because it assumes the opponent will preserve the same documents. The rest of this guide takes the relay one leg at a time.

Front-end event	Governing rule	Trigger / deadline
Duty to preserve attaches	Common law; Fed. R. Civ. P. 37(e)	When litigation is reasonably anticipated
Rule 26(f) conference	Fed. R. Civ. P. 26(f)(1)	At least 21 days before the scheduling conference or Rule 16(b) order due date
Initial disclosures served	Fed. R. Civ. P. 26(a)(1)(C)	At or within 14 days after the 26(f) conference
Written discovery plan filed	Fed. R. Civ. P. 26(f)(2)	Within 14 days after the 26(f) conference
Rule 16(b) scheduling order	Fed. R. Civ. P. 16(b)(2)	Earlier of 90 days after service or 60 days after appearance
Expert disclosures	Fed. R. Civ. P. 26(a)(2)(D)	As court orders; default 90 days before trial
Pretrial disclosures	Fed. R. Civ. P. 26(a)(3)(B)	At least 30 days before trial

Phase 1: Preserve Evidence and Issue the Litigation Hold

• [ ] Determine whether the duty to preserve has already attached; it arises when litigation is reasonably anticipated, which frequently precedes the filing of the complaint.
• [ ] Identify every custodian who may hold relevant information: named parties, decision-makers, key employees, departed employees, IT and records personnel, and third parties within the client's control.
• [ ] Issue a written litigation hold from a person with authority, tailored to the matter, and collect signed acknowledgments.
• [ ] Suspend routine auto-deletion, document-retention purges, and reassignment or re-imaging of departing employees' devices for the covered categories.
• [ ] Map data sources beyond corporate email: text and chat, collaboration platforms (Slack, Teams), ephemeral-messaging apps, mobile devices, personal email and personal devices used for work, cloud storage, and structured databases.
• [ ] Send periodic reminders, re-issue the hold as custodians and issues change, and document every step of the preservation effort.

Why preservation comes first. Spoliation can convert a winning case into a losing one without regard to the merits. The duty to preserve is a creature of common law that predates any discovery request, and courts have located its source in the moment a party "reasonably anticipates litigation." The obligation does not wait for a complaint. A demand letter, an internal escalation, a regulatory inquiry, or an executive's email predicting a lawsuit can each start the clock. Because a well-drafted demand often triggers the recipient's duty (and confirms the sender's own), the two documents belong on the same desk; see our checklist on writing an effective demand letter, which treats the litigation hold as a companion step.

The single most important thing to understand about preservation is whose job it is. The duty runs first to counsel, not just to the client. A lawyer who fires off a hold notice and then looks away has not discharged the obligation. The canonical statement comes from the Zubulake litigation: counsel must take "affirmative steps to monitor compliance so that all sources of discoverable information are identified and searched," which means, at minimum, communicating with the key custodians directly and following up. Zubulake v. UBS Warburg LLC (Zubulake V), 229 F.R.D. 422, 432 (S.D.N.Y. 2004); see also Zubulake v. UBS Warburg LLC (Zubulake IV), 220 F.R.D. 212 (S.D.N.Y. 2003) (fixing the duty to preserve). Counsel's active-supervision role has been echoed in decisions such as Cache La Poudre Feeds, LLC v. Land O'Lakes, Inc., 244 F.R.D. 614 (D. Colo. 2007). The lesson for a checklist is blunt: "sent the hold" is not the same as "did the hold."

Since 2015, the sanction for losing electronically stored information carries a defined structure. Rule 37(e) applies where ESI "that should have been preserved in the anticipation or conduct of litigation is lost because a party failed to take reasonable steps to preserve it, and it cannot be restored or replaced through additional discovery." On a showing of prejudice, the court "may order measures no greater than necessary to cure the prejudice." But the severe sanctions—an adverse-inference instruction, a mandatory or permissive presumption that the lost information was unfavorable, dismissal, or default—are reserved for a finding that the party "acted with the intent to deprive another party of the information's use in the litigation." Fed. R. Civ. P. 37(e)(2). The 2015 amendment was written specifically to foreclose the more freewheeling negligence-based adverse-inference approach some courts had adopted, so intent, not carelessness, is now the gateway to the case-ending remedies. That does not make carelessness safe: curative measures under Rule 37(e)(1) can still hurt, and the fight over intent is expensive and unpredictable.

Worked example. Halcyon Robotics sues a former lead engineer and his new employer, Meridian Dynamics, for trade-secret misappropriation. Halcyon's counsel issues a broad written hold the day the complaint is filed. What counsel forgets: the engineering team coordinates on a chat platform whose default setting deletes messages after 30 days, and the departed engineer's laptop is already sitting in an IT reclamation queue scheduled for re-imaging. Neither is corporate email, so neither triggers anyone's instinct. Six weeks later, Meridian's messages about the disputed source code are gone, and the reclaimed laptop has been wiped and reassigned. Whether that becomes a curative instruction or a case-ending sanction turns on intent under Rule 37(e)(2)—but the entire dispute was avoidable with a hold that named chat platforms and device queues as covered sources on day one. Preservation is the rare litigation task you complete first and ask questions about later. For the parallel discipline when the lost data are the client's own confidential information, compare our trade-secret incident-response checklist and the checklist on protecting trade secrets when employees leave.

Phase 2: Map the Case to the Elements Before You Disclose

• [ ] Write out the elements of each claim, counterclaim, and affirmative defense, drawn from the controlling statute or cause of action, the pattern jury instructions, and the verdict form.
• [ ] Build a proof matrix: for each element, identify the witness who supplies it, the documents and ESI that support it, and the evidentiary objections you expect.
• [ ] Identify, by category, the documents and ESI the party may use to support its own claims or defenses; that phrase, not "everything relevant," is the touchstone for initial disclosures.
• [ ] Develop a preliminary damages model with categories you can compute and support, and note which supporting materials will have to be produced or made available.
• [ ] Locate any insurance policy that might indemnify or satisfy a judgment, and any indemnification agreement that functions like one.

Why map before you disclose. Rule 26(a)(1) does not ask a party to hand over its whole file. It asks for the witnesses, documents, and damages the party "may use to support its claims or defenses." Fed. R. Civ. P. 26(a)(1)(A)(i)–(iii). That is an affirmative-case standard, not a relevance standard, and you cannot apply it accurately to material you have not yet catalogued. Mapping the case to its elements is how you find out what you actually have to disclose—and, just as usefully, what you do not.

The proof matrix pays dividends far beyond the disclosure statement. It tells you which custodians and documents carry the weight of the case, which sharpens the litigation hold you issued in Phase 1 and the search-term negotiation you will have in Phase 4. It tells you where your evidence is thin, which shapes your settlement posture. And it forces the damages conversation early, before a court-imposed deadline turns a soft estimate into a hard admission. This mapping is the same discipline that drives early case assessment generally; for the larger decision of whether and how aggressively to litigate, see our checklist for evaluating a new civil case and the deeper framework for turning case-evaluation instinct into a repeatable method.

A word on damages, because it is where the mapping most often goes wrong. Rule 26(a)(1)(A)(iii) calls for "a computation of each category of damages," together with the documents on which each computation rests, "made available for inspection and copying." "Computation" means arithmetic and method, not a placeholder. A plaintiff who writes "damages to be determined" or drops in a single lump sum has not disclosed a computation, and courts treat that failure seriously. In Design Strategy, Inc. v. Davis, 469 F.3d 284 (2d Cir. 2006), the Second Circuit upheld the exclusion of lost-profits evidence where the plaintiff never provided the required computation, treating preclusion under Rule 37(c)(1) as the default consequence. Build the model now, while it is a strategic exercise, rather than later, when it is a sanctions defense. On how damages are actually computed across theories, our guides to contract damages and what an intellectual-property case is worth give the categories a disclosure statement has to name.

Phase 3: Prepare and Serve Rule 26(a)(1) Initial Disclosures

• [ ] Disclose each individual likely to have discoverable information the party may use to support its case, with name and, if known, address and telephone number, plus the subjects of that information.
• [ ] Disclose a copy—or a description by category and location—of the documents, ESI, and tangible things the party may use to support its case (impeachment-only materials are excluded).
• [ ] Provide a computation of each category of damages and make the non-privileged supporting materials available for inspection and copying.
• [ ] Identify and produce (or make available) any insurance agreement that may cover or indemnify part of a judgment.
• [ ] Confirm the case is not within a Rule 26(a)(1)(B) exemption; if it is, the automatic-disclosure duty does not apply.
• [ ] Base the disclosures on information then reasonably available; do not withhold because your investigation is incomplete, the opponent's disclosures look deficient, or the opponent has not disclosed.
• [ ] Calendar the deadline: at or within 14 days after the Rule 26(f) conference, unless a stipulation or court order sets a different time.
• [ ] Have an attorney of record sign the disclosures, satisfying the certification of Rule 26(g).

The one place you give without being asked. Initial disclosures are the only point in federal practice where a party must surrender core case information before anyone serves a discovery request. Congress and the rulemakers designed the requirement to accelerate settlement and to spare both sides a round of formulaic opening interrogatories. The 1993 Advisory Committee Notes describe the object plainly: to make available, at the start, the information a party would otherwise have to extract through discovery. The 2000 Notes narrow the field usefully—a party discloses only what it "may use to support" its position at a pretrial conference, in a motion, at trial, or in discovery other than in response to a request. Material a party holds but will not affirmatively use need not be listed, though of course it may still be discoverable on request.

The four buckets, precisely. Under Rule 26(a)(1)(A), a party must provide (i) the identifying information and subjects for each supporting witness; (ii) a copy or a category-and-location description of supporting documents, ESI, and tangible things, excepting impeachment-only items; (iii) a computation of each damages category with supporting materials; and (iv) any applicable insurance agreement. The witness and document buckets share the "may use to support" limiter. The insurance bucket does not: a defendant discloses coverage even though it will never "use" the policy to support a defense, because the rule exists to inform the other side's settlement math.

The exemptions. Rule 26(a)(1)(B) exempts nine categories of proceedings from the automatic-disclosure regime, among them an action for review on an administrative record, a forfeiture action in rem arising from a federal statute, a petition for habeas corpus or other challenge to a criminal conviction or sentence, a pro se action brought by a person in custody, an action to enforce or quash an administrative summons or subpoena, an action by the United States to recover benefit payments or to collect on a student loan, a proceeding ancillary to a proceeding in another court, and an action to enforce an arbitration award. If your case sits in one of these boxes, the Rule 26(a)(1) machinery does not run at all—useful to know before you spend a week preparing a disclosure statement no one is entitled to.

No excuses, then or later. Rule 26(a)(1)(E) forecloses the three excuses lawyers reach for most. A party is not relieved of its disclosure duty because it "has not fully investigated the case," because "it challenges the sufficiency of another party's disclosures," or because "another party has not made its disclosures." The obligation is measured against information "reasonably available" at the time. The rule expects a good-faith opening disclosure that is then supplemented as the picture sharpens, not a strategic withholding dressed up as diligence.

The self-executing sanction. Rule 37(c)(1) is what gives the deadline its bite. A party that fails to disclose or to 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." Nothing further is required to trigger it—no motion to compel, no prior court order, no warning. The witness you forgot and the damages theory you never computed can simply disappear from the case. Courts across the circuits apply multi-factor tests to the justification-and-harmlessness escape hatch, weighing surprise, the ability to cure it, disruption to trial, the importance of the evidence, and the offering party's explanation. The mechanics of that preclusion analysis, and the circuit-by-circuit variations, are the subject of our dedicated guide to Rule 37(c)(1) and the preclusion of undisclosed evidence.

The Rule 26(g) signature is not a formality. Every disclosure must be signed by at least one attorney of record. Fed. R. Civ. P. 26(g)(1). That signature certifies that, after a reasonable inquiry, the disclosure is "complete and correct as of the time it is made." When the signature is missing, "other parties have no duty to act on it" until it is supplied. Fed. R. Civ. P. 26(g)(2). And where a certification violates the rule "without substantial justification," sanctions are mandatory: the court "must impose an appropriate sanction on the signer, the party on whose behalf the signer was acting, or both." Fed. R. Civ. P. 26(g)(3). Rule 26(g) is the discovery analogue of Rule 11, and it is aimed at both the padded, over-broad disclosure and the thin, evasive one. The point is to make counsel stop and think before signing.

Mechanics. Initial disclosures are served on all parties by a method authorized in Rule 5(b)(2); they are generally not filed on the court's docket. Fed. R. Civ. P. 5(d)(1) (disclosures under Rule 26(a)(1) "must not be filed until they are used in the proceeding or the court orders filing"). Service by email requires the recipient's consent under Rule 5(b)(2)(E). If a disclosure must reveal a trade secret or other sensitive information, make it under a protective order or a confidentiality stipulation; a party need not choose between complying with Rule 26(a)(1) and protecting its crown jewels. See, e.g., Minter v. Wells Fargo Bank, N.A., No. 07-cv-3442, 2010 WL 5418910, at *1 n.1 (D. Md. Dec. 23, 2010) (disclosures made subject to a confidentiality order). Keep the signed original in the file.

Worked example. A wrongful-termination plaintiff serves initial disclosures listing four supporting witnesses and, under damages, a single line: "Lost wages and benefits, plus emotional distress, in an amount to be proven at trial." She never itemizes back pay, never states a benefits figure, and never produces her post-termination pay records. Months later, at the pretrial conference, her counsel wants to put on an economist to model front pay and lost benefits over a decade. The defendant moves to preclude under Rule 37(c)(1), pointing to the absent computation. The plaintiff now bears the burden of showing the omission was substantially justified or harmless—a hard sell after Design Strategy. The theory may survive; the more likely outcome is a scramble, an emergency supplement, and a court that has lost patience. A one-page computation served on time would have made all of this a non-event.

Phase 4: Confer Under Rule 26(f)

• [ ] Calendar the conference for at least 21 days before the scheduling conference or before the Rule 16(b) scheduling order is due.
• [ ] Confirm who must attend and that counsel comes prepared to actually confer, not to trade form paragraphs.
• [ ] Discuss the nature and basis of the claims and defenses and the possibilities for prompt settlement or early resolution.
• [ ] Arrange for initial disclosures and discuss the preservation of discoverable information.
• [ ] Negotiate an ESI protocol: sources, custodians, date ranges, file types, search methodology, de-duplication, and production format.
• [ ] Confer in good faith about the method and timing of complying with Rule 26(b)(5)(A)—privilege-log practice—per the December 1, 2025 amendment to Rule 26(f)(3)(D).
• [ ] Agree to seek an order under Federal Rule of Evidence 502(d).
• [ ] Address the scope of discovery, any phasing, and any proportionality limits the parties will jointly propose.

Why this conference matters more than it looks. The Rule 26(f) conference is the quiet room where cooperative counsel win cases by avoiding fights they were going to lose anyway. Rule 26(f)(1) makes it mandatory and puts the scheduling obligation on the parties, not the court: they "must confer as soon as practicable." Rule 26(f)(2) sets the agenda—consider the nature and basis of the claims and defenses, discuss settlement, arrange for the Rule 26(a)(1) disclosures, discuss preservation, and develop a proposed discovery plan. This is a genuine meet-and-confer, and courts increasingly police the difference between conferring and performing the ritual. Judge Bennett's exasperated opinion in Liguria Foods, Inc. v. Griffith Laboratories, Inc., 320 F.R.D. 168 (N.D. Iowa 2017)—a broadside against boilerplate objections and reflexive, non-cooperative discovery conduct—is required reading for anyone tempted to treat the conference as theater.

The ESI protocol. Electronically stored information is now the center of gravity in most cases, and Rule 26(f)(3)(C) requires the plan to address "any issues about disclosure, discovery, or preservation of electronically stored information, including the form or forms in which it should be produced." Because the Rules do not prescribe the content of an ESI agreement, these documents vary widely, and that flexibility is an opportunity. A well-built protocol addresses cooperation and proportionality as governing principles, designates e-discovery liaisons, fixes preservation obligations, and then gets specific: custodians, date ranges, file types, and data sources; how ESI will be collected, processed, and searched (including search terms or technology-assisted review); the production format and metadata fields; de-duplication and threading; phased or rolling production; and the mechanics of asserting privilege and clawing back inadvertently produced material. Many practitioners draft a standalone ESI protocol and incorporate it into the Rule 26(f) report by reference, keeping the report readable while satisfying the rule. Because the protocol shapes what the responding party must ultimately produce and log, it pairs naturally with our checklist on responding to Rule 34 document requests and the comprehensive guide to objecting and responding to requests for production.

Privilege logging, moved to the front. The December 1, 2025 amendment to Rule 26(f)(3)(D) is the most consequential recent change to front-end practice. The plan must now state the parties' views on "the method and timing" of complying with Rule 26(b)(5)(A)—the rule that requires a party withholding material on privilege or work-product grounds to describe the withheld items in a manner that lets the other side assess the claim. In plain terms, the parties are now expected to negotiate how they will log privileged material—document-by-document or by category—and when logs are due, at the outset rather than after a production dispute erupts. Categorical logging, endorsed by the Advisory Committee and long permitted where document-by-document logging would be unduly burdensome, can be agreed up front: for example, treating "all post-complaint communications between a party and its litigation counsel concerning this action" as a single logged category rather than thousands of line items. Deciding this early, when neither side yet has an advantage to protect, is far cheaper than litigating it later. For the substance of building a log that survives challenge, see our checklist for building a privilege log.

FRE 502(d): the strongest clawback there is. If you take one thing from Phase 4, take this. In any case where large volumes of documents will change hands, ask the court for a Federal Rule of Evidence 502(d) order, and put the request in the Rule 26(f) plan. Rule 502(d) authorizes a federal court to order that disclosure of privileged or protected material "does not operate as a waiver" in the pending litigation, and—critically—"in any other federal or state proceeding." That is a dramatic protection, and it is stronger than the alternatives in two specific ways.

Compare it to Rule 502(b), the default safe harbor. Rule 502(b) prevents waiver by inadvertent disclosure only if the holder "took reasonable steps to prevent disclosure" and "promptly took reasonable steps to rectify the error." Every one of those elements is a fact question a court can decide against you: Was the disclosure really inadvertent? Were your review steps reasonable given the volume? Did you catch it promptly? A 502(d) order sweeps those questions away. It does not require a showing of inadvertence, it does not condition non-waiver on the reasonableness of your privilege review, and by its own terms it travels with the documents into every future federal and state proceeding. As Practical Law's own treatment of clawback instruments puts it, parties seek a 502(d) order precisely to "establish a process and standard that is more protective of the privilege or protection than would otherwise apply under FRE 502(b)." In a matter where several hundred thousand documents move across the wire, a 502(d) order is the difference between a recoverable mistake and a privilege catastrophe. There is essentially no downside to asking for one, and courts grant them routinely. The clawback mechanics that a 502(d) order protects are the same ones your privilege log has to reflect, which is why the log conversation and the 502(d) conversation belong in the same meeting.

Worked example. In a commercial dispute between two software vendors, the parties agree at their Rule 26(f) conference to a 502(d) order and a categorical privilege log, and they incorporate a detailed ESI protocol by reference into their plan. During a rolling production of 400,000 documents, the responding vendor's review platform mis-tags a folder and produces 60 privileged emails between the company and its outside counsel. Under Rule 502(b), the producing party would now have to prove the disclosure was inadvertent and its review reasonable—an anxious motion with real risk. Under the 502(d) order already in place, counsel simply invokes the clawback: a notice, a demand for return or destruction, and the emails come back with no waiver, in this case or any future one. The half-hour spent negotiating the order at the conference bought a full margin of safety for the life of the litigation.

Phase 5: Build and Submit the Written Discovery Plan

• [ ] Draft the Rule 26(f) discovery plan so that it addresses each item enumerated in Rule 26(f)(3)(A)–(F).
• [ ] State the parties' views on the timing, form, and need for Rule 26(a) disclosures, and whether any changes should be made.
• [ ] Propose the subjects, timing, and phasing of discovery, and any changes to the presumptive limits on depositions, interrogatories, and requests to admit.
• [ ] Address ESI, including preservation and form of production, by agreement or by identifying the disputes that need the court's guidance.
• [ ] State the parties' views on the method and timing for complying with Rule 26(b)(5)(A) and on any agreement under FRE 502, per Rule 26(f)(3)(D) as amended.
• [ ] Identify any other orders the court should enter under Rule 16(b) or Rule 26(c).
• [ ] Submit the plan within 14 days after the Rule 26(f) conference, or on any shorter deadline the court sets.

What the plan must cover. Rule 26(f)(3) enumerates the plan's contents: the parties' views on initial disclosures (subsection A); the subjects, timing, and phasing of discovery (B); ESI issues, including form of production (C); privilege and work-product issues, including the newly emphasized method and timing of Rule 26(b)(5)(A) compliance and any FRE 502 agreement (D); changes to the discovery limits and any other limitations (E); and any other orders the court should enter under Rule 16(b) or Rule 26(c) (F). A plan that walks these subsections in order, resolving what the parties agree on and flagging what they do not, is what a busy magistrate judge wants to see.

Coordinate the paper so it does not contradict itself. A recurring, avoidable problem is that the same subject—privilege clawback, ESI format, discovery limits—gets addressed in several documents at once: the 26(f) report, a separate ESI protocol, a confidentiality order, a standalone 502(d) order, and eventually the Rule 16(b) order. If these instruments say slightly different things, the parties have manufactured a future dispute about which controls. The disciplined approach is to pick a home for each topic, address it comprehensively there, and incorporate it by reference elsewhere rather than restating it inconsistently. Where the 26(f) report, the ESI order, or the 16(b) order already covers clawback and non-waiver in adequate detail, a separate FRE 502 agreement may be unnecessary; where they do not, put the comprehensive treatment in one place and cross-reference it. Consistency across the front-end paper is itself a deliverable.

Categorical and phased discovery. The plan is the cheapest place to install two cost controls. The first is categorical privilege logging, discussed above—agreeing that entire families of obviously privileged material may be logged by category. The second is phasing: proposing that discovery proceed in stages, with an initial phase limited to the documents and custodians most likely to resolve the case or to tee up an early dispositive motion, and later phases opened only if needed. Phasing is an application of proportionality, and it is far more palatable to a court when the parties propose it jointly than when one side later moves to compel a phase the other resists.

The plan becomes the scheduling order. The court is required to enter a Rule 16(b) scheduling order after receiving the parties' report or holding a conference, within the earlier of 90 days after any defendant is served or 60 days after any defendant appears. Fed. R. Civ. P. 16(b)(1)–(2). That order must limit the time to join parties, amend pleadings, complete discovery, and file motions. Fed. R. Civ. P. 16(b)(3)(A). It may also address the timing of disclosures, the scope of discovery, ESI preservation and production, clawback and non-waiver procedures, the need for a pre-motion conference before any discovery motion, and—reflecting the 2025 amendments—the method and timing of privilege logging under Rule 16(b)(3)(B)(iv). Because the scheduling order is what the parties actually live under, and because Rule 16(b)(4) lets it be modified "only for good cause and with the judge's consent," the numbers the parties propose in the plan matter. Propose deadlines you can meet; "good cause" is a real burden, and a schedule negotiated in optimism becomes a straitjacket in reality. On how the scheduling order sits within the broader life of a case, see our roadmap to federal civil litigation from complaint to appeal and the phase-by-phase federal litigation resource guide.

Phase 6: Calendar the Later Disclosure Tiers and the Duty to Supplement

• [ ] Calendar expert disclosures under Rule 26(a)(2): the identity of each testifying expert and, for retained experts, a signed written report.
• [ ] Confirm the retained-expert report contains all six required components: the opinions and their bases, the facts and data considered, exhibits, qualifications and a ten-year publication list, prior testimony over four years, and compensation.
• [ ] Note the lighter Rule 26(a)(2)(C) disclosure for non-retained experts—subject matter and a summary of facts and opinions—and do not skip it.
• [ ] Calendar pretrial disclosures under Rule 26(a)(3): trial witnesses, deposition designations, and exhibits, generally at least 30 days before trial, with objections due 14 days later.
• [ ] Build a standing tickler to supplement disclosures and discovery responses under Rule 26(e) whenever a disclosure becomes materially incomplete or incorrect.

The disclosure obligation does not end at the front. Rule 26(a) has three tiers, and the initial disclosures are only the first. Expert disclosures under Rule 26(a)(2) come due on the schedule the court sets, defaulting to 90 days before trial, with rebuttal experts disclosed within 30 days of the disclosure they answer. Fed. R. Civ. P. 26(a)(2)(D). For a retained expert—or one whose duties as an employee regularly involve giving expert testimony—the disclosure must include a written report, signed by the expert, containing a complete statement of all opinions and the basis for each, the facts or data considered, any supporting exhibits, the expert's qualifications and publications from the last ten years, a list of other cases in which the expert testified at trial or deposition in the previous four years, and the compensation paid. Fed. R. Civ. P. 26(a)(2)(B). Witnesses who were not retained to testify—a treating physician, say—require only the shorter Rule 26(a)(2)(C) disclosure of subject matter and a summary of the facts and opinions, but that shorter disclosure is mandatory, and omitting it invites the same Rule 37(c)(1) preclusion that governs the rest of Rule 26. The gatekeeping that follows disclosure, under Rule 702 and the Daubert line, is a separate battle; our guide to Daubert and expert-testimony gatekeeping picks up where the disclosure leaves off.

Pretrial disclosures under Rule 26(a)(3) close the loop: at least 30 days before trial, each party discloses the witnesses it expects to call and those it may call if needed, the witnesses whose testimony will be presented by deposition (with the specific designations), and the exhibits it expects to offer and those it may offer if needed. Objections to the deposition designations and to the exhibits are generally due within 14 days, and an objection not made then—other than under Federal Rules of Evidence 402 and 403—is waived. Fed. R. Civ. P. 26(a)(3)(B).

Supplementation is a standing obligation, not a courtesy. Rule 26(e) requires a party to supplement or correct its disclosures and its discovery responses "in a timely manner if the party learns that in some material respect the disclosure or response is incomplete or incorrect, and if the additional or corrective information has not otherwise been made known to the other parties during the discovery process or in writing." The duty is continuous, and it applies to expert reports and deposition testimony as well. Fed. R. Civ. P. 26(e)(2). The enforcement mechanism is, once again, Rule 37(c)(1): a witness or document you learn of after your initial disclosures but never add can be excluded just as surely as one you forgot at the start. Treat the tickler as part of your case-management system, not an afterthought.

Proportionality: The Thread Through Everything

Every front-end decision—how far to cast the preservation net, which custodians to name in the ESI protocol, how many depositions to propose in the plan—runs into a single organizing principle. Since the 2015 amendments, Rule 26(b)(1) defines the scope of discovery as any nonprivileged matter "relevant to any party's claim or defense and proportional to the needs of the case." The proportionality factors are the importance of the issues at stake, 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. Fed. R. Civ. P. 26(b)(1).

The 2015 amendment did not create proportionality—the factors had lived in Rule 26(b)(2)(C) for years—but it moved them into the definition of scope, deliberately, to make proportionality a front-line constraint rather than a fallback objection. Chief Justice Roberts devoted his 2015 Year-End Report on the Federal Judiciary to the change, framing it as a cultural correction toward cost-conscious, cooperative discovery. The practical consequence for the front end is that proportionality is a lever you pull affirmatively in the discovery plan—by proposing phasing, narrowing custodians, and setting sensible date ranges—rather than a shield you raise defensively after the requests arrive. A party that builds proportionality into its plan is speaking the court's language; a party that first invokes it in a boilerplate objection, of the sort Liguria Foods condemned, has waited too long. The scope defined by Rule 26(b)(1) also sets the outer boundary for the written discovery that follows, from Rule 33 interrogatories to Rule 36 requests for admission, and it deserves attention now, when it is cheap, rather than later, when it is a motion.

Common Failure Modes

A short catalogue of the mistakes that turn a manageable front end into a costly one.

• Treating preservation as the opponent's problem. The duty to preserve runs to your client and your firm first, and counsel must actively monitor compliance, not merely paper it. A hold that ignores chat platforms, personal devices, and departing-employee data queues is a Rule 37(e) exposure waiting to mature. Document the hold and its follow-through.
• A damages "computation" that is just a number. A lump sum with no method and no supporting materials is not a computation. It invites a motion and risks preclusion of the underlying theory under Rule 37(c)(1), as Design Strategy illustrates. Show the categories and the arithmetic.
• Skipping the privilege-log and 502(d) conversation. After the December 1, 2025 amendments, method-and-timing of privilege logging belongs in every Rule 26(f) conference and plan, and a 502(d) order should be a reflex in any document-heavy case. Silence here is a gift to future you's adversary.
• Boilerplate disclosures. A padded, reflexive, or evasive disclosure is a Rule 26(g) certification problem, because the signature certifies a reasonable inquiry and a complete, correct statement. Over-disclosure and under-disclosure are both violations.
• Forgetting the Rule 26(g) signature. An attorney of record must sign, and an unjustified certification violation carries mandatory sanctions. The "stop and think" function is the point, not a technicality.
• Ignoring local rules and standing orders. Many districts impose their own initial-disclosure formats, ESI guidelines, model protective and 502(d) orders, and individual-judge requirements that supplement or override the federal defaults. The Northern District of California's ESI guidelines and New Jersey's joint-proposed-discovery-plan form are two well-known examples. Always read the local and standing rules and the assigned judge's individual practices before you draft anything.
• Proposing a schedule you cannot keep. Rule 16(b)(4) lets the court modify the scheduling order "only for good cause." An optimistic deadline negotiated at the conference becomes a hard wall four months later. Propose dates you can hit.

A Consolidated Front-End Checklist

For the practitioner who wants the whole sequence on one screen:

• [ ] Preserve. Confirm the preservation trigger; identify custodians and non-email data sources; issue a written, acknowledged hold; suspend auto-deletion and device reclamation; monitor compliance; document everything.
• [ ] Map. Chart the elements of every claim, counterclaim, and defense; build the proof matrix; identify the "may use to support" universe; build a preliminary damages model; locate insurance.
• [ ] Disclose. Prepare the four Rule 26(a)(1) buckets; confirm no Rule 26(a)(1)(B) exemption applies; base disclosures on reasonably available information without excuses; compute damages with method; obtain the Rule 26(g) signature; calendar the 14-day deadline; serve, do not file.
• [ ] Confer. Hold the Rule 26(f) conference at least 21 days before the scheduling order is due; negotiate the ESI protocol; agree on privilege-log method and timing; secure agreement to seek a 502(d) order; discuss settlement, phasing, and proportionality.
• [ ] Plan. Draft the written plan covering Rule 26(f)(3)(A)–(F); coordinate the paper so instruments do not conflict; propose categorical logging and phasing; submit within 14 days.
• [ ] Calendar forward. Docket expert disclosures under Rule 26(a)(2), pretrial disclosures under Rule 26(a)(3), and a standing Rule 26(e) supplementation tickler.

Primary and Secondary Authority

Federal Rules of Civil Procedure.

• Rule 26(a)(1) — initial disclosures (witnesses, documents and ESI, damages computation, insurance); 26(a)(1)(B) — exempt proceedings; 26(a)(1)(C) — timing; 26(a)(1)(E) — no-excuses rule.
• Rule 26(a)(2) — expert disclosures and the retained-expert report; 26(a)(3) — pretrial disclosures.
• Rule 26(b)(1) — scope of discovery: relevance and proportionality.
• Rule 26(b)(5)(A) — claims of privilege and the description requirement underlying the privilege log.
• Rule 26(e) — the continuing duty to supplement.
• Rule 26(f) — the conference and discovery plan; 26(f)(3)(D) (as amended Dec. 1, 2025) — views on the method and timing of privilege logging and any FRE 502 agreement.
• Rule 26(g) — certification by the signing attorney; mandatory sanctions for unjustified violations.
• Rule 16(b) — the scheduling order, its timing, and its required and permitted contents; 16(b)(3)(B)(iv) — privilege-log timing and method; 16(b)(4) — modification only for good cause.
• Rule 37(c)(1) — automatic exclusion of undisclosed witnesses and information; 37(e) — the framework for lost ESI, with intent required for the severe sanctions.
• Rule 5(b)(2), (d)(1) — service and the non-filing of disclosures.

Federal Rules of Evidence.

• Rule 502(d) — court-ordered non-waiver of privilege, effective in the pending case and in any other federal or state proceeding; 502(b) — the narrower inadvertent-disclosure default.

Key decisions.

• Zubulake v. UBS Warburg LLC (Zubulake IV), 220 F.R.D. 212 (S.D.N.Y. 2003) (duty to preserve); (Zubulake V), 229 F.R.D. 422 (S.D.N.Y. 2004) (counsel's duty to monitor the hold).
• Cache La Poudre Feeds, LLC v. Land O'Lakes, Inc., 244 F.R.D. 614 (D. Colo. 2007) (counsel's active preservation role).
• Design Strategy, Inc. v. Davis, 469 F.3d 284 (2d Cir. 2006) (preclusion of damages evidence for want of a Rule 26(a)(1) computation).
• Liguria Foods, Inc. v. Griffith Laboratories, Inc., 320 F.R.D. 168 (N.D. Iowa 2017) (condemning boilerplate objections and non-cooperative discovery conduct).
• Minter v. Wells Fargo Bank, N.A., No. 07-cv-3442, 2010 WL 5418910 (D. Md. Dec. 23, 2010) (disclosures under a confidentiality order).

Secondary and interpretive authority. Advisory Committee Notes to Rule 26 (1993, 2000, and 2015 amendments); The Sedona Conference, The Sedona Principles, Third Edition: Best Practices, Recommendations & Principles for Addressing Electronic Document Production (2018); Chief Justice John G. Roberts, Jr., 2015 Year-End Report on the Federal Judiciary (discussing the proportionality amendment); 8A Charles Alan Wright & Arthur R. Miller, Federal Practice and Procedure §§ 2051–2053 (disclosure and discovery planning).

Related UpLaw Resources

Related Guides

• Federal Civil Discovery: Mastering the Tools, Rules, and Pitfalls
• Rule 37(c)(1) and the Preclusion of Undisclosed Evidence: A Practical Guide
• Federal Civil Litigation Filings: A Comprehensive Guide from Complaint to Appeal
• Requests for Production: A Comprehensive Guide to Objecting and Responding
• What an IP Case Is Worth: A Guide to Intellectual Property Damages

Related Checklists

• Building a Privilege Log: A Practical Checklist
• Responding to Rule 34 Document Requests: A Practical Checklist
• Answering Rule 33 Interrogatories: A Practical Checklist
• Answering Rule 36 Requests for Admission: A Practical Checklist
• Evaluating a New Civil Case: A Practical Checklist
• When a Breach Hits Your Crown Jewels: A Trade Secret Incident-Response Checklist
• Preparing to Take a Deposition: 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

Related Articles

• Assessing a Civil Lawsuit: A Comprehensive Early-Case Framework
• Navigating Federal Civil Litigation as a Small Business: A Stage-by-Stage Guide
• Interrogatories in Civil Litigation: A Comprehensive Guide to Objecting and Responding
• Taking Depositions in Federal Civil Litigation: A Comprehensive Guide
• Daubert and the Consumer Survey: A Practical Guide to Excluding Expert Testimony

This checklist is general legal information, not legal advice. The Federal Rules of Civil Procedure and local rules vary and change; verify current rules, deadlines, and your court's standing orders before relying on any step.