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