The Hidden Cost of Inconsistent ESI Protocols

When every matter starts from a different draft, the organization pays to relearn positions it has already developed, defended, and negotiated.

Ask a litigation team how many ESI protocols it has negotiated over the last two years, and it can usually give you a number. Ask how many of those protocols were built on the same structure, the same defaults, and the same fallback positions, and the answer is often much smaller.

Some of that variation is exactly right. Courts differ, judges differ, and claims and data environments differ. But much of it often has nothing to do with the case. It reflects which outside counsel team drafted the protocol, which precedent they started from, and the fact that nobody on the new team could see why the last protocol ended up where it did.

That’s not case-specific judgment. That’s an organization repeatedly paying to relearn what it already knew.

Where the Cost Actually Sits

The visible cost of an ESI protocol is the negotiation: outside counsel hours spent drafting, redlining, and meeting and conferring with opposing counsel. That cost is real, but it is rarely the largest one.

The larger cost is harder to see. Positions get renegotiated even though the organization has already developed and defended them in prior matters. Defaults get missed because the drafting attorney was not staffed on the last three matters. Execution gaps surface after collection has started, when fixing them is no longer cheap.

None of that appears on an invoice labeled “inconsistency.” It shows up as rework, delay, and disputes that better-informed early decisions could have reduced.

What Outside Counsel Variation Actually Looks Like

Every firm brings its own playbook, and no single firm’s approach is wrong. The problem appears at the portfolio level. Consider six matters handled for the same organization:

• Matter A limits custodians and defines an escalation process before additional custodians are added.
• Matter B leaves custodians effectively open-ended.
• Matter C addresses Teams and Slack data expressly.
• Matter D says nothing about collaboration data.
• Matter E defines the metadata fields to be produced.
• Matter F incorporates broad production obligations without asking whether those fields are useful.

Those differences may be justified. A different court, a judge’s standing order, different claims, or a different data environment can each warrant a different position.

The problem is when nobody can tell whether the variation reflects deliberate case-specific judgment or simply whoever drafted the protocol.

That distinction matters because ESI positions are anchored in procedural requirements. Rule 26(f) requires the parties to confer on preservation and to address ESI issues, including form of production, in their discovery plan. Many courts add their own guidance. The Northern District of California, for example, publishes ESI guidelines, a meet-and-confer checklist, and a model stipulated order that counsel are expected to consult. When protocol language shifts from matter to matter with no record of why, the organization cannot say whether it chose a position or inherited one.

Institutional Memory Doesn’t Live Anywhere

The knowledge of what worked often lives with whoever handled the last matter. Examples include:

• which search methodology was accepted, challenged, or required additional validation
• which phasing structure kept volume and cost under control
• which production format caused problems downstream

When that person changes firms, changes roles, or simply isn’t staffed on the next case, the knowledge doesn’t transfer. The next team starts cold.

Nothing is technically lost. The old protocols still exist in a matter file or an email thread. But they are rarely usable, because nobody captured why a position was taken, how the negotiation went, or what the team would do differently next time.

Repeatability Is a Cost Control, Not a Convenience

A repeatable starting point saves drafting time. That starting point includes:

• known defaults
• a defined set of negotiable and non-negotiable positions
• a standard approach to phasing and escalation

More importantly, it lets the team spend its negotiating effort on what is genuinely different about this matter instead of rebuilding what is the same.

Repeatability can improve defensibility when the organization can explain both its standard position and why a particular matter required a departure from it. A default is not defensible simply because it has been used before. Proportionality under Rule 26(b)(1) is assessed in the context of each case, so a standard position has to be tested against the governing rules, the court’s orders, and the facts every time.

Standardization should not mean identical protocols. It should mean a consistent decision framework for identifying what is genuinely matter-specific.

From Matter Precedent to Institutional Intelligence

This is not mainly a drafting problem. It requires a structured way to retain the reasoning behind protocol decisions, not just the final signed document. That could be in-house counsel, legal operations, or a process that does not depend on one person’s memory.

For each significant provision, that record should capture:

1. What provision was proposed
2. What changed in negotiation
3. Why it changed
4. The applicable rule, order, or other source
5. The client constraint that shaped it
6. The negotiation position taken
7. The fallback
8. The outcome
9. What the team would do next time

This is what we mean by procedural intelligence. It traces each decision through a chain of links:

1. A source, such as a federal rule, a local guideline, or a judge’s standing order
2. The requirement that source creates
3. The protocol issue the requirement raises
4. The risk that issue carries
5. The attorney decision or negotiation position taken
6. The downstream impact on scope, cost, and burden

Captured across matters, that chain turns a folder of signed protocols into an informed starting position for the next one.

Without it, consistency depends on institutional luck. It depends on whether the same partner happens to be staffed again, whether someone remembers the last negotiation, and whether anyone thinks to ask. Luck is not a cost control strategy, and it is not a defensibility strategy either.

Questions Litigation Teams Should Be Able to Answer

1. Do we have a standard starting structure for ESI protocols, or does each matter begin from whatever precedent outside counsel brings?
2. Who owns updating that structure as our data environment, the rules, and relevant court guidance change?
3. Is our position history (what we proposed, what we conceded, and why) documented anywhere outside individual matter files?
4. Does new outside counsel see that history before drafting, or draft from its own firm’s defaults?
5. Can we distinguish our organizational default from a case-specific departure, and explain why we departed?
6. Can we point to what has and has not worked across our last several matters?

Inconsistent ESI protocols are not a drafting inefficiency. Their cost is set when the protocol is negotiated, long before anyone opens a document for review. Fixing that does not require eliminating case-specific judgment. It requires making sure case-specific judgment, rather than turnover, timing, or whichever template was closest, is the reason a protocol changes.

ESI Flow is building procedural intelligence for ESI negotiation: helping litigation teams connect procedural sources, protocol language, client constraints, risk, and negotiation history so each new matter starts with institutional knowledge rather than a blank page.

Learn more about ESI Flow or apply to join the Early Access Program.

Sources and Further Reading

1. Federal Rule of Civil Procedure 26(f). Requires the parties to confer, discuss preserving discoverable information, and state their views on ESI issues, including form of production, in a proposed discovery plan. law.cornell.edu/rules/frcp/rule_26
2. Federal Rule of Civil Procedure 26(b)(1). Defines the scope of discovery and the proportionality factors courts weigh in each case. law.cornell.edu/rules/frcp/rule_26
3. Federal Rule of Civil Procedure 16(b)(3)(B)(iii). Permits a scheduling order to provide for disclosure, discovery, or preservation of ESI. law.cornell.edu/rules/frcp/rule_16
4. Federal Rule of Civil Procedure 34(b). Governs how a requesting party may specify, and a responding party may object to, the form of producing ESI. law.cornell.edu/rules/frcp/rule_34
5. U.S. District Court for the Northern District of California, E-Discovery (ESI) Guidelines, Checklist, and Model Stipulated Order. An example of court-specific guidance that counsel are expected to review and that shapes ESI protocol content. cand.uscourts.gov
6. The Sedona Principles, Third Edition (2017). Best-practice principles for preservation and production of ESI, including proportionality and the responding party’s role in selecting appropriate procedures and methods. thesedonaconference.org
7. The Sedona Conference Commentary on Proportionality in Electronic Discovery (2017). Guidance on applying proportionality to specific discovery decisions. thesedonaconference.org