Skip to content

ESI Protocols and the Rule 26(f) Meet-and-Confer: A Texas Business Guide for 2026

By Donovan Brown
November 19, 2026
8 sections
ESI Protocols and the Rule 26(f) Meet-and-Confer: A Texas Business Guide for 2026 — Industry article cover card from LayerLogix, with a office building icon

Your ESI protocol decides what discovery costs. A legal and IT guide for Texas SMBs and law firm clients preparing for the Rule 26(f) meet-and-confer, including new privilege log rules.

01

Introduction

Most discovery fights are not won or lost in front of a judge. They are decided months earlier, at the Rule 26(f) meet-and-confer, when the lawyers agree on an ESI protocol: what electronic data gets preserved, searched, and produced, and in what form. For a Texas SMB, the ESI protocol is where your IT reality either gets represented accurately or gets traded away. If your attorney walks into that conference without knowing where your data lives, you can end up promising productions your systems cannot deliver, at a price nobody budgeted for.

02

What an ESI Protocol Is (and Why IT Belongs in the Room)

An ESI protocol is a written agreement, often entered as a court order, that sets the ground rules for electronically stored information in a case. In federal court, Rule 26(f) requires the parties to discuss preservation and discovery of ESI and to submit a discovery plan. Texas state courts follow a parallel approach under Texas Rule of Civil Procedure 196.4, which requires the requesting party to specifically ask for electronic data and the form it wants, and limits the responding party to data reasonably available in the ordinary course of business unless the court orders otherwise.

Both systems reward the party that understands its own data. Your attorney negotiates the protocol, but the facts behind it come from IT: which mailboxes exist, how long Teams chats are kept, whether former employees' OneDrive accounts still exist, and how fast data can be exported. That is why we recommend your IT lead or managed IT provider prepare your counsel before the conference, not after.

03

The Privilege Log Change Every Texas Business Should Know

Amendments to the Federal Rules of Civil Procedure that took effect December 1, 2025 added a new item to the Rule 26(f) agenda: the parties must now discuss the timing and method for complying with privilege log obligations under Rule 26(b)(5)(A), and Rule 16(b) scheduling orders may address it. In practice, privilege logs are now negotiated up front. Options include traditional document-by-document logs, categorical logs, metadata-generated logs, or excluding entire categories such as communications with outside litigation counsel after the suit was filed.

For an SMB this matters because privilege logging is one of the most expensive parts of review. A metadata-based log is far cheaper to generate, but only if your email and document systems capture reliable sender, recipient, date, and subject fields. Knowing that before the conference lets your attorney push for the cheaper method with confidence. It also connects to how you handle privilege during a crisis, which we cover in our guide to attorney-client privilege in incident response.

04

Before the Meet-and-Confer: Your Data Map Checklist

Give your attorney a one-page data map that answers these questions:

  • Systems in scope: Microsoft 365 email, OneDrive, SharePoint, Teams, line-of-business apps, file servers, and any SaaS tools where custodians work.
  • Custodians: Who the key people are, including departed employees, and whether their accounts and devices were preserved.
  • Retention settings: What deletes automatically and when. Our data retention guide for Texas businesses walks through how to document this.
  • Mobile and chat: Whether texts, WhatsApp, or Signal are used for business. See our post on mobile text message eDiscovery.
  • Collaboration data: How Teams and Slack messages, threads, and linked files export. Our Teams and Slack eDiscovery guide explains the gotchas.
  • Legal holds in place: When the hold was issued and which accounts it covers, per our Microsoft 365 litigation hold guide.
05

Key Terms to Negotiate in the Protocol

  1. Form of production. Native files, TIFF images with load files, or searchable PDF. Native is usually cheapest for spreadsheets and chats; agree on it explicitly.
  2. Metadata fields. Specify which fields are produced (custodian, dates, author, file path). Do not agree to fields your systems do not store.
  3. Search methodology. Search terms, date ranges, and whether technology-assisted review or AI-assisted review is permitted, with hit reports shared before review begins.
  4. Short message format. How chats and texts are grouped, for example 24-hour conversation blocks instead of one message per document.
  5. Deduplication and threading. Global deduplication and email threading can cut review volume significantly.
  6. Privilege log method. Agree on categorical or metadata logs where possible, plus a clawback order under Federal Rule of Evidence 502(d).
  7. Proportionality limits. Data that is not reasonably accessible, such as legacy backups, should be called out so restoring it requires agreement or a cost-shifting discussion.

Each of these terms directly drives cost. Our article on eDiscovery cost control shows how volume and review choices add up.

06

Common Mistakes Texas SMBs Make

  • Agreeing to forensic imaging of every device when targeted collection would do. Our comparison of self-collection vs forensic collection helps you scope it.
  • Overpromising on departed employees. If a mailbox was deleted under a routine offboarding process, say so early. Hiding it invites a spoliation sanctions fight.
  • Ignoring AI-generated content. Copilot summaries and AI drafts are increasingly requested. See our post on AI-generated evidence.
  • Skipping security terms. Productions contain sensitive data. The protocol should require encrypted transfer and defined handling of personal information.
07

Where to Start

This week, build your data map: list every system where business communications and documents live, note retention settings, and identify who can export from each. Store it with your litigation readiness documents so it is ready the next time a demand letter or subpoena arrives. If you need help, our eDiscovery services prepare Texas businesses and law firms for meet-and-confer conferences, and our Microsoft 365 managed services make sure retention, hold, and export tools are configured correctly. For a broader view of how your IT stacks up, see our Texas SMB IT and cybersecurity benchmark report. This article is general information, not legal advice; consult your attorney about your specific matter.

Back to Blog
Keep Reading

Related Articles

Need Expert IT Support?

Let our team help your Houston business with enterprise-grade IT services and cybersecurity solutions.

Call NowBook a Call