When should a discovery neutral handle an ESI protocol fight?

When the parties cannot agree on format, scope, custodians, or metadata and production has stalled, a neutral pressure-tests each proposal against how the systems actually work and produces a workable protocol — by agreement or by order — faster than a motion calendar.

When should a discovery neutral handle a spoliation dispute?

When ESI is alleged lost or altered, a forensic neutral examines what actually happened on the systems, separates genuine loss from ordinary system behavior, and frames a proportionate record — often defusing a sanctions fight before it consumes the case.

When should a discovery neutral handle a TAR or search-term dispute?

When one side challenges technology-assisted review or proposed search terms, a neutral sets a defensible validation protocol and mediates the recall and sampling questions, giving both sides a methodology they can live with.

When should a discovery neutral handle a privilege review dispute?

When privilege designations, log adequacy, or review methodology are challenged at scale, a neutral reviews sampled or contested entries, sets a consistent standard, and resolves the calls — relieving the court of an unmanageable in-camera burden.

When should a discovery neutral handle a forensic inspection?

When one party needs access to another's systems or devices, a neutral designs and supervises the inspection protocol — scope, tooling, chain of custody, and what the requesting party may see — protecting privacy and trade secrets.

When should a discovery neutral handle AI or algorithm discovery?

When models, training data, or algorithmic systems are discoverable, a technically fluent neutral crafts a production and inspection protocol that protects legitimate secrecy while giving the requesting party meaningful discovery, consistent with the JAMS AI Dispute Resolution Rules.

Decision framework

When a discovery dispute is worth handing to a neutral.

Knowing when to use a discovery neutral comes down to six fights that account for most of the time and money lost in modern discovery. For each, here is what the fight looks like, why motion practice is slow, what a neutral does instead, and the procedural vehicle that gets you there.

Last updated: June 2026

ESI protocol fights

Format, scope, custodians, date ranges, deduplication, and metadata fields — the parties cannot agree on the rules of production, so production never starts.

The fight: Each side proposes an ESI protocol; the disagreements are technical, the stakes are framed as precedent, and neither side will move first.
Why motion practice is slow: The court schedules briefing on a question that is really an engineering negotiation. Months pass before a judge with a full docket reaches a protocol the parties could have settled in a session.
What a neutral does: Convenes the parties, pressure-tests each proposal against how the systems actually work, and produces a workable protocol — by agreement where possible, by recommendation or order where not.
Vehicle: FRCP 53CCP §§ 638–639Stipulated ESI mediation

Spoliation of evidence

Servers, mobile devices, cloud accounts, collaboration tools, and even biometric timekeeping data are said to be lost, wiped, or altered — and one side wants sanctions.

The fight: An allegation that ESI was not preserved, escalating toward a sanctions or adverse-inference motion that can swing the case.
Why motion practice is slow: Resolving it requires reconstructing what happened on the systems — retention settings, sync behavior, deletion logs — which courts rarely have time or technical footing to do on a paper record.
What a neutral does: Examines the forensic facts, separates genuine loss from ordinary system behavior, and frames a proportionate record for the court — often defusing the sanctions fight before it consumes the case.
Vehicle: FRCP 53Forensic neutral (stipulated)

TAR and search-term protocols

Disputes over predictive coding, training, validation, recall and precision targets, and search-term lists — methodology fights dressed up as discovery motions.

The fight: One side challenges the other's use of technology-assisted review or proposed search terms as inadequate, opaque, or overbroad.
Why motion practice is slow: The dispute turns on statistics and information-retrieval methods that resist resolution by competing declarations and a hearing.
What a neutral does: Sets a defensible validation protocol, mediates the recall and sampling questions, and gives the parties a methodology they can both live with instead of relitigating it at every production.
Vehicle: FRCP 53CCP §§ 638–639Stipulated ESI mediation

Privilege review disputes

Log volume, review methodology, claw-back, and the eternal fight over whether a privilege call was right — multiplied across hundreds of thousands of documents.

The fight: Challenges to privilege designations, the adequacy of a log, or the review process that produced it, frequently with in-camera review demanded.
Why motion practice is slow: Document-by-document review is exactly what a busy court cannot do at scale; the dispute stalls production for everyone.
What a neutral does: Reviews sampled or contested entries, sets a consistent standard, and resolves the calls — relieving the court of an unmanageable in-camera burden.
Vehicle: FRCP 53CCP §§ 638–639

Forensic inspection protocols

One party needs access to the other's systems or devices — and the protocol governing how that access happens is itself the dispute.

The fight: Demands to image devices or inspect systems collide with privacy, trade-secret, and proportionality objections.
Why motion practice is slow: The court is asked to design a technical access protocol it has neither the time nor the tooling to draft and supervise.
What a neutral does: Designs and supervises an inspection protocol — scope, tooling, chain of custody, and what the requesting party may and may not see — and serves as the neutral who actually runs it.
Vehicle: Forensic neutral (stipulated)FRCP 53

AI and algorithm discovery

Models, training data, weights, prompts, and algorithmic systems are now discoverable evidence — and the rules for producing them are still being written.

The fight: Whether and how a party must produce an AI system, its training data, or its outputs — with novel questions of trade secret, reproducibility, and format.
Why motion practice is slow: There is little settled authority, and the technical questions outrun what a hearing can resolve.
What a neutral does: Brings working fluency in how these systems are built to craft a production and inspection protocol that protects legitimate secrecy while giving the requesting party meaningful discovery.
Vehicle: JAMS AI Dispute Resolution RulesFRCP 53

The procedural vehicles

The same fight can be routed three ways. The right one depends on the forum and what the parties will stipulate to.

FRCP 53: In federal court, the court may appoint a Special Master to address pretrial matters — including discovery — that cannot be effectively and timely addressed by the judge. The order defines the master's duties, standard of review, and compensation.
CCP §§ 638–639: In California, a court may appoint a discovery referee by the parties' agreement (§ 638) or, in defined circumstances, on its own motion (§ 639). The referee hears and determines the referred discovery disputes.
Stipulation / arbitration: Outside any appointment, parties can simply stipulate to a forensic neutral or ESI mediator — including within an arbitration — to design protocols or mediate the protocol fight before it hardens into a motion.

This page is an educational overview, not legal advice. The right procedural vehicle for a specific matter should be selected with counsel. See the Model Orders & Stipulations for illustrative template language.

Have a dispute that fits one of these?

To request him for a matter, engage through JAMS — or send a short inquiry to discuss the right vehicle.

Engage through JAMS → Send an inquiry