Build FRCP 26(f) ESI Protocol
Skill: Convert a case data inventory into an FRCP Rule 26(f) ESI protocol
Region: United States Category: Legal / eDiscovery Does: Takes the case's data-source inventory and the parties' agreed parameters and assembles a structured FRCP Rule 26(f) ESI protocol — the discovery-of-electronically-stored-information agreement covering preservation, sources/custodians, search methodology, production format, privilege handling, and dispute resolution. Authority: FRCP 26(f) / 26(b)(2)(B) / 34(b)(2)(E) · The Sedona Conference WG1 Principles & Commentary · (often entered as a stipulated order)
The ESI protocol is negotiated at the Rule 26(f) "meet-and-confer" and frequently entered as a court order. It is the contract that governs how every later step (collection, review, production) is done — getting production format and privilege/clawback terms right here prevents the most common downstream disputes. This drafts a protocol from structured inputs; the negotiated terms are the parties' and counsel's to set.
When this applies
- Preparing for or memorializing the Rule 26(f) conference; standing up the discovery plan in federal litigation (and many state analogues).
- Feeds directly off the custodian ESI source map and informs the review coding protocol and production specs.
Input data required
| Group | Fields |
|---|---|
| Case | caption, court, claims, relevant date range |
| Sources | data sources & custodians (from the ESI source map); not-reasonably-accessible sources |
| Preservation | scope, hold status, auto-deletion suspensions, exclusions agreed |
| Search | search terms / TAR approach, validation method, iteration process |
| Format | production form (native vs image), load-file spec, metadata fields, de-duplication, family handling |
| Privilege | clawback (FRE 502(d)), privilege-log format (doc-by-doc / metadata / categorical) |
| Process | phasing, rolling-production cadence, cost allocation, dispute-resolution mechanism |
Protocol sections
1. Scope & definitions (ESI, custodian, document family, metadata)
2. Preservation — scope, sources on hold, auto-deletion suspension, agreed exclusions
3. Identification of sources & custodians — in-scope list; not-reasonably-accessible sources (26(b)(2)(B))
4. Collection — methods; forensic vs targeted
5. Search methodology — search terms and/or TAR; validation/sampling; iteration & disclosure
6. De-duplication & threading — global vs custodial dedup; email-thread suppression rules
7. Form of production — native categories; image+text+load file; load-file format (DAT/OPT/EDRM);
METADATA FIELD LIST; redaction handling; color/confidentiality endorsement; Bates conventions
8. Privilege — FRE 502(d) clawback (non-waiver); privilege-log format and timing; redaction of privileged content
9. Phasing & timing — rolling-production cadence; substantial-completion date
10. Cost allocation & proportionality (FRCP 26(b)(1))
11. Dispute resolution — meet-and-confer escalation; court intervention process
Drafting rules
- The metadata field list and production form are the heart of the protocol — enumerate the exact load-file fields, which file types produce natively (spreadsheets, databases), text/OCR delivery, and redaction format. Vague format terms cause re-production fights.
- Search methodology must be disclosed and validated — if using search terms, specify the terms (or the process to agree them) and a sampling/validation method; if TAR, state the workflow and validation (ties to the TAR validation report) per evolving Sedona/case-law expectations.
- Lock in FRE 502(d) clawback so inadvertent production doesn't waive privilege; specify the privilege-log format (doc-by-doc vs metadata vs categorical) and timing to match the privilege-log skill.
- Identify not-reasonably-accessible sources (legacy, backup) up front under 26(b)(2)(B) to frame cost/burden and proportionality.
- Make it proportional (FRCP 26(b)(1)) — scope sources, terms, and phasing to the matter's stakes.
- Write it to be entered as a stipulated order where the court allows.
Worked example (key terms excerpt)
Sources: M365 (mail, OneDrive, SharePoint, Teams) for 6 custodians; legacy SAP archive = NOT
reasonably accessible (preserved, production only on showing of need / cost-shift).
Search: Agreed term list (Exhibit A) with validation by 10% null-set sampling; TAR permitted for
the email population with recall-based validation disclosed to opposing counsel.
Format: TIFF + extracted text + Concordance DAT/OPT; spreadsheets & DBs produced NATIVELY with
slip-sheets; metadata fields per Exhibit B (Custodian, From/To/CC, DateSent, Subject,
FileName, MD5Hash, BegBates/EndBates/BegAttach/EndAttach, Confidentiality).
Privilege: FRE 502(d) order; metadata-style privilege log served within 30 days of each volume.
Phasing: Rolling productions every 30 days; substantial completion by 2026-09-15.
Validation checklist
- All sections present (scope, preservation, sources, collection, search, dedup, format, privilege, phasing, cost, disputes)
- Metadata field list and form of production (native vs image, load-file spec) enumerated precisely
- Search methodology (terms and/or TAR) specified with a validation/sampling method and disclosure
- FRE 502(d) clawback included; privilege-log format and timing specified
- Not-reasonably-accessible sources identified under 26(b)(2)(B); proportionality (26(b)(1)) addressed
- De-duplication and email-threading rules stated; family handling defined
- Phasing/rolling cadence and a dispute-resolution mechanism set
- Consistent with the ESI source map; drafted to be enterable as a stipulated order
Last updated: 2026-05-31 — ESI-protocol terms are negotiated by counsel; confirm format, search-validation, and privilege/clawback provisions against current FRCP 26(f)/26(b)/34(b), FRE 502(d), the court's local rules, and current Sedona Conference guidance before relying on the protocol.