Article

2026-11-17

Last updated

ESI protocols and proportionality: what to settle at meet-and-confer

ESI protocols and proportionality: what to settle at meet-and-confer

Rule 26(f) is when both sides settle preservation, custodians, production formats and privilege logs, including defaults used in two federal districts.

Rule 26(f) is when both sides settle preservation, custodians, production formats and privilege logs, including defaults used in two federal districts.

Rule 26(f) is when both sides settle preservation, custodians, production formats and privilege logs, including defaults used in two federal districts.

An ESI protocol should settle what information to preserve, which sources to examine, how production will arrive and how privilege will be handled. Those decisions belong in the Rule 26(f) discussion. Once the protocol is set, the team still has to understand what actually came in. At Turbo Law, we help connect matter facts to their source pages.

What should an ESI protocol settle at the Rule 26(f) conference?

The protocol should turn the parties' discovery proposals into specific terms for preservation and production, with unresolved points identified. Start with the records.

In a hypothetical construction dispute, consider the superintendent's daily report. The discussion might address who kept it and the period it covers, then move to the form in which the other party will receive it. Calling everything project documents leaves those questions unanswered. The same exercise applies to electronically stored information held by either side.

The Federal Rules of Civil Procedure apply in federal court, local rules and standing orders often add more, and state practice differs. This is a general planning guide, not advice on a particular protocol.

Under Rule 26(f)(3)(C), the written discovery plan must state the parties' views and proposals concerning ESI disclosure, discovery or preservation, including the form or forms of production. We would organize the Rule 26(f) conference discussion around these decisions:

  • Preservation: Identify the information in scope and the reasonable steps proposed to preserve it. Put disagreements about exclusions in writing.

  • Sources and custodians: Connect proposed custodians to the issues they know about. Address non-custodial sources separately, rather than assuming a list of people covers the file.

  • Production: Specify the form of production, including any native-file exceptions. Address searchable text and metadata expressly.

  • Privilege: Discuss the nature and scope of the privilege log, including whether alternatives to document-by-document entries fit the matter.

A format needs more than a label. If the proposed term is searchable PDF, the discussion should still identify what accompanying text and metadata are contemplated and which files require different treatment. Rule 34(b)(2)(E) supplies the federal production framework; Delaware's more specific image-production default is a local example, discussed below.

There is also a route into the scheduling order. Rule 16 permits provisions concerning ESI disclosure, discovery or preservation and agreements under Evidence Rule 502. For the privilege discussion, see Privilege logs under the amended federal rules: what Rules 26(f) and 16(b) now ask.

What should an ESI protocol settle at the Rule 26(f) conference?

The protocol should turn the parties' discovery proposals into specific terms for preservation and production, with unresolved points identified. Start with the records.

In a hypothetical construction dispute, consider the superintendent's daily report. The discussion might address who kept it and the period it covers, then move to the form in which the other party will receive it. Calling everything project documents leaves those questions unanswered. The same exercise applies to electronically stored information held by either side.

The Federal Rules of Civil Procedure apply in federal court, local rules and standing orders often add more, and state practice differs. This is a general planning guide, not advice on a particular protocol.

Under Rule 26(f)(3)(C), the written discovery plan must state the parties' views and proposals concerning ESI disclosure, discovery or preservation, including the form or forms of production. We would organize the Rule 26(f) conference discussion around these decisions:

  • Preservation: Identify the information in scope and the reasonable steps proposed to preserve it. Put disagreements about exclusions in writing.

  • Sources and custodians: Connect proposed custodians to the issues they know about. Address non-custodial sources separately, rather than assuming a list of people covers the file.

  • Production: Specify the form of production, including any native-file exceptions. Address searchable text and metadata expressly.

  • Privilege: Discuss the nature and scope of the privilege log, including whether alternatives to document-by-document entries fit the matter.

A format needs more than a label. If the proposed term is searchable PDF, the discussion should still identify what accompanying text and metadata are contemplated and which files require different treatment. Rule 34(b)(2)(E) supplies the federal production framework; Delaware's more specific image-production default is a local example, discussed below.

There is also a route into the scheduling order. Rule 16 permits provisions concerning ESI disclosure, discovery or preservation and agreements under Evidence Rule 502. For the privilege discussion, see Privilege logs under the amended federal rules: what Rules 26(f) and 16(b) now ask.

What does proportionality actually require in an ESI plan?

