Scope, form of production, an enumerated metadata field list, search methodology and its validation, de-duplication treatment, privilege logging and a Rule 502(d) order, and explicit handling of chat and mobile data. Anything left out becomes a motion later, at many times the cost of agreeing it now.
The provisions that earn their space
Scope. Custodians, date range, and systems — including which sources both sides agree are not reasonably accessible, so that question is closed rather than left to surface later.
Form of production. Native, near-native or image, specified per format. This is where the most expensive disputes originate, because producing a spreadsheet as a static image destroys the formulas and producing an email as a PDF discards the routing headers.
An enumerated metadata field list. Not "standard metadata" — an actual list. Different platforms and vendors mean different things by that phrase, and the disagreement surfaces only once a production is loaded and something essential is missing.
Search methodology. Terms, predictive coding, or both. If terms: whether hit counts are exchanged before the list is finalised, which is what stops a list nobody has costed being agreed. If TAR: the validation protocol and the stopping rule.
De-duplication and threading. Global or per-custodian. This materially changes what a custodian appears to have possessed, so if any issue turns on who saw what, custodial de-duplication or a preserved custodian field is required.
Privilege. Log format, categorical logging where appropriate, and a clawback provision entered as a Rule 502(d) order rather than a bare agreement between the parties. The order form binds third parties and other proceedings; the agreement does not. It costs nothing extra to ask for.
Modern data types. Chat and collaboration platforms, ephemeral messaging, mobile data, and how threads are unitised for production. A protocol drafted from a 2012 template is silent on the sources where most current disputes live.
An amendment mechanism. Facts develop and volumes turn out differently than estimated. A protocol that cannot change without a motion becomes an obstacle instead of a framework.
The failure that recurs
A protocol copied from another matter, signed by counsel on both sides, with nobody technical having read it. Provisions get agreed that cannot be executed in the parties' actual systems, and the impossibility is discovered at production — by which point one side has usually already spent the money.
Having the people who will run the collection review the draft costs an hour and prevents most of this.
Where a neutral is worth it
Where the parties are sophisticated and hostile, or the data environment is genuinely complex, a technical special master at the protocol stage resolves disputes in days rather than through months of motion practice. Courts increasingly appoint one before the disputes arrive rather than after — which is also the cheaper point, because prevention costs less per dispute than adjudication.
From our work
Need this looked at properly?
Our examiners and testifying experts work these questions for a living. Tell us what you're facing.
Reviewed by Law & Forensics. See our editorial standards.