E-Discovery Protocol Agreement
Drafts a litigation-ready ESI Protocol Agreement covering search methodology, production formats, privilege procedures, and clawback protections for U.S. commercial litigation.
Prerequisites
Collect before drafting:
- Court caption — court name, case number, party names, assigned judge
- Case materials — meet-and-confer correspondence, prior ESI orders, discovery requests
- Custodian list — names and roles of key custodians per party
- ESI sources — email platforms, DMS, collaboration tools, mobile, cloud storage
- Search terms — agreed Boolean/proximity terms or TAR parameters
- Date ranges — preservation trigger date and production date range
- Production specs — native vs. TIFF, agreed metadata fields (if pre-negotiated)
Quick Start
- Gather prerequisites from uploaded case materials
- Draft sections in order below, resolving all bracketed gaps
- Format as joint stipulation with neutral, cooperative tone
- Append proposed court order with FRE 502(d) incorporation
Agreement Sections
1. Caption & Recitals
- Full court caption mirroring prior filings; all counsel of record
- Rule 26(f) conference date; good-faith cooperation statement
- Rule 26(b)(1) proportionality commitment
2. Preservation
| Element |
Content |
| Trigger date |
Date preservation obligations arose |
| Key custodians |
Name, title, party affiliation |
| ESI sources in scope |
Email, DMS, shared drives, mobile, cloud, collaboration tools |
| Excluded sources |
Basis for exclusion under FRCP 26(b)(2)(B) |
| Litigation hold |
Confirmation holds issued; IT contact per party |
3. Search Methodology
Option A — Keyword Search:
- Terms in Exhibit A with Boolean/proximity operators
- Specify custodian-specific vs. across-the-board application
- Iterative refinement; meet-and-confer on hit count reports
Option B — TAR/Predictive Coding:
- Platform and vendor identification
- Seed set composition and training protocol
- QC metrics: elusion rate, recall/precision targets
- Validation via statistical sampling; disclosure to opposing counsel
4. Production Format
| Document Type |
Format |
Notes |
| Standard documents |
TIFF (Group IV) + extracted text + load file |
Unitized per document |
| Native-required |
Native + TIFF slip-sheet placeholder |
Spreadsheets, audio, video, CAD |
| Email |
TIFF or native (per agreement) |
Threading preserved |
| Databases |
Field-level export per meet-and-confer |
TBD by data type |
Required metadata fields: BegBates, EndBates, BegAttach, EndAttach, Custodian, FilePath, FileName, FileExt, FileSize, DateCreated, DateModified, DateSent, DateReceived, Author, To, CC, BCC, Subject, MD5Hash, Confidentiality
5. Deduplication
- Specify global (cross-custodian) or custodian-level
- Hash method: MD5 or SHA-1
- Reflect all custodians in metadata for de-duped documents
6. Privilege Log
Required fields: Bates range, date, author/sender, recipients (To/CC/BCC), document type, privilege basis, subject (non-revealing description).
- Set deadline: [X] days after each rolling production or fixed date
- Categorical logs permitted where specified (e.g., post-hold attorney-client communications)
- Include sampling/extrapolation provisions if volume warrants
7. FRE 502(d) Clawback
Agreement constitutes a court order under FRE 502(d) upon approval — inadvertent production waives neither privilege nor work-product protection in this or any other proceeding.
Clawback procedure:
- Producing party notifies in writing within [X] days of discovering inadvertent production
- Receiving party ceases review, sequesters, and returns/destroys within [X] days
- No copies retained; receiving party may challenge by motion (burden on producing party)
8. Additional Provisions
Include as applicable:
- Cost allocation — inaccessible/legacy sources under Rule 26(b)(2)(B)
- PII/confidentiality — handling protocol for sensitive personal data
- Forensic imaging — chain of custody if device forensics required
- IT/custodian depositions — 30(b)(6) topics re: ESI systems
- Dispute resolution — meet-and-confer → magistrate referral → motion practice
9. Proposed Court Order
- Signature blocks for all counsel of record
- Judge signature line incorporating FRE 502(d) protections
- Case number and order title formatted for docketing
Pitfalls & Checks
- No brackets in final output — resolve all gaps from case materials or flag for attorney input
- State court — cross-check against applicable state e-discovery rules; not all states track FRCP
- Sedona Principles — reference current edition as interpretive backdrop where appropriate; verify edition number
- Technical specs — must be implementable by IT vendors without further clarification
- Tone — maintain neutral, cooperative language; this is a joint stipulation, not adversarial pleading
- Include rolling production schedule and volume estimates if available from meet-and-confer materials
1---2name: e-discovery-protocol-agreement3description: Drafts court-ready ESI Protocol Agreements governing electronically stored information exchange in U.S. federal litigation. Covers FRCP 26(f)/34 compliance, FRE 502(d) clawback, TAR methodology, privilege logs, and production format specs. Use when drafting e-discovery stipulations, ESI protocols, meet-and-confer agreements, or joint discovery plans.4---5
6# E-Discovery Protocol Agreement
7
8Drafts a litigation-ready ESI Protocol Agreement covering search methodology, production formats, privilege procedures, and clawback protections for U.S. commercial litigation.
9
10## Prerequisites
11
12Collect before drafting:
13
14- **Court caption** — court name, case number, party names, assigned judge
15- **Case materials** — meet-and-confer correspondence, prior ESI orders, discovery requests
16- **Custodian list** — names and roles of key custodians per party
17- **ESI sources** — email platforms, DMS, collaboration tools, mobile, cloud storage
18- **Search terms** — agreed Boolean/proximity terms or TAR parameters
19- **Date ranges** — preservation trigger date and production date range
20- **Production specs** — native vs. TIFF, agreed metadata fields (if pre-negotiated)
21
22## Quick Start
23
241. Gather prerequisites from uploaded case materials
252. Draft sections in order below, resolving all bracketed gaps
263. Format as joint stipulation with neutral, cooperative tone
274. Append proposed court order with FRE 502(d) incorporation
28
29## Agreement Sections
30
31### 1. Caption & Recitals
32
33- Full court caption mirroring prior filings; all counsel of record
34- Rule 26(f) conference date; good-faith cooperation statement
35- Rule 26(b)(1) proportionality commitment
36
37### 2. Preservation
38
39| Element | Content |
40|---|---|
41| Trigger date | Date preservation obligations arose |
42| Key custodians | Name, title, party affiliation |
43| ESI sources in scope | Email, DMS, shared drives, mobile, cloud, collaboration tools |
44| Excluded sources | Basis for exclusion under FRCP 26(b)(2)(B) |
45| Litigation hold | Confirmation holds issued; IT contact per party |
46
47### 3. Search Methodology
48
49**Option A — Keyword Search:**
50- Terms in **Exhibit A** with Boolean/proximity operators
51- Specify custodian-specific vs. across-the-board application
52- Iterative refinement; meet-and-confer on hit count reports
53
54**Option B — TAR/Predictive Coding:**
55- Platform and vendor identification
56- Seed set composition and training protocol
57- QC metrics: elusion rate, recall/precision targets
58- Validation via statistical sampling; disclosure to opposing counsel
59
60### 4. Production Format
61
62| Document Type | Format | Notes |
63|---|---|---|
64| Standard documents | TIFF (Group IV) + extracted text + load file | Unitized per document |
65| Native-required | Native + TIFF slip-sheet placeholder | Spreadsheets, audio, video, CAD |
66| Email | TIFF or native (per agreement) | Threading preserved |
67| Databases | Field-level export per meet-and-confer | TBD by data type |
68
69**Required metadata fields:** `BegBates`, `EndBates`, `BegAttach`, `EndAttach`, `Custodian`, `FilePath`, `FileName`, `FileExt`, `FileSize`, `DateCreated`, `DateModified`, `DateSent`, `DateReceived`, `Author`, `To`, `CC`, `BCC`, `Subject`, `MD5Hash`, `Confidentiality`
70
71### 5. Deduplication
72
73- Specify global (cross-custodian) or custodian-level
74- Hash method: MD5 or SHA-1
75- Reflect all custodians in metadata for de-duped documents
76
77### 6. Privilege Log
78
79Required fields: Bates range, date, author/sender, recipients (To/CC/BCC), document type, privilege basis, subject (non-revealing description).
80
81- Set deadline: [X] days after each rolling production or fixed date
82- Categorical logs permitted where specified (e.g., post-hold attorney-client communications)
83- Include sampling/extrapolation provisions if volume warrants
84
85### 7. FRE 502(d) Clawback
86
87Agreement constitutes a **court order under FRE 502(d)** upon approval — inadvertent production waives neither privilege nor work-product protection in this or any other proceeding.
88
89Clawback procedure:
901. Producing party notifies in writing within [X] days of discovering inadvertent production
912. Receiving party ceases review, sequesters, and returns/destroys within [X] days
923. No copies retained; receiving party may challenge by motion (burden on producing party)
93
94### 8. Additional Provisions
95
96Include as applicable:
97
98- **Cost allocation** — inaccessible/legacy sources under Rule 26(b)(2)(B)
99- **PII/confidentiality** — handling protocol for sensitive personal data
100- **Forensic imaging** — chain of custody if device forensics required
101- **IT/custodian depositions** — 30(b)(6) topics re: ESI systems
102- **Dispute resolution** — meet-and-confer → magistrate referral → motion practice
103
104### 9. Proposed Court Order
105
106- Signature blocks for all counsel of record
107- Judge signature line incorporating FRE 502(d) protections
108- Case number and order title formatted for docketing
109
110## Pitfalls & Checks
111
112- **No brackets in final output** — resolve all gaps from case materials or flag for attorney input
113- **State court** — cross-check against applicable state e-discovery rules; not all states track FRCP
114- **Sedona Principles** — reference current edition as interpretive backdrop where appropriate; verify edition number
115- **Technical specs** — must be implementable by IT vendors without further clarification
116- **Tone** — maintain neutral, cooperative language; this is a joint stipulation, not adversarial pleading
117- Include rolling production schedule and volume estimates if available from meet-and-confer materials
CaseMark