Proportionality requires tying the proposed discovery to the needs of the case under Rule 26(b)(1). A smaller production is not, by itself, proof of a proportionate plan. Nor does a larger request explain its own scope.

Take that hypothetical superintendent's report. A requesting party could explain which disputed event the report may address and why the proposed period matters; the producing party could explain where the reports are kept and what difficulty the proposed scope creates. Now there is something concrete to discuss. A bare assertion of burden gives the conference much less to work with.

We would make the reasoning visible beside each proposed boundary: why this custodian, why this subject matter, why this period. If the parties disagree, record the competing explanations. Do the same for preservation scope, rather than leaving an exclusion hidden in a general promise to cooperate.

Accessibility deserves its own discussion. Rule 26(b)(2)(B) addresses ESI from sources not reasonably accessible because of undue burden or cost. Identify the source and the asserted difficulty specifically. Do not let a discussion about a difficult source stand in for the entire ESI proportionality analysis.

Both parties need that discipline. A plaintiff seeking an organization's records may also be producing relevant communications; a defendant producing those records may be requesting information from the plaintiff. The proposed limits should make sense when either party is receiving the production.

For volume-related context, see Antitrust litigation and the document volume problem. In the protocol itself, put the proposed limit next to the reason for it.

What defaults do some federal districts use if the parties do not agree?

Delaware supplies fallback discovery terms, while Northern California combines required preparation and reporting with voluntary planning tools. These are local examples. They are not interchangeable national defaults.

District of Delaware: local fallback terms. The court's Default Standard for Discovery, including ESI applies when the parties do not agree on other terms, subject to further court order. It calls for cooperative, reasonable and proportional efforts, including limits on custodians and subject matter, along with time periods and other discovery parameters.

Its initial disclosures are concrete. Within 30 days after the Rule 16 conference, each party identifies the 10 custodians most likely to have discoverable information, giving their names and titles, their roles in the dispute and the subject matter of their knowledge. Each also lists non-custodial sources most likely to contain non-duplicative discoverable information.

Search terms have a separate default. If the producing party elects to use them, it must disclose them; absent a showing of good cause, the requesting party may request no more than 10 additional terms. The standard expects focused terms.

For production, the standard specifies searchable image files, with extracted text or OCR and specified metadata. It provides for native format for files not easily converted to images, including spreadsheet and database files. Parties must also confer about privilege-log scope and alternatives to document-by-document logs.

The preservation provisions need careful reading. Delaware recognizes a common law obligation to take reasonable and proportional preservation steps. Its appendix identifies categories generally exempt from preservation absent good cause, including certain forensic-only data and substantially duplicative backups. It also addresses certain mobile-device data. That is not a blanket exemption for mobile information. For the separate messaging discussion, see Litigation holds for text messages and chat apps: what courts expect.

Northern District of California: local requirements and voluntary tools. The court's ESI guidance page identifies court-approved Guidelines, a Checklist and a Model Stipulated Order for consultation at the beginning of a case. The Guidelines and Checklist were updated effective December 1, 2015.

All counsel are expected to review the Guidelines. Under the Standing Order described on that page, the Joint Case Management Statement must certify that review and confirm a Rule 26(f) conference about reasonable and proportionate preservation steps for evidence relevant to reasonably evident issues. The Checklist and Model Stipulated Order are highly recommended, but voluntary.

What should plaintiff and defense each bring to the meet-and-confer?

Each should bring a source-specific proposal and enough information about its own records to discuss the other party's requests. Prepare from both positions.

For a hypothetical employment dispute, picture the HR file from 2023 alongside the employee's relevant messages. Counsel seeking the HR file should be ready to explain the proposed scope; counsel seeking the messages should do the same, while each producing party addresses the information it holds. Neither side's place in the caption supplies the answer.

Our suggested preparation for the meet and confer is a short working document:

  • A proposed custodian list, with each person's role and relevant knowledge.

  • A separate source list, identifying any asserted accessibility problems.

  • Proposed preservation boundaries, with reasons for disputed inclusions or exclusions.

  • Production-format and privilege-log proposals, marking the terms that remain open.

Bring litigation support and eDiscovery colleagues into the preparation wherever their knowledge is needed to explain those proposals. Use the conference to settle what can be settled and describe the remaining disagreement precisely. If a production dispute later reaches a motion to compel, Rule 37(a) requires certification of good-faith conferral or attempted conferral.

