Electronic Discovery

ESI Protocol and Meet-and-Confer Support

Technical discovery issues are easiest to solve before an ESI protocol is signed. Custodians, systems, metadata, native files, search terms, production format, and preservation limits should be negotiated with the actual data in mind.

The Protocol Becomes the Operating Manual

An ESI protocol can quietly decide how the case will be litigated. It may control metadata fields, load files, native-file treatment, search methodology, production format, redactions, privilege handling, time zones, deduplication, family relationships, and how exceptions are handled. If those choices are made without technical understanding, counsel may inherit problems that are expensive or impossible to fix later.

PowellPath helps attorneys identify the technical terms that need attention before the meet-and-confer. The goal is to make the protocol practical, proportional, and specific enough to avoid later fights.

The Meet-and-Confer Should Ask Technical Questions

Discovery conferences often stay at a high level: custodians, date ranges, and search terms. Those topics matter, but they are not enough. Counsel should also ask where the data lives, what systems are in scope, what exports are available, how metadata will be preserved, whether chats and cloud files require special handling, how deleted items are treated, and what logs may exist.

A good technical issue list lets counsel negotiate from knowledge rather than guessing. It also helps identify where a declaration, affidavit, or expert explanation may be needed if the parties disagree.

Protocol Topics That Deserve Care

  • Custodians, repositories, devices, cloud platforms, chat systems, databases, and third-party sources.
  • Preservation scope, litigation holds, retention settings, deleted items, and audit logs.
  • Search terms, date filters, deduplication method, de-NISTing, and exception handling.
  • Metadata fields, native-file treatment, OCR, text extraction, load files, and Bates numbering.
  • Privilege review, clawback process, redactions, confidentiality labels, and family relationships.
  • Proportionality limits, inaccessible sources, phased discovery, and cost allocation issues.

Proportionality Needs Technical Facts

A party claiming burden should be able to explain the systems, volumes, access limits, export difficulty, and costs that create the burden. A party seeking broader discovery should be able to explain why the source is likely to contain relevant evidence. Technical facts make proportionality arguments more credible.

PowellPath helps counsel frame those facts. That can include source maps, collection estimates, platform limitations, format comparisons, or technical language for discovery letters and motions.

What Counsel Receives

Deliverables may include an ESI protocol issue list, meet-and-confer outline, metadata-field recommendations, production-format language, technical questions for opposing counsel, source-mapping notes, or support for discovery letters and motions.