After production, the files still have to be read. Our Review and Assistant help teams read productions and other case records in the matter file, link facts to source pages and prepare work product. Turbo Law is not an eDiscovery collection or hosting platform.

For the hypothetical employment matter, the next task might be checking a factual statement against the HR file and the messages together. The protocol settles the production terms; the team still needs the source page behind each point in its account of the case.

FAQ

Is a written ESI protocol required in every federal case?

No universal requirement calls for a separate document bearing that title. Rule 26(f) provides for a conference and written discovery plan, subject to its exceptions and court directions. Under Rule 26(f)(3)(C), that plan addresses the parties' ESI proposals, including production forms. A separately titled protocol and the required discovery plan are distinct questions.

How many custodians do I have to include?

There is no nationwide number supplied by these rules. Delaware's default calls for identifying the 10 custodians most likely to have discoverable information in initial disclosures within 30 days after the Rule 16 conference. That is a local initial-disclosure provision, not a national custodian cap. The proposed scope needs a case-specific explanation.

Do I have to produce files in native format?

Not in every instance. Under Rule 34(b)(2)(E), absent a stipulation or order, if a request does not specify a form, ESI must be produced as ordinarily maintained or in a reasonably usable form. The rule does not require producing the same ESI in multiple forms. Native file production should be addressed expressly; Delaware's default provides for natives when files are not easily converted to images.

What happens if ESI that should have been preserved is lost?

Loss alone does not settle the question. Rule 37(e) addresses information that should have been preserved in anticipation or conduct of litigation, was lost because reasonable preservation steps were not taken, and cannot be restored or replaced through additional discovery.

Under the rule's text, prejudice may support measures no greater than necessary to cure it. The specified adverse presumptions or jury instructions, dismissal or default require a finding of intent to deprive another party of the information's use in litigation. Every gap in a production is not automatically spoliation.

Related reading

Sources

  1. Federal Rule of Civil Procedure 26, Cornell Legal Information Institute

  2. Federal Rule of Civil Procedure 16, Cornell Legal Information Institute

  3. Federal Rule of Civil Procedure 34, Cornell Legal Information Institute

  4. Federal Rule of Civil Procedure 37, Cornell Legal Information Institute

  5. District of Delaware, Default Standard for Discovery, including ESI (PDF)

  6. Northern District of California, E-Discovery (ESI) Guidelines and Model Stipulated Orders

FAQ

Is a written ESI protocol required in every federal case?

No universal requirement calls for a separate document bearing that title. Rule 26(f) provides for a conference and written discovery plan, subject to its exceptions and court directions. Under Rule 26(f)(3)(C), that plan addresses the parties' ESI proposals, including production forms. A separately titled protocol and the required discovery plan are distinct questions.

How many custodians do I have to include?

There is no nationwide number supplied by these rules. Delaware's default calls for identifying the 10 custodians most likely to have discoverable information in initial disclosures within 30 days after the Rule 16 conference. That is a local initial-disclosure provision, not a national custodian cap. The proposed scope needs a case-specific explanation.

Do I have to produce files in native format?

Not in every instance. Under Rule 34(b)(2)(E), absent a stipulation or order, if a request does not specify a form, ESI must be produced as ordinarily maintained or in a reasonably usable form. The rule does not require producing the same ESI in multiple forms. Native file production should be addressed expressly; Delaware's default provides for natives when files are not easily converted to images.

What happens if ESI that should have been preserved is lost?

Loss alone does not settle the question. Rule 37(e) addresses information that should have been preserved in anticipation or conduct of litigation, was lost because reasonable preservation steps were not taken, and cannot be restored or replaced through additional discovery.

Under the rule's text, prejudice may support measures no greater than necessary to cure it. The specified adverse presumptions or jury instructions, dismissal or default require a finding of intent to deprive another party of the information's use in litigation. Every gap in a production is not automatically spoliation.

Related reading

Sources

  1. Federal Rule of Civil Procedure 26, Cornell Legal Information Institute

  2. Federal Rule of Civil Procedure 16, Cornell Legal Information Institute

  3. Federal Rule of Civil Procedure 34, Cornell Legal Information Institute

  4. Federal Rule of Civil Procedure 37, Cornell Legal Information Institute

  5. District of Delaware, Default Standard for Discovery, including ESI (PDF)

  6. Northern District of California, E-Discovery (ESI) Guidelines and Model Stipulated Orders